utility patent application transmittal - · pdf fileutility patent application transmittal...

UTILITY PATENT APPLICATION

TRANSMITTAL (Only for new nonprovisional applications under 37 CFR 1.53(b))

Attorney Docket No. HW708564 Client Reference No. 81356140US16

First Inventor WU, Wenfu

Title

METHOD, SYSTEM, AND DEVICE FOR USER DETACHMENT WHEN A HANDOVER OR CHANGE OCCURS IN HETEROGENEOUS NETWORK

APPLICATION ELEMENTS ADDRESS Commissioner for Patents P.O. Box 1450

TO: Alexandria, VA 22313-1450

1.

2.

3.

4. 5.

a ❑

a

El a a. b.

Utility

1.27.

❑ ''.

I.

Applicant

Specification

Drawings Declaration

Patent Application Transmittal Form claims small entity status. See 37 CFR

(including claims and abstract) [Total Pages 48]

[Total Sheets 12] [Total Pages 4]

Newly executed Copy from prior application

[Note Box 6 below] ❑ Deletion of Inventor(s) Signed statement attached

ACCOMPANYING APPLICATION PARTS 10. ❑

11. ❑

12.

13. ❑ 14. ❑

15. rj

16. ❑❑

18.

19. ❑

20. a 21. a 22. a 23. a

24. a

37

a

be

Pre

Applicant publication Assignment (cover

Assignee) Power English Information

applications) Preliminary Return (Should Claim Document(s) Request 122(b)(2)(B)(i)

months) Petition Accelerated

Translation Verification Translation Verification

requests early publication. (include fee under 37 CFR 1.18(d))

Papers sheet and document(s))

CFR 3.73(b) Statement (when there is an

of Attorney Translation Document (if applicable)

Disclosure Statement (IDS) Form PTO-1449 Copies of References (except for U.S. patents and

Amendment17. Receipt Postcard

be specifically itemized) of Priority & Certified Copy of Priority

& Certification Under 35 USC (Form PTO/SB/35 or its equivalent must

submitted with this application to prevent publication at 18

for Special Status Examination Support Document

-Examination Search Document of CN Priority Document w/

of PCT Priority Document w/

6.

7. 8.

9.

a

' ❑

a. b.

c.

Nucleotide

deleting inventor(s) named in the prior application Incorporation by Reference: The entire disclosure of the prior application, from which an oath or declaration is supplied under Box 5b is considered as part of the disclosure of the accompanying application and is hereby incorporated by reference. Application Data Sheet. See 37 CFR 1.76 Large Table or Computer Program (Appendix) in Computer Readable Form (CRF), or on CD-ROM or CD-R in duplicate.

and/or Amino Acid Sequence Submission ❑ Computer Readable Form (CRF) Specification Sequence Listing on: i. ❑ CD-ROM or CD-R (2 copies); or ii. ❑ Paper Copy ❑ Statement verifying identity of above copies

21. If gi

a CONTINUING APPLICATION, check appropriate box and supply the requisite information below: Continuation ❑ Divisional PI Continuation-in-part of prior application no. 12/479,216. Prior application information: Examiner: MATHARU, Manpreet S.; Group Art Unit: 2617

APPLICATION FEES

SMALL ENTITY OTHER THAN A

SMALL ENTITY FILING FEE $82 (EFS) $330

SEARCH FEE $270 $540 EXAM FEE $110 $220

CLAIMS NUMBER FILED NUMBER EXTRA RATE

ADD'L CLAIM FEE RATE

ADD'L CLAIM FEE

Total Claims 14 - 20 = 0 x 26 = x 52 = $0 Independent Claims 2 - 3 = 0 x 110 = x 220 = $0 ❑ First Presentation of Multiple Dependent Claim + 195 = + 390 =

U Application Size Fee - If the application transmittals, data sheet, specification, claims, abstract, drawings, and preliminary amendment exceed 100 sheets of paper, enter number of sheets here: - If application is filed in paper form, enter this number in Total Sheets, below. - If application is filed via EFS-Web, multiply this number by 0.75 and enter result in Total Sheets, below. Total Sheets = - 100 = + 50 =

(round itp to a whole number) x 135 = x 270 =

❑ Assignment Fee + 40 = + 40 = ❑ Early Publication Fee + 300 = + 300 = a Petition for Special Status 37 CFR 1.17(h) $130

[ of 2]

NSN677-1002, Page 1

ellic

Text Box

IPR2017-00657

(TOTAL AMOUNT TO BE CHARGED TOTAL TOTAL $1220

UTILITY PATENT APPLICATION TRANSMITTAL Attorney Docket No. HW708564 Client Reference No. 81356140US16

22. CII Please charge my Deposit Account No. 12-1216 in the amount of $1220.

in the amount of $ is enclosed.

is hereby authorized to credit overpayments or charge any additional fees of the following types No. 12-1216:

required under 37 CFR 1.16. required under 37 CFR 1.17.

is hereby generally authorized under 37 CFR 1.136(a)(3) to treat any future reply in this or application filed pursuant to 37 CFR 1.53 requiring an extension of time as incorporating a request

and the Commissioner is hereby specifically authorized to charge Deposit Account No. 12-1216 for that may be due in connection with such a request for an extension of time.

23. ❑ A check

24. The Commissioner to Deposit Account a. .E4 Fees b. ►l. Fees

25. The Commissioner any related therefor, any fee

26. CORRESPONDENCE ADDRESS IM Customer No.:

77399

❑ , Reg. No. Leydig, Voit & Mayer, Ltd. Two Prudential Plaza, Suite 4900 180 North Stetson Avenue Chicago, Illinois 60601-6731 (312) 616-5600 (telephone) (312) 616-5700 (facsimile)

Name John K. Winn, Reg. No. 58,579

Signature P--- (P. -

Date June 27, 2011

Utility Transmittal (Revised 10/1/2008)

[ of 2]

NSN677-1002, Page 2

Attorney Docket Number

Application Number

HW708564 Application Data Sheet 37 CFR 1.76

METHOD, SYSTEM, AND DEVICE FOR USER DETACHMENT WHEN A HANDOVER OR CHANGE OCCURS IN HETEROGENEOUS NETWORK Title of Invention

The application data sheet is part of the provisional or nonprovisional application for which it is being submitted. The following form contains the bibliographic data arranged in a format specified by the United States Patent and Trademark Office as outlined in 37 CFR 1.76. This document may be completed electronically and submitted to the Office in electronic format using the Electronic Filing System (EFS) or the document may be printed and included in a paper filed application.

PTO/SB/14 (11-08) Approved for use through 09/30/2010. OMB 0651-0032

U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE

Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.

Secrecy Order 37 CFR 5.2 Portions or all of the application associated with this Application Data Sheet may fall under a Secrecy Order pursuant to 37 CFR 5.2 (Paper filers only. Applications that fall under Secrecy Order may not be filed electronically.)

Applicant Information: Applicant 1

Remove

Applicant Authority ®Inventor °Legal Representative under 35 U.S.C. 117 0Party of Interest under 35 U.S.C. 118

Prefix Given Name Middle Name Family Name Suffix

Wenfu WU

Residence Information (Select One) 0 US Residency 0 Non US Residency 0 Active US Military Service

City Shanghai Country Of Residencei CN

Citizenship under 37 CFR 1.41(b) i CN

Mailing Address of Applicant:

Address 1 Huawei Administration Building

Address 2 Bantian, Longgang District

City Shenzhen, Guangdong State/Province

Postal Code 518129 Countryi CN

Applicant 2 Remove

Applicant Authority ®Inventor °Legal Representative under 35 U.S.C. 117 °Party of Interest under 35 U.S.C. 118


Weihua HU

Residence Information (Select One) 0 US Residency C) Non US Residency 0 Active US Military Service


Citizenship under 37 CFR 1.41(b) i CN






Applicant 3 Remove

Applicant Authority ®Inventor °Legal Representative under 35 U.S.C. 117 °Party of Interest under 35 U.S.C. 118


Shanhan WANG

Residence Information (Select One) 0 US Residency ® Non US Residency 0 Active US Military Service


EFS Web 2.2.2

NSN677-1002,


U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.

Application Data Sheet 37 CFR 1.76 Attorney Docket Number HW708564

Application Number

Title of Invention METHOD, SYSTEM, AND DEVICE FOR USER DETACHMENT WHEN A HANDOVER OR CHANGE OCCURS IN HETEROGENEOUS NETWORK

Citizenship under 37 CFR 1.41(b) i






All Inventors Must Be Listed - Additional Inventor Information blocks may be generated within this form by selecting the Add button.

Add

Correspondence Information: Enter either Customer Number or complete the Correspondence Information section below. For further information see 37 CFR 1.33(a).

❑ An Address is being provided for the correspondence Information of this application.

Customer Number 77399

Email Address [email protected] Add Email Remove Email

Application Information:

Title of the Invention METHOD, SYSTEM, AND DEVICE FOR USER DETACHMENT WHEN A HANDOVER OR CHANGE OCCURS IN HETEROGENEOUS NETWORK

Attorney Docket Number HW708564 Small Entity Status Claimed ❑

Application Type Nonprovisional

Subject Matter Utility

Suggested Class (if any) Sub Class (if any)

Suggested Technology Center (if any)

Total Number of Drawing Sheets (if any) 12 Suggested Figure for Publication (if any)

Publication Information: ❑ Request Early Publication (Fee required at time of Request 37 CFR 1.219)

Request Not to Publish. I hereby request that the attached application not be published under 35 U.S.

C. 122(b) and certify that the invention disclosed in the attached application has not and will not be the subject of an application filed in another country, or under a multilateral international agreement, that requires publication at eighteen months after filing.

Representative Information:

Representative information should be provided for all practitioners having a power of attorney in the application. Providing this information in the Application Data Sheet does not constitute a power of attorney in the application (see 37 CFR 1.32). Enter either Customer Number or complete the Representative Name section below. If both sections are completed the Customer Number will be used for the Representative Information during processing.

Please Select One: 0 Customer Number 0 US Patent Practitioner 0 Limited Recognition (37 CFR 11.9)

EFS Web 2.2.2

NSN677-1002,




Application Number


Customer Number 77399

Domestic Benefit/National Stage Information: This section allows for the applicant to either claim benefit under 35 U.S.C. 119(e), 120, 121, or 365(c) or indicate National Stage entry from a PCT application. Providing this information in the application data sheet constitutes the specific reference required by 35 U.S.C. 119(e) or 120, and 37 CFR 1.78(a)(2) or CFR 1.78(a)(4), and need not otherwise be made part of the specification.

Prior Application Status Pending Remove

Application Number Continuity Type Prior Application Number Filing Date (YYYY-MM-DD)

Continuation of 12479216 2009-06-05

Prior Application Status Expired Remove

Application Number Continuity Type Prior Application Number Filing Date (YYYY-MM-DD)

12479216 Continuation of PCTCN2008071842 2008-07-31

Additional Domestic BenefitJNational Stage Data may be generated within this form by selecting the Add button.

Add

Foreign Priority Information: This section allows for the applicant to claim benefit of foreign priority and to identify any prior foreign application for which priority is not claimed. Providing this information in the application data sheet constitutes the claim for priority as required by 35 U.S.C. 119(b) and 37 CFR 1.55(a).

Remove

Application Number Country i Parent Filing Date (YYYY-MM-DD) Priority Claimed

200710137568.8 CN 2007-08-07 0 Yes 0 No

Additional Foreign Priority Data may be generated within this Add button.

form by the selecting Add

Assignee Information: Providing this information in the application data sheet does not substitute for compliance with any requirement of part 3 of Title 37 of the CFR to have an assignment recorded in the Office.

Assignee 1 Remove

If the Assignee is an Organization check here. X

Organization Name Huawei Technologies Co., Ltd.

Mailing Address Information:




Country i CN Postal Code 518129

Phone Number Fax Number

Email Address

Additional Assignee Data may be generated within this form by selecting the Add button.

Add

EFS Web 2.2.2

NSN677-1002,




Application Number


Signature: A signature of the applicant or representative is required in accordance with 37 CFR 1.33 and 10.18. Please see 37 CFR 1.4(d) for the form of the signature.

Signature /John K. Winn/ Date (YYYY-MM-DD) 2011-06-27

First Name John K. Last Name Winn Registration Number 58579

This collection of information is required by 37 CFR 1.76. The information is required to obtain or retain a benefit by the public which is to file (and by the USPTO to process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.14. This collection is estimated to take 23 minutes to complete, including gathering, preparing, and submitting the completed application data sheet form to the USPTO. Time will vary depending upon the individual case. Any comments on the amount of time you require to complete this form and/or suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S. Patent and Trademark Office, U.S. Department of Commerce, P.O. Box 1450, Alexandria, VA 22313-1450. DO NOT SEND FEES OR COMPLETED FORMS TO THIS ADDRESS. SEND TO: Commissioner for Patents, P.O. Box 1450, Alexandria, VA 22313-1450.

EFS Web 2.2.2

NSN677-1002,

Privacy Act Statement

The Privacy Act of 1974 (P.L. 93-579) requires that you be given certain information in connection with your submission of the attached form related to a patent application or patent Accordingly, pursuant to the requirements of the Act, please be advised that: (1) the general authority for the collection of this information is 35 U.S.C. 2(b)(2); (2) furnishing of the information solicited is voluntary; and (3) the principal purpose for which the information is used by the U.S. Patent and Trademark Office is to process and/or examine your submission related to a patent application or patent. If you do not furnish the requested information, the U.S. Patent and Trademark Office may not be able to process and/or examine your submission, which may result in termination of proceedings or abandonment of the application or expiration of the patent.

The information provided by you in this form will be subject to the following routine uses:

1. The information on this form will be treated confidentially to the extent allowed under the Freedom of Information Act (5 U.S.C. 552) and the Privacy Act (5 U.S.C. 552a). Records from this system of records may be disclosed to the Department of Justice to determine whether the Freedom of Information Act requires disclosure of these records.

2. A record from this system of records may be disclosed, as a routine use, in the course of presenting evidence to a court, magistrate, or administrative tribunal, including disclosures to opposing counsel in the course of settlement negotiations.

3. A record in this system of records may be disclosed, as a routine use, to a Member of Congress submitting a request involving an individual, to whom the record pertains, when the individual has requested assistance from the Member with respect to the subject matter of the record.

4. A record in this system of records may be disclosed, as a routine use, to a contractor of the Agency having need for the information in order to perform a contract Recipients of information shall be required to comply with the requirements of the Privacy Act of 1974, as amended, pursuant to 5 U.S.C. 552a(m).

5. A record related to an International Application filed under the Patent Cooperation Treaty in this system of records may be disclosed, as a routine use, to the International Bureau of the World Intellectual Property Organization, pursuant to the Patent Cooperation Treaty.

6. A record in this system of records may be disclosed, as a routine use, to another federal agency for purposes of National Security review (35 U.S.C. 181) and for review pursuant to the Atomic Energy Act (42 U.S.C. 218(c)).

7. A record from this system of records may be disclosed, as a routine use, to the Administrator, General Services, or his/her designee, during an inspection of records conducted by GSA as part of that agency's responsibility to recommend improvements in records management practices and programs, under authority of 44 U.S.C. 2904 and 2906. Such disclosure shall be made in accordance with the GSA regulations governing inspection of records for this purpose, and any other relevant (i.e., GSA or Commerce) directive. Such disclosure shall not be used to make determinations about individuals.

8. A record from this system of records may be disclosed, as a routine use, to the public after either publication of the application pursuant to 35 U.S.C. 122(b) or issuance of a patent pursuant to 35 U.S.C. 151. Further, a record may be disclosed, subject to the limitations of 37 CFR 1.14, as a routine use, to the public if the record was filed in an application which became abandoned or in which the proceedings were terminated and which application is referenced by either a published application, an application open to public inspections or an issued patent.

9. A record from this system of records may be disclosed, as a routine use, to a Federal, State, or local law enforcement agency, if the USPTO becomes aware of a violation or potential violation of law or regulation.

EFS Web 2.2.2

NSN677-1002,

Doc Code: PET.SPRE.ACX PTOISB/28 (07-09)

Doc Description: Petition for 12-month Accelerated Exam Approved for use through 07/31/2012. OMB 0651-0031 U.S. Patent and Trademark Office; U. S. DEPARTMENT OF COMMERCE

Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it displays a valid OMB control number.

PETITION TO MAKE SPECIAL UNDER ACCELERATED EXAMINATION PROGRAM


HW708564 First Named Inventor

WU, Wenfu

Application Number (if Known)

Title of Invention


APPLICANT HEREBY PETITIONS TO MAKE THE ABOVE-IDENTIFIED APPLICATION SPECIAL UNDER THE REVISED ACCELERATED EXAMINATION PROGRAM. See Instruction sheet on page 3. 1. Claims of the application:

a. The application must contain three (3) or fewer independent claims and twenty (20) or fewer total claims. The application may not contain any multiple dependent claims.

b. Applicant hereby agrees not to separately argue the patentability of any dependent claim during any appeal in the application. Specifically, the applicant agrees that the dependent claims will be grouped together with and not argued separately from the independent claim from which they depend in any appeal brief filed in the application (37 CFR 41.37(c)(1)(vii)).

c. The claims must be directed to a single invention.

2. Interviews: Applicant hereby agrees to have (if requested by examiner): a. An interview (including an interview before a first Office action) to discuss the prior art and any potential

rejections or objections with the intention of clarifying and possibly resolving all issues with respect to patentability at that time, and

b. A telephonic interview to make an election without traverse if the Office determines that the claims are not obviously directed to a single invention.

3. Preexamination Search Statement and Accelerated Examination Support Document: With this petition, applicant is providing: a preexamination search statement, in compliance with the requirements set forth in item 8 of the instruction sheet, and an "accelerated examination support document" that includes: a. An information disclosure statement in compliance with 37 CFR 1.98 citing each reference deemed most

closely related to the subject matter of each of the claims;

b. For each reference cited, an identification of all the limitations of the claims that are disclosed by the reference specifying where the limitation is disclosed in the cited reference;

c. A detailed explanation of how each of the claims are patentable over the references cited with the particularity required by 37 CFR 1.111(b) and (c);

d. A concise statement of the utility of the invention as defined in each of the independent claims (unless the application is a design application);

e. An identification of any cited references that may be disqualified as prior art under 35 U.S.C. 103(c) as amended by the CREATE act; and

f. A showing of where each limitation of the claims finds support under the first paragraph of 35 U.S.C. 112 in the written description of the specification. If applicable, the showing must also identify: (1) each means-(or step-) plus-function claim element that invokes consideration under 35 U.S.C. 112, ¶6; and (2) the structure, material, or acts that correspond to any means- (or step-) plus-function claim element that invokes consideration under 35 U.S.C. 112, ¶6. If the application claims the benefit of one or more applications under title 35, United St ates Code, the showing must also include where each limitation of the claims finds support under the first paragraph of 35 U.S.C. 112 in each such application in which such support exists.

The information is required to obtain or retain a benefit by the public which is to file (and by the USPTO to process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.11 and 1.14. This form is estimated to take 12 hours to complete, including gathering, preparing, and submitting the completed application form to the USPTO. Time will vary depending upon the individual case. Any comments on the amount of time you require to complete this form and/or suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S. Patent and Trademark Office, U.S. Department of Commerce, P.O. Box 1450, Alexandria, VA 22313-1450. DO NOT SEND FEES OR COMPLETED FORMS TO THIS ADDRESS. If you need assistance in completing the form, call 1-800-PTO-9199 and select option 2. EFS Web 2.2.20

NSN677-1002,

Doc Code: PET.SPRE.ACX PTO/SB/28 (07-09)



PETITION TO MAKE SPECIAL UNDER ACCELERATED EXAMINATION PROGRAM (Continued)


HW708564 First Named Inventor

WU, Wenfu

Attachments:

a. Accelerated Examination Support Document (see item 3 above).

b A statement, in compliance with the requirements set forth in item 8 of the instruction sheet, detailing the preexamination search which was conducted.

c. Information Disclosure Statement.

d.

Other (e.g., a statement that the claimed subject matter is directed to environmental quality, energy, or countering terrorism (37 CFR 1.102(c)(2)).

Fees: The following fees must be filed electronically via EFS or EFS-Web:

a. The basic filing fee, search fee, examination fee, and application size fee (if required) under 37 CFR 1.16.

b. Petition fee under 37 CFR 1.17(h) - unless the petition is filed with a showing under 37 CFR 1.102(c)(2).

Signature:

Click Remove if you wish to remove this signatory Remove

Signature /John K. Winn/ Date 2011-06-27

Name (Print/Typed)

John K. Winn Registration Number

58579

Click Add if you wish to add additional signatory Add

Note: Signatures of ail the inventors or assignees of record of the entire interest or their representative(s) are required in accordance with 37 CFR 1.33 and 10.18. Please CFR 1.4(d) for the form of the signature. see 37

EFS Web 2.2.20

NSN677-1002,

Doc Code: PET.SPRE.ACX PTO/SB/28 (07-09)



Instruction Sheet Petition to Make Special Under the Accelerated Examination

A grantable petition must meet the following conditions: 1. The petition to make special under the accelerated examination program must be filed with the application and accompanied by the

fee set forth in 37 CFR 1.17(h) or a statement that the claimed subject matter is directed to environmental quality, energy, or countering terrorism.

2. The application must be a non-reissue utility or design application filed under 35 U.S.C. 111(a).

3. The application must be filed electronically using the Office electronic filing system (EFS) or EFS-Web.

4. The application must be complete under 37 CFR 1.51 and in condition for examination on tiling. For example, the application must be filed together with the basic filing fee, search fee, examination fee, and application size fee (if applicable), and an oath or declaration under 37 CFR 1.63.

5. The application must contain three (3) or fewer independent claims and twenty (20) or fewer total claims. The application may not contain any multiple dependent claims. The petition must include a statement that applicant will agree not to separately argue the patentability of any dependent claim during any appeal in the application. Specifically, the applicant is agreeing that the dependent claims will be grouped together with and not argued separately from the independent claim from which they depend in any appeal brief tiled in the application (37 CFR 41.37(c)(1)(vii)).

6. The claims must be directed to a single invention. The petition must include a statement that applicant will agree to have a telephonic interview to make an election without traverse in a telephonic interview if the Office determines that all the claims are not directed to a single invention.

7. The petition must include a statement that applicant will agree to have an interview (including an interview before a first Office action) to discuss the prior art and any potential rejections or objections with the intention of clarifying and possibly resolving all issues with respect to patentability at that time.

8. At the time of filing, applicant must provide a statement that a preexamination search was conducted, including an identification of the field of search by United States class and subclass and the date of the search, where applicable, and, for database searches, the search logic or chemical structure or sequence used as a query, the name of the file or files searched and the database service, and the date of the search. a. This preexamination search must involve U.S. patents and patent application publications, foreign patent documents, and nonpatent

literature, unless the applicant can justify with reasonable certainty that no references more pertinent than those already identified are likely to be found in the eliminated source and includes such a justification with this statement.

b. This preexamination search must be directed to the claimed invention and encompass all of the features of the independent claims, giving the claims the broadest reasonable interpretation.

c. The preexamination search must also encompass the disclosed features that may be claimed, in that an amendment to the claims (including any new claim) that is not encompassed by the preexamination search will be treated as non-responsive and will not be entered.

d. A search report from a foreign patent office will not be accepted unless the search report satisfies the requirements set forth above. e. Any statement in support of a petition to make special must be based on a good faith belief that the preexamination search was

conducted in compliance with these requirement. See 37 CFR 1.56 and 10.18.

9. At the time of filing, applicant must provide in support of the petition an accelerated examination support document that includes: a. An information disclosure statement in compliance with 37 CFR 1.98 citing each reference deemed most closely

related to the subject matter of each of the claims;

b. For each reference cited, an identification of all the limitations of the claims that are disclosed by the reference specifying where the limitation is disclosed in the cited reference;

c. A detailed explanation of how each of the claims are patentable over the references cited with the particularity required by 37 CFR 1.111(b) and (c);

d. A concise statement of the utility of the invention as defined in each of the independent claims (unless the application is a design application);

e. An identification of any cited references that may be disqualified as prior art under 35 U.S.C. 103(c) as am ende d by the CREATE act; and

f. A showing of where each limitation of the claims finds support under the first paragraph of 35 U.S.C. 112 in the written description of the specification. If applicable, the showing must also identify: (1) each means- (or step-) plus-function claim element that invokes consideration under 35 U.S.C. 112, If6; and (2) the structure, material, or acts that correspond to any means- (or step-) plus-function claim element that invokes consideration under 35 U.S.C. 112,16. If the application claims the benefit of one or more applications under title 35, United States Code, the showing must also include where each limitation of the claims finds support under the first paragraph of 35 U.S.C. 112 in each such application in which such support exists. For more information, see notice "Changes to Practice for Petitions in Patent Applications to Make Special and for Accelerated Examination" available on the USPTO web site at http://www.uspto.goviweb/office stpacIdapplogsheethtml

EFS Web 2.2.20

NSN677-1002,


The Privacy Act of 1974 (P.L. 93-579) requires that you be given certain information in connection with your submission of the attached form related to a patent application or patent. Accordingly, pursuant to the requirements of the Act, please be advised that: (1) the general authority for the collection of this information is 35 U.S.C. 2(b)(2); (2) furnishing of the information solicited is voluntary; and (3) the principal purpose for which the information is used by the U.S. Patent and Trademark Office is to process and/or examine your submission related to a patent application or patent. If you do not furnish the requested information, the U.S. Patent and Trademark Office may not be able to process and/or examine your submission, which may result in termination of proceedings or abandonment of the application or expiration of the patent.


1. The information on this form will be treated confidentially to the extent allowed under the Freedom of Information Act (5 U.S.C. 552) and the Privacy Act (5 U.S.C. 552a). Records from this system of records may be disclosed to the Department of Justice to determine whether the Fr eedom of Information Act requires disclosure of these records.



4. A record in this system of records may be disclosed, as a routine use, to a contractor of the Agency having need for the information in order to perform a contract. Recipients of information shall be required to comply with the requirements of the Privacy Act 011974, as amended, pursuant to 5 U.S.C. 552a(m).



7. A record from this system of records may be disclosed, as a routine use, to the Administrator, General Services, or his/her designee, during an inspection of records conducted by GSA as part of that agency's responsibility to recommend improvements in records management practices and programs, under authority of 44 U.S.C. 2904 and 2906. Such disclosure shall be made in accordance with the GSA regulations governing inspection of records for this purpose, and any other relevant (i.e., GSA or Commerce) directive. Such disclosure shall not be used to make determinations about indivi duals.

8. A record from this system of records may be disclosed, as a routine use, to the public after either publication of the application pursuant to 35 U.S.C. 122(b) or issuance of a patent pursuant to 35 U.S.C. 15t Further, a record may be disclosed, subject to the limitations of 37 CFR 1.14, as a routine use, to the public if the record was filed in an application which became abandoned or in which the proceedings were terminated and which application is referenced by either a published application, an application open to public inspections or an issued patent.


EFS Web 2.2.20

NSN677-1002,

Declaration and Power of Attorney for Patent Application

VI,IrporTans

Chinese Language Declaration

r1=15f*FA f#14T;StlifIgit TUElltit*: As a below named inventor, I hereby declare that:

itiltAllE • enitHaMiiiii*AgEtt167 My residence, post office address and citizenship are as stated next to my name.

IME-PM • 111-0401i-4341914 (0154M-A fICAMIUM-VIA#NDOt(ORINRARC. tift±611PAPPNWOMOMT

OFIETO.M-444PAMMTRIlliSMft:

gmoptgoveesa PCT 110114303Ili6

I believe I am the original, first and sole inventor (if only one name is listed below) or an original, first and joint inventor (if plural names are listed below) of the subject matter which is claimed and for which a patent is sought on the invention entitled

METHOD, SYSTEM, AND DEVICE FOR USER

DETACHMENT WHEN A HANDOVER OR CHANGE

• OCCURS IN HETEROGENEOUS NETWORK

the specification of which is attached hereto unless the following box is checked:

El was filed on 31 July2008

as United States Application Number or 13C1'

International Application Number

AXT PCT/CN2008/071842 and was amended on

OE+ (414fil) (if applicable).

110010111UMWEN±MINIMMO•tICUle 010ZAWOMOICCIV*.

I hereby state that I have reviewed and understand the contents of the above identified specification, including the claims, as amended by any amendment referred to above.

101110#8/Mrla.---F-Linfl- • HAIM X*11filehlettitrdel •

I acknowledge the duty to disclose information which is material to patentability as defined in Title 37, Code of Federal Regulations, § 1.56. •

PTO/SB/101 (5-95) Approved for use through 9(30/98. OMB 0651-0032

Patent and Trademark Office: U.S. DEPARTMENT OF COMMERCE Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.

NSN677-1002,

Chinese Language Peclaration

41141$tItAX10111116k.OLMH-FEMS-7-1/"-FilAta )-(b)Xngi 365 05(b)IIIMATTI-Mill4f140111*2 rinlittegilgl 365 tiVagliAlffiflial PCT1491141ittiitg!) V-4,010.3WEPI-Eiff=041-Eillfrat • AVIEVIDIVI lltAXSZIgh • flial41•114444111111IM1►1 1111ratii PCT

1041411** •

Prior Foreign Applications) 014if5t:41 111PN

200710137568.8 China

1 hereby claim foreign priority under.Title 35, United States Cede, 119(a)0) or § 365(b) of any lbreigit apPlierdien(s) ftir patent or

inventor's certificate, or § 365 (a) of any PCT International application, uhith designated at !cast one country other than the United. Sttes, listed below and have alio identified below, by Checking the box, arty foreign application for patent or inventor's certificate. or PCT International application having a filing dun before (hat of the application on which priority is claimed.

Priority Not Claimed *301Zekitll

7 August 2007 (Number) (MN)

(timnbcr) Otis)

(Country) ((E S)

(Country) (N)

(DaylMotutgYear Filed) MIMS /14/if )

(Day/MonthrYeer Filed) ('r18 /)

(Numbe) (Country) ( O) (11%)

Ritilillittigniiitin 35 VI 119(e)3' WA1;CFEC-(61Viii WWI 011411615THI

(OnyakenthtYear Filed) ( ritt#fl f A t sr)

I hereby claim the benefit under Title 35, United States Code. a 119(e) of any United States provisional application(s) listed below.

(Application Nn.) (Filing Date)

(*S*Elltl)

(Application No)

(14441/%10)

(Finns Dare)

(ti Mil )

1243104MISHM it6305:-.±.10841---m-hiaDn1 365 11§(C)/Mf3 i7 KT litifillriffritiatAllfilttritAME FilMilitiffierOJA • tigitithvfMlitiVia.M4110-1112*

RIV9110Mat per 1041 1111114E-FE1101—W::-F4 M—Kftti 4z4VAIIMMirdEPIIIVILUI motorail SIOIMIRM -a`±E.111141— • Mt (13 ) 4131PM411411 ItilltiVO4 • Zt-iMitiM .5ft•T-1A4fIrlitdinAlc eight

• ffitE5i is t PCT 13 •

I hereby claim the benefit under Title 35, United States Code. 120 of any United States application(s), or § 365(c) of any PCT

International application designating the United States, listed below arid, insofar as, the subject Mallet of each or the claims of this appIhMtiOnts not disclosed in the prior United States or PCT InternatiOnal: *illation in the manner provided by the first Paragraph of Tide 35, United States Code, § 112, 1 acknowledge the duty to disclose inforMation which is material to patentability as defined in 1111e 37, Code or Federal Reguiationsi § 1,56 which became available between the filing date Of the prior application and the national or PCT International filing date of this application.

PCT/CN2008/071842 31 July 2008

Pending

(AMicuirobto)

(431iVillnt%)

(Filing Date) (

(Slates) (patented, podia& abandoned) (ffta)(Elliaffle • • WV)

(Application No) . Mina Dace)

(t1MMROU mum) aeftwimumwecnrimwmatutom.mgo riORMMITONTIMICOMM:UMWE,VMMIEMW litAMM-9"-*-41 , SNWSOMOVVION1MMA OVM0•4141**0 MME.MONXIMMtV014t& llt4INIVA4MEINO1 ed].

(Status) (patented, pending, abandoned) (M)(2,1(14#1ii • 41110irll • Triilb

I hereby declare that ali statements made herein of my own knowledge arc true and that all statements made on information and belief are believed to be true; and further that these statements were made with the knowledge that wilifill false statements and the like so made arc punishable by fine or imprisonment, or both, under Section loot of Title 18 of the United States Code and that such willful false statements may jeopardize the validity of the application riflery patent issued thereon.

. rrom rsoi (5-95) . • Apixovid ferric Math 91.10.198. • OM13 06514132

Patent and Tradurre:Office: U.S. DEPARTMENT OF COMMERCE Under the Paperwork Reduction AM of 1988, no persons are required *respond to a collection of Intonation unless tt contains a valid ONS controiniarter

NSN677-1002,

PTO/SR/tat 1545) Approved tbr use through 9/311/int. time 001 4)0.12

Patent and Tradenuirk Orrice: t/.8. t)LIPAR'IMENT lrh Ct>nimetteli Under the Paperwork !leder:km Act of 1095. no parsons are required to respond to a etilluclicsi 01 information unless It contains a valid OMB control number.


J.* vanitirrAL 1-• v dzitEml.

r rli;i111114krit*IS!.14 fthfitiaWW14M111'1111i itr4011111,ftlfi :flig1,.11114VMW

Pt)WFilt OE ATTORNEY: As a named inventor, t hereby appoint the following tatorncy(s) and/or agent(s) to pmsecolc this application and transact :111 hosinems in 11w Patent and Trademark Office connected therewith: (list name and registration number)

171'0 Customer Number 85854

Darby & Darby P.C.

Sold Correspoodeneo to:

Address associated with Customer Number 85854

Direct Telephone Calls tin (now and Orphan', minihri)

Pierre rt. Yanney, 2 I 2-527-7700

ZIA '51140 .11'.1.091'sn it 4'1 Pull name L.11.NIIIC ilt first inventor

Wean WU

e 111 441414 1.1101 inventors signature Date

i)ePt r Oil k_____,TV.v4:Lg., . fillip Reside et

Shenzl)en, China

NU Citizenship China

11i.liniltatl: Post Orrice Address

thntwei AdMinistratiOn Building Bastliatt, Longgung District Shenzhen 518129, Ouungdolw P.R.. China

;IS IN Ali'il01411V.17'r.i(Alifi) -,

iltia mune of second jiii»I inventor. Wilily Weihtut UU

tg *". fligl. IN X Nil'• 11181 Smoint inventor's signature Quito

06114,kis BR_ June ?v _____k4 .1.101: Realtlenee

Shenzben, China KINI Citizenship

China ftliKiitlittl: • Post °Moo Address

Fluawei Administration Building Bant kin, Ltinggang District Shenzhen 5 t A 129, Guangdong P.12. China

(Supply similar informatinn and signature tar third and subsequent ZIS '''.(1/44111:filt

joint inventors.)

NSN677-1002,

SUPPLEMENTAL INVENTOR sHeET (PTO/Se/101)


014?.1111.91 lilt./ .4 • Aer.ot 03: 'Z. 1-N4 Safi Fl Vi: -I:RU.)14k t.ellt./1101,1P.ffil-W (rim' ti ;el t 9111 01; 4(1 ,P1ii:t.1111DX6/14/

POWER OF ATTORNEY: Ash immix' inventor. I hereby appoint Ihr Iidluwing aitorney(s) anti/or agent(s) to prosecute this application and !outset:I all busines.-1 in the Patent and Trademark I Mice connected therewith: (list name and registration nuns her)

110 Cummins. Number 85854

Darby & Durhy P.C'.

.'40.11i10//11: Send Correspondence its:

Address associated with Customer Number 85854

l'Et/itItZ) f.)ireet Telephone Culls to: (tome and telepluirie windier)

Pierre It. Yanncy, 212-527-770U •-•-•-•-

7:4.- 41 JkliO3:14)11r; 1"rl'itt1111'i1 ran name of third joint inventor. irony

Shasishan WANG . _______. .......

3)4 5l la, S:11:•.:ft(1019•1•M`i: n (DI 'third inventor

. s signature Date

aisk , 194t lithi/l/k liltlik

.

Ikesidenee

Shenzhen, China isztl7i Citizen4sip

China !irsks)/IMI:

.

Post Office Address

Hun wei Administration Building Bastian, Lunggang District Shenziten 518129, Guangdong P.R. Chinn

111'11111:#4141•Rlo I lit- ti Mit() Nil intiOr IN r limo!' joint inventor. if:my

iilla111/1fRigi'N'A'r • t 1 JO fourth iiwkaiiiir'N signature Dale

Illthl• Residence

PM Citizenship

griiIkhl: Posi Office Address

(LI 71: fIlt:11;1..!Itti/191.isigti!IRtslaiNtl•fitt4-t: (Supply similar information and signature for fiilh anti subsequent joint inventors.)

NSN677-1002,

VERIFICATION OF TRANSLATION

I, Zhouping hereby solemnly affirm that I have a fluent knowledge of English and

Chinese languages and that the attached document is the true and accurate translation of

the CN application number 200710137568.8

Dated this 17 day of June,2011

Signature of Translate lila pill

NSN677-1002,

DF078307331

Abstract

A method for user detachment when a handover/change occurs in a heterogeneous network is

provided. The method includes: handing over or switching a user equipment (UE) from a source

network to a target network; and determining, by the source network, whether to detach the UE

5 from the source network, and if yes, detaching the UE from the source network; otherwise, not

detaching the UE from the source network. A system and a device for user detachment when a

handover/change occurs in a heterogeneous network, and another method for user detachment when

a handover/change occurs in a heterogeneous network are also provided. The detachment solutions

achieve the detachment of the UE from the source network by a network side and the detachment of

10 the UE from the source network when the UE is handed over or switched from the source network

to the target network.

1

NSN677-1002,

DF078307331

Representative Drawing

UE MME Non-3 GPP GW

Serving GW

PDN GW

HSS/AAA Server

602

601. Access a 3GPP network

The UE triggers handover or switching.

603. Access request

604. Access authentication process

605a. Proxy binding update

605b. Binding update

606a. Proxy binding Ack

606b. Binding Ack

607. Access accept

608a. Delete bearer request

608b. Delete bearer request

608b. Binding revocation

Ind

609a. Delete bearer response

509b. Delete bearer response


Ack

610. Detach request

610. Detach accept 611. Purge UE

611. Purge UE Ack if

2

NSN677-1002,

DF078307331

Claims 1. A method for user detachment when a handover/change occurs in a heterogeneous network,

comprising:

handing over or switching a user equipment (UE) from a source network to a target network;

5 and

determining, by the source network, whether to detach the UE from the source network, and if

yes, detaching the UE from the source network; otherwise, not detaching the UE from the source

network.

2. The method according to claim 1, wherein the source network is a 3rd-generation partnership

10 project (3GPP) network and the target network is a non-3GPP network; or the source network is a

non-3GPP network and the target network is a 3GPP network.

3. The method according to claim 1, wherein the determining step comprises:

if it is known that the UE is handed over or switched from the source network to the target

network, determining, by the source network, to detach the UE from the source network; or

15 if it is known that the UE is handed over or switched from the source network to the target

network, determining according to terminal capability of the UE: if the terminal capability of the

UE is single radio capability, determining, by the source network, to detach the UE from the source

network; or


20 network, determining according to access policy information of an operator: if the access policy

information of the operator is single radio access, determining, by the source network, to detach the

UE from the source network; or


network, determining according to the terminal capability of the UE and the access policy

25 information of the operator: if the terminal capability of the UE is dual radio capability and the

access policy information of the operator is the single radio access; or if the terminal capability of

the UE is the single radio capability and the access policy information of the operator is dual radio

access; or if the terminal capability of the UE is the single radio capability and the access policy

information of the operator is the dual radio access, determining, by the source network, to detach

30 the UE from the source network.

4. The method according to claim 1, wherein the determining to detach the UE from the source

network comprises:

determining, by a packet data network gateway (PDN GW) of the source network, whether to

delete a default bearer, and if yes, sending a delete bearer request message of the default bearer to a

3

NSN677-1002,

DF078307331

serving gateway (serving GW) of the source network, sending, by the serving GW of the source

network, the received delete bearer request message to a mobility management network element

(MME), and deleting, by the MME, a mobility management context (MM context) and bearer

resources; or

5 sending, by the PDN GW of the source network, a binding revocation indication (Ind) message

to the serving GW of the source network; and determining, by the serving GW of the source

network, whether to delete a default bearer of the UE, and if yes, sending a delete bearer request

message of the default bearer to the MME, and deleting, by the MME, the MM context and the

bearer resources.

10 5. The method according to claim 3, wherein before the determining step, the method

comprises:

sending, by a PDN GW of the source network, a delete bearer request message to an MME

through a serving GW of the source network, wherein the delete bearer request message comprises

a cause value indicating a reason for the UE to be handed over or switched from the source network

15 to the target network; or sending, by the PDN GW of the source network, a release bearer request

message to the MME, wherein the release bearer request message indicates that the UE is handed

over or switched from the source network to the target network; or when the UE is handed over or

switched from the source network to the target network, sending, by a PDN GW of the source

network, a normal delete bearer request message to the MME.

20 6. The method according to claim 3, wherein after the determining step, the method comprises:

sending, by a PDN GW of the source network, a detach request message to an MME through a

serving GW of the source network; or sending, by the PDN GW of the source network, the detach

request message to the MME; or sending, by the PDN GW of the source network, a binding

revocation Ind message to the serving GW of the source network, and sending, by the serving GW

25 of the source network, the detach request message to the MME; and

receiving, by the MME of the source network, the detach request message and deleting an MM

context related to the UE; and initiating, by the MME of the source network, a delete bearer process

and deleting bearer resources of the UE in the source network.

7. The method according to claim 3, wherein after the determining step, the method comprises:

30 sending, by a PDN GW of the source network, a detach request message to a GW of the source

network; and

receiving, by the GW of the source network, the detach request message and deleting an MM

context related to the UE.


4

NSN677-1002,

DF078307331

sending, by a network element on the target network, a register request message carrying a

current access network type of the UE to a home subscriber server (HSS); and sending, by the HSS,

a cancel location message to an MME when the HSS determines that an access network type that

the UE registers last time is inconsistent with an access network type that the UE registers this time;

5 and

deleting, by the MME, an MM context related to the UE.


sending, by a network element on the target network, a register request message carrying a

current access network type of the UE to an HSS; and sending, by the HSS, a cancel location

10

message to a non-3GPP GW when the HSS determines that an access network type that the UE

registers last time is inconsistent with an access network type that the UE registers this time; and

deleting, by the non-3GPP GW, an MM context related to the UE.

10. The method according to claim 3, wherein after the determining step, the method

comprises:

15

sending, by the target network, a handover/change complete (HO complete) message to an

MME of the source network; and deleting, by the MME of the source network, an MM context

related to the UE, initiating a delete bearer process, and deleting bearer resources of the UE in the

source network.

11. The method according to claim 3, wherein after the determining step, the method

20 comprises:

sending, by the target network, an HO complete message to a non-3GPP GW of the source

network; and deleting, by the non-3GPP GW of the source network, an MM context related to the

UE.

12. The method according to claim 4, wherein the determining to delete the default bearer

25 comprises:

determining to delete the default bearer of the UE according to a handover/change of the UE in

an access network: determining whether the UE is handed over or switched from the source

network to the target network, and if yes, deleting the default bearer of the UE; or

determining to delete the default bearer of the UE according to the handover/change of the UE

30 in the access network and the terminal capability of the UE: determining whether the UE is handed

over or switched from the source network to the target network and whether the terminal capability

of the UE is the single radio capability, and if yes, deleting the default bearer of the UE; or

determining to delete the default bearer of the UE according to the handover or switching of the

UE in the access network and the access policy infoltnation of the operator: determining whether

5

NSN677-1002,

DF078307331

the UE is handed over or switched from the source network to the target network and whether the

access policy information of the operator is the single radio access, and if yes, deleting the default

bearer of the UE; or

determining to delete the default bearer of the UE according to the handover or switching of the

5 UE in the access network, the terminal capability of the UE, and the access policy information of

the operator: if the UE is handed over or switched from the source network to the target network,

the terminal capability of the UE is the dual radio capability, and the access policy information of

the operator is the single radio access; or if the UE is handed over or switched from the source

network to the target network, the access policy information of the operator is the dual radio access,

10 and the terminal capability of the UE is the single radio capability; or if the UE is handed over or

switched from the source network to the target network, the terminal capability of the UE is the

single radio capability, and the access policy information of the operator is the single radio access,

deleting the default bearer of the UE.

13. The method according to claim 3 or 12, wherein the obtaining the terminal capability of the

15 UE comprises:

carrying the terminal capability of the UE in an attach request message, a tracking area update

(TAU) request message, a routing area update (RAU) request message, or an access request

message when the UE sends the attach request message, the TAU request message, the RAU request

message, or the access request message to the network element of the source network, wherein the

20 network element of the source network is the MME or the non-3GPP GW.

14. The method according to claim 3 or 12, wherein the obtaining the terminal capability of the

UE further comprises:

sending, by the MME of the source network, a create bearer request message carrying the

terminal capability of the UE to the serving GW of the source network; and sending, by the serving

25 GW of the source network, the create bearer request message the PDN GW of the source network;

or

sending, by the MME of the source network, an update location request message carrying the

terminal capability of the UE to the HSS of the source network.

15. The method according to claim 3 or 12, wherein the obtaining the access policy information

30 of the operator comprises:

notifying, by the MME of the source network, the configured access policy information of the

operator to the source network; or

notifying, by the non-3GPP GW of the source network, the configured access policy

information of the operator to the source network.

6

NSN677-1002,

DF078307331

16. The method according to claim 3 or 12, wherein the obtaining the access policy information

of the operator comprises:

notifying, by the HSS, the configured access policy information of the operator to the MME of

the source network and notifying, by the MME of the source network, the configured access policy

5 information of the operator to the source network; or

notifying, by the HSS, the configured access policy information of the operator to the

non-3GPP GW of the source network and notifying, by the non-3GPP GW of the source network,

the configured access policy information of the operator to the source network; or

notifying, by a policy and charging rule function (PCRF) entity, the configured access policy

10 information of the operator to the source network.

17. The method according to claim 3 or 12, wherein the UE notifies the terminal capability of

the UE or the access policy information of the operator to the source network when a location area

of the UE changes and the terminal capability of the UE changes.

18. The method according to claim 7, wherein the detach request message carries a cause value

15 indicating that the detach request is caused by the handover or switching of the UE from the source

network to the target network.

19. A method for user detachment when a handover/change occurs in a heterogeneous network,

comprising:

triggering, by a user equipment (UE), handover or switching from a source network to a target

20 network; and

determining, by the UE, whether to detach the UE from the source network, and if yes,

detaching the UE from the source network; otherwise, not detaching the UE from the source

network.

20. The method according to claim 19, wherein after the triggering, by the UE, handover or

25 switching from the source network to the target network, the method comprises:

handing over or switching the UE from the source network to the target network.

21. The method according to claim 19, wherein after the UE is detached from the source

network, the method comprises:

sending, by the UE, a detach request message to a mobility management network element

30 (MME); and

receiving, by the MME, the detach request message, deleting a mobility management context

(MM context) of the UE in the MME, initiating a delete bearer process, and deleting bearer

resources of the UE related to a 3rd-generation partnership project (3GPP) network.

22. The method according to claim 19, wherein after the UE is detached from the source

7

NSN677-1002,

DF078307331


sending, by the UE, a detach request message to a non-3GPP GW; and

receiving, by the non-3GPP GW, the detach request message and deleting an MM context of

the UE related to the non-3GPP GW.

5 23. The method according to claim 19, wherein after the UE is detached from the source


setting, by the MME of the source network, a state of the UE to an invalid state.

24. The method according to claim 19 or 20, wherein the determining, by the UE, whether to

detach the UE from the source network comprises:

10 deleting bearer resources and an MM context related to the source network when the UE knows

that the UE is handed over or switched from the source network to the target network; or

determining whether to detach the UE from the source network according to terminal capability

of the UE when the UE knows that the UE is handed over or switched from the source network to

the target network: if the terminal capability of the UE is single radio capability, deleting bearer

15 resources and an MM context related to the source network; or

determining whether to detach the UE from the source network according to access policy

information of an operator when the UE knows that the UE is handed over or switched from the

source network to the target network: if the access policy information of the operator is single radio

access, deleting the bearer resources and the MM context related to the source network; or

20 determining whether to detach the UE from the source network according to the terminal

capability of the UE and the access policy information of the operator when the UE knows that the

UE is handed over or switched from the source network to the target network: if the terminal

capability of the UE is dual radio capability and the access policy information of the operator is the

single radio access; or if the terminal capability of the UE is the single radio capability and the

25 access policy information of the operator is dual radio access; or if the terminal capability of the UE

is the single radio capability and the access policy information of the operator is the dual radio

access, deleting, by the UE, the bearer resources and the MM context related to the source network.

25. The method according to claim 21, wherein before the UE sends the detach request message,

the method comprises: determining to send the detach request message,

30 the determining to send the detach request message comprises:

detemaining to send the detach request message according to a handover or switching of the UE

in an access network: determining whether the UE is handed over or switched from the source

network to the target network, and if yes, determining to send the detach request message to the

MME; or

8

NSN677-1002,

DF078307331

determining to send the detach request message according to the handover or switching of the

UE in an access network and terminal capability of the UE: if the UE is handed over or switched

from the source network to the target network and the telminal capability of the UE is single radio

capability, sending the detach request message to the MME; or

5 determining according to the handover or switching of the UE in the access network and access

policy information of the operator: if the UE is handed over or switched from the source network to

the target network and the access policy information of the operator is single radio access, sending

the detach request message to the MME; or

determining to delete the MM context of the UE according to the handover or switching of the

10 UE in the access network, the terminal capability of the UE, and the access policy information of

the operator: if the UE is handed over or switched from the source network to the target network,

the terminal capability of the UE is dual radio capability, and the access policy information of the

operator is the single radio access; or if the UE is handed over or switched from the source network

to the target network, the access policy information of the operator is dual radio access, and the

15 terminal capability of the UE is the single radio capability; or if the UE is handed over or switched

from the source network to the target network, the terminal capability of the UE is the single radio

capability, and the access policy information of the operator is the single radio access, sending the

detach request message to the MME.

26. The method according to claim 21 or 22, wherein the detach request message carries a

20 cause value indicating that the detach request is caused by the handover or switching of the UE

from the source network to the target network.

27. The method according to claim 23, wherein the setting the state of the UE to the invalid

state comprises:

deleting, by the MME of the source network, subscription data information of the UE and an

25 MM context of the UE; or

setting, by the MME of the source network, a state of the MME used by the UE to the invalid

state; or

setting, by the MME of the source network, an address of the MME used by the UE to an

invalid value; or

30 setting, by the MME of the source network, a change flag location of the MME used by the UE

to a changed state.

28. A system for user detachment when a handover/change occurs in a heterogeneous network,

comprising a user equipment (UE) and a network side, wherein

the UE is configured to be handed over or switched from a source network on the network side

9

NSN677-1002,

DF078307331

to a target network on the network side; and

the network side is configured to handover or switch the UE from the source network to the

target network and to detach the UE from the source network.

29. The system according to claim 28, wherein the UE comprises a first handover/change

5 module and a first detachment module, and the network side comprises a second handover/change

module and a second detachment module;

the first handover/change module is configured to enable the UE to be handed over or switched

from the source network to the target network;

the first detachment module is configured to detach the UE from the source network;

10 the second handover/change module is configured to enable the network side to hand over or

switch the UE from the source network to the target network; and

the second detachment module is configured to enable the network side to detach the UE from

the source network.

30. A device for user detachment when a handover/change occurs in a heterogeneous network,

15 comprising a second handover/change module and a second detachment module disposed on a

network side, wherein

the second handover/change module is configured to hand over or switch a user equipment (UE)

from a source network on the network side to a target network on the network side; and

the second detachment module is configured to detach the UE from the source network.

20 31. The device according to claim 30, comprising a second detachment determination module

configured to determine whether to detach the UE from the source network, wherein if yes, an

initiating instruction is sent to the second detachment module to initiate the second detachment

module.

32. The device according to claim 30, comprising a module for receiving terminal capability of

25 the UE configured to receive the terminal capability of the UE sent by the UE.

33. The device according to claim 31, wherein the second detachment determination module is

disposed in a mobility management network element (MME), a packet data network gateway (PDN

GW), a serving Gateway (serving GW), a non-3rd-generation partnership project gateway

(non-3GPP GW), or a home subscriber server/authentication, authorization, and accounting server

30 (HSS/A A A server).

34. The device according to claim 30, comprising a module for sending access policy

information of an operator configured to send the access policy information of the operator to the

UE.

35. A device for user detachment when a handover/change occurs in a heterogeneous network,

10

NSN677-1002,

DF078307331

comprising a first handover/change module and a first detachment module disposed in a user

equipment (UE), wherein

the first handover/change module is configured to hand over or switch the UE from a source

network to a target network; and

5 the first detachment module is configured to detach the UE from the source network.

36. The device according to claim 35, comprising a first detachment determination module

configured to determine whether to detach the UE from the source network, wherein if yes, an

initiating instruction is sent to the first detachment module to initiate the first detachment module.

37. The device according to claim 35, comprising a module for sending terminal capability of

10 the UE configured to send the terminal capability of the UE to a network side.

38. The device according to claim 35, comprising a module for receiving access policy

information of an operator configured to receive the access policy information of the operator sent

by the network side.

11

NSN677-1002,

DF078307331

Specification

METHOD, SYSTEM, AND DEVICE FOR USER DETACHMENT WHEN A

HANDOVER/CHANGE OCCURS IN HETEROGENEOUS NETWORK

FIELD OF THE TECHNOLOGY

5 [0001] The present invention relates to the network communication technology and more

particularly to a method, system, and device for user detachment when a handover/change occurs in

a heterogeneous network.

BACKGROUND

[0002] To improve the competitiveness of networks in the future, a new evolution network is

10 now researched for a 3rd-generation partnership project (3GPP) network. FIG. 1 is a schematic

structural view of an evolution network system for a 3GPP network. The system includes: an

evolved UMTS terrestrial radio access network (E-UTRAN), for implementing all functions related

to the wireless feature of the evolution network; a mobility management entity (MME), for mobility

management of a control plane, including management of a user context and a mobility state and

15 allocation of temporary user identities; a serving gateway (serving GW) entity, for acting as a user

plane anchor point between access networks of the 3GPP network for terminating the E-UTRAN; a

packet data network gateway (PDN GW) entity, for acting as a user anchor point between an access

network of the 3GPP network and an access network of a non-3GPP network, and an interface for

terminating the external PDN; a policy and charging rule function (PCRF) entity, for implementing

20 functions of policy control decision and flow-based charging control; and a home subscriber server

(HSS), for storing subscription information of users.

[0003] The UMTS terrestrial radio access network (UTRAN) or GSM/EDGE radio access

network (GERAN) implements all functions relevant to the wireless feature of the existing

UMTS/GPRS network; a serving GPRS supporting node (SGSN) implements functions of route

25 forwarding, mobility management, session management, and user information storage in the

GPRS/UMTS network.

[0004] IP access networks of the non-3GPP network mainly include access networks defined by

non-3GPP network organizations, for example, wireless local area network (WLAN), worldwide

interoperability for microwave access (Wimax), and code division multiple access (CDMA)

30 network.

12

NSN677-1002,

DF078307331

[0005] An authentication, authorization, and accounting server (AAA server) mainly

implements access authentication, authorization, and accounting for user equipment (UE).

[0006] It should be noted that, the schematic structural view of FIG. 1 is not the only schematic

structural view of the evolution network system for a 3GPP network. The evolution network of a

5 3GPP network may have various structures.

[0007] One requirement on the evolution network of a 3GPP network is to realize the handover

or switching of the UE between a 3GPP network and a non-3GPP network. FIG. 2 is a flow chart of

a process that the UE is handed over or switched from a 3GPP network to a non-3GPP network in

the prior art. The process includes the following steps.

10 [0008] In Step 201, the UE accesses the 3GPP network through a serving GW and a PDN GW.

[0009] In FIG. 2, the mobility management network element (MME) and the serving GW

belong to the 3GPP network, a non-3GPP GW belongs to the non-3GPP network, and the PDN GW

and HSS/AAA server are common network elements shared by the 3GPP network and the

non-3GPP network.

15 [0010] In Step 202, the UE triggers the handover or switching from the 3GPP network to the

non-3GPP network.

[0011] In Step 203, the UE sends an Access Request message to the non-3GPP GW, and

requests to access the non-3GPP GW.

[0012] As for a WLAN system, the non-3GPP GW in this step is an evolved packet data

20 gateway (EPDG); as for a Wimax system, the non-3GPP GW in this step is an access service

network gateway (ASN GW); and as for a CDMA system, the non-3GPP GW is an access gateway

(AGW).

[0013] In Step 204, an access authentication process is performed between the UE, the

non-3GPP GW, and the HSS/AAA server, and the non-3GPP GW obtains the PDN GW address

25 information used by the UE.

[0014] In Step 205a, the non-3GPP GW sends a proxy binding update message to the PDN GW.

[0015] In this step, it is assumed that an interface protocol between the non-3GPP GW and the

PDN GW is the proxy mobile internet protocol (PMIP). If an interface protocol between the UE and

the PDN GW is the client mobile internet protocol (CMIP), Step 205a is replaced by Step 205b, in

30 which the UE sends a binding update message to the PDN GW.

[0016] In Step 206a, the PDN GW sends a proxy binding acknowledgement message to the

non-3GPP GW.

[0017] In this step, it is assumed that the interface protocol between the non-3GPP GW and the

PDN GW is the PMIP. If the interface protocol between the UE and the PDN GW is the CMIP, Step

13

NSN677-1002,

DF078307331

206a is replaced by Step 206b, in which the PDN GW sends a binding Ack message to the UE.

[0018] In Step 207, the non-3GPP GW returns an access accept message to the UE.

[0019] In Step 208, the PDN GW sends a delete bearer request message to the serving GW, and

the serving GW sends the delete bearer request message to the MME.

5 [0020] In Step 209, the MME deletes bearer resources related to the UE, returns a delete bearer

response message to the serving GW, and the serving GW returns the delete bearer response

message to the PDN GW.

[0021] The above flow is a specific example of the process that the UE is handed over or

switched from a 3GPP network to a non-3GPP network. Certainly, the handover/change process is

10 not limited to the above descriptions. A 3GPP network involved in the handover/change may be

GERAN, UTRAN, or EUTRAN. A non-3GPP network involved in the handover/change may be

WLAN, Wimax, or CDMA system.

[0022] Once the UE accesses a 3GPP network, the 3GPP network creates bearer resources of

the UE and a mobility management context of the UE. The mobility management context of the UE

15 exists in the MME. Furthermore, bearer resources of a 3GPP network and a mobility management

context of a 3GPP network are also created in the UE. Therefore, when the UE is handed over or

switched from a 3GPP network to a non-3GPP network, user detachment needs to be performed to

save network resources. The user detachment includes detachment of the 3GPP network and

detachment of the UE. The detachment of the 3GPP network indicates that the 3GPP network

20 deletes the bearer resources of the UE and the mobility management context of the UE, and the

detachment of the UE indicates that the UE deletes the bearer resources of the 3GPP network and

the mobility management context of the 3GPP network. Here, the mobility management context of

the UE exists in the MME.

[0023] However, in the process shown in FIG. 2, when the UE is handed over or switched from

25 a 3GPP network to a non-3GPP network, the 3GPP network merely deletes the bearer resources of

the UE, but does not delete the mobility management context of the UE, and meanwhile, the UE

does not delete the bearer resources and mobility management context of the 3GPP network as well.

[0024] As known from the above that, the prior art neither provides a method for 3GPP network

detachment when the UE is handed over or switched from a 3GPP network to a non-3GPP network,

30 nor provides a specific method for user detachment of the UE when the UE is handed over or

switched from a 3GPP network to a non-3GPP network. That is to say, no specific solution for user

detachment when handover/change occurs in a heterogeneous network is provided in the prior art.

[0025] In addition, if the UE has a single radio capability, that is, the UE can access only one

network, after the UE is handed over or switched from a 3GPP network to a non-3GPP network,

14

NSN677-1002,

DF078307331

user detachment needs to be performed, that is, the 3GPP network needs to detach the UE, and the

UE needs to be detached from the 3GPP network. The detaching, by the 3GPP network, the UE

includes that the 3GPP network deletes the bearer resources of the UE on the 3GPP network side,

and the mobility management context of the UE in the MME. The detaching, by the UE, from the

5 3GPP network includes that the UE deletes the bearer resources and mobility management context

created when the UE accesses the 3GPP network.

[0026] If the UE has a dual radio capability, that is, the UE can access two networks at the same

time, after the UE is handed over or switched from a 3GPP network to a non-3GPP network, it is

judged whether the 3GPP network needs to detach the UE according to, for example, information of

10 operator policies. In other words, the prior art does not provide a solution for determining whether

to perform the user detachment when the UE is handed over or switched from a 3GPP network to a

non-3GPP network.

[0027] To sum up, the prior art neither provides a specific solution for user detachment when a

handover/change occurs in a heterogeneous network, nor provides a solution for judging whether to

15 perform user detachment when handover/change occurs in a heterogeneous network.

SUMMARY

[0028] An embodiment of the present invention provides a method for detaching a user when a

handover/change occurs in a heterogeneous network.

[0029] An embodiment of the present invention further provides another method for detaching a

20 user when a handover/change occurs in a heterogeneous network.

[0030] An embodiment of the present invention provides a system for detaching a user when a


[0031] An embodiment of the present invention provides a device for detaching a user when a


25 [0032] An embodiment of the present invention further provides a device for detaching a user

when a handover/change occurs in a heterogeneous network.

[0033] A method for detaching a user when handover/change occurs in a heterogeneous

network includes the following steps.

[0034] First, a UE is handed over or switched from a source network to a target network.

30 [0035] Next, the source network determines whether to detach the UE from the source network;

and if yes, detaches the UE from the source network; otherwise, does not detach the UE from the

source network.

[0036] Another method for user detachment when a handover/change occurs in a heterogeneous

15

NSN677-1002,

DF078307331


[0037] First, a UE triggers handover or switching from a source network to a target network.

[0038] Next, the UE determines whether to be detached from the source network; if yes, the UE

is detached from the source network.

5 [0039] A system for user detachment when a handover/change occurs in a heterogeneous

network includes a UE and a network side.

[0040] The UE is adapted to be handed over or switched from a source network on the network

side to a target network on the network side.

[0041] The network side is adapted to hand over or switch the UE from the source network to

10 the target network, and detach the UE from the source network.

[0042] A device for detaching a user when a handover/change occurs in a heterogeneous

network includes a second handover/change module and a second detachment module on a network

side.

[0043] The second handover or switching module is adapted to hand over or switch a UE from a

15 source network on the network side to a target network on the network side.

[0044] The second detachment module is adapted to detach the UE from the source network.

[0045] A device for detaching a user when a handover/change occurs in a heterogeneous

network includes a first handover/change module and a first detachment module in a UE.

[0046] The first handover/change module is adapted to hand over or switch the UE from a

20 source network to a target network.

[0047] The first detachment module is adapted to detach the UE from the source network.

[0048] As known from the above solutions that, in the embodiments of the present invention,

when a handover/change occurs in the heterogeneous network, the UE is detached from the source

network after being determined by the source network or the UE is detached from the source

25 network after being determined by the UE. Thus, detachment of the user is realized by the source

network or the UE, when the handover/change occurs in the heterogeneous network.

BRIEF DESCRIPTION OF THE DRAWINGS

[0049] FIG. 1 is a schematic structural view of an evolution network system for a 3GPP network

in the prior art;

30 [0050] FIG. 2 is a flow chart of a process that the UE is handed over or switched from a 3GPP

network to a non-3GPP network in the prior art;

[0051] FIG. 3 is a flow chart of a process that a network element in a 3GPP network acquires

terminal capability of UE and access policy information of an operator when the UE accesses the

16

NSN677-1002,

DF078307331

3GPP network according to an embodiment of the present invention;


terminal capability of UE and access policy information of an operator when a location area or

terminal capability of the UE changes according to an embodiment of the present invention;

5 [0053] FIG. 5 is a flow chart of a process that a network element in a non-3GPP network

acquires terminal capability of UE and access policy information of an operator when the UE

accesses the non-3GPP network according to an embodiment of the present invention;

[0054] FIG. 6 shows a first example of a method for user detachment when a handover/change

occurs in a heterogeneous network according to an embodiment of the present invention;

10 [0055] FIG. 7 shows

handover/change occurs in

invention;

[0056] FIG. 8 shows


15 invention;

[0057] FIG. 9 shows


invention;

[0058] FIG. 10 shows

20 handover/change occurs in

invention;

[0059] FIG. 11 shows

a second example of the method for

a heterogeneous network according to an

a third example of the method for


a fourth example of the method for


a fifth example of the method for


a sixth example of the method for

user detachment when a

embodiment of the present








handover/change occurs in a heterogeneous network according to an embodiment of the present

invention; and

25 [0060] FIG. 12 is a schematic structural view of a system for user detachment when a


invention.

DETAILED DESCRIPTION

[0061] To make the objectives, technical solutions, and beneficial effects of the present

30 invention more comprehensible, the present invention is described in detail below with reference to

the accompanying drawings and embodiments.

[0062] FIGs. 6-10 respectively show the first to fifth examples of a method for user detachment

when a handover/change occurs in a heterogeneous network according to an embodiment of the

17

NSN677-1002,

DF078307331

present invention. The main ideas of the examples are described as follows:

[0063] The UE is handed over or switched from a source network to a target network; the

source network determines whether to detach the UE from the source network; if yes, the UE will

be detached from the source network; otherwise, the UE will not be detached from the source

5 network.

[0064] FIG. 11 shows a sixth example of a method for user detachment when a handover/change

occurs in a heterogeneous network according to an embodiment of the present invention. The main

idea of this example is described as follows.

[0065] The UE triggers a handover or switching from a source network to a target network; the

10 UE determines whether to be detached from the source network; if yes, the UE will be detached

from the source network; otherwise, the UE will not be detached from the source network.

[0066] The two networks involved in the handover/change in the heterogeneous network

according to the embodiments of the present invention may be one of the 3GPP networks (such as a

GERAN network, a UTRAN network, or an EUTRAN network) and one of the non-3GPP networks

15 (such as a WLAN network, Wimax network, or CDMA network). Specifically, the embodiments

include the handover or switching of the UE from a 3GPP network to a non-3GPP network or the

handover or switching of the UE from a non-3GPP network to a 3GPP network. Here, the network

where the UE originally exists during the handover/change process is referred to as the source

network, and the other network involved in the handover/change process is referred as the target

20 network.

[0067] Then, the handover or switching from a 3GPP network to a non-3GPP network is taken

as an example to illustrate the first embodiment to the sixth embodiment of the method for UE

detachment when a handover/change occurs in the heterogeneous network of the present invention.

[0068] The UE and the network element in the 3GPP network acquire the terminal capability of

25 the UE, and the network element obtains access policy information of the operator, which are

provided for being used in the solution for UE detachment when the UE is handed over or switched

from the 3GPP network to the non-3GPP network according to the embodiments of the present

invention. Here, FIGs. 3 and 4 are used to illustrate the process that the network element in a 3GPP

network acquires the terminal capability of the UE and the access policy information of the operator

30 according to the embodiments of the present invention. FIG. 3 is a flow chart of a process that a

network element in a 3GPP network acquires terminal capability of UE and access policy

information of an operator when the UE accesses the 3GPP network. FIG. 4 is a flow chart of a

process that a network element in a 3GPP network acquires terminal capability of UE and access

policy information of an operator when a location area or terminal capability of the UE changes

18

NSN677-1002,

DF078307331

after the UE accesses the 3GPP network according to an embodiment of the present invention.

[0069] Referring to FIG. 3, the process that the network element in the 3GPP network acquires

the terminal capability of the UE and the access policy information of the operator when the UE

accesses the 3GPP network includes the following steps.

5 [0070] In step 301, the UE sends an attach request message carrying terminal capability of the

UE to the MME.

[0071] In this step, if the access network of the UE is GERAN/UTRAN, the SGSN serves as the

MME; if the access network of the UE is EUTRAN, the MME serves as the MME.

[0072] In this step, the terminal capability of the UE is represented by information element (IE)

10 of the radio capability supported by the UE. The radio capability supported by the UE is a single

radio capability (which indicates that the UE can access only one network at a certain time point) or

a dual radio capability (which indicates that the UE can access two or more networks at a certain

time point). An exemplary structure of the IE carrying the radio capability supported by the UE is

listed as follows. The IE includes a radio capability parameter supported by the UE. The parameter

15 may be: 1) the UE has a single radio capability; 2) the UE has a dual radio capability.

<UE Network Capability value part> ::=

UE Support Radio Capability


0 Single Radio Capability

1 Dual Radio Capability

[0073] In step 302, the UE, the MME, and the HSS/AAA server implement an authentication

process of the UE to authenticate the UE.

20 [0074] In step 303, if the MME finds that the UE is in an invalid state, the MME sends an

update location message to the HSS/AAA server, and registers the UE with the HSS/AAA server.

The update location message carries the terminal capability of the UE.

[0075] In this step, if the access policy information of the operator is configured in the MME,

the update location request may carry the access policy information of the operator. The access

25 policy information of the operator includes: 1) a single radio access, that is, the UE can access only

one access network at a certain time point; and 2) a dual radio access, that is, the UE can access a

19

NSN677-1002,

DF078307331

plurality of access networks at a certain time point.

[0076] In step 304, the HSS/AAA server inserts subscription data of a user into the MME.

[0077] In this step, if the access policy information of the operator is configured or subscribed

in the HSS/AAA server, the HSS/AAA server carries the access policy information of the operator

5 in the subscription data, and sends the subscription data to the MME.

[0078] In step 305, the HSS/AAA server returns an update location Ack message to the MME.

[0079] In Step 306, the MME sends a create bearer request message to the serving GW, and the

serving GW sends the create bearer request message to the PDN GW.

[0080] In this step, the MME initiates a default bearer establishment process, so as to create a

10 default bearer of the UE in the MME, serving GW, and PDN GW. The create bearer request

message further carries a bearer type IE. The MME uses the bearer type IE to notify the created

bearer type to the serving GW and the PDN GW. If the MME sets the bearer type IE to default

bearer, the serving GW and the PDN GW are notified that the created bearer is a default bearer.

[0081] In this step, the terminal capability of the UE and the access policy information of the

15 operator are carried in the create bearer request message and sent to the serving GW and the PDN

GW.

[0082] Steps 307 and 308 are performed only when the policy and charging rules used by the

default bearer need to be obtained from the PCRF, and the access policy information of the operator

is configured in the PCRF.

20 [0083] In step 307, the PDN GW sends a PCC rules request message to the PCRF to obtain the

policy and charging rules used by the default bearer.

[0084] In step 308, the PCRF returns a PCC rules provision message to the PDN GW, and the

PCC rules provision message carries the access policy information of the operator.

[0085] In step 309, the PDN GW and the serving GW create a bearer context, and sets the

25 created bearer as the default bearer; the PDN GW returns a create bearer response message to the

serving GW, and the serving GW returns the create bearer response message to the MME.

[0086] If the access policy information of the operator is configured in the PCRF entity, or the

access policy information of the operator is configured in the PDN GW, or the access policy

information of the operator is configured in the serving GW, this step includes the following: the

30 create bearer response message carries the access policy information of the operator configured by

the PCRF, the PDN GW, or the serving GW.

[0087] In this step, the bearer context created by the PDN GW and the serving GW includes

bearer type information, which has two values: default bearer and dedicated bearer. For the default

bearer, the PDN GW and the serving GW set the bearer type information in the bearer context to

20

NSN677-1002,

DF078307331

default bearer. The PDN GW and the serving GW may know that the created bearer is a default

bearer in the following two manners.

[0088] 1) In step 306, the MME carries the bearer type IE in the create bearer request message,

and notifies the bearer type to the serving GW and the PDN GW through the bearer type IE. If the

5 carried bearer type IE set by the MME is in the value of default bearer, the created bearer is the

default bearer.

[0089] 2) The serving GW and the PDN GW determine whether the created bearer is the first

bearer created in the packet data network (PDN); if yes, the serving GW and the PDN GW

determine that the created bearer is a default bearer.

10 [0090] Other bearers are dedicated bearers. In this case, the serving GW and the PDN GW set

the bearer type information in the bearer context to dedicated bearer.

[0091] Step 310a is performed only when the access network type (RAT type) information in

the 3GPP network has been registered with the HSS/AAA server by the MME.

[0092] In step 310a, the MME registers access situations of the UE in the 3GPP network (for

15 example, the RAT type used by the UE) with the HSS/AAA server.

[0093] Step 310b is performed only when the RAT type information of the UE in the 3GPP

network has been registered with the HSS/AAA server by the PDN GW.

[0094] In step 310b, the PDN GW registers the access situations of the UE in the 3GPP network

(for example, the RAT type used by the UE) with the HSS/AAA server.

20 [0095] Through this step, the HSS/AAA server obtains the access network situations of the UE.

For example, in this embodiment, the HSS/AAA server knows that the RAT type of the UE is a

3GPP network type, or a specific network type in a 3GPP network.

[0096] The RAT type of the UE includes the following two situations.

[0097] 1) The RAT type of the UE is categorized into a 3GPP network and a non-3GPP

25 network.

[0098] 2) The RAT type of the UE is a specific network type used by the UE, for example,

GERAN network, UTRAN network, EUTRAN network, WLAN network, Wimax network, CDMA

network, etc.

[0099] In Step 311, the MME returns an Attach Accept message to a network element on an

30 access side, and the Attach Accept message carries information of the radio bearer to be established

by the UE.

[0100] As for the EUTRAN access network, the network element on the access side is ENodeB;

as for the UTRAN access network, the network element on the access side is RNC; as for the

GERAN access network, the network element on the access side is BSS. The MME may carry the

21

NSN677-1002,

DF078307331

access policy information of the operator in the Attach Accept message.

[0101] In step 312, the network element on the access side sends a bearer establishment request

message to the UE, and requests the UE to establish a radio bearer. The message carries the access

policy information of the operator sent by the MME.

5 [0102] The access policy information of the operator may also be notified to the UE in a

broadcast message of a cell.

[0103] In step 313, the UE establishes the bearer context, sets the created bearer to a default

bearer, and returns a radio bearer establishment response message to the network element on the

access side.

10 [0104] The UE adds bearer type information to the established bearer context, and the bear type

has the following two values: default bearer and dedicated bearer. For the default bearer, the UE

sets the bearer type information in the bearer context to default bearer. The bearer type added to the

established bearer context by the UE may be acquired through the following manners.

[0105] 1) In step 311, the MME carries a bearer type IE in the Attach Accept message, and

15 notifies the bearer type to the UE by the network element on the access side through the bearer type

IE. For the default bearer, the value of the bearer type IE carried by the MME is Default Bearer.

[0106] 2) The UE determines whether the created bearer is the first bearer created in the PDN;

if yes, the UE determines that the created bearer is a default bearer.

[0107] Other bearers are dedicated bearers. hi this case, the UE sets the bearer type information

20 in the bearer context to dedicated bearer.

[0108] In this embodiment, it should be noted that, the HSS and the AAA server may be

configured in different entities or in a same entity. If the HSS and the AAA server are configured in

different entities, the register message sent by the PDN GW in step 310a is forwarded to the HSS by

the AAA server, and the register message sent by the MME in step 310b is forwarded to the AAA

25 server by the HSS.



terminal capability of the UE changes. The process includes the following steps.

[0110] In step 401, the UE sends a tracking area update or routing area update request

30 (TAU/RAU request) message carrying changed terminal capability of the UE to the MME.

[0111] If the access network of the UE is GERAN/UTRAN, the message sent by the UE is the

RAU request message; if the access network of the UE is EUTRAN, the message sent by the UE is

the TAU request message.

[0112] The terminal capability of the UE is represented by IEs of the radio capability supported

22

NSN677-1002,

DF078307331

by the UE. The radio capability supported by the UE is a single radio capability (which indicates

that the UE can access only one network at a certain time point) or a dual radio capability (which

indicates that the UE can access two or more networks at a certain time point). An exemplary

structure of the TE carrying the radio capability supported by the UE is listed as follows. The IE

5

includes a radio capability parameter supported by the UE. The parameter may be: 1) the UE has a

single radio capability; 2) the UE has a dual radio capability.






[0113] In step 402, the MME sends an update location message to the HSS/AAA server, and

10 registers the UE with the HSS/AAA server, in which the update location message carries the

changed terminal capability of the UE.


the update location request message carries the access policy information of the operator. The

access policy information of the operator includes: 1) a single radio access, that is, the UE can

15 access only one access network at a certain time point; and 2) a dual radio access, that is, the UE

can access a plurality of access networks at a certain time point.



in the HSS/AAA server, the HSS/AAA server delivers the changed access policy information of the

20 operator to the MME.

[0117] In Step 404, the HSS/AAA server returns an update location Ack message to the MME.

[0118] In Step 405, when the MME determines that the access policy information of the

operator and the terminal capability of the UE has changed, the MME sends an update bearer

request message to the serving GW, and the serving GW sends the update bearer request message to

25 the PDN GW, in which the update bearer request message carries the changed access policy

information of the operator and the changed terminal capability of the UE.

23

NSN677-1002,

DF078307331

[0119] In this step, the changed access policy information of the operator and the changed

terminal capability of the UE are notified to the serving GW and the PDN GW.

[0120] Step 406a is performed only when the RAT type information in the 3GPP network has

been registered with the HSS/AAA server by the MME and the information has changed.

5 [0121] In Step 406a, the MME registers the access situations of the UE in the 3GPP network


[0122] Step 406b is performed only when the RAT type information in the 3GPP network has

been registered with the HSS/AAA server by the PDN GW and the information has changed.

[0123] In step 406b, if the RAT type information in the 3GPP network has been registered with

10 the HSS/AAA server by the PDN GW and the information has changed, the PDN GW registers the

access situations of the UE in the 3GPP network (for example, the RAT type used by the UE) with

the HSS/AAA server.

[0124] In step 407, the MME returns a TAU/RAU accept message to the UE, and the MME

may deliver the changed access policy information of the operator to the UE in the TAU/RAU

15 accept message.

[0125] The changed access policy information of the operator may also be notified to the UE in

a broadcast message of the cell.

[0126] FIG. 4 shows the process that the network element in a 3GPP network acquires the

changed terminal capability of the UE and the changed access policy information of the operator

20 when the terminal capability of the UE and the access policy information of the operator both have

changed. The process that the network element in the 3GPP network acquires the changed terminal

capability of the UE or the changed access policy information of the operator when the terminal

capability of the UE or the access policy information of the operator has changed is similar to the

process of FIG. 4, which thus is not described in detail here.

25 [0127] The UE and the network element in a non-3GPP network acquire the terminal capability

of the UE, and the network element acquires the access policy information of the operator, which

are provided for being used in the solution for UE detachment when the UE is handed over or

switched from the non-3GPP network to a 3GPP network according to the embodiments of the

present invention. FIG. 5 is used to illustrate the process that the network element in a non-3GPP

30 network acquires the terminal capability of the UE and the access policy information of the operator

according to the embodiments of the present invention. FIG. 5 is a flow chart of a process that a

network element in a non-3GPP network acquires terminal capability of UE and access policy

information of an operator when the UE accesses the non-3GPP network.

[0128] Referring to FIG. 5, the process that the network element in the non-3GPP network

24

NSN677-1002,

DF078307331

acquires the terminal capability of the UE and the access policy information of the operator when

the UE accesses the non-3GPP network includes the following steps.

[0129] In step 501, the UE sends an access request message carrying the terminal capability of

the UE to a non-3GPP GW.

5 [0130] In this step, if the non-3GPP network is a WLAN network, the non-3GPP GW is an

EPDG; if the non-3GPP network is a Wimax network, the non-3GPP GW is an ASN GW; and if the

non-3GPP network is a CDMA network, the non-3GPP GW is an AGW.

[0131] In this step, the terminal capability of the UE is represented by IEs of the radio

capability supported by the UE. The radio capability supported by the UE is a single radio

10 capability (which indicates that the UE can access only one network at a certain time point) or a

dual radio capability (which indicates that the UE can access two or more networks at a certain time

point). An exemplary structure of the IE carrying the radio capability supported by the UE is listed

as follows. The IE includes a radio capability parameter supported by the UE. The parameter may

be: 1) the UE has a single radio capability; 2) the UE has a dual radio capability.

15






[0132] In step 502, an authentication process is performed between the UE, the non-3GPP GW,

and the HSS/AAA server.

[0133] In this step, if the access policy information of the operator is configured in the

20 non-3GPP GW, an access authentication message may carry the access policy information of the

operator to the HSS/AAA server. The access policy information of the operator includes: 1) a single

radio access, that is, the UE can access only one access network at a certain time point; and 2) a

dual radio access, that is, the UE can access a plurality of access networks at a certain time point. In

this step, if the access policy information of the operator is configured in the HSS/AAA server, the

25 access authentication message may carry the access policy information of the operator to the

non-3GPP GW.

25

NSN677-1002,

DF078307331

[0134] In step 503a, the non-3GPP GW sends a proxy binding update message to the PDN GW.


PDN GW is the proxy mobile internet protocol (PMIP). If an interface protocol between the UE and

the PDN GW is the client mobile internet protocol (CMIP), step 503a is replaced by step 503b, in

5 which the UE sends a binding update message to the PDN GW.


operator may be carried in the proxy binding update message or the binding update message and

sent to the PDN GW.

[0137] In step 504, if the policy and charging rules used by the UE need to be obtained from the

10 PCRF, the PDN GW sends a PCC rules request message to the PCRF to obtain the policy and

charging rules used by the UE.

[0138] In step 505, the PCRF provides a PCC rules provision message of the policy and

charging rules used by the UE to the PDN GW. If the access policy information of the operator is

configured in the PCRF, the PCRF transmits the access policy information of the operator to the

15 PDN GW via the PCC rules provision message.

[0139] In step 506, if the policy and charging rules used by the UE need to be obtained from the

PCRF, the non-3GPP GW sends a PCC rules request message to the PCRF to obtain the policy and



20 charging rules used by the UE to the non-3GPP GW. If the access policy information of the operator

is configured in the PCRF, the PCRF transmits the access policy information of the operator to the

non-3GPP GW via the PCC rules provision message.

[0141] In step 508a, the PDN GW sends a proxy binding Ack message to the non-3GPP GW.

[0142] In this step, it is assumed that the interface protocol between the non-3GPP GW and the

25 PDN GW is the PMIP. If the interface protocol between the UE and the PDN GW is the CMIP, step

508a is replaced by step 508b, in which the PDN GW sends a binding Ack message to the UE.

[0143] In step 509, if the RAT type information in the non-3GPP network is registered with the

HSS/AAA server by the PDN GW, the PDN GW registers the access situations of the UE in the

non-3GPP network (for example, the RAT type used by the UE) with the HSS/AAA server.

30 [0144] In step 510, if the RAT type information in the non-3GPP network is registered with the

HSS/AAA server by the non-3GPP GW, the non-3GPP GW registers the access situations of the UE

in the non-3GPP network (for example, the RAT type used by the UE) with the HSS/AAA server.

[0145] Through step 509 or step 510, the HSS/AAA server obtains the access network situations

of the UE. For example, in this embodiment, the HSS/AAA server knows that the RAT type of the

26

NSN677-1002,

DF078307331

UE is a non-3GPP network type, or a specific network type in the non-3GPP network. This step is

optional.

[0146] The RAT type used by the UE may be processed through the following two manners.

[0147] 1) The RAT type used by the UE is categorized into a 3GPP network and a non-3GPP

5 network.

[0148] 2) The RAT type used by the UE is a specific network type used by the UE, for example,

a GERAN network, a UTRAN network, an EUTRAN network, a WLAN network, Wimax network,

or a CDMA network.

[0149] In step 511, the non-3GPP GW returns an access accept message to the UE. The

10 non-3GPP GW may carry the access policy information of the operator in the access accept

message.


configured in different entities or in the same entity. If the HSS and the AAA server are configured

in different entities, the register message sent by the PDN GW in step 509 is forwarded to the HSS

15 by the AAA server, and the register message sent by the non-3GPP GW in Step 510 is forwarded to

the AAA server by the HSS.

[0151] FIG. 6 shows a first example of a method for detaching a user when a handover/change

occurs in a heterogeneous network according to an embodiment of the present invention. The

method includes the following steps.

20 [0152] Steps 601-607 are the same as steps 201-207 in FIG. 2.

[0153] In step 608a, the PDN GW sends a delete bearer request message to the serving GW, and

then the serving GW sends the received delete bearer request message to the MME, and adds a

cause IE in the delete bearer request message to indicate the reason of the deletion, and the MME

deletes the bearer resources.

25 [0154] In this step, as for the bearer deletion caused by the handover or switching of the UE

from the 3GPP network to the non-3GPP network, the PDN GW sets the cause IE as "UE's

accessing RAT changed from a 3GPP network to a non-3GPP network". As for the bearer deletion

that is not caused by the handover/change, the PDN GW sets the cause IE to other values.

Alternatively, the delete bearer request message sent by the PDN GW does not carry the cause IE,

30 and in this case, once the MME receives the delete bearer request message sent by the serving GW,

the message is defaulted to be caused by the handover or switching of the UE from the 3GPP

network to the non-3GPP network. In this embodiment, the message carrying the cause IE is taken

as an example.

[0155] In this step, it is assumed that an interface protocol between the PDN GW and the

27

NSN677-1002,

DF078307331

serving GW is GPRS tunneling protocol (GTP). If the interface protocol between the PDN GW and

the serving GW is the PMIP, step 608a is replaced by step 608b, in which the PDN GW sends a

binding revocation indication message to the serving GW; the cause IE is added to the binding

revocation indication message; the serving GW sends the delete bearer request message carrying the

5 cause IE sent by the PDN GW to the MME; and the MME deletes the bearer resources after

receiving the delete bearer request message.

[0156] As for the binding revocation indication caused by the handover or switching of the UE


accessing RAT changed from a 3GPP network to a non-3GPP network". As for the bearer deletion

10 that is not caused by the handover/change, the PDN GW sets the cause IE to other values.

Alternatively, the binding revocation indication message sent by the PDN GW does not carry the

cause IE, and in this case, once the MME receives the delete bearer request message sent by the

serving GW, the message is default to be caused by the handover or switching of the UE from the

3GPP network to the non-3GPP network. In this embodiment, the message carrying the cause IE is

15 taken as an example.

[0157] Step 608a or step 608b further includes the following: the MME deletes the bearer

resources after receiving the delete bearer request message. If the MME finds that all bearer

resources of the UE are deleted, the MME further determines whether to delete an MM context (i.e.,

detaching the UE from the 3GPP network) and whether to send a detach request message to the UE.

20 Specifically, the process includes the following circumstances.

[0158] 1) The MME makes the following determination according to the cause IE carried in the

delete bearer request. The MME determines whether the cause IE carried in the received delete

bearer request message is represented as "UE's accessing RAT changed from a 3GPP network to a

non-3GPP network"; if yes, the MME deletes the MM context of the UE, and does not send the

25 detach request message to the UE; otherwise, the MME sends the detach request message to the UE

and notifies the UE to delete the MM context and the bearer resources of the 3GPP network in the

UE.

[0159] 2) The MME makes the following determination according to the IE carried in the delete

bearer request and the terminal capability of the UE. If the MME determines that the IE carried in

30 the received delete bearer request message is represented as "UE's accessing RAT changed from a

3GPP network to a non-3GPP network", and the MME knows that the terminal capability of the UE

is "single radio capability", the MME deletes the MM context of the UE, and does not send the

detach request message to the UE; as for the bearer deletion caused by other reasons, the MME

deletes the MM context of the UE, and sends the detach request message to the UE. If the MME

28

NSN677-1002,

DF078307331

knows that the terminal capability of the UE is "multi radio capability", the MME does not delete

the MM context of the UE (that is, does not detach the UE from the 3GPP network).


bearer request and the access policy information of the operator. If the MME determines that the IE

5 carried in the received delete bearer request message is represented as "UE's accessing RAT

changed from a 3GPP network to a non-3GPP network", and the MME knows that the access policy

information of the operator is "single radio access", the MME deletes the MM context of the UE,

and does not send the detach request message to the UE; as for the bearer deletion caused by other

reasons, the MME deletes the MM context of the UE, and sends the detach request message to the

10 UE. If the MME knows that the access policy information of the operator is "multi radio access",

the MME does not delete the MM context of the UE (that is, does not detach the UE from the 3GPP

network).


bearer request, the terminal capability of the UE, and the access policy information of the operator.

15 If the MME determines that the IE carried in the received delete bearer request message is

represented as "UE's accessing RAT changed from a 3GPP network to a non-3GPP network", the

terminal capability of the UE is "dual radio capability", and the access policy information of the

operator is "single radio access", or if the MME determines that the IE carried in the received delete

bearer request message is represented as "UE's accessing RAT changed from a 3GPP network to a

20 non-3GPP network", the access policy information of the operator is "multi radio access", and the

terminal capability of the UE is "single radio capability", or if the MME determines that the IE

carried in the received delete bearer request message is represented as "UE's accessing RAT

changed from a 3GPP network to a non-3GPP network", the terminal capability of the UE is "single

radio capability", and the access policy information of the operator is "single radio access", the

25 MME deletes the MM context of the UE, and does not send the detach request message to the UE;

as for the bearer deletion caused by other reasons, the MME deletes the MM context of the UE, and

sends the detach request message to the UE. If the MME knows that the terminal capability of the

UE is "dual radio capability" and the access policy information of the operator is "multi radio

access", the MME does not delete the MM context of the UE (that is, does not detach the UE from

30 the 3GPP network).

[0162] In step 609a, the MME returns a delete bearer response message to the serving GW, and

the serving GW returns the delete bearer response message to the PDN GW.

[0163] In this step, the interface protocol between the PDN GW and the serving GW is the GIP,

and if the interface protocol between the PDN GW and the serving GW is the PMIP, Step 609a is

29

NSN677-1002,

DF078307331

replaced by step 609b, in which the MME returns the delete bearer response message to the serving

GW, and the serving GW returns a binding revocation Ack message to the PDN GW.

[0164] In step 610, if the MME sends the detach request message to the UE, the UE deletes the

MM context and the bearer resources after receiving the detach request message, and returns a

5 Detach Accept message to the MME.

[0165] In step 611, if the MME finds that the subscription data and the MM context of the UE

are deleted, the MME sends a purge UE message to the HSS/AAA server, and the HSS/AAA server

purges the record of the UE, and returns a purge UE Ack message to the MME.

[0166] In this step, it is determined whether to delete the subscription data of the UE by the

10 MME according to the actual conditions. This step is optional.

[0167] In the above embodiment, after step 607, it is determined whether to detach the UE from

the 3GPP network. Specifically, the determination process is described as follows: according to the

handover/change in the access network, or according to the handover/change of the UE in the

access network and the terminal capability of the UE, or according to the handover/change of the

15 UE in the access network and the access policy information of the operator, or according to the

handover/change of the UE in the access network, the terminal capability of the UE, and the access

policy information of the operator, it is determined whether to detach the UE from the 3GPP

network, which particularly includes the following four circumstances.

[0168] 1) It is determined whether the UE is handed over or switched from the 3GPP network to

20 the non-3GPP network; if yes, the MM context and bearer resources used by the UE in the 3GPP

network are deleted.


the non-3GPP network and whether the terminal capability of the UE is "single radio capability"; if

yes, the bearer resources and the MM context used by the UE in the 3GPP network are deleted.

25 [0170] 3) It is determined whether the UE is handed over or switched from the 3GPP network to

the non-3GPP network and whether the access policy information of the operator is "single radio

access"; if yes, the bearer resources and the MM context used by the UE in the 3GPP network are

deleted.

[0171] 4) It is determined whether the handover/change of the UE in the access network, the

30 terminal capability of the UE, and the access policy information of the operator satisfy one of the

following three conditions: 1. the UE is handed over or switched from the 3GPP network to the

non-3GPP network, the terminal capability of the UE is "dual radio capability", and the access

policy information of the operator is "single radio access"; 2. the UE is handed over or switched

from the 3GPP network to the non-3GPP network, the access policy information of the operator is

30

NSN677-1002,

DF078307331

"multi radio access", and the terminal capability of the UE is "single radio capability"; and 3. the

UE is handed over or switched from the 3GPP network to the non-3GPP network, the terminal

capability of the UE is "single radio capability", and the access policy information of the operator is

"single radio access".

5 [0172] If yes, the bearer resources and the MM context used by the UE in the 3GPP network are

deleted.

[0173] Moreover, the delete bearer request added with the cause IE in step 608 may be replaced

by another message, for example, replaced by a release bearer request message. The release bearer

request message indicates that the reason for deleting the bearer is the handover or switching of the

10 UE from the 3GPP network to the non-3GPP network; alternatively, the delete bearer request

message sent in step 608 does not carry the reason for deleting the bearer, and when the UE is

handed over or switched from the 3GPP network to the non-3GPP network, a normal delete bearer

request is sent to the MME. In step 608, after receiving the specific message or the normal delete

bearer request message, the MME deletes the bearer resources; and the operations of the MME after

15 the bearer resources are deleted are similar to the operations of the MME after receiving the delete

bearer request message.

[0174] As for the first embodiment, it should be noted that the detachment method in this

embodiment is also applicable to the handover or switching of the UE from a non-3GPP network to

a 3GPP network.

20 [0175] In step I, after the UE is handed over or switched to a 3GPP network, the PDN GW

sends the binding revocation indication message to a non-3GPP GW. The message carries the cause

IE indicating the reason for the binding revocation. As for the binding revocation caused by the

handover or switching from the non-3GPP network to the 3GPP network, the PDN GW sets the

cause IE as "UE's accessing RAT changed from a non-3GPP network to a 3GPP network"; and as

25 for the binding revocation that is not caused by the handover/change, the PDN GW sets the cause IE

to other values.

[0176] In step II, the non-3GPP GW deletes the bearer resources after receiving the binding

revocation indication message. If the non-3GPP GW finds that all bearer resources of the UE are

deleted, the non-3GPP GW further determines whether to delete the MM context of the UE (that is,

30 to detach the UE from the non-3GPP network), which specifically includes the following

circumstances.

[0177] 1) The non-3GPP GW makes the following determination according to the Cause IE

carried in the binding revocation indication message, in which the non-3GPP GW determines

whether the cause IE carried in the binding revocation indication message is represented as "UE's

31

NSN677-1002,

DF078307331

accessing RAT changed from a non-3GPP network to a 3GPP network"; if yes, the non-3GPP GW

deletes the MM context of the UE, and does not send the detach request message to the UE;

otherwise, the non-3GPP GW sends the detach request message to the UE, and notifies the UE to

delete the MM context and bearer resources of the non-3GPP network in the UE.

5 [0178] 2) The non-3GPP GW makes the following determination according to the IE carried in

the binding revocation indication message and the terminal capability of the UE, in which if the

non-3GPP GW determines that the IE carried in the received binding revocation indication message

is represented as "UE's accessing RAT changed from a non-3GPP network to a 3GPP network", and

the non-3GPP GW knows that the terminal capability of the UE is "single radio capability", the

10 non-3GPP GW deletes the MM context of the UE, and does not send the detach request message to

the UE; as for the bearer deletion caused by other reasons, the non-3GPP GW deletes the MM

context of the UE, and sends the detach request message to the UE. If the non-3GPP GW knows

that the terminal capability of the UE is "multi radio capability", the non-3GPP GW does not delete

the MM context of the UE (that is, does not detach the UE from the non-3GPP network).

15 [0179] 3) The non-3GPP GW makes the following determination according to the IE carried in

the binding revocation indication message and the access policy information of the operator, in

which if the non-3GPP GW determines that the IE carried in the received binding revocation

indication message is represented as "UE's accessing RAT changed from a non-3GPP network to a

3GPP network", and the non-3GPP GW knows that the access policy information of the operator is

20 "single radio access", the non-3GPP GW deletes the MM context of the UE, and does not send the

detach request message to the UE; as for the bearer deletion caused by other reasons, the non-3GPP

GW deletes the MM context of the UE, and sends the detach request message to the UE. If the

non-3GPP GW knows that the access policy information of the operator is "multi radio access", the

non-3GPP GW does not delete the MM context of the UE (that is, does not detach the UE from the

25 non-3GPP network).

[0180] 4) The non-3GPP GW makes the following determination according to the IE carried in

the binding revocation indication message, the terminal capability of the UE, and the access policy

information of the operator, in which if the non-3GPP GW determines that the IE carried in the

received binding revocation indication message is represented as "UE's accessing RAT changed

30 from a non-3GPP network to a 3GPP network", the terminal capability of the UE is "dual radio

capability", and the access policy information of the operator is "single radio access", or if the

non-3GPP GW determines that the IE carried in the received binding revocation indication message

is represented as "UE's accessing RAT changed from a non-3GPP network to a 3GPP network", the

access policy information of the operator is "multi radio access", and the terminal capability of the

32

NSN677-1002,

DF078307331

UE is "single radio capability", or if the non-3GPP GW determines that the IE carried in the

received binding revocation indication message is represented as "UE's accessing RAT changed

from a non-3GPP network to a 3GPP network", the terminal capability of the UE is "single radio

capability", and the access policy information of the operator is "single radio access", the non-3GPP

5 GW deletes the MM context of the UE, and does not send the detach request message to the UE; as

for the bearer deletion caused by other reasons, the non-3GPP GW deletes the MM context of the

UE, and sends the detach request message to the UE. If the non-3GPP GW knows that the terminal

capability of the UE is "dual radio capability", and the access policy information of the operator is

"multi radio access", the non-3GPP GW does not delete the MM context of the UE (that is, does not

10 detach the UE from the non-3GPP network).

[0181] FIG. 7 shows a second example of the method for user detachment when a


invention. The method includes the following steps.

[0182] Steps 701-707 are the same as steps 201-207 in FIG. 2.

15 [0183] In step 708a, the PDN GW determines whether to delete the default bearer of the UE; if

yes, the PDN GW sends the delete bearer request message corresponding to the default bearer to the

serving GW, and the serving GW sends the received delete bearer request message to the MME.

[0184] The default bearer is a part of the bearer resources.

[0185] In this step, the interface protocol between the PDN GW and the serving GW is the GTP.

20 If the interface protocol between the PDN GW and the serving GW is the PMIP, step 708a is

replaced by step 708b, in which the PDN GW sends the binding revocation indication message to

the serving GW, and the serving GW determines whether to delete the default bearer of the UE; if

yes, the serving GW sends the delete bearer request message corresponding to the default bearer to

the MME, and the MME deletes the MM context and the bearer resources.

25 [0186] In step 708a or 708b, the PDN GW/serving GW determines whether to delete the default

bearer of the UE in the following manners. The PDN GW/serving GW determines whether to delete

the default bearer of the UE according to the handover/change of the UE in the access network, or

according to the handover/change of the UE in the access network and the terminal capability of the

UE, or according to the handover/change of the UE in the access network and the access policy

30 information of the operator, or according to the handover/change of the UE in the access network,

the terminal capability of the UE, and the access policy information of the operator. The terminal

capability of the UE and the access policy information of the operator are obtained by the network

elements according to the flows shown in FIGs. 3 and 4. Specifically, the determination process

includes the following circumstances.

33

NSN677-1002,

DF078307331

[0187] 1) The PDN GW/serving GW determines whether to delete the default bearer of the UE

according to the handover/change of the UE in the access network, in which the PDN GW/serving

GW determines whether the UE is handed over or switched from the 3GPP network to the

non-3GPP network; if yes, the PDN GW/serving GW determines to delete the default bearer of the

5 UE, and sends the delete bearer request message corresponding to the default bearer to the MME.


according to the handover/change of the UE in the access network and the terminal capability of the

UE, in which the PDN GW/serving GW determines whether the UE is handed over or switched

from the 3GPP network to the non-3GPP network and whether the terminal capability of the UE is

10 "single radio capability"; if yes, the PDN GW/serving GW determines to delete the default bearer of

the UE, and sends the delete bearer request message corresponding to the default bearer to the

MME.


according to the handover/change of the UE in the access network and the access policy

15 information of the operator, in which the PDN GW/serving GW determines whether the UE is

handed over or switched from the 3GPP network to the non-3GPP network and whether the access

policy information of the operator is "single radio access"; if yes, the PDN GW/serving GW

determines to delete the default bearer of the UE, and sends the delete bearer request message

corresponding to the default bearer to the MME.

20 [0190] 4) The PDN GW/serving GW determines whether to delete the default bearer of the UE

according to the handover/change of the UE in the access network, the terminal capability of the UE,

and the access policy information of the operator, in which the PDN GW/serving GW determines

whether the handover/change of the UE in the access network, the terminal capability of the UE,

and the access policy information of the operator satisfy one of the following three conditions: 1.

25 the UE is handed over or switched from the 3GPP network to the non-3GPP network, the terminal


"single radio access"; 2. the UE is handed over or switched from the 3GPP network to the

non-3GPP network, the access policy information of the operator is "multi radio access", and the

terminal capability of the UE is "single radio capability"; and 3. the UE is handed over or switched

30 from the 3GPP network to the non-3GPP network, the terminal capability of the UE is "single radio

capability", and the access policy information of the operator is "single radio access".

[0191] If yes, the PDN GW/serving GW determines to delete the default bearer of the UE, and

sends the delete bearer request message corresponding to the default bearer to the MME.

[0192] In step 709a, the MME returns a delete bearer response message to the serving GW, and

34

NSN677-1002,

DF078307331

the serving GW returns the delete bearer response message to the PDN GW.

[0193] In this step, the interface protocol between the PDN GW and the serving GW is the GTP.

If the interface protocol between the PDN GW and the serving GW is the PMIP, step 709a is

replaced by step 709b, in which the MME returns the delete bearer response message to the serving

5 GW, and the serving GW returns the binding revocation Ack message to the PDN GW.

[0194] In step 710, if the MME finds that the default bearer of the UE is deleted, the MME

deletes the MM context of the UE (that is, the MME detaches the UE from the 3GPP network).

[0195] If the MME finds that the subscription data and the MM context of the UE are deleted,

the MME sends a purge UE message to the HSS/AAA server, and the HSS/AAA server purges the

10 record of the UE, and returns a purge UE Ack message to the MME.


MME according to the actual conditions. This step is optional.

[0197] Step 709 and step 710 may be performed at any order.

[0198] In the above embodiment, the UE is detached after step 707. The detachment process is

15 as follows: according to the handover/change of the UE in the access network, or according to the

handover/change of the UE in the access network and the terminal capability of the UE, or


information of the operator, or according to the handover/change of the UE in the access network,

the terminal capability of the UE, and the access policy information of the operator, the UE

20 determines whether to perform the detachment, which specifically includes the following four

circumstances.


the non-3GPP network; if yes, the UE also deletes the default bearer, and deletes the MM context

and bearer resources used by the UE in the 3GPP network (that is, the UE is detached from the

25 3GPP network); otherwise, the UE does not delete the default bearer, and does not delete the MM

context used by the UE in the 3GPP network.


the non-3GPP network and whether the terminal capability of the UE is "single radio capability"; if

yes, the UE also deletes the default bearer, and deletes the MM context and bearer resources used

30 by the UE in the 3GPP network (that is, the UE is detached from the 3GPP network); otherwise, the

UE does not delete the default bearer, and does not delete the MM context used by the UE in the

3GPP network.


the non-3GPP network and whether the access policy information of the operator is "single radio

35

NSN677-1002,

DF078307331

access" ; if yes, the UE also deletes the default bearer, and deletes the MM context and bearer

resources used by the UE in the 3GPP network (that is, the UE is detached from the 3GPP network);

otherwise, the UE does not delete the default bearer, and does not delete the MM context used by

the UE in the 3GPP network.

5 [0202] 4) It is determined whether the handover/change of the UE in the access network, the

terminal capability of the UE, and the access policy information of the operator satisfy one of the




10 from the 3GPP network to the non-3GPP network, the access policy information of the operator is

"multi radio access", and the terminal capability of the UE is "single radio capability"; and 3. the

UE is handed over or switched from the 3GPP network to the non-3GPP network, the terminal

capability of the UE is "single radio capability", and the access policy information of the operator is


15 [0203] If yes, the UE deletes the default bearer, and deletes the MM context and bearer

resources used by the UE in the 3GPP network (that is, the UE is detached from the 3GPP network);

otherwise, the UE does not delete the default bearer, and does not delete the MM context used by

the UE in the 3GPP network.

[0204] FIG. 8 shows a third example of the method for user detachment when a

20 handover/change occurs in a heterogeneous network according to an embodiment of the present



[0206] In step 808a, the PDN GW sends a detach request message to the MME through the

serving GW, and the detach request message carries a cause value represented as "detach because of

25 UE's accessing RAT changed from a 3GPP network to a non-3GPP network", which indicates that

the detach request message is caused by the handover or switching of the UE from the 3GPP

network to the non-3GPP network.

[0207] In this step, no interface exists between the PDN GW and the MME. If an interface

exists between the PDN GW and the MME, step 808a is replaced by step 808b, in which the PDN

30 GW sends a Detach Request message to the MME, and the Detach Request message carries a Cause

value represented as "Detach because of UE's accessing RAT changed from a 3GPP network to a

non-3GPP network", indicating that the detach request message is caused by the handover/change

of the UE from the 3GPP network to the non-3GPP network.

[0208] If the interface protocol between the PDN GW and the MME is the PMIP, step 808a is

36

NSN677-1002,

DF078307331

replaced by step 808c, in which the PDN GW sends a binding revocation Ind message to the serving

GW, and the serving GW sends the detach request message to the MME, and the detach request

message carries a cause value represented as "detach because of UE's accessing RAT changed from

a 3GPP network to a non-3GPP network", indicating that the detach request message is caused by

5 the handover/change of the UE from the 3GPP network to the non-3GPP network.

[0209] In step 808a, 808b, or 808c, before the detach request message is sent, the process

further includes determining whether to send the detach request message according to the

handover/change of the UE in the access network, or according to the handover/change of the UE in

the access network and the terminal capability of the UE, or according to the handover/change of

10 the UE in the access network and the access policy information of the operator, or according to the

handover/change of the UE in the access network, the terminal capability of the UE, and the access

policy information of the operator; if yes, the detach request message is sent to the MME; otherwise,

the process ends. In steps 808a and 808b, the determination is performed by the PDN GW, and in

step 808c, the determination is performed by the serving GW. Whether to send the detach request

15 message may be determined according to the following circumstances.

[0210] 1) The PDN GW/serving GW determines whether to send the detach request message to

the MME according to the handover/change of the UE in the access network, in which the PDN

GW/serving GW determines whether the UE is handed over from the 3GPP network to the

non-3GPP network; if yes, the detach request message is sent to the MME; otherwise, the process

20 ends.


the MME according to the handover/change of the UE in the access network and the terminal

capability of the UE, in which the PDN GW/serving GW determines whether the UE is handed over

or switched from the 3GPP network to the non-3GPP network and whether the terminal capability

25 of the UE is "single radio capability"; if yes, the detach request message is sent to the MME;

otherwise, the process ends.


the MME according to the handover/change of the UE in the access network and the access policy

information of the operator, in which the PDN GW/serving GW determines whether the UE is

30 handed over or switched from the 3GPP network to the non-3GPP network and whether the access

policy information of the operator is "single radio access"; if yes, the detach request message is sent

to the MME; otherwise, the process ends.


the MME according to the handover/change of the UE in the access network, the terminal capability

37

NSN677-1002,

DF078307331

of the UE, and the access policy information of the operator, in which the PDN GW/serving GW

determines whether the handover/change of the UE in the access network, the terminal capability of

the UE, and the access policy information of the operator satisfy one of the following three

conditions: 1. the UE is handed over or switched from the 3GPP network to the non-3GPP network,

5 the terminal capability of the UE is "dual radio capability", and the access policy information of the

operator is "single radio access"; 2. the UE is handed over or switched from the 3GPP network to

the non-3GPP network, the access policy information of the operator is "multi radio access", and the

terminal capability of the UE is "single radio capability"; and 3. the UE is handed over or switched

from the 3GPP network to the non-3GPP network, the terminal capability of the UE is "single radio

10 capability", and the access policy information of the operator is "single radio access".

[0214] If yes, the detach request message is sent to the MME; otherwise, the process ends.

[0215] In step 809a, the MME receives the detach request message, deletes the MM context,

and sends a detach response message to the PDN GW through the serving GW.


15 exists between the PDN GW and the MME, step 809a is replaced by step 809b, in which the MME

receives the detach request message, deletes the MM context, and directly sends a detach response



replaced by step 809c, in which the PDN GW sends the detach response message to the serving GW,

20 and the serving GW returns a binding revocation Ack message to the PDN GW.

[0218] In step 810, the MME initiates a bearer deletion process to delete the bearer resources

used by the UE on the 3GPP network side (including the MME, serving GW, and PDN GW).


are deleted, the MME sends a purge UE message to the HSS/AAA server, and then the HSS/AAA

25 server purges the record of the UE, and returns a purge UE Ack message to the MME.



[0221] Step 809 and Step 811 may be performed at any order.

[0222] In this embodiment, the UE is detached after step 807, and the detailed process thereof

30 can be known with reference to the descriptions of the third example of the method for user

detachment.

[0223] In this embodiment, it should be noted that, the detach request message sent by the PDN

GW or serving GW may not carry the cause value.

[0224] In this embodiment, it should be noted that, the method in this embodiment is also

38

NSN677-1002,

DF078307331

applicable to the handover or switching of the UE from the non-3GPP network to the 3GPP

network.

[0225] After the UE is handed over or switched from the non-3GPP network to the 3GPP

network, the PDN GW determines whether to detach the UE from the non-3GPP network and

5 whether to send the detach request message to the non-3GPP GW, which includes determining

whether to send the detach request message according to the handover/change of the UE in the

access network, or according to the handover/change of the UE in the access network and the

terminal capability of the UE, or according to the handover/change of the UE in the access network

and the access policy information of the operator, or according to the handover/change of the UE in

10 the access network, the terminal capability of the UE, and the access policy information of the

operator; if yes, the detach request message is sent to the non-3GPP GW. The detailed process

thereof can be known with reference to the descriptions of the above embodiment.

[0226] FIG. 9 shows a fourth example of the method for user detachment when a


15 invention. The method includes the following steps.


[0228] In step 908, the PDN GW sends a register request message to the HSS/AAA server, and

the message carries an RAT type of the UE.

[0229] The value of the RAT Type may be one of the following two circumstances.

20 [0230] The RAT Type may be a 3GPP network, which indicates that the network that the UE

accesses currently is a 3GPP network; and the RAT Type may be a non-3GPP network, which

indicates that the network that the UE accesses currently is a non-3GPP network.

[0231] The RAT Type of the UE may also be a specific network type, for example, GERAN,

UTRAN, or EUTRAN network in the 3GPP networks, or WLAN, Wimax, and CDMA network in

25 the non-3GPP networks.


[0233] In step 909, the HSS/AAA server returns a register response message to the PDN GW.

[0234] In step 910, when the HSS/AAA server determines that the RAT Type of the UE

registered last time is inconsistent with that of the UE registered this time, the HSS/AAA server

30 sends a cancel location message to the MME, in which the cancel location message carries a cause

value represented as "Cancel because of UE's accessing RAT changed from a 3GPP network to a

non-3GPP network", indicating that the cancel location is caused by the handover or switching of

the UE from the 3GPP network to the non-3GPP network.

[0235] In this step, before the cancel location message is sent to the MME, the process further

39

NSN677-1002,

DF078307331

includes that the HSS/AAA server determines whether to send the cancel location message

according to the handover/change of the UE in the access network, or according to the

handover/change of the UE in the access network and the terminal capability of the UE, or


5 information of the operator, or according to the handover/change of the UE in the access network,

the terminal capability of the UE, and the access policy information of the operator; if yes, the

HSS/AAA server sends the cancel location message to the MME; otherwise, the HSS/AAA server

does not send the cancel location message to the MME, and the process ends. Specifically, the

determination process specifically includes the following circumstances.

10 [0236] 1) The HSS/AAA server determines whether to send the cancel location message to the

MME according to the handover/change of the UE in the access network, in which the HSS/AAA

server determines whether the UE is handed over or switched from the 3GPP network to the

non-3GPP network; if yes, the HSS/AAA server sends the cancel location message to the MME;

otherwise, the HSS/AAA server does not send the cancel location message to the MME, and the

15 process ends.

[0237] 2) The HSS/AAA server determines whether to send the cancel location message to the

MME according to the handover or switching of the UE in the access network and the terminal

capability of the UE, in which if the HSS/AAA server determines that the UE is handed over or

switched from the 3GPP network to the non-3GPP network, and the terminal capability of the UE is

20 "single radio capability", the HSS/AAA server sends the cancel location message to the MME; if

the HSS/AAA server determines that the terminal capability of the UE is "multi radio capability",

the HSS/AAA server does not send the cancel location message to the MME.


MME according to the handover/change of the UE in the access network and the access policy

25 information of the operator, in which if the HSS/AAA server determines that the UE is handed over

or switched from the 3GPP network to the non-3GPP network, and the access policy information of

the operator is "single radio access", the HSS/AAA server sends the cancel location message to the

MME; if the HSS/AAA server determines that the UE is handed over or switched from the 3GPP

network to the non-3GPP network, and the access policy information of the operator is "multi radio

30 access", the HSS/AAA server does not send the cancel location message to the MME.


MME according to the handover or switching of the UE in the access network, the terminal

capability of the UE, and the access policy information of the operator, in which if the HSS/AAA

server determines that the UE is handed over or switched from the 3GPP network to the non-3GPP

40

NSN677-1002,

DF078307331

network, the terminal capability of the UE is "dual radio capability", and the access policy

information of the operator is "single radio access", or if the HSS/AAA server determines that the

UE is handed over or switched from the 3GPP network to the non-3GPP network, the access policy

information of the operator is "multi radio access", and the terminal capability of the UE is "single

5 radio capability", or if the HSS/AAA server determines that the UE is handed over or switched from

the 3GPP network to the non-3GPP network, the terminal capability of the UE is "single radio

capability", and the access policy information of the operator is "single radio access", the HSS/AAA

server sends the cancel location message to the MME; if the HSS/AAA server determines that the

terminal capability of the UE is "dual radio capability" and the access policy information of the

10 operator is "multi radio access", the HSS/AAA server does not send the cancel location message to

the MME.

[0240] In step 911, after receiving the cancel location message, the MME deletes the MM

context of the UE, and returns a cancel location Ack message to the HSS/AAA server.


15 are deleted, the MME sends a purge UE message to the HSS/AAA server, and then the HSS/AAA

server purges the record of the UE, and returns a purge UE Ack message to the MME.




20 used by the UE on the 3GPP network side (including the MME, serving GW, and PDN GW).


can be known with reference to the descriptions of the third example of the method for user

detachment.


25 configured in different entities or in a same entity. When the HSS and the AAA server are

configured in different entities, the register request message sent by the PDN GW in step 908 is

forwarded to the HSS through the AAA server, the register response message sent by the HSS in

step 909 is forwarded to the PDN GW through the AAA server, the cancel location message sent to

the MME in step 910 is sent to the MME by the HSS, and the purge UE message sent by the MME

30 in step 912 is sent to the HSS. The cancel location message sent by the HSS/AAA server may not

carry the cause value.


applicable to the handover or switching of the UE from a non-3GPP network to a 3GPP network.

[0247] In Step I, after the UE is handed over or switched from the non-3GPP network to the

41

NSN677-1002,

DF078307331

3GPP network, the MME or the PDN GW registers a new RAT Type of the UE with the HSS/AAA

server.

[0248] In Step 11, if the HSS/AAA server determines that the RAT type of the UE registered last

time is inconsistent with that of the UE registered this time, the HSS/AAA server determines

5 whether to send the cancel location message to a non-3GPP GW (to notify the non-3GPP GW to

detach the UE from the non-3GPP network) according to the handover/change of the UE in the

access network, or according to the handover/change of the UE in the access network and the



10 the access network, the terminal capability of the UE, and the access policy information of the

operator. If yes, the HSS/AAA server sends the cancel location message to the non-3GPP GW. The

detailed process thereof can be known with reference to the descriptions of the above embodiment.

[0249] FIG. 10 shows a fifth example of the method for user detachment when a



[0250] In step 1001, the UE accesses a 3GPP access network through the serving GW and the

PDN GW.

[0251] In step 1002, the UE triggers a handover or switching from the 3GPP network to the

non-3GPP network.

20 [0252] In step 1003, the MME sends a handover or switching request (HO Request) message to

a non-3GPP GW.

[0253] In this step, as for a WLAN system, the non-3GPP GW is an EPDG; as for a Wimax

system, the non-3GPP GW is an ASN GW; and as for a CDMA system, the non-3GPP GW is an

AGW.

25 [0254] In Step 1004, the non-3GPP GW performs a resource create procedure.

[0255] In this step, the resource create procedure includes performing the processes of user

authentication and PMIP tunnel binding.

[0256] In step 1005, the non-3GPP GW returns an HO response message to the MME.

[0257] In step 1006, the MME sends an HO command message to the UE, and commands the

30 UE to hand over or switch to an access network of the non-3GPP network.

[0258] In step 1007, the UE sends an access request message to the non-3GPP GW, and is

handed over or switched to the non-3GPP network.

[0259] In step 1008, the non-3GPP GW returns an access accept message to the UE.

[0260] Steps 1001-1008 and the process of the handover or switching of the UE from a 3GPP

42

NSN677-1002,

DF078307331

network to a non-3GPP network in the prior art implement functions similar to that of steps 201-207

in FIG. 2.

[0261] In step 1009, the non-3GPP GW returns an HO complete message to the MME.

[0262] In step 1010, the MME returns an HO complete Ack message to the non-3GPP GW.

5 [0263] Step 1010 further includes: determining, by the MME, whether to delete the MM context

of the UE (that is, to detach the UE from the 3GPP network) according to the handover/change of

the UE in the access network, or according to the handover/change of the UE in the access network

and the terminal capability of the UE, or according to the handover/change of the UE in the access

network and the access policy information of the operator, or according to the handover/change of

10 the UE in the access network, the terminal capability of the UE, and the access policy information

of the operator; if yes, the MME deletes the MM context of the UE; otherwise, the process ends.

Specifically, the determination process includes the following four circumstances.

[0264] 1) The MME determines whether to delete the MM context of the UE according to the

handover/change of the UE in the access network, in which if the MME determines that the UE is

15 handed over or switched from the 3GPP network to the non-3GPP network, the MME deletes the

MM context of the UE; otherwise, the MME does not delete the MM context of the UE.


handover/change of the UE in the access network and the terminal capability of the UE, in which if

the MME determines that the UE is handed over or switched from the 3GPP network to the

20 non-3GPP network, and the terminal capability of the UE is "single radio capability", the MME

deletes the MM context of the UE; if the MME determines that the terminal capability of the UE is

"multi radio capability", the MME does not delete the MM context of the UE.


handover/change of the UE in the access network and the access policy information of the operator,

25 in which if the MME determines that the UE is handed over or switched from the 3GPP network to

the non-3GPP network, and the access policy information of the operator is "single radio access",

the MME deletes the MM context of the UE; if the MME determines that the access policy

information of the operator is "multi radio access", the MME does not delete the MM context.


30 handover/change of the UE in the access network, the terminal capability of the UE, and the access

policy information of the operator, in which if the MME determines that the UE is handed over or

switched from the 3GPP network to the non-3GPP network, the terminal capability of the UE is

"dual radio capability", and the access policy information of the operator is "single radio access", or

if the MME determines that the UE is handed over or switched from the 3GPP network to the

43

NSN677-1002,

DF078307331


terminal capability of the UE is "single radio capability", or if the MME determines that the UE is

handed over or switched from the 3GPP network to the non-3GPP network, the terminal capability

of the UE is "single radio capability", and the access policy information of the operator is "single

5 radio access", the MME deletes the MM context of the UE; if the MME determines that the

terminal capability of the UE is "dual radio capability", and the access policy information of the

operator is "multi radio access", the MME does not delete the MM context of the UE.



10 server purges the record of the UE, and returns a purge UE Ack message to the MME.





15 [0271] In this embodiment, the UE is detached after Step 1007, and the detailed process thereof


detachment.



20 network.

[0273] In Step I, after the UE is handed over or switched from the non-3GPP network to

network, the MME returns an HO complete message to the non-3GPP GW.

[0274] In step II, the non-3GPP GW determines whether to delete the MM context of the UE

(that is, to detach the UE from the non-3GPP network) according to the handover/change of the UE

25 in the access network, or according to the handover/change of the UE in the access network and the



the access network, the terminal capability of the UE, and the access policy information of the

operator; if yes, the non-3GPP GW deletes the MM context of the UE. The detailed process thereof

30 can be known with reference to the descriptions of the above embodiment.

[0275] FIG. 11 shows a sixth example of the method for user detachment when a




44

NSN677-1002,

DF078307331

[0277] In step 1103, the UE sends a detach request message to the MME, and the detach request

message carries a cause value represented as "detach because of UE's accessing RAT changed from

a 3GPP network to a non-3GPP network", indicating that the detach request message is caused by

the handover/change of the UE from the 3GPP network to the non-3GPP network.

5 [0278] In this step, before the UE sends the detach request message to MME, the process

further includes determining whether to detach the UE from the 3GPP network according to the

handover of the UE in the access network, or according to the handover of the UE in the access

network and the terminal capability of the UE, or according to the handover of the UE in the access

network and the access policy information of the operator, or according to the handover of the UE

10 in the access network, the terminal capability of the UE, and the access policy information of the

operator. If yes, the UE sends the detach request message to the MME; otherwise, step 1107 is

performed. The terminal capability of the UE and the access policy information of the operator are

obtained by the network elements according to the processes of FIGs. 3 and 4. Specifically, the

determination process includes the following circumstances.

15 [0279] 1) The UE determines whether to detach the UE from the 3GPP network and whether to

send the detach request message to the MME according to the handover/change of the UE in the

access network, in which the UE determines whether the UE is handed over or switched from the

3GPP network to the non-3GPP network; if yes, the MM context and bearer resources of the 3GPP

network in the UE are deleted, and the detach request message is sent to the MME; otherwise, step

20 1107 is performed.

[0280] 2) The UE determines whether to detach the UE from the 3GPP network and whether to


access network and the terminal capability of the UE, in which if the UE determines that the UE is

handed over or switched from the 3GPP network to the non-3GPP network, and the telininal

25 capability of the UE is "single radio capability", the MM context and the bearer resources of the

3GPP network in the UE are deleted, and the detach request message is sent to the MME; if the UE

determines that the terminal capability of the UE is "multi radio capability", the MM context of the

3GPP network in the UE is not deleted (that is, the UE is not detached from the 3GPP network), the

detach request message is not sent to the MME, and step 1107 is performed.

30 [0281] 3) The UE determines whether to detach the UE from the 3GPP network and whether to


access network and the access policy information of the operator, in which if the UE determines that

the UE is handed over or switched from the 3GPP network to the non-3GPP network, and the access

policy information of the operator is "single radio access", the MM context and the bearer resources

45

NSN677-1002,

DF078307331

of the 3GPP network in the UE are deleted, and the detach request message is sent to the MME; if

the UE determines that the access policy information of the operator is "multi radio access", the

MM context of network in the UE is not deleted (that is, the UE is not detached from the 3GPP

network), the detach request message is not sent to the MME, and step 1107 is performed.

5 [0282] 4) The UE determines whether to detach the UE from the 3GPP network according to

the handover/change of the UE in the access network, the terminal capability of the UE, and the

access policy information of the operator, in which if the UE determines that the UE is handed over

or switched from the 3GPP network to the non-3GPP network, the terminal capability of the UE is

"dual radio capability", and the access policy information of the operator is "single radio access", or

10 if the UE determines that the UE is handed over or switched from the 3GPP network to the


terminal capability of the UE is "single radio capability", or if the UE determines that the UE is

handed over or switched from the 3GPP network to the non-3GPP network, the terminal capability


15 radio access", the MM context and the bearer resources of the 3GPP network in the UE are deleted,

and the detach request message is sent to the MME. If the UE determines that the terminal


"multi radio access", the MM context of the 3GPP network in the UE is not deleted (that is, the UE

is not detached from the 3GPP network), the detach request message is not sent to the MME, and

20 step 1107 is performed.

[0283] In step 1104, after the MME receives the detach request message, the MME deletes the

MM context of the UE in the MME, initiates a bearer deletion process, and deletes the bearer

resources used by the UE on the 3GPP network side.

[0284] In this step, the bearer resources used by the UE on the 3GPP network side include the

25 bearer resources used by the UE in the MME, serving GW, and PDN GW.





30 MME according to the actual conditions. This step is optional.

[0287] In step 1106, the MME sends a Detach Accept message to the UE.




46

NSN677-1002,

DF078307331


network.

[0291] When the UE is handed over from the non-3GPP network to the 3GPP network, the UE

determines whether to detach the UE from the non-3GPP network according to the handover of the

5 UE in the access network, or according to the handover of the UE in the access network and the

terminal capability of the UE, or according to the handover of the UE in the access network and the

access policy information of the operator, or according to the handover of the UE in the access

network, the terminal capability of the UE, and the access policy infatmation of the operator. If yes,

the UE sends the detach request message to the non-3GPP GW. The detailed process thereof can be

10 known with reference to the description of the above embodiment.

[0292] It should be noted that, in this embodiment, the serving GW and the PDN GW may be

configured in different entities or in the same entity. When the serving GW and the PDN GW are

configured in the same entity, the messages between the serving GW and the PDN GW are

transmitted in the same entity. The HSS and the AAA server may be configured in different entities

15 or in the same entity. If the HSS and the AAA server are configured in different entities, the MME

sends the purge UE message to the HSS.

[0293] In the embodiments of the present invention, if the user detachment is caused by the

handover/change of the UE from the 3GPP network to the non-3GPP network, after the user

detachment, the process may further include: setting, by the MME of the 3GPP, the state of the UE

20 to an invalid state. Specifically, the process of setting, by the MME of the 3GPP, the state of the UE

to an invalid state is implemented as follows.

[0294] The MME deletes the subscription date information and the MM context of the UE.

[0295] Alternatively, the MME retains the subscription data information of the UE, but sets the

state of the MME used by the UE to an invalid state.

25 [0296] Alternatively, the state of the MME used by the UE is set to an invalid value.

[0297] Alternatively, the MME retains the subscription data information of the UE, but sets a

change flag location of the MME used by the UE to a changed state.


handover or switching of the UE from the non-3GPP network to the 3GPP network, after the user

30 detachment, the process may further include: setting, by the non-3GPP GW of the non-3GPP, the

state of the UE to an invalid state. Specifically, the process of setting, by the non-3GPP GW of the

non-3GPP, the state of the UE to an invalid state is implemented as follows.

[0299] The non-3GPP GW deletes the subscription data information and the MM context of the

UE.

47

NSN677-1002,

DF078307331

[0300] Alternatively, the non-3GPP GW retains the subscription data information of the user,

but sets the state of the non-3GPP GW used by the UE to an invalid state.

[0301] Alternatively, the address of the non-3GPP GW used by the UE is set to an invalid value.

[0302] Alternatively, a non-3GPP GW retains the subscription data information of the user, but

5 sets a change flag position of the non-3GPP GW used by the UE to a changed state.

[0303] FIG. 12 shows a system for user detachment when a handover/change occurs in a

heterogeneous network according to an embodiment of the present invention. The system includes a

UE and a network side.

[0304] The UE is adapted to be handed over or switched from a source network on the network

10 side to a target network.


the target network to detach the UE from the source network.

[0306] The UE may include a first handover/change module, and the network side may include

a second handover/change module and a second detachment module.

15 [0307] The first handover/change module is adapted to enable the UE to be handed over or

switched from the source network to the target network.

[0308] The second handover/change module is adapted to enable the network side to hand over

or switch the UE from the source network to the target network.

[0309] The second detachment module is adapted to enable the network side to detach the UE

20 from the source network.

[0310] Optionally, the UE includes a first detachment module adapted to detach the UE from

the source network.

[0311] Optionally, the UE includes a first detachment determination module and a second

detachment determination module disposed on the network side.

25 [0312] The first detachment determination module is adapted to determine whether to detach

the UE from the source network, and if yes, an enable instruction is sent to the first detachment

module to enable the first detachment module.

[0313] The second detachment determination module is adapted to determine whether to detach

the UE from the source network, and if yes, an enable instruction is sent to the second detachment

30 module to enable the second detachment module. The second detachment determination module

may be disposed in a network element on a network side, such as an MME, a PDN GW, a serving

GW, or an HSS/AAA server.

[0314] The UE further includes a module for sending terminal capability of a UE and a module

for receiving access policy information of an operator, and the network side further includes a

48

NSN677-1002,

DF078307331

module for receiving the terminal capability of the UE and a module for sending the access policy

information of the operator.

[0315] The module for sending the terminal capability of the UE is adapted to send the terminal

capability of the UE to the network side, and the module for receiving the access policy information

5 of the operator is adapted to receive the access policy information of the operator sent by the

network side.

[0316] The module for receiving the terminal capability of the UE is adapted to receive the

terminal capability of the UE sent by the UE, and the module for sending the access policy

information of the operator is adapted to send the access policy information of the operator to the

10 UE.

[0317] Based on the solutions for user detachment when a handover/change occurs in a

heterogeneous network according to the embodiments of the present invention, when the UE is

handed over or switched from the source network on the network side to the target network on the

network side, the source network can detach the UE from the source network, and the UE can

15 detach the UE from the source network.

[0318] It will be apparent to those skilled in the art that various modifications and variations can

be made to the present invention without departing from the scope of the invention. In view of the

foregoing, it is intended that the present invention cover modifications and variations of this

invention provided that they fall within the scope of the following claims and their equivalents.

49

NSN677-1002,

(GERAN)\ \N/

(JTRAN SGSN

MME

HSS

PCRF

(E-UTRAN) Serving Gateway

PDN Gateway

AAA Server UE

DF078307331

Drawings

1/10

Non-3GPP IPA Access

FIG. 1

UE MME Non-3GPP GW

Serving GW

PDN GW

HSS/AAA Server

I I 201. Access a 3GPP network

1.-41

he handover switching.

UE triggers or

203. Access request o.




206a. Proxy Proxy binding Ack

206b. Binding Ack

207. Access accept

208. Delete bearer request

209. Delete bearer 1.1

response

FIG. 2

50

NSN677-1002,

PCRF HS S/AAA Server UE MME Serving

GW Network element on an access side

PDN GW

301. Attach request

302. Authentication process of the UE

303. Update location request

304. Insert subscription data

305. Update location Ack

306. Create bearer request

307. PCC rules request

308. PCC rules provision

309. Create bearer response

310a. Register

311. Attach accept 1

312. Radio bearer establishment request

313. Radio bearer establishment response

310b. Register 4 -0-

DF078307331

2/10

FIG. 3

5 1

NSN677-1002,

PDN GW

UE PDN GW

PCRF HSS/AAA

Server Non-3GPP

GW

DF078307331

3/10

UE

401. TAU/RAU request .

Serving GW

402. Update location request I I

403. Insert subscription data

404. Update location Ack

HS S/AAA Server

405. Update bearer request 00-

406a. Register

406b. Register

407. TAU/RAU accept

FIG. 4

NSN677-1002,

DF078307331

4/10

UE MME Non-3 GPP GW

Serving GW

PDN GW

HSS/AAA Server

602

601. Access a 3GPP network 0-41


603. Access request



605b. Binding Binding update


606b. Binding Ack

607. Access accept




Ind


609b. Binding 509b. Delete bearer revocation

response Ack

610. Detach request 4 - - -

610. Detach accept 611. Purge UE

611. Purge UE Ack 4- if

FIG. 6

53

NSN677-1002,

DF078307331

703. Acces s request

5/10

702

FIG. 7

Non-3 GPP GW

Serving GW

PDN GW

HSS/AAA Server UE MME



704. Acce



..4706a. Proxy binding Ack

706b. Binding Ack

707. Access accept


ss authentic ation process

1


708b. Binding revocation Ind update

4


709b. Delete bearer response


Ack

710. Purge UE

710. Purge UE Ack

54

NSN677-1002,

DF078307331

6/10

UE MME Nod] 3GPP

GW Serving

GW PDN GW

HS S/AAA Server

802


The UE triggers

handover or switching.

803. Access request

804. Access authentication process 1041

805a. Proxy binding update 805b. Binding update


806b. Binding Ack 807. Access accept

808a.Detach request 1-4

808b.Detach request

808c. Binding 808c.Detach request revocation Ind

809a. Detach response

809b. Detach response

809c. Detach response 809c. Binding

revocation Ack

810. Delete bearer response

811. Purge UE

811. Purge UE Ack

FIG. 8

55

NSN677-1002,

DF078307331

7/10

902

FIG. 9

MME NonU 3GPP

GW Serving

GW PDN GW

HSS/AAA Server UE

901. Access a 3GPP network ►~ The UE triggers

handover or switching.

903. Access request

904. Access authentication process ►H



906a. Proxy binding Ack •

906b. Binding Ack

907. Access accept 908. Register

request

909. Register response

910. Cancel location

911. Cancel location Ack

912. Purge UE

912. Purge UE Ack

913. Bearer deletion process

56

NSN677-1002,

DF078307331

8/10

UE MME Non 3GPP

GW Serving

GW PDN GW

HSS/AAA Server

1001. Access a 3GPP network OP .411

1002 The UE triggers handover. 1003. HO

request

1004.Resource create procedure

1006. HO command

1005. HO response

-41

1007. Access request

1008. Access accept

1009. HO complete

-41

1010. HO complete Acl(v

1011. Purge UE b

1011. Purge UE Ack


FIG 10

57

NSN677-1002,

DF078307331

9/10

UE MME Non 3 GPP

GW Serving

GW PDN GW

HSS/AAA Server

1102



1 103. Detach request


1105. Purge UE b

1105. Purge UE Ack

1106. Detach accept -41

1107. Access request

1108. Access authentication




1110b. Binding Ack

1111. Access accept

FIG 11

58

NSN677-1002,

First detachment determination module

First handover/change module

First detachment module

Module for sending terminal capability of a

UE

Module for receiving access policy information

of an operator

Module for receiving the terminal capability of the

UE

Second detachment determination module

Second handover/change module

Second detachment module

Module for sending the access policy information

of the operator

Network side UE

DF078307331

10/10

FIG. 12

59

NSN677-1002,

VERIFICATION OF TRANSLATION

Jinzhe, MENG hereby solemnly affirm that I have a fluent knowledge of English and

Chinese languages and that the attached document is the true and accurate translation of

the PCT application number PCT/CN2008/071842.

Dated this day of jam., 00 1j

Signature of Translator: Jinzhe, MENG

H \/c Jtozke

NSN677-1002,


HANDOVER OR CHANGE OCCURS IN HETEROGENEOUS NETWORK


[0001] The present invention relates to the network communication technology and more

5 particularly to a method, system, and device for user detachment when a handover or

change occurs in a heterogeneous network.

BACKGROUND

[0002] To improve the competitiveness of networks in the future, a new evolution

network is now researched for a 3rd-generation partnership project (3GPP) network. FIG. 1

10 is a schematic structural view of an evolution network system for a 3GPP network. The

system includes: an evolved UMTS terrestrial radio access network (E-UTRAN), for

implementing all functions related to the wireless feature of the evolution network; a

mobility management entity (MME), for mobility management of a control plane, including

management of a user context and a mobility state and allocation of temporary user

15 identities; a serving gateway (serving GW) entity, for acting as a user plane anchor point

between access networks of the 3GPP network for terminating the E-UTRAN; a packet data

network gateway (PDN GW) entity, for acting as a user anchor point between an access

network of the 3GPP network and an access network of a non-3GPP network, and an

interface for terminating the external PDN; a policy and charging rule function (PCRF)

20 entity, for implementing functions of policy control decision and flow-based charging

control; and a home subscriber server (HSS), for storing subscription information of users.

[0003] The UMTS terrestrial radio access network (UTRAN) or GSM/EDGE radio

access network (GERAN) implements all functions relevant to the wireless feature of the

existing UMTS/GPRS network; a serving GPRS supporting node (SGSN) implements

25 functions of route forwarding, mobility management, session management, and user

information storage in the GPRS/UMTS network.

NSN677-1002,

2

[0004] IP access networks of the non-3GPP network mainly include access networks

defined by non-3GPP network organizations, for example, wireless local area network

(WLAN), worldwide interoperability for microwave access (Wimax), and code division

multiple access (CDMA) network.

5 [0005] An authentication, authorization, and accounting server (AAA server) mainly


[0006] It should be noted that, the schematic structural view of FIG. 1 is not the only

schematic structural view of the evolution network system for a 3GPP network. The

evolution network of a 3GPP network may have various structures.

10 [0007] One requirement on the evolution network of a 3GPP network is to realize the

handover or switching of the UE between a 3GPP network and a non-3GPP network. FIG. 2

is a flow chart of a process that the UE is handed over or switched from a 3GPP network to

a non-3GPP network in the prior art. The process includes the following steps.

[0008] In Step 201, the UE accesses the 3GPP network through a serving GW and a

15 PDN GW.


belong to the 3GPP network, a non-3GPP GW belongs to the non-3GPP network, and the

PDN GW and HS S/AAA server are common network elements shared by the 3GPP

network and the non-3GPP network.

20 [0010] In Step 202, the UE triggers the handover or switching from the 3GPP network to

the non-3GPP network.




NSN677-1002,

3

gateway (EPDG); as for a Wimax system, the non-3GPP GW in this step is an access

service network gateway (ASN GW); and as for a CDMA system, the non-3GPP GW is an

access gateway (AGW).


5 non-3GPP GW, and the HSS/AAA server, and the non-3GPP GW obtains the PDN GW

address information used by the UE.

[0014] In Step 205a, the non-3GPP GW sends a proxy binding update message to the

PDN GW.

[0015] In this step, it is assumed that an interface protocol between the non-3GPP GW

10 and the PDN GW is the proxy mobile internet protocol (PMIP). If an interface protocol

between the UE and the PDN GW is the client mobile internet protocol (CMIP), Step 205a

is replaced by Step 205b, in which the UE sends a binding update message to the PDN GW.

[0016] In Step 206a, the PDN GW sends a proxy binding acknowledgement message to

the non-3GPP GW.

15 [0017] In this step, it is assumed that the interface protocol between the non-3GPP GW

and the PDN GW is the PMIP. If the interface protocol between the UE and the PDN GW is

the CMIP, Step 206a is replaced by Step 206b, in which the PDN GW sends a binding Ack

message to the UE.


20 [0019] In Step 208, the PDN GW sends a delete bearer request message to the serving

GW, and the serving GW sends the delete bearer request message to the MME.

[0020] In Step 209, the MME deletes bearer resources related to the UE, returns a delete

bearer response message to the serving GW, and the serving GW returns the delete bearer

response message to the PDN GW.

NSN677-1002,

4


switched from a 3GPP network to a non-3GPP network. Certainly, the handover or change

process is not limited to the above descriptions. A 3GPP network involved in the handover

or change may be GERAN, UTRAN, or EUTRAN. A non-3GPP network involved in the

5 handover or change may be WLAN, Wimax, or CDMA system.

[0022] Once the UE accesses a 3GPP network, the 3GPP network creates bearer

resources of the UE and a mobility management context of the UE. The mobility

management context of the UE exists in the MME. Furthermore, bearer resources of a

3GPP network and a mobility management context of a 3GPP network are also created in

10 the UE. Therefore, when the UE is handed over or switched from a 3GPP network to a

non-3GPP network, user detachment needs to be performed to save network resources. The

user detachment includes detachment of the 3GPP network and detachment of the UE. The

detachment of the 3GPP network indicates that the 3GPP network deletes the bearer

resources of the UE and the mobility management context of the UE, and the detachment of

15 the UE indicates that the UE deletes the bearer resources of the 3GPP network and the

mobility management context of the 3GPP network. Here, the mobility management

context of the UE exists in the MME.

[0023] However, in the process shown in FIG. 2, when the UE is handed over or

switched from a 3GPP network to a non-3GPP network, the 3GPP network merely deletes

20 the bearer resources of the UE, but does not delete the mobility management context of the

UE, and meanwhile, the UE does not delete the bearer resources and mobility management

context of the 3GPP network as well.

[0024] As known from the above that, the prior art neither provides a method for 3GPP

network detachment when the UE is handed over or switched from a 3GPP network to a

25 non-3GPP network, nor provides a specific method for user detachment of the UE when the

UE is handed over or switched from a 3GPP network to a non-3GPP network. That is to say,

no specific solution for user detachment when handover or change occurs in a

NSN677-1002,

5

heterogeneous network is provided in the prior art.

[0025] In addition, if the UE has a single radio capability, that is, the UE can access only

one network, after the UE is handed over or switched from a 3GPP network to a non-3GPP

network, user detachment needs to be performed, that is, the 3GPP network needs to detach

5 the UE, and the UE needs to be detached from the 3GPP network. The detaching, by the

3GPP network, the UE includes that the 3GPP network deletes the bearer resources of the

UE on the 3GPP network side, and the mobility management context of the UE in the

MME. The detaching, by the UE, from the 3GPP network includes that the UE deletes the

bearer resources and mobility management context created when the UE accesses the 3GPP

10 network.

[0026] If the UE has a dual radio capability, that is, the UE can access two networks at

the same time, after the UE is handed over or switched from a 3GPP network to a

non-3GPP network, it is judged whether the 3GPP network needs to detach the UE

according to, for example, information of operator policies. In other words, the prior art

15 does not provide a solution for determining whether to perform the user detachment when

the UE is handed over or switched from a 3GPP network to a non-3GPP network.

[0027] To sum up, during researches and applications, the inventor(s) of the present

invention finds that the prior art has at least the following problems: the prior art neither

provides a specific solution for user detachment when a handover or change occurs in a

20 heterogeneous network, nor provides a solution for judging whether to perform user

detachment when handover or change occurs in a heterogeneous network.

SUMMARY

[0028] An embodiment of the present invention provides a method for detaching a user

when a handover or change occurs in a heterogeneous network.

25 [0029] An embodiment of the present invention further provides another method for

detaching a user when a handover or change occurs in a heterogeneous network.

NSN677-1002,

6

[0030] An embodiment of the present invention provides a system for detaching a user


[0031] An embodiment of the present invention provides a device for detaching a user


5 [0032] An embodiment of the present invention further provides a device for detaching a

user when a handover or change occurs in a heterogeneous network.

[0033] A method for detaching a user when handover or change occurs in a

heterogeneous network includes the following steps.


10 [0035] Next, a network element on a network side determines whether to detach the UE

from the source network; if yes, the UE is detached from the source network.

[0036] Another method for user detachment when a handover or change occurs in a


[0037] First, a UE triggers handover or switching from a source network to a target

15 network.

[0038] Next, the UE determines whether to be detached from the source network; if yes,

the UE is detached from the source network.

[0039] A system for user detachment when a handover or change occurs in a

heterogeneous network includes a UE and a network side.

20 [0040] The UE is adapted to be handed over or switched from a source network on the

network side to a target network on the network side.

[0041] The network side is adapted to hand over or switch the UE from the source

network to the target network, and detach the UE from the source network.

NSN677-1002,

7

[0042] A device for detaching a user when a handover or change occurs in a

heterogeneous network includes a second handover or change module and a second

detachment module on a network side.

[0043] The second handover or switching module is adapted to hand over or switch a UE

5 from a source network on the network side to a target network on the network side.

[0044] The second detachment module is adapted to detach the UE from the source

network.

[0045] A device for detaching a user when a handover or change occurs in a

heterogeneous network includes a first handover or change module and a first detachment

10 module in a UE.

[0046] The first handover or change module is adapted to hand over or switch the UE

from a source network to a target network;

[0047] The first detachment module is adapted to detach the UE from the source

network.

15 [0048] As known from the above solutions that, in the embodiments of the present

invention, when a handover or change occurs in the heterogeneous network, the UE is

detached from the source network after being determined by the source network or the UE

is detached from the source network after being determined by the UE. Thus, detachment of

the user is realized by the source network or the UE, when the handover or change occurs in

20 the heterogeneous network.


[0049] FIG. 1 is a schematic structural view of an evolution network system for a 3GPP

network in the prior art;

[0050] FIG. 2 is a flow chart of a process that the UE is handed over or switched from a

NSN677-1002,

8

3GPP network to a non-3GPP network in the prior art;

[0051] FIG. 3 is a flow chart of a process that a network element in a 3GPP network

acquires terminal capability of UE and access policy information of an operator when the

UE accesses the 3GPP network according to an embodiment of the present invention;

5 [0052] FIG. 4 is a flow chart of a process that a network element in a 3GPP network

acquires terminal capability of UE and access policy information of an operator when a

location area or terminal capability of the UE changes according to an embodiment of the

present invention;

[0053] FIG. 5 is a flow chart of a process that a network element in a non-3GPP network

10 acquires terminal capability of UE and access policy information of an operator when the

UE accesses the non-3GPP network according to an embodiment of the present invention;

[0054] FIG. 6 shows a first example of a method for user detachment when a handover

or change occurs in a heterogeneous network according to an embodiment of the present

invention;

15 [0055] FIG. 7 shows a second example of the method for user detachment when a

handover or change occurs in a heterogeneous network according to an embodiment of the

present invention;

[0056] FIG. 8 shows a third example of the method for user detachment when a handover


20 invention;

[0057] FIG. 9 shows a fourth example of the method for user detachment when a


present invention;


25 handover or change occurs in a heterogeneous network according to an embodiment of the

NSN677-1002,

9

present invention;



present invention; and

5 [0060] FIG. 12 is a schematic structural view of a system for user detachment when a


present invention.



10 invention more comprehensible, the present invention is described in detail below with

reference to the accompanying drawings and embodiments.

[0062] FIGs. 6-10 respectively show the first to fifth examples of a method for user

detachment when a handover or change occurs in a heterogeneous network according to an

embodiment of the present invention. The main ideas of the examples are described as

15 follows:


source network determines whether to detach the UE from the source network; if yes, the

UE will be detached from the source network; otherwise, the UE will not be detached from

the source network.

20 [0064] FIG. 11 shows a sixth example of a method for user detachment when a handover


invention. The main idea of this example is described as follows.

[0065] The UE triggers a handover or switching from a source network to a target

network; the UE determines whether to be detached from the source network; if yes, the UE

25 will be detached from the source network; otherwise, the UE will not be detached from the

NSN677-1002,

10

source network.

[0066] The two networks involved in the handover or change in the heterogeneous

network according to the embodiments of the present invention may be one of the 3GPP

networks (such as a GERAN network, a UTRAN network, or an EUTRAN network) and

5 one of the non-3GPP networks (such as a WLAN network, Wimax network, or CDMA

network). Specifically, the embodiments include the handover or switching of the UE from

a 3GPP network to a non-3GPP network or the handover or switching of the UE from a

non-3GPP network to a 3GPP network. Here, the network where the UE originally exists

during the handover or change process is referred to as the source network, and the other

10 network involved in the handover or change process is referred as the target network.

[0067] Then, the handover or switching from a 3GPP network to a non-3GPP network is

taken as an example to illustrate the first embodiment to the sixth embodiment of the

method for UE detachment when a handover or change occurs in the heterogeneous

network of the present invention.

15 [0068] The UE and the network element in the 3GPP network acquire the terminal

capability of the UE, and the network element obtains access policy information of the

operator, which are provided for being used in the solution for UE detachment when the UE

is handed over or switched from the 3GPP network to the non-3GPP network according to

the embodiments of the present invention. Here, FIGs. 3 and 4 are used to illustrate the

20 process that the network element in a 3GPP network acquires the terminal capability of the

UE and the access policy information of the operator according to the embodiments of the

present invention. FIG. 3 is a flow chart of a process that a network element in a 3GPP

network acquires terminal capability of UE and access policy information of an operator

when the UE accesses the 3GPP network. FIG. 4 is a flow chart of a process that a network

25 element in a 3GPP network acquires terminal capability of UE and access policy

information of an operator when a location area or terminal capability of the UE changes

after the UE accesses the 3GPP network according to an embodiment of the present

NSN677-1002,

11

invention.

[0069] Referring to FIG. 3, the process that the network element in the 3GPP network

acquires the terminal capability of the UE and the access policy information of the operator

when the UE accesses the 3GPP network includes the following steps.

5 [0070] In step 301, the UE sends an attach request message carrying terminal capability

of the UE to the MME.

[0071] In this step, if the access network of the UE is GERAN/UTRAN, the SGSN

serves as the MME; if the access network of the UE is EUTRAN, the MME serves as the

MME.

10 [0072] In this step, the terminal capability of the UE is represented by information

element (IE) of the radio capability supported by the UE. The radio capability supported by

the UE is a single radio capability (which indicates that the UE can access only one network

at a certain time point) or a dual radio capability (which indicates that the UE can access

two or more networks at a certain time point). An exemplary structure of the IE carrying the

15 radio capability supported by the UE is listed as follows. The IE includes a radio capability

parameter supported by the UE. The parameter may be: 1) the UE has a single radio

capability; 2) the UE has a dual radio capability.



NSN677-1002,

12




[0073] In step 302, the UE, the MME, and the HSS/AAA server implement an

authentication process of the UE to authenticate the UE.

[0074] In step 303, if the MME finds that the UE is in an invalid state, the MME sends

5 an update location message to the HSS/AAA server, and registers the UE with the

HS S/AAA server. The update location message carries the terminal capability of the UE.


MME, the update location request may carry the access policy information of the operator.

The access policy information of the operator includes: 1) a single radio access, that is, the

10 UE can access only one access network at a certain time point; and 2) a dual radio access,

that is, the UE can access a plurality of access networks at a certain time point.

[0076] In step 304, the HSS/AAA server inserts subscription data of a user into the

MME.

[0077] In this step, if the access policy information of the operator is configured or

15 subscribed in the HSS/AAA server, the HSS/AAA server carries the access policy

information of the operator in the subscription data, and sends the subscription data to the

MME.

[0078] In step 305, the HSS/AAA server returns an update location Ack message to the

MME.

20 [0079] In Step 306, the MME sends a create bearer request message to the serving GW,

NSN677-1002,

13

and the serving GW sends the create bearer request message to the PDN GW.

[0080] In this step, the MME initiates a default bearer establishment process, so as to

create a default bearer of the UE in the MME, serving GW, and PDN GW. The create

bearer request message further carries a bearer type IE. The MME uses the bearer type IE to

5 notify the created bearer type to the serving GW and the PDN GW. If the MME sets the

bearer type IE to default bearer, the serving GW and the PDN GW are notified that the

created bearer is a default bearer.

[0081] In this step, the terminal capability of the UE and the access policy information of

the operator are carried in the create bearer request message and sent to the serving GW and

10 the PDN GW.

[0082] Steps 307 and 308 are performed only when the policy and charging rules used by

the default bearer need to be obtained from the PCRF, and the access policy information of

the operator is configured in the PCRF.

[0083] In step 307, the PDN GW sends a PCC rules request message to the PCRF to

15 obtain the policy and charging rules used by the default bearer.

[0084] In step 308, the PCRF returns a PCC rules provision message to the PDN GW,

and the PCC rules provision message carries the access policy information of the operator.

[0085] In step 309, the PDN GW and the serving GW create a bearer context, and sets

the created bearer as the default bearer; the PDN GW returns a create bearer response

20 message to the serving GW, and the serving GW returns the create bearer response message

to the MME.

[0086] If the access policy information of the operator is configured in the PCRF entity,

or the access policy information of the operator is configured in the PDN GW, or the access

policy information of the operator is configured in the serving GW, this step includes the

25 following: the create bearer response message carries the access policy information of the

NSN677-1002,

14

operator configured by the PCRF, the PDN GW, or the serving GW.

[0087] In this step, the bearer context created by the PDN GW and the serving GW

includes bearer type information, which has two values: default bearer and dedicated bearer.

For the default bearer, the PDN GW and the serving GW set the bearer type information in

5 the bearer context to default bearer. The PDN GW and the serving GW may know that the

created bearer is a default bearer in the following two manners.

[0088] 1) In step 306, the MME carries the bearer type IE in the create bearer request

message, and notifies the bearer type to the serving GW and the PDN GW through the

bearer type IE. If the carried bearer type IE set by the MME is in the value of default bearer,

10 the created bearer is the default bearer.

[0089] 2) The serving GW and the PDN GW determine whether the created bearer is the

first bearer created in the packet data network (PDN); if yes, the serving GW and the PDN

GW determine that the created bearer is a default bearer.

[0090] Other bearers are dedicated bearers. In this case, the serving GW and the PDN

15 GW set the bearer type information in the bearer context to dedicated bearer.

[0091] Step 310a is performed only when the access network type (RAT type)

information in the 3GPP network has been registered with the HS S/AAA server by the

MME.

[0092] In step 310a, the MME registers access situations of the UE in the 3GPP network

20 (for example, the RAT type used by the UE) with the HSS/AAA server.

[0093] Step 310b is performed only when the RAT type information of the UE in the

3GPP network has been registered with the HSS/AAA server by the PDN GW.

[0094] In step 310b, the PDN GW registers the access situations of the UE in the 3GPP

network (for example, the RAT type used by the UE) with the HSS/AAA server.

NSN677-1002,

15

[0095] Through this step, the HSS/AAA server obtains the access network situations of

the UE. For example, in this embodiment, the HSS/AAA server knows that the RAT type of

the UE is a 3GPP network type, or a specific network type in a 3GPP network.


5 [0097] 1) The RAT type of the UE is categorized into a 3GPP network and a non-3GPP

network.

[0098] 2) The RAT type of the UE is a specific network type used by the UE, for

example, GERAN network, UTRAN network, EUTRAN network, WLAN network,

Wimax network, CDMA network, etc.

10 [0099] In Step 311, the MME returns an Attach Accept message to a network element on

an access side, and the Attach Accept message carries information of the radio bearer to be

established by the UE.

[0100] As for the EUTRAN access network, the network element on the access side is

ENodeB; as for the UTRAN access network, the network element on the access side is

15 RNC; as for the GERAN access network, the network element on the access side is BSS.

The MME may carry the access policy information of the operator in the Attach Accept

message.

[0101] In step 312, the network element on the access side sends a bearer establishment

request message to the UE, and requests the UE to establish a radio bearer. The message

20 carries the access policy information of the operator sent by the MME.

[0102] The access policy information of the operator may also be notified to the UE in a


[0103] In step 313, the UE establishes the bearer context, sets the created bearer to a

default bearer, and returns a radio bearer establishment response message to the network

NSN677-1002,

16

element on the access side.

[0104] The UE adds bearer type information to the established bearer context, and the

bear type has the following two values: default bearer and dedicated bearer. For the default

bearer, the UE sets the bearer type information in the bearer context to default bearer. The

5 bearer type added to the established bearer context by the UE may be acquired through the

following manners.

[0105] 1) In step 311, the MME carries a bearer type IE in the Attach Accept message,

and notifies the bearer type to the UE by the network element on the access side through the

bearer type IE. For the default bearer, the value of the bearer type IE carried by the MME is

10 Default Bearer.

[0106] 2) The UE determines whether the created bearer is the first bearer created in the

PDN; if yes, the UE determines that the created bearer is a default bearer.

[0107] Other bearers are dedicated bearers. In this case, the UE sets the bearer type

information in the bearer context to dedicated bearer.

15 [0108] In this embodiment, it should be noted that, the HSS and the AAA server may be

configured in different entities or in a same entity. If the HS S and the AAA server are

configured in different entities, the register message sent by the PDN GW in step 310a is

forwarded to the HSS by the AAA server, and the register message sent by the MME in step

310b is forwarded to the AAA server by the HSS.

20 [0109] FIG. 4 is a flow chart of a process that a network element in a 3GPP network

acquires terminal capability of UE and access policy information of an operator when a

location area or terminal capability of the UE changes. The process includes the following

steps.


25 (TAU/RAU request) message carrying changed terminal capability of the UE to the MME.

NSN677-1002,

17

101111 If the access network of the UE is GERAN/UTRAN, the message sent by the UE

is the RAU request message; if the access network of the UE is EUTRAN, the message sent

by the UE is the TAU request message.

[0112] The terminal capability of the UE is represented by lEs of the radio capability

5 supported by the UE. The radio capability supported by the UE is a single radio capability

(which indicates that the UE can access only one network at a certain time point) or a dual

radio capability (which indicates that the UE can access two or more networks at a certain

time point). An exemplary structure of the IE carrying the radio capability supported by the

UE is listed as follows. The IE includes a radio capability parameter supported by the UE.

10 The parameter may be: 1) the UE has a single radio capability; 2) the UE has a dual radio

capability.



UE Support Radio Capability 0 Single Radio Capability 1 Dual Radio Capability

[0113] In step 402, the MME sends an update location message to the HSS/AAA server,

15 and registers the UE with the HSS/AAA server, in which the update location message

carries the changed terminal capability of the UE.


MME, the update location request message carries the access policy information of the

operator. The access policy information of the operator includes: 1) a single radio access,

20 that is, the UE can access only one access network at a certain time point; and 2) a dual

radio access, that is, the UE can access a plurality of access networks at a certain time point.

NSN677-1002,

18

[0115] In step 403, the HSS/AAA server inserts subscription data of a user into the

MME.

[0116] In this step, if the access policy information of the operator is configured or

subscribed in the HSS/AAA server, the HSS/AAA server delivers the changed access

5 policy information of the operator to the MME.

[0117] In Step 404, the HSS/AAA server returns an update location Ack message to the

MME.


operator and the terminal capability of the UE has changed, the MME sends an update

10 bearer request message to the serving GW, and the serving GW sends the update bearer

request message to the PDN GW, in which the update bearer request message carries the

changed access policy information of the operator and the changed terminal capability of

the UE.

[0119] In this step, the changed access policy information of the operator and the

15 changed terminal capability of the UE are notified to the serving GW and the PDN GW.

[0120] Step 406a is performed only when the RAT type information in the 3GPP

network has been registered with the HSS/AAA server by the MME and the information

has changed.

[0121] In Step 406a, the MME registers the access situations of the UE in the 3GPP

20 network (for example, the RAT type used by the UE) with the HSS/AAA server.

[0122] Step 406b is performed only when the RAT type information in the 3GPP

network has been registered with the HSS/AAA server by the PDN GW and the

information has changed.

[0123] In step 406b, if the RAT type information in the 3GPP network has been

NSN677-1002,

19

registered with the HS S/AAA server by the PDN GW and the information has changed, the

PDN GW registers the access situations of the UE in the 3GPP network (for example, the

RAT type used by the UE) with the HSS/AAA server.

[0124] In step 407, the MME returns a TAU/RAU accept message to the UE, and the

5 MME may deliver the changed access policy information of the operator to the UE in the

TAU/RAU accept message.

[0125] The changed access policy information of the operator may also be notified to the

UE in a broadcast message of the cell.

[0126] FIG. 4 shows the process that the network element in a 3GPP network acquires

10 the changed terminal capability of the UE and the changed access policy information of the

operator when the terminal capability of the UE and the access policy information of the

operator both have changed. The process that the network element in the 3GPP network

acquires the changed terminal capability of the UE or the changed access policy information

of the operator when the terminal capability of the UE or the access policy information of

15 the operator has changed is similar to the process of FIG. 4, which thus is not described in

detail here.

[0127] The UE and the network element in a non-3GPP network acquire the terminal

capability of the UE, and the network element acquires the access policy information of the

operator, which are provided for being used in the solution for UE detachment when the UE

20 is handed over or switched from the non-3GPP network to a 3GPP network according to the

embodiments of the present invention. FIG. 5 is used to illustrate the process that the

network element in a non-3GPP network acquires the terminal capability of the UE and the

access policy information of the operator according to the embodiments of the present

invention. FIG. 5 is a flow chart of a process that a network element in a non-3GPP network

25 acquires terminal capability of UE and access policy information of an operator when the

UE accesses the non-3GPP network.

NSN677-1002,

20

[0128] Referring to FIG. 5, the process that the network element in the non-3GPP

network acquires the terminal capability of the UE and the access policy information of the

operator when the UE accesses the non-3GPP network includes the following steps.

[0129] In step 501, the UE sends an access request message carrying the terminal

5 capability of the UE to a non-3GPP GW.

[0130] In this step, if the non-3GPP network is a WLAN network, the non-3GPP GW is

an EPDG; if the non-3GPP network is a Wimax network, the non-3GPP GW is an ASN

GW; and if the non-3GPP network is a CDMA network, the non-3GPP GW is an AGW.


10 capability supported by the UE. The radio capability supported by the UE is a single radio

capability (which indicates that the UE can access only one network at a certain time point)

or a dual radio capability (which indicates that the UE can access two or more networks at a

certain time point). An exemplary structure of the IE carrying the radio capability supported

by the UE is listed as follows. The IE includes a radio capability parameter supported by the

15 UE. The parameter may be: 1) the UE has a single radio capability; 2) the UE has a dual

radio capability.




[0132] In step 502, an authentication process is performed between the UE, the

non-3GPP GW, and the HSS/AAA server.

20 [0133] In this step, if the access policy information of the operator is configured in the

NSN677-1002,

21

non-3GPP GW, an access authentication message may carry the access policy information

of the operator to the HSS/AAA server. The access policy information of the operator

includes: 1) a single radio access, that is, the UE can access only one access network at a

certain time point; and 2) a dual radio access, that is, the UE can access a plurality of access

5 networks at a certain time point. In this step, if the access policy information of the operator

is configured in the HSS/AAA server, the access authentication message may carry the

access policy information of the operator to the non-3GPP GW.

[0134] In step 503a, the non-3GPP GW sends a proxy binding update message to the

PDN GW.

10 [0135] In this step, it is assumed that an interface protocol between the non-3GPP GW

and the PDN GW is the proxy mobile internet protocol (PMIP). If an interface protocol

between the UE and the PDN GW is the client mobile internet protocol (CMIP), step 503a

is replaced by step 503b, in which the UE sends a binding update message to the PDN GW.

[0136] In this step, the terminal capability of the UE and the access policy information of

15 the operator may be carried in the proxy binding update message or the binding update

message and sent to the PDN GW.

[0137] In step 504, if the policy and charging rules used by the UE need to be obtained

from the PCRF, the PDN GW sends a PCC rules request message to the PCRF to obtain the

policy and charging rules used by the UE.

20 [0138] In step 505, the PCRF provides a PCC rules provision message of the policy and

charging rules used by the UE to the PDN GW. If the access policy information of the

operator is configured in the PCRF, the PCRF transmits the access policy information of

the operator to the PDN GW via the PCC rules provision message.

[0139] In step 506, if the policy and charging rules used by the UE need to be obtained

25 from the PCRF, the non-3GPP GW sends a PCC rules request message to the PCRF to

obtain the policy and charging rules used by the UE.

NSN677-1002,

22


charging rules used by the UE to the non-3GPP GW. If the access policy information of the

operator is configured in the PCRF, the PCRF transmits the access policy information of

the operator to the non-3GPP GW via the PCC rules provision message.

5 [0141] In step 508a, the PDN GW sends a proxy binding Ack message to the non-3GPP

GW.

[0142] In this step, it is assumed that the interface protocol between the non-3GPP GW

and the PDN GW is the PMIP. If the interface protocol between the UE and the PDN GW is

the CMIP, step 508a is replaced by step 508b, in which the PDN GW sends a binding Ack

10 message to the UE.

[0143] In step 509, if the RAT type information in the non-3GPP network is registered

with the HSS/AAA server by the PDN GW, the PDN GW registers the access situations of

the UE in the non-3GPP network (for example, the RAT type used by the UE) with the

HS S/AAA server.

15 [0144] In step 510, if the RAT type information in the non-3GPP network is registered

with the HSS/AAA server by the non-3GPP GW, the non-3GPP GW registers the access

situations of the UE in the non-3GPP network (for example, the RAT type used by the UE)

with the HSS/AAA server.

[0145] Through step 509 or step 510, the HSS/AAA server obtains the access network

20 situations of the UE. For example, in this embodiment, the HS S/AAA server knows that the

RAT type of the UE is a non-3GPP network type, or a specific network type in the

non-3GPP network. This step is optional.

[0146] The RAT type used by the UE may be processed through the following two

manners.

25 [0147] 1) The RAT type used by the UE is categorized into a 3GPP network and a

NSN677-1002,

23

non-3GPP network.

[0148] 2) The RAT type used by the UE is a specific network type used by the UE, for

example, a GERAN network, a UTRAN network, an EUTRAN network, a WLAN network,

Wimax network, or a CDMA network.

5 [0149] In step 511, the non-3GPP GW returns an access accept message to the UE. The

non-3GPP GW may carry the access policy information of the operator in the access accept

message.


configured in different entities or in the same entity. If the HSS and the AAA server are

10 configured in different entities, the register message sent by the PDN GW in step 509 is

forwarded to the HSS by the AAA server, and the register message sent by the non-3GPP

GW in Step 510 is forwarded to the AAA server by the HSS.

[0151] FIG. 6 shows a first example of a method for detaching a user when a handover or

change occurs in a heterogeneous network according to an embodiment of the present



[0153] In step 608a, the PDN GW sends a delete bearer request message to the serving

GW, and then the serving GW sends the received delete bearer request message to the

MME, and adds a cause IE in the delete bearer request message to indicate the reason of the

20 deletion, and the MME deletes the bearer resources.

[0154] In this step, as for the bearer deletion caused by the handover or switching of the

UE from the 3GPP network to the non-3GPP network, the PDN GW sets the cause IE as

"UE's accessing RAT changed from a 3GPP network to a non-3GPP network". As for the

bearer deletion that is not caused by the handover or change, the PDN GW sets the cause IE

25 to other values. Alternatively, the delete bearer request message sent by the PDN GW does

NSN677-1002,

24

not carry the cause IE, and in this case, once the MME receives the delete bearer request

message sent by the serving GW, the message is defaulted to be caused by the handover or

switching of the UE from the 3GPP network to the non-3GPP network. In this embodiment,

the message carrying the cause IE is taken as an example.

5 [0155] In this step, it is assumed that an interface protocol between the PDN GW and the

serving GW is GPRS tunneling protocol (GTP). If the interface protocol between the PDN

GW and the serving GW is the PMIP, step 608a is replaced by step 608b, in which the PDN

GW sends a binding revocation indication message to the serving GW; the cause IE is

added to the binding revocation indication message; the serving GW sends the delete bearer

10 request message carrying the cause IE sent by the PDN GW to the MME; and the MME

deletes the bearer resources after receiving the delete bearer request message.

[0156] As for the binding revocation indication caused by the handover or switching of

the UE from the 3GPP network to the non-3GPP network, the PDN GW sets the cause IE as

"UE's accessing RAT changed from a 3GPP network to a non-3GPP network". As for the

15 bearer deletion that is not caused by the handover or change, the PDN GW sets the cause IE

to other values. Alternatively, the binding revocation indication message sent by the PDN

GW does not carry the cause IE, and in this case, once the MME receives the delete bearer

request message sent by the serving GW, the message is default to be caused by the

handover or switching of the UE from the 3GPP network to the non-3GPP network. In this

20 embodiment, the message carrying the cause IE is taken as an example.

[0157] Step 608a or step 608b further includes the following: the MME deletes the

bearer resources after receiving the delete bearer request message. If the MME finds that all

bearer resources of the UE are deleted, the MME further determines whether to delete an

MM context (i.e., detaching the UE from the 3GPP network) and whether to send a detach

25 request message to the UE. Specifically, the process includes the following circumstances.

[0158] 1) The MME makes the following determination according to the cause IE carried

in the delete bearer request. The MME determines whether the cause IE carried in the

NSN677-1002,

25

received delete bearer request message is represented as "UE's accessing RAT changed

from a 3GPP network to a non-3GPP network"; if yes, the MME deletes the MM context of

the UE, and does not send the detach request message to the UE; otherwise, the MME sends

the detach request message to the UE and notifies the UE to delete the MM context and the

5 bearer resources of the 3GPP network in the UE.

[0159] 2) The MME makes the following determination according to the IE carried in the

delete bearer request and the terminal capability of the UE. If the MME determines that the

IE carried in the received delete bearer request message is represented as "UE's accessing

RAT changed from a 3GPP network to a non-3GPP network", and the MME knows that the

10 terminal capability of the UE is "single radio capability", the MME deletes the MM context

of the UE, and does not send the detach request message to the UE; as for the bearer

deletion caused by other reasons, the MME deletes the MM context of the UE, and sends

the detach request message to the UE. If the MME knows that the terminal capability of the

UE is "multi radio capability", the MME does not delete the MM context of the UE (that is,

15 does not detach the UE from the 3GPP network).


delete bearer request and the access policy information of the operator. If the MME

determines that the IE carried in the received delete bearer request message is represented

as "UE's accessing RAT changed from a 3GPP network to a non-3GPP network", and the

20 MME knows that the access policy information of the operator is "single radio access", the

MME deletes the MM context of the UE, and does not send the detach request message to

the UE; as for the bearer deletion caused by other reasons, the MME deletes the MM

context of the UE, and sends the detach request message to the UE. If the MME knows that

the access policy information of the operator is "multi radio access", the MME does not

25 delete the MM context of the UE (that is, does not detach the UE from the 3GPP network).


delete bearer request, the terminal capability of the UE, and the access policy information of

NSN677-1002,

26

the operator. If the MME determines that the IE carried in the received delete bearer request

message is represented as "UE's accessing RAT changed from a 3GPP network to a

non-3GPP network", the terminal capability of the UE is "dual radio capability", and the

access policy information of the operator is "single radio access", or if the MME determines

5 that the IE carried in the received delete bearer request message is represented as "UE's

accessing RAT changed from a 3GPP network to a non-3GPP network", the access policy

information of the operator is "multi radio access", and the terminal capability of the UE is

"single radio capability", or if the MME determines that the IE carried in the received delete

bearer request message is represented as "UE's accessing RAT changed from a 3GPP

10 network to a non-3GPP network", the terminal capability of the UE is "single radio

capability", and the access policy information of the operator is "single radio access", the

MME deletes the MM context of the UE, and does not send the detach request message to

the UE; as for the bearer deletion caused by other reasons, the MME deletes the MM

context of the UE, and sends the detach request message to the UE. If the MME knows that

15 the terminal capability of the UE is "dual radio capability" and the access policy

information of the operator is "multi radio access", the MME does not delete the MM

context of the UE (that is, does not detach the UE from the 3GPP network).

[0162] In step 609a, the MME returns a delete bearer response message to the serving

GW, and the serving GW returns the delete bearer response message to the PDN GW.

20 [0163] In this step, the interface protocol between the PDN GW and the serving GW is

the GIP, and if the interface protocol between the PDN GW and the serving GW is the

PMIP, Step 609a is replaced by step 609b, in which the MME returns the delete bearer

response message to the serving GW, and the serving GW returns a binding revocation Ack


25 [0164] In step 610, if the MME sends the detach request message to the UE, the UE

deletes the MM context and the bearer resources after receiving the detach request message,

and returns a Detach Accept message to the MME.

NSN677-1002,

27

[0165] In step 611, if the MME finds that the subscription data and the MM context of

the UE are deleted, the MME sends a purge UE message to the HSS/AAA server, and the

HSS/AAA server purges the record of the UE, and returns a purge UE Ack message to the

MME.

5 [0166] In this step, it is determined whether to delete the subscription data of the UE by

the MME according to the actual conditions. This step is optional.

[0167] In the above embodiment, after step 607, it is determined whether to detach the

UE from the 3GPP network. Specifically, the determination process is described as follows:

according to the handover or change in the access network, or according to the handover or

10 change of the UE in the access network and the terminal capability of the UE, or according

to the handover or change of the UE in the access network and the access policy

information of the operator, or according to the handover or change of the UE in the access

network, the terminal capability of the UE, and the access policy information of the

operator, it is determined whether to detach the UE from the 3GPP network, which

15 particularly includes the following four circumstances.

[0168] 1) It is determined whether the UE is handed over or switched from the 3GPP

network to the non-3GPP network; if yes, the MM context and bearer resources used by the

UE in the 3GPP network are deleted.


20 network to the non-3GPP network and whether the terminal capability of the UE is "single

radio capability"; if yes, the bearer resources and the MM context used by the UE in the

3GPP network are deleted.


network to the non-3GPP network and whether the access policy information of the

25 operator is "single radio access"; if yes, the bearer resources and the MM context used by

the UE in the 3GPP network are deleted.

NSN677-1002,

28

[0171] 4) It is determined whether the handover or change of the UE in the access


operator satisfy one of the following three conditions: 1. the UE is handed over or switched

from the 3GPP network to the non-3GPP network, the terminal capability of the UE is

5 "dual radio capability", and the access policy information of the operator is "single radio

access"; 2. the UE is handed over or switched from the 3GPP network to the non-3GPP

network, the access policy information of the operator is "multi radio access", and the

terminal capability of the UE is "single radio capability"; and 3. the UE is handed over or

switched from the 3GPP network to the non-3GPP network, the terminal capability of the

10 UE is "single radio capability", and the access policy information of the operator is "single

radio access".

[0172] If yes, the bearer resources and the MM context used by the UE in the 3GPP


[0173] Moreover, the delete bearer request added with the cause 1E in step 608 may be

15 replaced by another message, for example, replaced by a release bearer request message.

The release bearer request message indicates that the reason for deleting the bearer is the

handover or switching of the UE from the 3GPP network to the non-3GPP network;

alternatively, the delete bearer request message sent in step 608 does not carry the reason

for deleting the bearer, and when the UE is handed over or switched from the 3GPP

20 network to the non-3GPP network, a normal delete bearer request is sent to the MME. In

step 608, after receiving the specific message or the normal delete bearer request message,

the MME deletes the bearer resources; and the operations of the MME after the bearer

resources are deleted are similar to the operations of the MME after receiving the delete

bearer request message.

25 [0174] As for the first embodiment, it should be noted that the detachment method in this

embodiment is also applicable to the handover or switching of the UE from a non-3GPP

network to a 3GPP network.

NSN677-1002,

29

[0175] In step I, after the UE is handed over or switched to a 3GPP network, the PDN

GW sends the binding revocation indication message to a non-3GPP GW. The message

carries the cause IE indicating the reason for the binding revocation. As for the binding

revocation caused by the handover or switching from the non-3GPP network to the 3GPP

5 network, the PDN GW sets the cause IE as "UE's accessing RAT changed from a non-3GPP

network to a 3GPP network"; and as for the binding revocation that is not caused by the

handover or change, the PDN GW sets the cause IE to other values.

[0176] In step II, the non-3GPP GW deletes the bearer resources after receiving the

binding revocation indication message. If the non-3GPP GW finds that all bearer resources

10 of the UE are deleted, the non-3GPP GW further determines whether to delete the MM

context of the UE (that is, to detach the UE from the non-3GPP network), which

specifically includes the following circumstances.

[0177] 1) The non-3GPP GW makes the following determination according to the Cause

IE carried in the binding revocation indication message, in which the non-3GPP GW

15 determines whether the cause IE carried in the binding revocation indication message is

represented as "UE's accessing RAT changed from a non-3GPP network to a 3GPP

network"; if yes, the non-3GPP GW deletes the MM context of the UE, and does not send

the detach request message to the UE; otherwise, the non-3GPP GW sends the detach

request message to the UE, and notifies the UE to delete the MM context and bearer

20 resources of the non-3GPP network in the UE.

[0178] 2) The non-3GPP GW makes the following determination according to the IE

carried in the binding revocation indication message and the terminal capability of the UE,

in which if the non-3GPP GW determines that the IE carried in the received binding

revocation indication message is represented as "UE's accessing RAT changed from a

25 non-3GPP network to a 3GPP network", and the non-3GPP GW knows that the terminal

capability of the UE is "single radio capability", the non-3GPP GW deletes the MM context

of the UE, and does not send the detach request message to the UE; as for the bearer

NSN677-1002,

30

deletion caused by other reasons, the non-3GPP GW deletes the MM context of the UE, and

sends the detach request message to the UE. If the non-3GPP GW knows that the terminal

capability of the UE is "multi radio capability", the non-3GPP GW does not delete the MM

context of the UE (that is, does not detach the UE from the non-3GPP network).

5 [0179] 3) The non-3GPP GW makes the following determination according to the IE

carried in the binding revocation indication message and the access policy information of

the operator, in which if the non-3GPP GW determines that the IE carried in the received

binding revocation indication message is represented as "UE's accessing RAT changed from

a non-3GPP network to a 3GPP network", and the non-3GPP GW knows that the access

10 policy information of the operator is "single radio access", the non-3GPP GW deletes the

MM context of the UE, and does not send the detach request message to the UE; as for the

bearer deletion caused by other reasons, the non-3GPP GW deletes the MM context of the

UE, and sends the detach request message to the UE. If the non-3GPP GW knows that the

access policy information of the operator is "multi radio access", the non-3GPP GW does

15 not delete the MM context of the UE (that is, does not detach the UE from the non-3GPP

network).

[0180] 4) The non-3GPP GW makes the following determination according to the IE

carried in the binding revocation indication message, the terminal capability of the UE, and

the access policy information of the operator, in which if the non-3GPP GW determines

20 that the IE carried in the received binding revocation indication message is represented as

"UE's accessing RAT changed from a non-3GPP network to a 3GPP network", the terminal

capability of the UE is "dual radio capability", and the access policy information of the

operator is "single radio access", or if the non-3GPP GW determines that the IE carried in

the received binding revocation indication message is represented as "UE's accessing RAT

25 changed from a non-3GPP network to a 3GPP network", the access policy information of

the operator is "multi radio access", and the terminal capability of the UE is "single radio

capability", or if the non-3GPP GW determines that the IE carried in the received binding

revocation indication message is represented as "UE's accessing RAT changed from a

NSN677-1002,

31

non-3GPP network to a 3GPP network", the terminal capability of the UE is "single radio


non-3GPP GW deletes the MM context of the UE, and does not send the detach request

message to the UE; as for the bearer deletion caused by other reasons, the non-3GPP GW

5 deletes the MM context of the UE, and sends the detach request message to the UE. If the

non-3GPP GW knows that the terminal capability of the UE is "dual radio capability", and

the access policy information of the operator is "multi radio access", the non-3GPP GW

does not delete the MM context of the UE (that is, does not detach the UE from the

non-3GPP network).

10 [0181] FIG. 7 shows a second example of the method for user detachment when a


present invention. The method includes the following steps.


[0183] In step 708a, the PDN GW determines whether to delete the default bearer of the

15 UE; if yes, the PDN GW sends the delete bearer request message corresponding to the

default bearer to the serving GW, and the serving GW sends the received delete bearer

request message to the MME.


[0185] In this step, the interface protocol between the PDN GW and the serving GW is

20 the GTP. If the interface protocol between the PDN GW and the serving GW is the PMIP,

step 708a is replaced by step 708b, in which the PDN GW sends the binding revocation

indication message to the serving GW, and the serving GW determines whether to delete

the default bearer of the UE; if yes, the serving GW sends the delete bearer request message

corresponding to the default bearer to the MME, and the MME deletes the MM context and

25 the bearer resources.

[0186] In step 708a or 708b, the PDN GW/serving GW determines whether to delete the

NSN677-1002,

32

default bearer of the UE in the following manners. The PDN GW/serving GW determines

whether to delete the default bearer of the UE according to the handover or change of the

UE in the access network, or according to the handover or change of the UE in the access

network and the terminal capability of the UE, or according to the handover or change of

5 the UE in the access network and the access policy information of the operator, or

according to the handover or change of the UE in the access network, the terminal

capability of the UE, and the access policy information of the operator. The terminal

capability of the UE and the access policy information of the operator are obtained by the

network elements according to the flows shown in FIGs. 3 and 4. Specifically, the

10 determination process includes the following circumstances.

[0187] 1) The PDN GW/serving GW determines whether to delete the default bearer of

the UE according to the handover or change of the UE in the access network, in which the

PDN GW/serving GW determines whether the UE is handed over or switched from the

3GPP network to the non-3GPP network; if yes, the PDN GW/serving GW determines to

15 delete the default bearer of the UE, and sends the delete bearer request message

corresponding to the default bearer to the MME.


the UE according to the handover or change of the UE in the access network and the

terminal capability of the UE, in which the PDN GW/serving GW determines whether the

20 UE is handed over or switched from the 3GPP network to the non-3GPP network and

whether the terminal capability of the UE is "single radio capability"; if yes, the PDN

GW/serving GW determines to delete the default bearer of the UE, and sends the delete

bearer request message corresponding to the default bearer to the MME.


25 the UE according to the handover or change of the UE in the access network and the access

policy information of the operator, in which the PDN GW/serving GW determines whether

the UE is handed over or switched from the 3GPP network to the non-3GPP network and

NSN677-1002,

33

whether the access policy information of the operator is "single radio access"; if yes, the

PDN GW/serving GW determines to delete the default bearer of the UE, and sends the

delete bearer request message corresponding to the default bearer to the MME.


5 the UE according to the handover or change of the UE in the access network, the terminal

capability of the UE, and the access policy information of the operator, in which the PDN

GW/serving GW determines whether the handover or change of the UE in the access



10 from the 3GPP network to the non-3GPP network, the terminal capability of the UE is

"dual radio capability", and the access policy information of the operator is "single radio


network, the access policy information of the operator is "multi radio access", and the


15 switched from the 3GPP network to the non-3GPP network, the terminal capability of the

UE is "single radio capability", and the access policy information of the operator is "single

radio access".

[0191] If yes, the PDN GW/serving GW determines to delete the default bearer of the

UE, and sends the delete bearer request message corresponding to the default bearer to the

20 MME.

[0192] In step 709a, the MME returns a delete bearer response message to the serving

GW, and the serving GW returns the delete bearer response message to the PDN GW.

[0193] In this step, the interface protocol between the PDN GW and the serving GW is

the GTP. If the interface protocol between the PDN GW and the serving GW is the PMIP,

25 step 709a is replaced by step 709b, in which the MME returns the delete bearer response

message to the serving GW, and the serving GW returns the binding revocation Ack


NSN677-1002,

34

[0194] In step 710, if the MME finds that the default bearer of the UE is deleted, the

MME deletes the MM context of the UE (that is, the MME detaches the UE from the 3GPP

network).

[0195] If the MME finds that the subscription data and the MM context of the UE are

5 deleted, the MME sends a purge UE message to the HSS/AAA server, and the HSS/AAA


[0196] In this step, it is determined whether to delete the subscription data of the UE by



10 [0198] In the above embodiment, the UE is detached after step 707. The detachment

process is as follows: according to the handover or change of the UE in the access network,

or according to the handover or change of the UE in the access network and the terminal

capability of the UE, or according to the handover or change of the UE in the access

network and the access policy information of the operator, or according to the handover or

15 change of the UE in the access network, the terminal capability of the UE, and the access

policy information of the operator, the UE determines whether to perform the detachment,

which specifically includes the following four circumstances.


network to the non-3GPP network; if yes, the UE also deletes the default bearer, and deletes

20 the MM context and bearer resources used by the UE in the 3GPP network (that is, the UE

is detached from the 3GPP network); otherwise, the UE does not delete the default bearer,

and does not delete the MM context used by the UE in the 3GPP network.


network to the non-3GPP network and whether the terminal capability of the UE is "single

25 radio capability"; if yes, the UE also deletes the default bearer, and deletes the MM context

and bearer resources used by the UE in the 3GPP network (that is, the UE is detached from

NSN677-1002,

35

the 3GPP network); otherwise, the UE does not delete the default bearer, and does not

delete the MM context used by the UE in the 3GPP network.


network to the non-3GPP network and whether the access policy information of the

5 operator is "single radio access" ; if yes, the UE also deletes the default bearer, and deletes

the MM context and bearer resources used by the UE in the 3GPP network (that is, the UE

is detached from the 3GPP network); otherwise, the UE does not delete the default bearer,

and does not delete the MM context used by the UE in the 3GPP network.

[0202] 4) It is determined whether the handover or change of the UE in the access

10 network, the terminal capability of the UE, and the access policy information of the



"dual radio capability", and the access policy information of the operator is "single radio


15 network, the access policy information of the operator is "multi radio access", and the




radio access".

20 [0203] If yes, the UE deletes the default bearer, and deletes the MM context and bearer

resources used by the UE in the 3GPP network (that is, the UE is detached from the 3GPP

network); otherwise, the UE does not delete the default bearer, and does not delete the MM


[0204] FIG. 8 shows a third example of the method for user detachment when a handover

25 or change occurs in a heterogeneous network according to an embodiment of the present


NSN677-1002,

36


[0206] In step 808a, the PDN GW sends a detach request message to the MME through

the serving GW, and the detach request message carries a cause value represented as

"detach because of UE's accessing RAT changed from a 3GPP network to a non-3GPP

5 network", which indicates that the detach request message is caused by the handover or

switching of the UE from the 3GPP network to the non-3GPP network.

[0207] In this step, no interface exists between the PDN GW and the MME. If an

interface exists between the PDN GW and the MME, step 808a is replaced by step 808b, in

which the PDN GW sends a Detach Request message to the MME, and the Detach Request

10 message carries a Cause value represented as "Detach because of UE's accessing RAT

changed from a 3GPP network to a non-3GPP network", indicating that the detach request

message is caused by the handover or change of the UE from the 3GPP network to the

non-3GPP network.

[0208] If the interface protocol between the PDN GW and the MME is the PMIP, step

15 808a is replaced by step 808c, in which the PDN GW sends a binding revocation Ind

message to the serving GW, and the serving GW sends the detach request message to the

MME, and the detach request message carries a cause value represented as "detach because

of UE's accessing RAT changed from a 3GPP network to a non-3GPP network", indicating

that the detach request message is caused by the handover or change of the UE from the

20 3GPP network to the non-3GPP network.



handover or change of the UE in the access network, or according to the handover or

change of the UE in the access network and the terminal capability of the UE, or according

25 to the handover or change of the UE in the access network and the access policy



NSN677-1002,

37

operator; if yes, the detach request message is sent to the MME; otherwise, the process ends.

In steps 808a and 808b, the determination is performed by the PDN GW, and in step 808c,

the determination is performed by the serving GW. Whether to send the detach request

message may be determined according to the following circumstances.

5 [0210] 1) The PDN GW/serving GW determines whether to send the detach request

message to the MME according to the handover or change of the UE in the access network,

in which the PDN GW/serving GW determines whether the UE is handed over from the

3GPP network to the non-3GPP network; if yes, the detach request message is sent to the

MME; otherwise, the process ends.

10 [0211] 2) The PDN GW/serving GW determines whether to send the detach request

message to the MME according to the handover or change of the UE in the access network

and the terminal capability of the UE, in which the PDN GW/serving GW determines

whether the UE is handed over or switched from the 3GPP network to the non-3GPP

network and whether the terminal capability of the UE is "single radio capability"; if yes,

15 the detach request message is sent to the MME; otherwise, the process ends.

[0212] 3) The PDN GW/serving GW determines whether to send the detach request

message to the MME according to the handover or change of the UE in the access network

and the access policy information of the operator, in which the PDN GW/serving GW

determines whether the UE is handed over or switched from the 3GPP network to the

20 non-3GPP network and whether the access policy information of the operator is "single

radio access"; if yes, the detach request message is sent to the MME; otherwise, the process

ends.

[0213] 4) The PDN GW/serving GW determines whether to send the detach request

message to the MME according to the handover or change of the UE in the access network,

25 the terminal capability of the UE, and the access policy information of the operator, in

which the PDN GW/serving GW determines whether the handover or change of the UE in

the access network, the terminal capability of the UE, and the access policy information of

NSN677-1002,

38

the operator satisfy one of the following three conditions: 1. the UE is handed over or


UE is "dual radio capability", and the access policy information of the operator is "single

radio access"; 2. the UE is handed over or switched from the 3GPP network to the

5 non-3GPP network, the access policy information of the operator is "multi radio access",

and the terminal capability of the UE is "single radio capability"; and 3. the UE is handed

over or switched from the 3GPP network to the non-3GPP network, the terminal capability

of the UE is "single radio capability", and the access policy information of the operator is


10 [0214] If yes, the detach request message is sent to the MME; otherwise, the process

ends.

[0215] In step 809a, the MME receives the detach request message, deletes the MM

context, and sends a detach response message to the PDN GW through the serving GW.

[0216] In this step, no interface exists between the PDN GW and the MME. If an

15 interface exists between the PDN GW and the MME, step 809a is replaced by step 809b, in

which the MME receives the detach request message, deletes the MM context, and directly

sends a detach response message to the PDN GW.

[0217] If the interface protocol between the PDN GW and the MME is the PMIP, step

809a is replaced by step 809c, in which the PDN GW sends the detach response message to

20 the serving GW, and the serving GW returns a binding revocation Ack message to the PDN

GW.

[0218] In step 810, the MME initiates a bearer deletion process to delete the bearer

resources used by the UE on the 3GPP network side (including the MME, serving GW, and

PDN GW).

25 [0219] In step 811, if the MME finds that the subscription data and the MM context of

the UE are deleted, the MME sends a purge UE message to the HSS/AAA server, and then

NSN677-1002,

39

the HSS/AAA server purges the record of the UE, and returns a purge UE Ack message to

the MME.



5 [0221] Step 809 and Step 811 may be performed at any order.

[0222] In this embodiment, the UE is detached after step 807, and the detailed process

thereof can be known with reference to the descriptions of the third example of the method

for user detachment.

[0223] In this embodiment, it should be noted that, the detach request message sent by

10 the PDN GW or serving GW may not carry the cause value.

[0224] In this embodiment, it should be noted that, the method in this embodiment is

also applicable to the handover or switching of the UE from the non-3GPP network to the

3GPP network.


15 network, the PDN GW determines whether to detach the UE from the non-3GPP network

and whether to send the detach request message to the non-3GPP GW, which includes

determining whether to send the detach request message according to the handover or

change of the UE in the access network, or according to the handover or change of the UE

in the access network and the terminal capability of the UE, or according to the handover or

20 change of the UE in the access network and the access policy information of the operator,

or according to the handover or change of the UE in the access network, the terminal

capability of the UE, and the access policy information of the operator; if yes, the detach

request message is sent to the non-3GPP GW. The detailed process thereof can be known

with reference to the descriptions of the above embodiment.

25 [0226] FIG. 9 shows a fourth example of the method for user detachment when a

NSN677-1002,

40




[0228] In step 908, the PDN GW sends a register request message to the HSS/AAA

5 server, and the message carries an RAT type of the UE.


[0230] The RAT Type may be a 3GPP network, which indicates that the network that the

UE accesses currently is a 3GPP network; and the RAT Type may be a non-3GPP network,

which indicates that the network that the UE accesses currently is a non-3GPP network.

10 [0231] The RAT Type of the UE may also be a specific network type, for example,

GERAN, UTRAN, or EUTRAN network in the 3GPP networks, or WLAN, Wimax, and

CDMA network in the non-3GPP networks.


[0233] In step 909, the HSS/AAA server returns a register response message to the PDN

15 GW.


registered last time is inconsistent with that of the UE registered this time, the HSS/AAA

server sends a cancel location message to the MME, in which the cancel location message

carries a cause value represented as "Cancel because of UE's accessing RAT changed from

20 a 3GPP network to a non-3GPP network", indicating that the cancel location is caused by

the handover or switching of the UE from the 3GPP network to the non-3GPP network.

[0235] In this step, before the cancel location message is sent to the MME, the process

further includes that the HSS/AAA server determines whether to send the cancel location

message according to the handover or change of the UE in the access network, or according

NSN677-1002,

41

to the handover or change of the UE in the access network and the terminal capability of the

UE, or according to the handover or change of the UE in the access network and the access

policy information of the operator, or according to the handover or change of the UE in the

access network, the terminal capability of the UE, and the access policy information of the

5 operator; if yes, the HSS/AAA server sends the cancel location message to the MME;

otherwise, the HSS/AAA server does not send the cancel location message to the MME,

and the process ends. Specifically, the determination process specifically includes the

following circumstances.

[0236] 1) The HSS/AAA server determines whether to send the cancel location message

10 to the MME according to the handover or change of the UE in the access network, in which

the HSS/AAA server determines whether the UE is handed over or switched from the 3GPP

network to the non-3GPP network; if yes, the HSS/AAA server sends the cancel location

message to the MME; otherwise, the HSS/AAA server does not send the cancel location

message to the MME, and the process ends.

15 [0237] 2) The HSS/AAA server determines whether to send the cancel location message

to the MME according to the handover or switching of the UE in the access network and the

terminal capability of the UE, in which if the HSS/AAA server determines that the UE is

handed over or switched from the 3GPP network to the non-3GPP network, and the

terminal capability of the UE is "single radio capability", the HSS/AAA server sends the

20 cancel location message to the MME; if the HSS/AAA server determines that the terminal

capability of the UE is "multi radio capability", the HSS/AAA server does not send the

cancel location message to the MME.

[0238] 3) The HSS/AAA server determines whether to send the cancel location message

to the MME according to the handover or change of the UE in the access network and the

25 access policy information of the operator, in which if the HSS/AAA server determines that

the UE is handed over or switched from the 3GPP network to the non-3GPP network, and

the access policy information of the operator is "single radio access", the HSS/AAA server

NSN677-1002,

42

sends the cancel location message to the MME; if the HSS/AAA server determines that the

UE is handed over or switched from the 3GPP network to the non-3GPP network, and the

access policy information of the operator is "multi radio access", the HSS/AAA server does

not send the cancel location message to the MME.

5 [0239] 4) The HSS/AAA server determines whether to send the cancel location message

to the MME according to the handover or switching of the UE in the access network, the

terminal capability of the UE, and the access policy information of the operator, in which if

the HSS/AAA server determines that the UE is handed over or switched from the 3GPP

network to the non-3GPP network, the terminal capability of the UE is "dual radio

10 capability", and the access policy information of the operator is "single radio access", or if

the HSS/AAA server determines that the UE is handed over or switched from the 3GPP

network to the non-3GPP network, the access policy information of the operator is "multi

radio access", and the terminal capability of the UE is "single radio capability", or if the

HSS/AAA server determines that the UE is handed over or switched from the 3GPP

15 network to the non-3GPP network, the terminal capability of the UE is "single radio


HSS/AAA server sends the cancel location message to the MME; if the HSS/AAA server

determines that the terminal capability of the UE is "dual radio capability" and the access

policy information of the operator is "multi radio access", the HSS/AAA server does not

20 send the cancel location message to the MME.

[0240] In step 911, after receiving the cancel location message, the MME deletes the

MM context of the UE, and returns a cancel location Ack message to the HS S/AAA server.



25 the HSS/AAA server purges the record of the UE, and returns a purge UE Ack message to

the MME.


NSN677-1002,

43




PDN GW).

5 [0244] In this embodiment, the UE is detached after step 907, and the detailed process




configured in different entities or in a same entity. When the HSS and the AAA server are

10 configured in different entities, the register request message sent by the PDN GW in step

908 is forwarded to the HSS through the AAA server, the register response message sent by

the HSS in step 909 is forwarded to the PDN GW through the AAA server, the cancel

location message sent to the MME in step 910 is sent to the MME by the HSS, and the

purge UE message sent by the MME in step 912 is sent to the HSS. The cancel location

15 message sent by the HSS/AAA server may not carry the cause value.


also applicable to the handover or switching of the UE from a non-3GPP network to a

3GPP network.


20 the 3GPP network, the MME or the PDN GW registers a new RAT Type of the UE with the

HSS/AAA server.

[0248] In Step II, if the HSS/AAA server determines that the RAT type of the UE

registered last time is inconsistent with that of the UE registered this time, the HSS/AAA

server determines whether to send the cancel location message to a non-3GPP GW (to

25 notify the non-3GPP GW to detach the UE from the non-3GPP network) according to the


NSN677-1002,

44





5 operator. If yes, the HSS/AAA server sends the cancel location message to the non-3GPP

GW. The detailed process thereof can be known with reference to the descriptions of the

above embodiment.



10 present invention. The method includes the following steps.

[0250] In step 1001, the UE accesses a 3GPP access network through the serving GW

and the PDN GW.

[0251] In step 1002, the UE triggers a handover or switching from the 3GPP network to


15 [0252] In step 1003, the MME sends a handover or switching request (HO Request)

message to a non-3GPP GW.

[0253] In this step, as for a WLAN system, the non-3GPP GW is an EPDG; as for a

Wimax system, the non-3GPP GW is an ASN GW; and as for a CDMA system, the

non-3GPP GW is an AGW.

20 [0254] In Step 1004, the non-3GPP GW performs a resource create procedure.

[0255] In this step, the resource create procedure includes performing the processes of

user authentication and PMIP tunnel binding.


[0257] In step 1006, the MME sends an HO command message to the UE, and

NSN677-1002,

45

commands the UE to hand over or switch to an access network of the non-3GPP network.

[0258] In step 1007, the UE sends an access request message to the non-3GPP GW, and

is handed over or switched to the non-3GPP network.


5 [0260] Steps 1001-1008 and the process of the handover or switching of the UE from a

3GPP network to a non-3GPP network in the prior art implement functions similar to that

of steps 201-207 in FIG. 2.


[0262] In step 1010, the MME returns an HO complete Ack message to the non-3GPP

10 GW.

[0263] Step 1010 further includes: determining, by the MME, whether to delete the MM

context of the UE (that is, to detach the UE from the 3GPP network) according to the



15 to the handover or change of the UE in the access network and the access policy



operator; if yes, the MME deletes the MM context of the UE; otherwise, the process ends.

Specifically, the determination process includes the following four circumstances.

20 [0264] 1) The MME determines whether to delete the MM context of the UE according

to the handover or change of the UE in the access network, in which if the MME

determines that the UE is handed over or switched from the 3GPP network to the non-3GPP

network, the MME deletes the MM context of the UE; otherwise, the MME does not delete

the MM context of the UE.

25 [0265] 2) The MME determines whether to delete the MM context of the UE according

NSN677-1002,

46

to the handover or change of the UE in the access network and the terminal capability of the

UE, in which if the MME determines that the UE is handed over or switched from the

3GPP network to the non-3GPP network, and the terminal capability of the UE is "single

radio capability", the MME deletes the MM context of the UE; if the MME determines that

5 the terminal capability of the UE is "multi radio capability", the MME does not delete the

MM context of the UE.

[0266] 3) The MME determines whether to delete the MM context of the UE according


information of the operator, in which if the MME determines that the UE is handed over or

10 switched from the 3GPP network to the non-3GPP network, and the access policy

information of the operator is "single radio access", the MME deletes the MM context of

the UE; if the MME determines that the access policy information of the operator is "multi

radio access", the MME does not delete the MM context.

[0267] 4) The MME determines whether to delete the MM context of the UE according

15 to the handover or change of the UE in the access network, the terminal capability of the

UE, and the access policy information of the operator, in which if the MME determines that

the UE is handed over or switched from the 3GPP network to the non-3GPP network, the

terminal capability of the UE is "dual radio capability", and the access policy information of

the operator is "single radio access", or if the MME determines that the UE is handed over

20 or switched from the 3GPP network to the non-3GPP network, the access policy

information of the operator is "multi radio access", and the terminal capability of the UE is

"single radio capability", or if the MME determines that the UE is handed over or switched


"single radio capability", and the access policy information of the operator is "single radio

25 access", the MME deletes the MM context of the UE; if the MME determines that the


the operator is "multi radio access", the MME does not delete the MM context of the UE.

NSN677-1002,

47




the MME.

5 [0269] In this step, it is determined whether to delete the subscription data of the UE by




PDN GW).

10 [0271] In this embodiment, the UE is detached after Step 1007, and the detailed process




also applicable to the handover or switching of the UE from the non-3GPP network to the

15 3GPP network.



[0274] In step II, the non-3GPP GW determines whether to delete the MM context of the

UE (that is, to detach the UE from the non-3GPP network) according to the handover or

20 change of the UE in the access network, or according to the handover or change of the UE

in the access network and the terminal capability of the UE, or according to the handover or

change of the UE in the access network and the access policy information of the operator,

or according to the handover or change of the UE in the access network, the terminal

capability of the UE, and the access policy information of the operator; if yes, the

25 non-3GPP GW deletes the MM context of the UE. The detailed process thereof can be

known with reference to the descriptions of the above embodiment.

NSN677-1002,

48





5 [0277] In step 1103, the UE sends a detach request message to the MME, and the detach

request message carries a cause value represented as "detach because of UE's accessing

RAT changed from a 3GPP network to a non-3GPP network", indicating that the detach

request message is caused by the handover or change of the UE from the 3GPP network to


10 [0278] In this step, before the UE sends the detach request message to MME, the process

further includes determining whether to detach the UE from the 3GPP network according to

the handover of the UE in the access network, or according to the handover of the UE in the

access network and the terminal capability of the UE, or according to the handover of the

UE in the access network and the access policy information of the operator, or according to

15 the handover of the UE in the access network, the terminal capability of the UE, and the

access policy information of the operator. If yes, the UE sends the detach request message

to the MME; otherwise, step 1107 is performed. The terminal capability of the UE and the

access policy information of the operator are obtained by the network elements according to

the processes of FIGs. 3 and 4. Specifically, the determination process includes the

20 following circumstances.

[0279] 1) The UE determines whether to detach the UE from the 3GPP network and

whether to send the detach request message to the MME according to the handover or

change of the UE in the access network, in which the UE determines whether the UE is

handed over or switched from the 3GPP network to the non-3GPP network; if yes, the MM

25 context and bearer resources of the 3GPP network in the UE are deleted, and the detach

request message is sent to the MME; otherwise, step 1107 is performed.

NSN677-1002,

49



change of the UE in the access network and the terminal capability of the UE, in which if

the UE determines that the UE is handed over or switched from the 3GPP network to the

5 non-3GPP network, and the terminal capability of the UE is "single radio capability", the

MM context and the bearer resources of the 3GPP network in the UE are deleted, and the

detach request message is sent to the MME; if the UE determines that the terminal

capability of the UE is "multi radio capability", the MM context of the 3GPP network in the

UE is not deleted (that is, the UE is not detached from the 3GPP network), the detach

10 request message is not sent to the MME, and step 1107 is performed.



change of the UE in the access network and the access policy information of the operator, in

which if the UE determines that the UE is handed over or switched from the 3GPP network

15 to the non-3GPP network, and the access policy information of the operator is "single radio

access", the MM context and the bearer resources of the 3GPP network in the UE are

deleted, and the detach request message is sent to the MME; if the UE determines that the

access policy information of the operator is "multi radio access", the MM context of

network in the UE is not deleted (that is, the UE is not detached from the 3GPP network),

20 the detach request message is not sent to the MME, and step 1107 is performed.

[0282] 4) The UE determines whether to detach the UE from the 3GPP network

according to the handover or change of the UE in the access network, the terminal

capability of the UE, and the access policy information of the operator, in which if the UE


25 network, the terminal capability of the UE is "dual radio capability", and the access policy

information of the operator is "single radio access", or if the UE determines that the UE is

handed over or switched from the 3GPP network to the non-3GPP network, the access

policy information of the operator is "multi radio access", and the terminal capability of the

NSN677-1002,

50

UE is "single radio capability", or if the UE determines that the UE is handed over or



radio access", the MM context and the bearer resources of the 3GPP network in the UE are

5 deleted, and the detach request message is sent to the MME. If the UE determines that the


the operator is "multi radio access", the MM context of the 3GPP network in the UE is not

deleted (that is, the UE is not detached from the 3GPP network), the detach request

message is not sent to the MME, and step 1107 is performed.

10 [0283] In step 1104, after the MME receives the detach request message, the MME

deletes the MM context of the UE in the MME, initiates a bearer deletion process, and

deletes the bearer resources used by the UE on the 3GPP network side.

[0284] In this step, the bearer resources used by the UE on the 3GPP network side

include the bearer resources used by the UE in the MME, serving GW, and PDN GW.

15 [0285] In step 1105, if the MME finds that the subscription data and the MM context of



the MME.


20 the MME according to the actual conditions. This step is optional.





25 also applicable to the handover or switching of the UE from the non-3GPP network to the

NSN677-1002,

51

3GPP network.

[0291] When the UE is handed over from the non-3GPP network to the 3GPP network,

the UE determines whether to detach the UE from the non-3GPP network according to the

handover of the UE in the access network, or according to the handover of the UE in the

5 access network and the terminal capability of the UE, or according to the handover of the

UE in the access network and the access policy information of the operator, or according to

the handover of the UE in the access network, the terminal capability of the UE, and the

access policy information of the operator. If yes, the UE sends the detach request message

to the non-3GPP GW. The detailed process thereof can be known with reference to the

10 description of the above embodiment.

[0292] It should be noted that, in this embodiment, the serving GW and the PDN GW

may be configured in different entities or in the same entity. When the serving GW and the

PDN GW are configured in the same entity, the messages between the serving GW and the

PDN GW are transmitted in the same entity. The HSS and the AAA server may be

15 configured in different entities or in the same entity. If the HSS and the AAA server are

configured in different entities, the MME sends the purge UE message to the HSS.

[0293] In the embodiments of the present invention, if the user detachment is caused by

the handover or change of the UE from the 3GPP network to the non-3GPP network, after

the user detachment, the process may further include: setting, by the MME of the 3GPP, the

20 state of the UE to an invalid state. Specifically, the process of setting, by the MME of the

3GPP, the state of the UE to an invalid state is implemented as follows.

[0294] The MME deletes the subscription date information and the MM context of the

UE.

[0295] Alternatively, the MME retains the subscription data information of the UE, but

25 sets the state of the MME used by the UE to an invalid state.

[0296] Alternatively, the state of the MME used by the UE is set to an invalid value.

NSN677-1002,

52

[0297] Alternatively, the MME retains the subscription data information of the UE, but

sets a change flag location of the MME used by the UE to a changed state.

[0298] In the embodiments of the present invention, if the user detachment is caused by

the handover or switching of the UE from the non-3GPP network to the 3GPP network,

5 after the user detachment, the process may further include: setting, by the non-3GPP GW of

the non-3GPP, the state of the UE to an invalid state. Specifically, the process of setting, by

the non-3GPP GW of the non-3GPP, the state of the UE to an invalid state is implemented

as follows.

[0299] The non-3GPP GW deletes the subscription data information and the MM context

10 of the UE.

[0300] Alternatively, the non-3GPP GW retains the subscription data information of the

user, but sets the state of the non-3GPP GW used by the UE to an invalid state.

[0301] Alternatively, the address of the non-3GPP GW used by the UE is set to an

invalid value.

15 [0302] Alternatively, a non-3GPP GW retains the subscription data information of the

user, but sets a change flag position of the non-3GPP GW used by the UE to a changed

state.

[0303] FIG. 12 shows a system for user detachment when a handover or change occurs in

a heterogeneous network according to an embodiment of the present invention. The system

20 includes a UE and a network side.

[0304] The UE is adapted to be handed over or switched from a source network on the

network side to a target network.

[0305] The network side is adapted to hand over or switch the UE from the source

network to the target network to detach the UE from the source network.

NSN677-1002,

53

[0306] The UE may include a first handover or change module, and the network side

may include a second handover or change module and a second detachment module.

[0307] The first handover or change module is adapted to enable the UE to be handed

over or switched from the source network to the target network.

5 [0308] The second handover or change module is adapted to enable the network side to

hand over or switch the UE from the source network to the target network.

[0309] The second detachment module is adapted to enable the network side to detach

the UE from the source network.

[0310] Optionally, the UE includes a first detachment module adapted to detach the UE

10 from the source network.

[0311] Optionally, the UE includes a first detachment determination module and a

second detachment determination module disposed on the network side.

[0312] The first detachment determination module is adapted to determine whether to

detach the UE from the source network, and if yes, an enable instruction is sent to the first

15 detachment module to enable the first detachment module.

[0313] The second detachment determination module is adapted to determine whether to

detach the UE from the source network, and if yes, an enable instruction is sent to the

second detachment module to enable the second detachment module. The second

detachment determination module may be disposed in a network element on a network side,

20 such as an MME, a PDN GW, a serving GW, or an HS S/AAA server.

[0314] The UE further includes a module for sending terminal capability of a UE and a

module for receiving access policy information of an operator, and the network side further

includes a module for receiving the terminal capability of the UE and a module for sending

the access policy information of the operator.

NSN677-1002,

54

[0315] The module for sending the terminal capability of the UE is adapted to send the

terminal capability of the UE to the network side, and the module for receiving the access

policy information of the operator is adapted to receive the access policy information of the

operator sent by the network side.

5 [0316] The module for receiving the terminal capability of the UE is adapted to receive

the terminal capability of the UE sent by the UE, and the module for sending the access

policy information of the operator is adapted to send the access policy information of the

operator to the UE.

[0317] Based on the solutions for user detachment when a handover or change occurs in

10 a heterogeneous network according to the embodiments of the present invention, when the

UE is handed over or switched from the source network on the network side to the target

network on the network side, the source network can detach the UE from the source

network, and the UE can detach the UE from the source network.

[0318] It will be apparent to those skilled in the art that various modifications and

15 variations can be made to the present invention without departing from the scope of the

invention. In view of the foregoing, it is intended that the present invention cover

modifications and variations of this invention provided that they fall within the scope of the

following claims and their equivalents.

20

NSN677-1002,

55

CLAIMS

What is claimed is:

1. A method for user detachment when a handover or change occurs in a

heterogeneous network, comprising:

5 handing over or switching a user equipment (UE) from a source network to a

target network; and

determining, by a network element on a network side, whether to detach the UE

from the source network; if yes, detaching the UE from the source network; otherwise, not

detaching the UE from the source network.

10 2. The method for user detachment when a handover or change occurs in a

heterogeneous network according to claim 1, wherein the source network is a

3rd-generation partnership project (3GPP) network and the target network is a non-3GPP

network; or the source network is a non-3GPP network and the target network is a 3GPP

network.


heterogeneous network according to claim 1, wherein the determining, by the network

element on the network side, whether to detach the UE from the source network comprises:

if it is known that the UE is handed over or switched from the source network to

the target network, determining, by the network element on the network side, to detach the

20 UE from the source network; or


the target network, determining according to terminal capability of the UE: if the terminal

capability of the UE is single radio capability, determining, by the network element on the

network side, to detach the UE from the source network; or

NSN677-1002,

56


the target network, determining according to access policy information of an operator: if the

access policy information of the operator is single radio access, determining, by the network

element on the network side, to detach the UE from the source network; or

5 if it is known that the UE is handed over or switched from the source network to

the target network, determining according to the terminal capability of the UE and the

access policy information of the operator: if the terminal capability of the UE is dual radio

capability and the access policy information of the operator is the single radio access, or if

the terminal capability of the UE is the single radio capability and the access policy

10 information of the operator is dual radio access, or if the terminal capability of the UE is the

single radio capability and the access policy information of the operator is the single radio

access, determining, by the network element on the network side, to detach the UE from the

source network.

4. The method for user detachment when a handover or change occurs in a

15 heterogeneous network according to claim 3, wherein the determining to detach the UE

from the source network further comprises:

if the network element on the network side is a packet data network gateway

(PDN GW), determining, by the PDN GW, whether to delete a default bearer; if yes,

sending a delete bearer request message of the default bearer to a serving gateway (serving

20 GW) of the source network, sending, by the serving GW of the source network, the received

delete bearer request message to a mobility management network element (MME) of the

source network, and detaching, by the MME of the source network, the UE; or

if the network element on the network side is the serving GW of the source

network, sending, by the PDN GW, a binding revocation indication (Ind) message to the

25 serving GW of the source network; determining, by the serving GW of the source network,

whether to delete a default bearer of the UE; if yes, sending a delete bearer request message

of the default bearer to the MME of the source network, and detaching, by the MME of the

NSN677-1002,

57

source network, the UE.


heterogeneous network according to claim 3, wherein:

before determining, by the MME of the source network, to detach the UE, the

5 method further comprises:

sending, by a PDN GW, a delete bearer request message or a binding revocation

Ind message to a serving GW of the source network, and sending, by the serving GW of the

source network, the delete bearer request message to an MME of the source network; or

sending, by the PDN GW, a release bearer request message to the MME of the source

10 network, wherein the release bearer request message indicates that the UE is handed over or

switched from the source network to the target network; and the delete bearer request

message or the binding revocation Ind message includes a cause value indicating a reason

for the UE to be handed over or switched from the source network to the target network;

Or

15 if the network element on the network side is a non-3GPP gateway (non-3GPP

GW), before determining, by the non-3GPP GW of the source network, to detach the UE,

the method further comprises:

sending, by the PDN GW, a binding revocation Ind message to the non-3GPP GW

of the source network; wherein the binding revocation Ind message includes a cause value

20 indicating a reason for the UE to be handed over or switched from the source network to the

target network.


heterogeneous network according to claim 3, wherein the determining to detach the UE


25 if the network element on the network side is a PDN GW, sending, by the PDN

NSN677-1002,

58

GW, a detach request message to an MME of the source network after the PDN GW

determines to detach the UE; or sending, by the PDN GW, a detach request message to a

non-3GPP GW of the source network after the PDN GW determines to detach the UE; or

if the network element on the network side is a serving GW of the source network,

5 sending, by the PDN GW, a binding revocation Ind message to the serving GW of the

source network, and sending, by the serving GW of the source network, a detach request

message to the MME of the source network after the serving GW of the source network

determines to detach the UE; and

receiving, by the MME of the source network or the non-3GPP GW of the source

10 network, the detach request message to detach the UE.




if the network element on the network side is a home subscriber server (HSS),

15 before the HSS determines to detach the UE, the method further comprising:

sending, by a network element on the target network, a register request message

carrying a current access network type of the UE; and sending, by the HSS, a cancel

location to an MME of the source network or a non-3GPP GW of the source network when

the HSS determines that an access network type that the UE registers last time is

20 inconsistent with an access network type that the UE registers this time; and

detaching, by the MME of the source network or the non-3GPP GW of the source

network, the UE.

8. The method for user detachment when a handover or switching occurs in a


25 from the source network further comprises:

NSN677-1002,

59

if the network element on the network side is an MME of the source network or a

non-3GPP GW of the source network, before the MME of the source network or the

non-3GPP GW of the source network determines to detach the UE, the method further

comprising:

5 sending, by the target network, a handover or change complete (HO Complete)

message to the MME of the source network or the non-3GPP GW of the source network.


heterogeneous network according to claim 4, wherein the determining to delete the default

bearer further comprises:

10 determining to delete the default bearer of the UE according to a handover or

change of the UE in an access network: determining whether the UE is handed over or

switched from the source network to the target network, if yes, deleting the default bearer of

the UE; or

determining to delete the default bearer of the UE according to the handover or

15 change of the UE in the access network and the terminal capability of the UE: determining

whether the UE is handed over or switched from the source network to the target network

and whether the terminal capability of the UE is the single radio capability, and if yes,

deleting the default bearer of the UE; or


20 switching of the UE in the access network and the access policy information of the operator:

determining whether the UE is handed over or switched from the source network to the

target network and whether the access policy information of the operator is the single radio

access, and if yes, deleting the default bearer of the UE; or


25 switching of the UE in the access network, the terminal capability of the UE, and the access

policy information of the operator: if the UE is handed over or switched from the source

NSN677-1002,

60

network to the target network, the terminal capability of the UE is the dual radio capability,

and the access policy information of the operator is the single radio access, or if the UE is

handed over or switched from the source network to the target network, the access policy

information of the operator is the dual radio access, and the terminal capability of the UE is

5 the single radio capability, or if the UE is handed over or switched from the source network

to the target network, the terminal capability of the UE is the single radio capability, and the

access policy information of the operator is the single radio access, deleting the default

bearer of the UE.


10 heterogeneous network according to any one of claims 3 to 9, wherein the obtaining the

terminal capability of the UE comprises:

carrying the terminal capability of the UE in an attach request message, a tracking

area update (TAU) request message, a routing area update (RAU) request message, or an

access request message when the UE sends the attach request message, the TAU request

15 message, the RAU request message, or the access request message to the network element

of the source network; and the network element of the source network is the MME of the

source network or the non-3GPP GW of the source network.


heterogeneous network according to any one of claims 3 to 9, wherein the obtaining the

20 terminal capability of the UE further comprises:

sending, by the MME of the source network, a create bearer request message

carrying the terminal capability of the UE to the serving GW of the source network; sending,

by the serving GW of the source network, the create bearer request message or a proxy

binding update message carrying the terminal capability of the UE to the PDN GW; or

25 sending, by the non-3GPP GW of the source network, a proxy binding update message

carrying the terminal capability of the UE to the PDN GW; or

NSN677-1002,

61

sending, by the MME of the source network or the non-3GPP GW of the source

network, an update location request message carrying the terminal capability of the UE to

the HSS.


5 heterogeneous network according to any one of claims 3 to 9, wherein the obtaining the

access policy of the operator further comprises:

notifying, by the MME of the source network, the configured access policy of the

operator to the UE or the HSS or the serving GW of the source network or the PDN GW; or

notifying, by the non-3GPP GW of the source network, the configured access

10 policy of the operator to the UE or the HSS or the PDN GW.


heterogeneous network according to any one of claims 3 to 9, wherein the obtaining the

access policy of the operator further comprises:

notifying, by the HSS, the configured access policy of the operator to the MME of

15 the source network and notifying, by the MME of the source network, the configured access

policy of the operator to the UE or the serving GW of the source network or the PDN GW;

Or

notifying, by the HSS, the configured access policy of the operator to the

non-3GPP GW of the source network and notifying, by the non-3GPP GW of the source

20 network, the configured access policy of the operator to the UE or the PDN GW; or

notifying, by a policy and charging rule function (PCRF) entity, the configured

access policy of the operator to the source network.


heterogeneous network according to any one of claims 3 to 9, wherein the UE notifies the

25 terminal capability of the UE or the access policy of the operator to the source network

NSN677-1002,

62

when a location area of the UE changes and the terminal capability of the UE changes.


heterogeneous network according to claim 6, wherein the detach request message carries a

cause value indicating that the detach request is caused by the handover or switching of the

5 UE from the source network to the target network.

16. A method for user detachment when a handover or change occurs in a

heterogeneous network, comprising:

triggering, by a user equipment (UE), handover or switching from a source

network to a target network; and

10 determining, by the UE, whether to detach the UE from the source network; if yes,

detaching the UE from the source network; otherwise, not detaching the UE from the source

network.


heterogeneous network according to claim 16, further comprising:

15 sending, by the UE, a detach request message to a mobility management entity

(MME) of the source network or a non-3GPP gateway (non-3GPP GW) of the source

network; and

detaching, by the MME of the source network or the non-3GPP GW of the source

network, the UE, after the MME of the source network or the non-3GPP GW of the source

20 network receives the detach request message.


heterogeneous network according to claim 16, wherein after the UE is detached from the

source network, the method further comprises:

setting, by the MME of the source network, a state of the UE to an invalid state.

NSN677-1002,

63


heterogeneous network according to claim 16, wherein the determining, by the UE, whether

to detach the UE from the source network comprises:

deleting bearer resources and mobility management context (MM context) of the

5 source network when the UE knows that the UE is handed over or switched from the source

network to the target network; or

determining whether to detach the UE from the source network according to

terminal capability of the UE when the UE knows that the UE is handed over or switched

from the source network to the target network: if the terminal capability of the UE is single

10 radio capability, deleting bearer resources and MM context of the source network; or

determining whether to detach the UE from the source network according to

access policy information of an operator when the UE knows that the UE is handed over or

switched from the source network to the target network: if the access policy information of

the operator is single radio access, deleting bearer resources and MM context of the source

15 network; or

determining whether to detach the UE from the source network according to the

terminal capability of the UE and the access policy information of the operator when the

UE knows that the UE is handed over or switched from the source network to the target

network: if the terminal capability of the UE is dual radio capability and the access policy

20 information of the operator is the single radio access, or if the terminal capability of the UE

is single radio capability and the access policy information of the operator is dual radio

access, or if the terminal capability of the UE is the single radio capability and the access

policy information of the operator is the single radio access, deleting, by the UE, bearer

resources and MM context of the source network.


heterogeneous network according to claim 17, wherein before the UE sends the detach

NSN677-1002,

64

request message, the method further comprises: determining to send the detach request

message;

the determining to send the detach request message comprises:

determining to send the detach request message according to a handover or

5 switching of the UE in an access network: determining whether the UE is handed over or

switched from the source network to the target network; if yes, determining to send the

detach request message to the MME; or

determining to send the detach request message according to a handover or

switching of the UE in an access network and terminal capability of the UE: if the UE is

10 handed over or switched from the source network to the target network and the terminal

capability of the UE is single radio capability, sending the detach request message to the

MME; or

determining according to the handover or switching of the UE in the access

network and access policy information of the operator: if the UE is handed over or switched

15 from the source network to the target network and the access policy information of the

operator is the single radio access, sending the detach request message to the MME; or

determining to send the detach request message according to the handover or

switching of the UE in the access network, terminal capability of the UE, and access policy

information of the operator: if the UE is handed over or switched from the source network

20 to the target network, the terminal capability of the UE is dual radio capability, and the

access policy information of the operator is single radio access; or if the UE is handed over

or switched from the source network to the target network, the access policy information of

the operator is dual radio access, and the terminal capability of the UE is the single radio

capability; or if the UE is handed over or switched from the source network to the target

25 network, the terminal capability of the UE is the single radio capability, and the access

policy information of the operator is the single radio access, sending the detach request

NSN677-1002,

65

message to the MME.


heterogeneous network according to claim 17, wherein the detach request message carries a

cause value indicating that the detach request is caused by the handover or change of the

5 UE from the source network to the target network.


heterogeneous network according to claim 18, wherein the setting the state of the UE to an

invalid state comprises:

deleting, by the MME of the source network, subscription data information of the

10 UE and MM context of the UE; or

setting, by the MME of the source network, a state of the MME used by the UE to

the invalid state; or

setting, by the MME of the source network, an address of the MME used by the

UE to an invalid value; or

15 setting, by the MME of the source network, a change flag location of the MME

used by the UE to a changed state.

23. A system for user detachment when a handover or change occurs in a

heterogeneous network, comprising a user equipment (UE) and a network side, wherein

the UE is adapted to be handed over or switched from a source network on the

20 network side to a target network on the network side; and

the network side is adapted to handover or changed the UE from the source

network to the target network and to detach the UE from the source network.

24. The system for user detachment when a handover or change occurs in a

NSN677-1002,

66

heterogeneous network according to claim 23, wherein the UE comprises a first handover

or change module and a first detachment module, and the network side comprises a second

handover or change module and a second detachment module;

the first handover or change module is adapted to enable the UE to be handed

5 over or switched from the source network to the target network;

the first detachment module is adapted to detach the UE from the source network;

the second handover or change module is adapted to enable the network side to

hand over or switch the UE from the source network to the target network; and

the second detachment module is adapted to enable the network side to detach the

10 UE from the source network.

25. A device for user detachment when a handover or change occurs in a

heterogeneous network, comprising a second handover or change module and a second

detachment module disposed on a network side; wherein

the second handover or change module is adapted to hand over or switch a user

15 equipment (UE) from a source network on the network side to a target network on the

network side; and

the second detachment module is adapted to detach the UE from the source

network.

26. The device for user detachment when a handover or change occurs in a

20 heterogeneous network according to claim 25, further comprising a second detachment

determination module adapted to determine whether to detach the UE from the source

network, wherein if yes, an initiating instruction is sent to the second detachment module to

initiate the second detachment module.


NSN677-1002,

67

heterogeneous network according to claim 25, further comprising a module for receiving

terminal capability of the UE adapted to receive the terminal capability of the UE sent by

the UE.


5 heterogeneous network according to claim 26, wherein the second detachment

determination module is disposed in a mobility management entity (MME), a packet data

network gateway (PDN GW), a serving Gateway (serving GW), a non-3GPP gateway

(non-3GPP GW), or a home subscriber server/authentication, authorization, and accounting

server (HS S/AAA server).

10 29. The device for user detachment when a handover or change occurs in a

heterogeneous network according to claim 25, further comprising a module for sending

access policy information of an operator adapted to send the access policy information of

the operator to the UE.

30. A device for user detachment when a handover or change occurs in a

15

heterogeneous network, comprising a first handover or change module and a first

detachment module disposed in a user equipment (UE); wherein

the first handover or change module is adapted to hand over or switch the UE

from a source network to a target network; and

the first detachment module is adapted to detach the UE from the source network.


heterogeneous network according to claim 30, further comprising a first detachment

determination module adapted to determine whether to detach the UE from the source

network, wherein if yes, an initiating instruction is sent to the first detachment module to

initiate the first detachment module.


NSN677-1002,

68

heterogeneous network according to claim 30, further comprising a module for sending

terminal capability of the UE adapted to sending the terminal capability of the UE to a

network side.


5

heterogeneous network according to claim 30, further comprising a module for receiving

access policy information of an operator adapted to receive the access policy information of

the operator sent by a network side.

NSN677-1002,

69

ABSTRACT

A method for user detachment when a handover or change occurs in a heterogeneous

network is provided. The method includes: a user equipment (UE) is handed over or

switched from a source network to a target network; a network element on a network side

5 determines whether to detach the UE from the source network, and if yes, the network

element on the network side detaches the UE from the source network, otherwise, the

network element on the network side does not detach the UE from the source network. A

system and a device for user detachment when a handover or change occurs in a

heterogeneous network, and another method for user detachment when a handover or

10 change occurs in a heterogeneous network are also provided. The detachment solutions

achieve the detachment of the UE from the source network and the detachment of the UE

from the source network by the network side when the UE is handed over or switched from

the source network to the target network.

NSN677-1002,

70

1/10

FIG. 1

UE

MMNE

Non-3GPP Serving GW GW

201 Access the 3G1-1-' network ►

PDN GW

HSS/AAA Server

202 UE triggers the handover/

change

2034ccess Request ►

204 Access authentication process

205a Proxy Binding Update 0.

205b Binding Update

I 206a Proxy Binding Ack

206b Binding Ack

207 Access Accept

208 Delete Bearer Request

209 Delete Bearer Response ..-

FIG. 2

NSN677-1002,

UE

Nctwork element on the access

e 301 Attach Request

Servin g GW

PDN GW

isio 308 PCC Rules Pro

309 Create Bearer Response

.310a Reister

71

2/10

10. 302 Authentication process for the UE

303 Update Location

304Insert Subscription data '4

305 Update Location

I-Ack 306 Create Bea er Request

MMNE HSS/ AAA

Server

307 PCC Rules Request

310b Register 311 Attach Accept

312 Bearer establishment request

313 Radio Bearer establishment response

FIG. 4

PCR F

FIG. 3 ervin

H SS/AAA Server

MMNE PDN GW

UE

401TAU/RAU Request •

402 Update Location

403 Insert Subscription data

404 Update Location Ack

405 Update Bearerlftequest

4406a Register

406b Register

407 TAU/RAU Accept I

NSN677-1002,

72

3/10

UE

501Access Request

Non-3GPP GW

authentication

PDN GW

HSS/AAA Server

PCRF

0..

502 Access process

Request ►

503a Proxy Binding Update 0.

504 PCC Rules

503b Binding Update 1.-


505 PCC Rules -4,

Provision

507 PCC Rules Provision

Proxy Binding Ack -4

508a

509 Register -4 N.

508b Binding Ack

511 Access Accept

510 Register -1.-

FIG. 5

NSN677-1002,

73

4/10

UE MMNE Non-3GPP

GW Serving

GW PDN GW

HSS/AAA Server

301 Access network

the 3GPP ..

602 UE the handover/

change

triggers

6033ccess Request

604 Access authentication process 0 4

605a Proxy Binding Update

605b Binding Update

606a Proxy Binding Ack ►

606b Binding Ack

607 Access Accept

608a Delete Bearer .41

Request

608b Delete Bearer Request .416 Binding Revocation

ilnd08b

609a Delete Bearer Response

509b Delete Bearer Response 609b Binding Revocation Ack .

610 Detach Request 4_ _ _ _ _

610 Detach Accept

.-

611 Purge

611 Purge

UE

UE Ack

Field Code Changed

FIG. 6

NSN677-1002,

74

5/10

UE MMNE Non-3GPP

GW Serving

GW PDN GW

HSS/AAA Server

701 Access network

the 3GPP •

702 UE the handover/

change

triggers

703\ccess Request


705a Proxy Binding Updateo.

705b Binding Update

706a Proxy Binding Ack ►

706b Binding Ack .II

707 Access Accept

708a Delete Bearer Request

708b Delete Bearer Reque3 0 8 b Binding

. ndicat ion

Revocation


709b Delete Bearer ResporK9b •.

Binding Revocation ►

Ack

710 710

Purge UE Purge UE Ack

Field Code Changed

FIG. 7

NSN677-1002,

75

6/10

Field Code Changed UE

H SS/AAA Server MMNE

PDN GW

802 UE triggers the ha dover/

change

network

8033ccess Request

the 801 Access

Serving GW

3GPP

Non-3GPP GW


805a Proxy Binding Update„.

05b Binding Update

806a Proxy Binding Ack

806b Binding Ack

807Access Accept -41 808a Detach Request

808b Detach Request

808c Detach Request 8 0 8c Binding Jindication

Revocation

809a Detach Response

809b Detach Response

809c Detach Response • 809c Binding F-revocation Ack

810 Delete Bearer Response

811 Purge UE

811 Purge UE Ack

FIG. 8

NSN677-1002,

76

7/10

UE Non-3GPP

GW PDN GW MMNE

901 Acc ss network

Serving GW

the 3GHP 0

HSS/AAA Server

Field Code Changed

902 UE triggers the ha dover/

change 903%ccess Recquest


905a Proxy Binding Update,.

905b Binding Update


906b Binding k 908 Register

Request 907 Access Accept

909 Register Response

910 Cancel Location

911 Cancel Location Ack

912 Purge UE

912 Purge UE Ack


FIG. 9

NSN677-1002,

8/10

FIG. 10

Field Code Changed Non-3GPP GW

Serving GW

HSS/AAA Server

UE MMNE PDN GW

1001 Access the 3GPP network 110.411

1002 UE triggers the handover

1003 HO Request

1004 Resource Create Procedure

1005 HO Response ..•

1006 HO Command -41

100Access Request

1008 Access Accept

1009 HO Compete ..•

1010 HO Complete Ack r

1011 Purge UE

1011 Purge UE Ack


77

NSN677-1002,

9/11

FIG. 11

UE PDN GW MMNE

HSS/AAA Server

Non-3GPP Serving GW GW


change 1103 Detach Request


1105 Purge UE

1105 Purge UE Ack

1106 Detach Accept I

1107 Access Request

1108 Access Authentication


1109b Binding Update


1110b Binding Ack

1111 Access Accept -411

1101 Access the 3GPP network 0

78

NSN677-1002,

Module for receiving access

policy information of operator

Module for sending terminal capability of UE

First handover module

First detachment module •

First detachment determination

module

UE

Second handover module

Second detachment

module •

Second detachment determination

module

Module for receiving terminal capability of UE

Module for sending access


Network side

79

10/10

FIG. 12

NSN677-1002,

Docket No. HW708564



CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is a continuation of U.S. Patent Application No. 12/479,216, filed on

Jun 5, 2009, which is a continuation of International Application No. PCT/CN2008/071842, filed

on July 31, 2008. The International Application claims priority to Chinese Patent Application

No. 200710137568.8, filed on August 7, 2007. The afore-mentioned patent applications are

hereby incorporated by reference in their entireties.


[0002] The present invention relates to the network communication technology and more

particularly to a method, system, and device for user detachment when a handover or change

occurs in a heterogeneous network.

BACKGROUND

[0003] To improve the competitiveness of networks in the future, a new evolution network is

now researched for a 3rd-generation partnership project (3GPP) network. FIG. 1 is a schematic

structural view of an evolution network system for a 3GPP network. The system includes: an

evolved UMTS terrestrial radio access network (E-UTRAN), for implementing all functions

related to the wireless feature of the evolution network; a mobility management entity (MME),

for mobility management of a control plane, including management of a user context and a

mobility state and allocation of temporary user identities; a serving gateway (serving GW) entity,

for acting as a user plane anchor point between access networks of the 3GPP network for

terminating the E-UTRAN; a packet data network gateway (PDN GW) entity, for acting as a user

anchor point between an access network of the 3GPP network and an access network of a

non-3GPP network, and an interface for terminating the external PDN; a policy and charging rule

function (PCRF) entity, for implementing functions of policy control decision and flow-based

charging control; and a home subscriber server (HSS), for storing subscription information of

1

NSN677-1002,

Docket No. HW708564

users.

[0004] The UMTS terrestrial radio access network (UTRAN) or GSM/EDGE radio access

network (GERAN) implements all functions relevant to the wireless feature of the existing

UMTS/GPRS network; a serving GPRS supporting node (SGSN) implements functions of route

forwarding, mobility management, session management, and user information storage in the

GPRS/UMTS network.

[0005] IP access networks of the non-3GPP network mainly include access networks defined

by non-3GPP network organizations, for example, wireless local area network (WLAN),

worldwide interoperability for microwave access (Wimax), and code division multiple access

(CDMA) network.

[0006] An authentication, authorization, and accounting server (AAA server) mainly


[0007] It should be noted that, the schematic structural view of FIG. 1 is not the only

schematic structural view of the evolution network system for a 3GPP network. The evolution

network of a 3GPP network may have various structures.

[0008] One requirement on the evolution network of a 3GPP network is to realize the

handover or switching of the UE between a 3GPP network and a non-3GPP network. FIG. 2 is a

flow chart of a process that the UE is handed over or switched from a 3GPP network to a

non-3GPP network in the prior art. The process includes the following steps.

[0009] In Step 201, the UE accesses the 3GPP network through a serving GW and a PDN

GW.


belong to the 3GPP network, a non-3GPP GW belongs to the non-3GPP network, and the PDN

GW and HSS/AAA server are common network elements shared by the 3GPP network and the

non-3GPP network.

[0011] In Step 202, the UE triggers the handover or switching from the 3GPP network to the

non-3GPP network.




2

NSN677-1002,

Docket No. HW708564

gateway (EPDG); as for a Wimax system, the non-3GPP GW in this step is an access service

network gateway (ASN GW); and as for a CDMA system, the non-3GPP GW is an access

gateway (AGW).


non-3GPP GW, and the HSS/AAA server, and the non-3GPP GW obtains the PDN GW address

information used by the UE.

[0015] In Step 205a, the non-3GPP GW sends a proxy binding update message to the PDN

GW.


PDN GW is the proxy mobile internet protocol (PMIP). If an interface protocol between the UE

and the PDN GW is the client mobile internet protocol (CMIP), Step 205a is replaced by Step

205b, in which the UE sends a binding update message to the PDN GW.

[0017] In Step 206a, the PDN GW sends a proxy binding acknowledgement message to the

non-3GPP GW.

[0018] In this step, it is assumed that the interface protocol between the non-3GPP GW and

the PDN GW is the PMIP. If the interface protocol between the UE and the PDN GW is the

CMIP, Step 206a is replaced by Step 206b, in which the PDN GW sends a binding Ack message

to the UE.


[0020] In Step 208, the PDN GW sends a delete bearer request message to the serving GW,

and the serving GW sends the delete bearer request message to the MME.

[0021] In Step 209, the MME deletes bearer resources related to the UE, returns a delete

bearer response message to the serving GW, and the serving GW returns the delete bearer



switched from a 3GPP network to a non-3GPP network. Certainly, the handover or change

process is not limited to the above descriptions. A 3GPP network involved in the handover or

change may be GERAN, UTRAN, or EUTRAN. A non-3GPP network involved in the handover

or change may be WLAN, Wimax, or CDMA system.

[0023] Once the UE accesses a 3GPP network, the 3GPP network creates bearer resources of

3

NSN677-1002,

Docket No. HW708564

the UE and a mobility management context of the UE. The mobility management context of the

UE exists in the MME. Furthermore, bearer resources of a 3GPP network and a mobility

management context of a 3GPP network are also created in the UE. Therefore, when the UE is

handed over or switched from a 3GPP network to a non-3GPP network, user detachment needs to

be performed to save network resources. The user detachment includes detachment of the 3GPP

network and detachment of the UE. The detachment of the 3GPP network indicates that the

3GPP network deletes the bearer resources of the UE and the mobility management context of

the UE, and the detachment of the UE indicates that the UE deletes the bearer resources of the

3GPP network and the mobility management context of the 3GPP network. Here, the mobility

management context of the UE exists in the MME.

[0024] However, in the process shown in FIG. 2, when the UE is handed over or switched

from a 3GPP network to a non-3GPP network, the 3GPP network merely deletes the bearer

resources of the UE, but does not delete the mobility management context of the UE, and

meanwhile, the UE does not delete the bearer resources and mobility management context of the

3GPP network as well.

[0025] As known from the above that, the prior art neither provides a method for 3GPP

network detachment when the UE is handed over or switched from a 3GPP network to a

non-3GPP network, nor provides a specific method for user detachment of the UE when the UE

is handed over or switched from a 3GPP network to a non-3GPP network. That is to say, no

specific solution for user detachment when handover or change occurs in a heterogeneous

network is provided in the prior art.

[0026] In addition, if the UE has a single radio capability, that is, the UE can access only one

network, after the UE is handed over or switched from a 3GPP network to a non-3GPP network,

user detachment needs to be performed, that is, the 3GPP network needs to detach the UE, and

the UE needs to be detached from the 3GPP network. The detaching, by the 3GPP network, the

UE includes that the 3GPP network deletes the bearer resources of the UE on the 3GPP network

side, and the mobility management context of the UE in the MME. The detaching, by the UE,

from the 3GPP network includes that the UE deletes the bearer resources and mobility

management context created when the UE accesses the 3GPP network.

[0027] If the UE has a dual radio capability, that is, the UE can access two networks at the

4

NSN677-1002,

Docket No. HW708564

same time, after the UE is handed over or switched from a 3GPP network to a non-3GPP

network, it is judged whether the 3GPP network needs to detach the UE according to, for

example, information of operator policies. In other words, the prior art does not provide a

solution for determining whether to perform the user detachment when the UE is handed over or

switched from a 3GPP network to a non-3GPP network.

[0028] To sum up, during researches and applications, the inventor(s) of the present invention

finds that the prior art has at least the following problems: the prior art neither provides a specific

solution for user detachment when a handover or change occurs in a heterogeneous network, nor

provides a solution for judging whether to perform user detachment when handover or change

occurs in a heterogeneous network.

SUMMARY

[0029] An embodiment of the present invention provides a method for detaching a user when

a handover or change occurs in a heterogeneous network.

[0030] An embodiment of the present invention further provides another method for detaching

a user when a handover or change occurs in a heterogeneous network.

[0031] An embodiment of the present invention provides a system for detaching a user when a

handover or change occurs in a heterogeneous network.

[0032] An embodiment of the present invention provides a device for detaching a user when a

handover or change occurs in a heterogeneous network.

[0033] An embodiment of the present invention further provides a device for detaching a user


[0034] A method for detaching a user when handover or change occurs in a heterogeneous



[0036] Next, a network element on a network side determines whether to detach the UE from

the source network; if yes, the UE is detached from the source network.

[0037] Another method for user detachment when a handover or change occurs in a


5

NSN677-1002,

Docket No. HW708564

[0038] First, a UE triggers handover or switching from a source network to a target network.

[0039] Next, the UE determines whether to be detached from the source network; if yes, the

UE is detached from the source network.

[0040] A system for user detachment when a handover or change occurs in a heterogeneous

network includes a UE and a network side.


network side to a target network on the network side.


the target network, and detach the UE from the source network.

[0043] A device for detaching a user when a handover or change occurs in a heterogeneous

network includes a second handover or change module and a second detachment module on a

network side.

[0044] The second handover or switching module is adapted to hand over or switch a UE from

a source network on the network side to a target network on the network side.

[0045] The second detachment module is adapted to detach the UE from the source network.

[0046] A device for detaching a user when a handover or change occurs in a heterogeneous

network includes a first handover or change module and a first detachment module in a UE.

[0047] The first handover or change module is adapted to hand over or switch the UE from a

source network to a target network;

[0048] The first detachment module is adapted to detach the UE from the source network.

[0049] As known from the above solutions that, in the embodiments of the present invention,

when a handover or change occurs in the heterogeneous network, the UE is detached from the

source network after being determined by the source network or the UE is detached from the

source network after being determined by the UE. Thus, detachment of the user is realized by the

source network or the UE, when the handover or change occurs in the heterogeneous network.


[0050] FIG. 1 is a schematic structural view of an evolution network system for a 3GPP

network in the prior art;

6

NSN677-1002,

Docket No. HW708564

[0051] FIG. 2 is a flow chart of a process that the UE is handed over or switched from a 3GPP

network to a non-3GPP network in the prior art;


terminal capability of UE and access policy information of an operator when the UE accesses the

3GPP network according to an embodiment of the present invention;



terminal capability of the UE changes according to an embodiment of the present invention;

[0054] FIG. 5 is a flow chart of a process that a network element in a non-3GPP network

acquires terminal capability of UE and access policy information of an operator when the UE

accesses the non-3GPP network according to an embodiment of the present invention;

[0055] FIG. 6 shows a first example of a method for user detachment when a handover or

change occurs in a heterogeneous network according to an embodiment of the present invention;

[0056] FIG. 7 shows a second example of the method for user detachment when a handover or


[0057] FIG. 8 shows a third example of the method for user detachment when a handover or


[0058] FIG. 9 shows a fourth example of the method for user detachment when a handover or


[0059] FIG. 10 shows a fifth example of the method for user detachment when a handover or


[0060] FIG. 11 shows a sixth example of the method for user detachment when a handover or


and

[0061] FIG. 12 is a schematic structural view of a system for user detachment when a


present invention.

7

NSN677-1002,

Docket No. HW708564



invention more comprehensible, the present invention is described in detail below with reference

to the accompanying drawings and embodiments.

[0063] FIGS. 6-10 respectively show the first to fifth examples of a method for user

detachment when a handover or change occurs in a heterogeneous network according to an

embodiment of the present invention. The main ideas of the examples are described as follows:


source network determines whether to detach the UE from the source network; if yes, the UE will

be detached from the source network; otherwise, the UE will not be detached from the source

network.

[0065] FIG. 11 shows a sixth example of a method for user detachment when a handover or

change occurs in a heterogeneous network according to an embodiment of the present invention.

The main idea of this example is described as follows.

[0066] The UE triggers a handover or switching from a source network to a target network;

the UE determines whether to be detached from the source network; if yes, the UE will be

detached from the source network; otherwise, the UE will not be detached from the source

network.

[0067] The two networks involved in the handover or change in the heterogeneous network

according to the embodiments of the present invention may be one of the 3GPP networks (such

as a GERAN network, a UTRAN network, or an EUTRAN network) and one of the non-3GPP

networks (such as a WLAN network, Wimax network, or CDMA network). Specifically, the

embodiments include the handover or switching of the UE from a 3GPP network to a non-3GPP

network or the handover or switching of the UE from a non-3GPP network to a 3GPP network.

Here, the network where the UE originally exists during the handover or change process is

referred to as the source network, and the other network involved in the handover or change

process is referred as the target network.

[0068] Then, the handover or switching from a 3GPP network to a non-3GPP network is taken

as an example to illustrate the first embodiment to the sixth embodiment of the method for UE

8

NSN677-1002,

Docket No. HW708564

detachment when a handover or change occurs in the heterogeneous network of the present

invention.

[0069] The UE and the network element in the 3GPP network acquire the terminal capability

of the UE, and the network element obtains access policy information of the operator, which are

provided for being used in the solution for UE detachment when the UE is handed over or

switched from the 3GPP network to the non-3GPP network according to the embodiments of the

present invention. Here, FIGS. 3 and 4 are used to illustrate the process that the network element

in a 3GPP network acquires the terminal capability of the UE and the access policy information

of the operator according to the embodiments of the present invention. FIG. 3 is a flow chart of a

process that a network element in a 3GPP network acquires terminal capability of UE and access

policy information of an operator when the UE accesses the 3GPP network. FIG. 4 is a flow chart

of a process that a network element in a 3GPP network acquires terminal capability of UE and

access policy information of an operator when a location area or terminal capability of the UE

changes after the UE accesses the 3GPP network according to an embodiment of the present

invention.

[0070] Referring to FIG. 3, the process that the network element in the 3GPP network acquires

the terminal capability of the UE and the access policy information of the operator when the UE

accesses the 3GPP network includes the following steps.

[0071] In step 301, the UE sends an attach request message carrying terminal capability of the

UE to the MME.

[0072] In this step, if the access network of the UE is GERAN/UTRAN, the SGSN serves as

the MME; if the access network of the UE is EUTRAN, the MME serves as the MME.

[0073] In this step, the terminal capability of the UE is represented by information element (IE)

of the radio capability supported by the UE. The radio capability supported by the UE is a single

radio capability (which indicates that the UE can access only one network at a certain time point)

or a dual radio capability (which indicates that the UE can access two or more networks at a

certain time point). An exemplary structure of the IE carrying the radio capability supported by

the UE is listed as follows. The IE includes a radio capability parameter supported by the UE.

The parameter may be: 1) the UE has a single radio capability; 2) the UE has a dual radio

capability.

9

NSN677-1002,

Docket No. HW708564






[0074] In step 302, the UE, the MME, and the HSS/AAA server implement an authentication

process of the UE to authenticate the UE.

[0075] In step 303, if the MME finds that the UE is in an invalid state, the MME sends an

update location message to the HSS/AAA server, and registers the UE with the HSS/AAA server.

The update location message carries the terminal capability of the UE.


the update location request may carry the access policy information of the operator. The access

policy information of the operator includes: 1) a single radio access, that is, the UE can access

only one access network at a certain time point; and 2) a dual radio access, that is, the UE can

access a plurality of access networks at a certain time point.



in the HSS/AAA server, the HSS/AAA server carries the access policy information of the

operator in the subscription data, and sends the subscription data to the MME.

[0079] In step 305, the HSS/AAA server returns an update location Ack message to the MME.

[0080] In Step 306, the MME sends a create bearer request message to the serving GW, and

the serving GW sends the create bearer request message to the PDN GW.

[0081] In this step, the MME initiates a default bearer establishment process, so as to create a

default bearer of the UE in the MME, serving GW, and PDN GW. The create bearer request

message further carries a bearer type IE. The MME uses the bearer type IE to notify the created

10

NSN677-1002,

Docket No. HW708564

bearer type to the serving GW and the PDN GW. If the MME sets the bearer type IE to default

bearer, the serving GW and the PDN GW are notified that the created bearer is a default bearer.


operator are carried in the create bearer request message and sent to the serving GW and the PDN

GW.

[0083] Steps 307 and 308 are performed only when the policy and charging rules used by the

default bearer need to be obtained from the PCRF, and the access policy information of the

operator is configured in the PCRF.

[0084] In step 307, the PDN GW sends a PCC rules request message to the PCRF to obtain the

policy and charging rules used by the default bearer.

[0085] In step 308, the PCRF returns a PCC rules provision message to the PDN GW, and the

PCC rules provision message carries the access policy information of the operator.

[0086] In step 309, the PDN GW and the serving GW create a bearer context, and sets the

created bearer as the default bearer; the PDN GW returns a create bearer response message to the

serving GW, and the serving GW returns the create bearer response message to the MME.

[0087] If the access policy information of the operator is configured in the PCRF entity, or the

access policy information of the operator is configured in the PDN GW, or the access policy

information of the operator is configured in the serving GW, this step includes the following: the

create bearer response message carries the access policy information of the operator configured

by the PCRF, the PDN GW, or the serving GW.

[0088] In this step, the bearer context created by the PDN GW and the serving GW includes

bearer type information, which has two values: default bearer and dedicated bearer. For the

default bearer, the PDN GW and the serving GW set the bearer type information in the bearer

context to default bearer. The PDN GW and the serving GW may know that the created bearer is

a default bearer in the following two manners.

[0089] 1) In step 306, the MME carries the bearer type IE in the create bearer request message,

and notifies the bearer type to the serving GW and the PDN GW through the bearer type IE. If

the carried bearer type IE set by the MME is in the value of default bearer, the created bearer is

the default bearer.

[0090] 2) The serving GW and the PDN GW determine whether the created bearer is the first

11

NSN677-1002,

Docket No. HW708564

bearer created in the packet data network (PDN); if yes, the serving GW and the PDN GW

determine that the created bearer is a default bearer.

[0091] Other bearers are dedicated bearers. In this case, the serving GW and the PDN GW set

the bearer type information in the bearer context to dedicated bearer.

[0092] Step 310a is performed only when the access network type (RAT type) information in

the 3GPP network has been registered with the HSS/AAA server by the MME.

[0093] In step 310a, the MME registers access situations of the UE in the 3GPP network (for

example, the RAT type used by the UE) with the HSS/AAA server.

[0094] Step 310b is performed only when the RAT type information of the UE in the 3GPP

network has been registered with the HSS/AAA server by the PDN GW.

[0095] In step 310b, the PDN GW registers the access situations of the UE in the 3GPP

network (for example, the RAT type used by the UE) with the HSS/AAA server.

[0096] Through this step, the HSS/AAA server obtains the access network situations of the

UE. For example, in this embodiment, the HSS/AAA server knows that the RAT type of the UE

is a 3GPP network type, or a specific network type in a 3GPP network.


[0098] 1) The RAT type of the UE is categorized into a 3GPP network and a non-3GPP

network.

[0099] 2) The RAT type of the UE is a specific network type used by the UE, for example,

GERAN network, UTRAN network, EUTRAN network, WLAN network, Wimax network,

CDMA network, etc.

[0100] In Step 311, the MME returns an Attach Accept message to a network element on an

access side, and the Attach Accept message carries information of the radio bearer to be

established by the UE.

[0101] As for the EUTRAN access network, the network element on the access side is

ENodeB; as for the UTRAN access network, the network element on the access side is RNC; as

for the GERAN access network, the network element on the access side is BSS. The MME may

carry the access policy information of the operator in the Attach Accept message.

[0102] In step 312, the network element on the access side sends a bearer establishment

request message to the UE, and requests the UE to establish a radio bearer. The message carries

12

NSN677-1002,

Docket No. HW708564

the access policy information of the operator sent by the MME.

[0103] The access policy information of the operator may also be notified to the UE in a


[0104] In step 313, the UE establishes the bearer context, sets the created bearer to a default

bearer, and returns a radio bearer establishment response message to the network element on the

access side.

[0105] The UE adds bearer type information to the established bearer context, and the bear

type has the following two values: default bearer and dedicated bearer. For the default bearer, the

UE sets the bearer type information in the bearer context to default bearer. The bearer type added

to the established bearer context by the UE may be acquired through the following manners.

[0106] 1) In step 311, the MME carries a bearer type IE in the Attach Accept message, and

notifies the bearer type to the UE by the network element on the access side through the bearer

type IE. For the default bearer, the value of the bearer type IE carried by the MME is Default

Bearer.

[0107] 2) The UE determines whether the created bearer is the first bearer created in the PDN;

if yes, the UE determines that the created bearer is a default bearer.

[0108] Other bearers are dedicated bearers. In this case, the UE sets the bearer type

information in the bearer context to dedicated bearer.


configured in different entities or in a same entity. If the HSS and the AAA server are configured

in different entities, the register message sent by the PDN GW in step 310a is forwarded to the

HSS by the AAA server, and the register message sent by the MME in step 310b is forwarded to

the AAA server by the HSS.



terminal capability of the UE changes. The process includes the following steps.


(TAU/RAU request) message carrying changed terminal capability of the UE to the MME.

[0112] If the access network of the UE is GERAN/UTRAN, the message sent by the UE is the

RAU request message; if the access network of the UE is EUTRAN, the message sent by the UE

13

NSN677-1002,

Docket No. HW708564

is the TAU request message.

[0113] The terminal capability of the UE is represented by IEs of the radio capability

supported by the UE. The radio capability supported by the UE is a single radio capability (which

indicates that the UE can access only one network at a certain time point) or a dual radio

capability (which indicates that the UE can access two or more networks at a certain time point).

An exemplary structure of the IE carrying the radio capability supported by the UE is listed as

follows. The IE includes a radio capability parameter supported by the UE. The parameter may

be: 1) the UE has a single radio capability; 2) the UE has a dual radio capability.




[0114] In step 402, the MME sends an update location message to the HSS/AAA server, and

registers the UE with the HSS/AAA server, in which the update location message carries the

changed terminal capability of the UE.


the update location request message carries the access policy information of the operator. The

access policy information of the operator includes: 1) a single radio access, that is, the UE can

access only one access network at a certain time point; and 2) a dual radio access, that is, the UE

can access a plurality of access networks at a certain time point.



in the HSS/AAA server, the HSS/AAA server delivers the changed access policy information of

the operator to the MME.

[0118] In Step 404, the HSS/AAA server returns an update location Ack message to the

MME.

14

NSN677-1002,

Docket No. HW708564


operator and the terminal capability of the UE has changed, the MME sends an update bearer

request message to the serving GW, and the serving GW sends the update bearer request message

to the PDN GW, in which the update bearer request message carries the changed access policy

information of the operator and the changed terminal capability of the UE.

[0120] In this step, the changed access policy information of the operator and the changed

terminal capability of the UE are notified to the serving GW and the PDN GW.

[0121] Step 406a is performed only when the RAT type information in the 3GPP network has

been registered with the HSS/AAA server by the MME and the information has changed.

[0122] In Step 406a, the MME registers the access situations of the UE in the 3GPP network


[0123] Step 406b is performed only when the RAT type information in the 3GPP network has

been registered with the HSS/AAA server by the PDN GW and the information has changed.

[0124] In step 406b, if the RAT type information in the 3GPP network has been registered

with the HSS/AAA server by the PDN GW and the information has changed, the PDN GW

registers the access situations of the UE in the 3GPP network (for example, the RAT type used

by the UE) with the HSS/AAA server.

[0125] In step 407, the MME returns a TAU/RAU accept message to the UE, and the MME

may deliver the changed access policy information of the operator to the UE in the TAU/RAU

accept message.

[0126] The changed access policy information of the operator may also be notified to the UE

in a broadcast message of the cell.

[0127] FIG. 4 shows the process that the network element in a 3GPP network acquires the

changed terminal capability of the UE and the changed access policy information of the operator

when the terminal capability of the UE and the access policy information of the operator both

have changed. The process that the network element in the 3GPP network acquires the changed

terminal capability of the UE or the changed access policy information of the operator when the

terminal capability of the UE or the access policy information of the operator has changed is

similar to the process of FIG. 4, which thus is not described in detail here.

[0128] The UE and the network element in a non-3GPP network acquire the terminal

15

NSN677-1002,

Docket No. HW708564

capability of the UE, and the network element acquires the access policy information of the

operator, which are provided for being used in the solution for UE detachment when the UE is

handed over or switched from the non-3GPP network to a 3GPP network according to the

embodiments of the present invention. FIG. 5 is used to illustrate the process that the network

element in a non-3GPP network acquires the terminal capability of the UE and the access policy

information of the operator according to the embodiments of the present invention. FIG. 5 is a

flow chart of a process that a network element in a non-3GPP network acquires terminal

capability of UE and access policy information of an operator when the UE accesses the

non-3GPP network.

[0129] Referring to FIG. 5, the process that the network element in the non-3GPP network

acquires the terminal capability of the UE and the access policy information of the operator when

the UE accesses the non-3GPP network includes the following steps.

[0130] In step 501, the UE sends an access request message carrying the terminal capability of

the UE to a non-3GPP GW.

[0131] In this step, if the non-3GPP network is a WLAN network, the non-3GPP GW is an

EPDG; if the non-3GPP network is a Wimax network, the non-3GPP GW is an ASN GW; and if

the non-3GPP network is a CDMA network, the non-3GPP GW is an AGW.


capability supported by the UE. The radio capability supported by the UE is a single radio

capability (which indicates that the UE can access only one network at a certain time point) or a

dual radio capability (which indicates that the UE can access two or more networks at a certain

time point). An exemplary structure of the IE carrying the radio capability supported by the UE is

listed as follows. The IE includes a radio capability parameter supported by the UE. The

parameter may be: 1) the UE has a single radio capability; 2) the UE has a dual radio capability.




16

NSN677-1002,

Docket No. HW708564

[0133] In step 502, an authentication process is performed between the UE, the non-3GPP GW,

and the HSS/AAA server.


non-3GPP GW, an access authentication message may carry the access policy information of the

operator to the HSS/AAA server. The access policy information of the operator includes: 1) a

single radio access, that is, the UE can access only one access network at a certain time point;

and 2) a dual radio access, that is, the UE can access a plurality of access networks at a certain

time point. In this step, if the access policy information of the operator is configured in the

HSS/AAA server, the access authentication message may carry the access policy information of

the operator to the non-3GPP GW.

[0135] In step 503a, the non-3GPP GW sends a proxy binding update message to the PDN

GW.


PDN GW is the proxy mobile internet protocol (PMIP). If an interface protocol between the UE

and the PDN GW is the client mobile internet protocol (CMIP), step 503a is replaced by step

503b, in which the UE sends a binding update message to the PDN GW.


operator may be carried in the proxy binding update message or the binding update message and

sent to the PDN GW.

[0138] In step 504, if the policy and charging rules used by the UE need to be obtained from

the PCRF, the PDN GW sends a PCC rules request message to the PCRF to obtain the policy and



charging rules used by the UE to the PDN GW. If the access policy information of the operator is

configured in the PCRF, the PCRF transmits the access policy information of the operator to the

PDN GW via the PCC rules provision message.

[0140] In step 506, if the policy and charging rules used by the UE need to be obtained from

the PCRF, the non-3GPP GW sends a PCC rules request message to the PCRF to obtain the

policy and charging rules used by the UE.

17

NSN677-1002,

Docket No. HW708564


charging rules used by the UE to the non-3GPP GW. If the access policy information of the

operator is configured in the PCRF, the PCRF transmits the access policy information of the

operator to the non-3GPP GW via the PCC rules provision message.

[0142] In step 508a, the PDN GW sends a proxy binding Ack message to the non-3GPP GW.

[0143] In this step, it is assumed that the interface protocol between the non-3GPP GW and

the PDN GW is the PMIP. If the interface protocol between the UE and the PDN GW is the

CMIP, step 508a is replaced by step 508b, in which the PDN GW sends a binding Ack message

to the UE.

[0144] In step 509, if the RAT type information in the non-3GPP network is registered with

the HSS/AAA server by the PDN GW, the PDN GW registers the access situations of the UE in

the non-3GPP network (for example, the RAT type used by the UE) with the HSS/AAA server.

[0145] In step 510, if the RAT type information in the non-3GPP network is registered with

the HSS/AAA server by the non-3GPP GW, the non-3GPP GW registers the access situations of

the UE in the non-3GPP network (for example, the RAT type used by the UE) with the

HSS/AAA server.

[0146] Through step 509 or step 510, the HSS/AAA server obtains the access network

situations of the UE. For example, in this embodiment, the HSS/AAA server knows that the RAT

type of the UE is a non-3GPP network type, or a specific network type in the non-3GPP network.

This step is optional.

[0147] The RAT type used by the UE may be processed through the following two manners.

[0148] 1) The RAT type used by the UE is categorized into a 3GPP network and a non-3GPP

network.

[0149] 2) The RAT type used by the UE is a specific network type used by the UE, for

example, a GERAN network, a UTRAN network, an EUTRAN network, a WLAN network,

Wimax network, or a CDMA network.

[0150] In step 511, the non-3GPP GW returns an access accept message to the UE. The

non-3GPP GW may carry the access policy information of the operator in the access accept

message.


18

NSN677-1002,

Docket No. HW708564

configured in different entities or in the same entity. If the HSS and the AAA server are

configured in different entities, the register message sent by the PDN GW in step 509 is

forwarded to the HSS by the AAA server, and the register message sent by the non-3GPP GW in

Step 510 is forwarded to the AAA server by the HSS.

[0152] FIG. 6 shows a first example of a method for detaching a user when a handover or


The method includes the following steps.


[0154] In step 608a, the PDN GW sends a delete bearer request message to the serving GW,

and then the serving GW sends the received delete bearer request message to the MME, and adds

a cause IE in the delete bearer request message to indicate the reason of the deletion, and the

MME deletes the bearer resources.

[0155] In this step, as for the bearer deletion caused by the handover or switching of the UE


accessing RAT changed from a 3GPP network to a non-3GPP network". As for the bearer

deletion that is not caused by the handover or change, the PDN GW sets the cause IE to other

values. Alternatively, the delete bearer request message sent by the PDN GW does not carry the

cause IE, and in this case, once the MME receives the delete bearer request message sent by the

serving GW, the message is defaulted to be caused by the handover or switching of the UE from

the 3GPP network to the non-3GPP network. In this embodiment, the message carrying the cause

IE is taken as an example.

[0156] In this step, it is assumed that an interface protocol between the PDN GW and the

serving GW is GPRS tunneling protocol (GTP). If the interface protocol between the PDN GW

and the serving GW is the PMIP, step 608a is replaced by step 608b, in which the PDN GW

sends a binding revocation indication message to the serving GW; the cause IE is added to the

binding revocation indication message; the serving GW sends the delete bearer request message

carrying the cause IE sent by the PDN GW to the MME; and the MME deletes the bearer

resources after receiving the delete bearer request message.

[0157] As for the binding revocation indication caused by the handover or switching of the UE


19

NSN677-1002,

Docket No. HW708564

accessing RAT changed from a 3GPP network to a non-3GPP network". As for the bearer

deletion that is not caused by the handover or change, the PDN GW sets the cause IE to other

values. Alternatively, the binding revocation indication message sent by the PDN GW does not

carry the cause IE, and in this case, once the MME receives the delete bearer request message

sent by the serving GW, the message is default to be caused by the handover or switching of the

UE from the 3GPP network to the non-3GPP network. In this embodiment, the message carrying

the cause IE is taken as an example.

[0158] Step 608a or step 608b further includes the following: the MME deletes the bearer

resources after receiving the delete bearer request message. If the MME finds that all bearer

resources of the UE are deleted, the MME further determines whether to delete an MM context

(i.e., detaching the UE from the 3GPP network) and whether to send a detach request message to

the UE. Specifically, the process includes the following circumstances.

[0159] 1) The MME makes the following determination according to the cause IE carried in

the delete bearer request. The MME determines whether the cause IE carried in the received

delete bearer request message is represented as "UE's accessing RAT changed from a 3GPP

network to a non-3GPP network"; if yes, the MME deletes the MM context of the UE, and does

not send the detach request message to the UE; otherwise, the MME sends the detach request

message to the UE and notifies the UE to delete the MM context and the bearer resources of the

3GPP network in the UE.


delete bearer request and the terminal capability of the UE. If the MME determines that the IE

carried in the received delete bearer request message is represented as "UE's accessing RAT

changed from a 3GPP network to a non-3GPP network", and the MME knows that the terminal

capability of the UE is "single radio capability", the MME deletes the MM context of the UE, and

does not send the detach request message to the UE; as for the bearer deletion caused by other

reasons, the MME deletes the MM context of the UE, and sends the detach request message to

the UE. If the MME knows that the terminal capability of the UE is "multi radio capability", the

MME does not delete the MM context of the UE (that is, does not detach the UE from the 3GPP

network).


20

NSN677-1002,

Docket No. HW708564

delete bearer request and the access policy information of the operator. If the MME determines

that the IE carried in the received delete bearer request message is represented as "UE's accessing

RAT changed from a 3GPP network to a non-3GPP network", and the MME knows that the

access policy information of the operator is "single radio access", the MME deletes the MM

context of the UE, and does not send the detach request message to the UE; as for the bearer

deletion caused by other reasons, the MME deletes the MM context of the UE, and sends the

detach request message to the UE. If the MME knows that the access policy information of the

operator is "multi radio access", the MME does not delete the MM context of the UE (that is,

does not detach the UE from the 3GPP network).


delete bearer request, the terminal capability of the UE, and the access policy information of the

operator. If the MME determines that the IE carried in the received delete bearer request message

is represented as "UE's accessing RAT changed from a 3GPP network to a non-3GPP network",

the terminal capability of the UE is "dual radio capability", and the access policy information of

the operator is "single radio access", or if the MME determines that the IE carried in the received

delete bearer request message is represented as "UE's accessing RAT changed from a 3GPP

network to a non-3GPP network", the access policy information of the operator is "multi radio

access", and the terminal capability of the UE is "single radio capability", or if the MME

determines that the IE carried in the received delete bearer request message is represented as

"UE's accessing RAT changed from a 3GPP network to a non-3GPP network", the terminal

capability of the UE is "single radio capability", and the access policy information of the operator

is "single radio access", the MME deletes the MM context of the UE, and does not send the

detach request message to the UE; as for the bearer deletion caused by other reasons, the MME

deletes the MM context of the UE, and sends the detach request message to the UE. If the MME

knows that the terminal capability of the UE is "dual radio capability" and the access policy

information of the operator is "multi radio access", the MME does not delete the MM context of

the UE (that is, does not detach the UE from the 3GPP network).

[0163] In step 609a, the MME returns a delete bearer response message to the serving GW,

and the serving GW returns the delete bearer response message to the PDN GW.

[0164] In this step, the interface protocol between the PDN GW and the serving GW is the

21

NSN677-1002,

Docket No. HW708564

GIP, and if the interface protocol between the PDN GW and the serving GW is the PMIP, Step

609a is replaced by step 609b, in which the MME returns the delete bearer response message to

the serving GW, and the serving GW returns a binding revocation Ack message to the PDN GW.

[0165] In step 610, if the MME sends the detach request message to the UE, the UE deletes

the MM context and the bearer resources after receiving the detach request message, and returns

a Detach Accept message to the MME.


are deleted, the MME sends a purge UE message to the HSS/AAA server, and the HSS/AAA




[0168] In the above embodiment, after step 607, it is determined whether to detach the UE

from the 3GPP network. Specifically, the determination process is described as follows:

according to the handover or change in the access network, or according to the handover or

change of the UE in the access network and the terminal capability of the UE, or according to the

handover or change of the UE in the access network and the access policy information of the

operator, or according to the handover or change of the UE in the access network, the terminal

capability of the UE, and the access policy information of the operator, it is determined whether

to detach the UE from the 3GPP network, which particularly includes the following four

circumstances.

[0169] 1) It is determined whether the UE is handed over or switched from the 3GPP network

to the non-3GPP network; if yes, the MM context and bearer resources used by the UE in the

3GPP network are deleted.


to the non-3GPP network and whether the terminal capability of the UE is "single radio

capability"; if yes, the bearer resources and the MM context used by the UE in the 3GPP network

are deleted.


to the non-3GPP network and whether the access policy information of the operator is "single

radio access"; if yes, the bearer resources and the MM context used by the UE in the 3GPP

22

NSN677-1002,

Docket No. HW708564


[0172] 4) It is determined whether the handover or change of the UE in the access network,

the terminal capability of the UE, and the access policy information of the operator satisfy one of

the following three conditions: 1. the UE is handed over or switched from the 3GPP network to

the non-3GPP network, the terminal capability of the UE is "dual radio capability", and the

access policy information of the operator is "single radio access"; 2. the UE is handed over or

switched from the 3GPP network to the non-3GPP network, the access policy information of the

operator is "multi radio access", and the terminal capability of the UE is "single radio capability";

and 3. the UE is handed over or switched from the 3GPP network to the non-3GPP network, the

terminal capability of the UE is "single radio capability", and the access policy information of the

operator is "single radio access".

[0173] If yes, the bearer resources and the MM context used by the UE in the 3GPP network

are deleted.

[0174] Moreover, the delete bearer request added with the cause IE in step 608 may be

replaced by another message, for example, replaced by a release bearer request message. The

release bearer request message indicates that the reason for deleting the bearer is the handover or

switching of the UE from the 3GPP network to the non-3GPP network; alternatively, the delete

bearer request message sent in step 608 does not carry the reason for deleting the bearer, and

when the UE is handed over or switched from the 3GPP network to the non-3GPP network, a

normal delete bearer request is sent to the MME. In step 608, after receiving the specific message

or the normal delete bearer request message, the MME deletes the bearer resources; and the

operations of the MME after the bearer resources are deleted are similar to the operations of the

MME after receiving the delete bearer request message.

[0175] As for the first embodiment, it should be noted that the detachment method in this

embodiment is also applicable to the handover or switching of the UE from a non-3GPP network

to a 3GPP network.

[0176] In step I, after the UE is handed over or switched to a 3GPP network, the PDN GW

sends the binding revocation indication message to a non-3GPP GW. The message carries the

cause IE indicating the reason for the binding revocation. As for the binding revocation caused by

the handover or switching from the non-3GPP network to the 3GPP network, the PDN GW sets

23

NSN677-1002,

Docket No. HW708564

the cause IE as "UE's accessing RAT changed from a non-3GPP network to a 3GPP network";

and as for the binding revocation that is not caused by the handover or change, the PDN GW sets

the cause IE to other values.

[0177] In step II, the non-3GPP GW deletes the bearer resources after receiving the binding

revocation indication message. If the non-3GPP GW finds that all bearer resources of the UE are

deleted, the non-3GPP GW further determines whether to delete the MM context of the UE (that

is, to detach the UE from the non-3GPP network), which specifically includes the following

circumstances.

[0178] 1) The non-3GPP GW makes the following determination according to the Cause IE

carried in the binding revocation indication message, in which the non-3GPP GW determines

whether the cause IE carried in the binding revocation indication message is represented as "UE's

accessing RAT changed from a non-3GPP network to a 3GPP network"; if yes, the non-3GPP

GW deletes the MM context of the UE, and does not send the detach request message to the UE;

otherwise, the non-3GPP GW sends the detach request message to the UE, and notifies the UE to

delete the MM context and bearer resources of the non-3GPP network in the UE.

[0179] 2) The non-3GPP GW makes the following determination according to the IE carried

in the binding revocation indication message and the terminal capability of the UE, in which if

the non-3GPP GW determines that the IE carried in the received binding revocation indication

message is represented as "UE's accessing RAT changed from a non-3GPP network to a 3GPP

network", and the non-3GPP GW knows that the terminal capability of the UE is "single radio

capability", the non-3GPP GW deletes the MM context of the UE, and does not send the detach

request message to the UE; as for the bearer deletion caused by other reasons, the non-3GPP GW

deletes the MM context of the UE, and sends the detach request message to the UE. If the

non-3GPP GW knows that the terminal capability of the UE is "multi radio capability", the

non-3GPP GW does not delete the MM context of the UE (that is, does not detach the UE from

the non-3GPP network).


in the binding revocation indication message and the access policy information of the operator, in

which if the non-3GPP GW determines that the IE carried in the received binding revocation

indication message is represented as "UE's accessing RAT changed from a non-3GPP network to

24

NSN677-1002,

Docket No. HW708564

a 3GPP network", and the non-3GPP GW knows that the access policy information of the

operator is "single radio access", the non-3GPP GW deletes the MM context of the UE, and does

not send the detach request message to the UE; as for the bearer deletion caused by other reasons,

the non-3GPP GW deletes the MM context of the UE, and sends the detach request message to

the UE. If the non-3GPP GW knows that the access policy information of the operator is "multi

radio access", the non-3GPP GW does not delete the MM context of the UE (that is, does not

detach the UE from the non-3GPP network).


in the binding revocation indication message, the terminal capability of the UE, and the access

policy information of the operator, in which if the non-3GPP GW determines that the IE carried

in the received binding revocation indication message is represented as "UE's accessing RAT

changed from a non-3GPP network to a 3GPP network", the terminal capability of the UE is

"dual radio capability", and the access policy information of the operator is "single radio access",

or if the non-3GPP GW determines that the IE carried in the received binding revocation

indication message is represented as "UE's accessing RAT changed from a non-3GPP network to

a 3GPP network", the access policy information of the operator is "multi radio access", and the

terminal capability of the UE is "single radio capability", or if the non-3GPP GW determines that

the IE carried in the received binding revocation indication message is represented as "UE's

accessing RAT changed from a non-3GPP network to a 3GPP network", the terminal capability


radio access", the non-3GPP GW deletes the MM context of the UE, and does not send the

detach request message to the UE; as for the bearer deletion caused by other reasons, the

non-3GPP GW deletes the MM context of the UE, and sends the detach request message to the

UE. If the non-3GPP GW knows that the terminal capability of the UE is "dual radio capability",

and the access policy information of the operator is "multi radio access", the non-3GPP GW does

not delete the MM context of the UE (that is, does not detach the UE from the non-3GPP

network).

[0182] FIG. 7 shows a second example of the method for user detachment when a handover or



25

NSN677-1002,

Docket No. HW708564


[0184] In step 708a, the PDN GW determines whether to delete the default bearer of the UE; if

yes, the PDN GW sends the delete bearer request message corresponding to the default bearer to

the serving GW, and the serving GW sends the received delete bearer request message to the

MME.



GTP. If the interface protocol between the PDN GW and the serving GW is the PMIP, step 708a

is replaced by step 708b, in which the PDN GW sends the binding revocation indication message

to the serving GW, and the serving GW determines whether to delete the default bearer of the UE;

if yes, the serving GW sends the delete bearer request message corresponding to the default

bearer to the MME, and the MME deletes the MM context and the bearer resources.

[0187] In step 708a or 708b, the PDN GW/serving GW determines whether to delete the

default bearer of the UE in the following manners. The PDN GW/serving GW determines

whether to delete the default bearer of the UE according to the handover or change of the UE in

the access network, or according to the handover or change of the UE in the access network and

the terminal capability of the UE, or according to the handover or change of the UE in the access


change of the UE in the access network, the terminal capability of the UE, and the access policy

information of the operator. The terminal capability of the UE and the access policy information

of the operator are obtained by the network elements according to the flows shown in FIGS. 3

and 4. Specifically, the determination process includes the following circumstances.

[0188] 1) The PDN GW/serving GW determines whether to delete the default bearer of the

UE according to the handover or change of the UE in the access network, in which the PDN

GW/serving GW determines whether the UE is handed over or switched from the 3GPP network

to the non-3GPP network; if yes, the PDN GW/serving GW determines to delete the default

bearer of the UE, and sends the delete bearer request message corresponding to the default bearer

to the MME.


UE according to the handover or change of the UE in the access network and the terminal

26

NSN677-1002,

Docket No. HW708564

capability of the UE, in which the PDN GW/serving GW determines whether the UE is handed

over or switched from the 3GPP network to the non-3GPP network and whether the terminal

capability of the UE is "single radio capability"; if yes, the PDN GW/serving GW determines to

delete the default bearer of the UE, and sends the delete bearer request message corresponding to

the default bearer to the MME.


UE according to the handover or change of the UE in the access network and the access policy

information of the operator, in which the PDN GW/serving GW determines whether the UE is

handed over or switched from the 3GPP network to the non-3GPP network and whether the

access policy information of the operator is "single radio access"; if yes, the PDN GW/serving

GW determines to delete the default bearer of the UE, and sends the delete bearer request

message corresponding to the default bearer to the MME.


UE according to the handover or change of the UE in the access network, the terminal capability

of the UE, and the access policy information of the operator, in which the PDN GW/serving GW

determines whether the handover or change of the UE in the access network, the terminal

capability of the UE, and the access policy information of the operator satisfy one of the




from the 3GPP network to the non-3GPP network, the access policy information of the operator

is "multi radio access", and the terminal capability of the UE is "single radio capability"; and 3.

the UE is handed over or switched from the 3GPP network to the non-3GPP network, the



[0192] If yes, the PDN GW/serving GW determines to delete the default bearer of the UE, and

sends the delete bearer request message corresponding to the default bearer to the MME.

[0193] In step 709a, the MME returns a delete bearer response message to the serving GW,

and the serving GW returns the delete bearer response message to the PDN GW.


27

NSN677-1002,

Docket No. HW708564

GTP. If the interface protocol between the PDN GW and the serving GW is the PMIP, step 709a

is replaced by step 709b, in which the MME returns the delete bearer response message to the

serving GW, and the serving GW returns the binding revocation Ack message to the PDN GW.

[0195] In step 710, if the MME finds that the default bearer of the UE is deleted, the MME

deletes the MM context of the UE (that is, the MME detaches the UE from the 3GPP network).

[0196] If the MME finds that the subscription data and the MM context of the UE are deleted,

the MME sends a purge UE message to the HSS/AAA server, and the HSS/AAA server purges

the record of the UE, and returns a purge UE Ack message to the MME.




[0199] In the above embodiment, the UE is detached after step 707. The detachment process is

as follows: according to the handover or change of the UE in the access network, or according to

the handover or change of the UE in the access network and the terminal capability of the UE, or

according to the handover or change of the UE in the access network and the access policy


network, the terminal capability of the UE, and the access policy information of the operator, the

UE determines whether to perform the detachment, which specifically includes the following

four circumstances.


to the non-3GPP network; if yes, the UE also deletes the default bearer, and deletes the MM

context and bearer resources used by the UE in the 3GPP network (that is, the UE is detached

from the 3GPP network); otherwise, the UE does not delete the default bearer, and does not

delete the MM context used by the UE in the 3GPP network.


to the non-3GPP network and whether the terminal capability of the UE is "single radio

capability"; if yes, the UE also deletes the default bearer, and deletes the MM context and bearer




28

NSN677-1002,

Docket No. HW708564


to the non-3GPP network and whether the access policy information of the operator is "single

radio access" ; if yes, the UE also deletes the default bearer, and deletes the MM context and

bearer resources used by the UE in the 3GPP network (that is, the UE is detached from the 3GPP



[0203] 4) It is determined whether the handover or change of the UE in the access network,










[0204] If yes, the UE deletes the default bearer, and deletes the MM context and bearer




[0205] FIG. 8 shows a third example of the method for user detachment when a handover or




[0207] In step 808a, the PDN GW sends a detach request message to the MME through the

serving GW, and the detach request message carries a cause value represented as "detach because

of UE's accessing RAT changed from a 3GPP network to a non-3GPP network", which indicates

that the detach request message is caused by the handover or switching of the UE from the 3GPP

network to the non-3GPP network.


29

NSN677-1002,

Docket No. HW708564

exists between the PDN GW and the MME, step 808a is replaced by step 808b, in which the

PDN GW sends a Detach Request message to the MME, and the Detach Request message carries

a Cause value represented as "Detach because of UE's accessing RAT changed from a 3GPP

network to a non-3GPP network", indicating that the detach request message is caused by the

handover or change of the UE from the 3GPP network to the non-3GPP network.


replaced by step 808c, in which the PDN GW sends a binding revocation Ind message to the

serving GW, and the serving GW sends the detach request message to the MME, and the detach

request message carries a cause value represented as "detach because of UE's accessing RAT


message is caused by the handover or change of the UE from the 3GPP network to the non-3GPP

network.



handover or change of the UE in the access network, or according to the handover or change of

the UE in the access network and the terminal capability of the UE, or according to the handover

or change of the UE in the access network and the access policy information of the operator, or

according to the handover or change of the UE in the access network, the terminal capability of

the UE, and the access policy information of the operator; if yes, the detach request message is

sent to the MME; otherwise, the process ends. In steps 808a and 808b, the determination is

performed by the PDN GW, and in step 808c, the determination is performed by the serving GW.

Whether to send the detach request message may be determined according to the following

circumstances.

[0211] 1) The PDN GW/serving GW determines whether to send the detach request message

to the MME according to the handover or change of the UE in the access network, in which the

PDN GW/serving GW determines whether the UE is handed over from the 3GPP network to the

non-3GPP network; if yes, the detach request message is sent to the MME; otherwise, the process

ends.


to the MME according to the handover or change of the UE in the access network and the

30

NSN677-1002,

Docket No. HW708564

terminal capability of the UE, in which the PDN GW/serving GW determines whether the UE is

handed over or switched from the 3GPP network to the non-3GPP network and whether the

terminal capability of the UE is "single radio capability"; if yes, the detach request message is

sent to the MME; otherwise, the process ends.


to the MME according to the handover or change of the UE in the access network and the access

policy information of the operator, in which the PDN GW/serving GW determines whether the

UE is handed over or switched from the 3GPP network to the non-3GPP network and whether

the access policy information of the operator is "single radio access"; if yes, the detach request

message is sent to the MME; otherwise, the process ends.


to the MME according to the handover or change of the UE in the access network, the terminal

capability of the UE, and the access policy information of the operator, in which the PDN

GW/serving GW determines whether the handover or change of the UE in the access network,










[0215] If yes, the detach request message is sent to the MME; otherwise, the process ends.

[0216] In step 809a, the MME receives the detach request message, deletes the MM context,

and sends a detach response message to the PDN GW through the serving GW.


exists between the PDN GW and the MME, step 809a is replaced by step 809b, in which the

MME receives the detach request message, deletes the MM context, and directly sends a detach


31

NSN677-1002,

Docket No. HW708564


replaced by step 809c, in which the PDN GW sends the detach response message to the serving

GW, and the serving GW returns a binding revocation Ack message to the PDN GW.




are deleted, the MME sends a purge UE message to the HSS/AAA server, and then the

HSS/AAA server purges the record of the UE, and returns a purge UE Ack message to the MME.



[0222] Step 809 and Step 811 may be performed at any order.



detachment.

[0224] In this embodiment, it should be noted that, the detach request message sent by the

PDN GW or serving GW may not carry the cause value.



network.


network, the PDN GW determines whether to detach the UE from the non-3GPP network and

whether to send the detach request message to the non-3GPP GW, which includes determining

whether to send the detach request message according to the handover or change of the UE in the

access network, or according to the handover or change of the UE in the access network and the

terminal capability of the UE, or according to the handover or change of the UE in the access



information of the operator; if yes, the detach request message is sent to the non-3GPP GW. The

detailed process thereof can be known with reference to the descriptions of the above

embodiment.

32

NSN677-1002,

Docket No. HW708564

[0227] FIG. 9 shows a fourth example of the method for user detachment when a handover or




[0229] In step 908, the PDN GW sends a register request message to the HSS/AAA server,

and the message carries an RAT type of the UE.


[0231] The RAT Type may be a 3GPP network, which indicates that the network that the UE

accesses currently is a 3GPP network; and the RAT Type may be a non-3GPP network, which

indicates that the network that the UE accesses currently is a non-3GPP network.

[0232] The RAT Type of the UE may also be a specific network type, for example, GERAN,

UTRAN, or EUTRAN network in the 3GPP networks, or WLAN, Wimax, and CDMA network

in the non-3GPP networks.


[0234] In step 909, the HSS/AAA server returns a register response message to the PDN GW.


registered last time is inconsistent with that of the UE registered this time, the HSS/AAA server

sends a cancel location message to the MME, in which the cancel location message carries a

cause value represented as "Cancel because of UE's accessing RAT changed from a 3GPP

network to a non-3GPP network", indicating that the cancel location is caused by the handover or

switching of the UE from the 3GPP network to the non-3GPP network.

[0236] In this step, before the cancel location message is sent to the MME, the process further

includes that the HSS/AAA server determines whether to send the cancel location message

according to the handover or change of the UE in the access network, or according to the

handover or change of the UE in the access network and the terminal capability of the UE, or

according to the handover or change of the UE in the access network and the access policy


network, the terminal capability of the UE, and the access policy information of the operator; if

yes, the HSS/AAA server sends the cancel location message to the MME; otherwise, the

HSS/AAA server does not send the cancel location message to the MME, and the process ends.

33

NSN677-1002,

Docket No. HW708564

Specifically, the determination process specifically includes the following circumstances.


MME according to the handover or change of the UE in the access network, in which the

HSS/AAA server determines whether the UE is handed over or switched from the 3GPP network

to the non-3GPP network; if yes, the HSS/AAA server sends the cancel location message to the

MME; otherwise, the HSS/AAA server does not send the cancel location message to the MME,

and the process ends.


MME according to the handover or switching of the UE in the access network and the terminal

capability of the UE, in which if the HSS/AAA server determines that the UE is handed over or

switched from the 3GPP network to the non-3GPP network, and the terminal capability of the

UE is "single radio capability", the HSS/AAA server sends the cancel location message to the

MME; if the HSS/AAA server determines that the terminal capability of the UE is "multi radio

capability", the HSS/AAA server does not send the cancel location message to the MME.


MME according to the handover or change of the UE in the access network and the access policy

information of the operator, in which if the HSS/AAA server determines that the UE is handed

over or switched from the 3GPP network to the non-3GPP network, and the access policy

information of the operator is "single radio access", the HSS/AAA server sends the cancel

location message to the MME; if the HSS/AAA server determines that the UE is handed over or

switched from the 3GPP network to the non-3GPP network, and the access policy information of

the operator is "multi radio access", the HSS/AAA server does not send the cancel location

message to the MME.


MME according to the handover or switching of the UE in the access network, the terminal

capability of the UE, and the access policy information of the operator, in which if the HSS/AAA

server determines that the UE is handed over or switched from the 3GPP network to the


policy information of the operator is "single radio access", or if the HSS/AAA server determines

that the UE is handed over or switched from the 3GPP network to the non-3GPP network, the

34

NSN677-1002,

Docket No. HW708564

access policy information of the operator is "multi radio access", and the terminal capability of

the UE is "single radio capability", or if the HSS/AAA server determines that the UE is handed

over or switched from the 3GPP network to the non-3GPP network, the terminal capability of the

UE is "single radio capability", and the access policy information of the operator is "single radio

access", the HSS/AAA server sends the cancel location message to the MME; if the HSS/AAA

server determines that the terminal capability of the UE is "dual radio capability" and the access

policy information of the operator is "multi radio access", the HSS/AAA server does not send the

cancel location message to the MME.

[0241] In step 911, after receiving the cancel location message, the MME deletes the MM

context of the UE, and returns a cancel location Ack message to the HSS/AAA server.


are deleted, the MME sends a purge UE message to the HSS/AAA server, and then the








detachment.


configured in different entities or in a same entity. When the HSS and the AAA server are

configured in different entities, the register request message sent by the PDN GW in step 908 is

forwarded to the HSS through the AAA server, the register response message sent by the HSS in

step 909 is forwarded to the PDN GW through the AAA server, the cancel location message sent

to the MME in step 910 is sent to the MME by the HSS, and the purge UE message sent by the

MME in step 912 is sent to the HSS. The cancel location message sent by the HSS/AAA server

may not carry the cause value.


applicable to the handover or switching of the UE from a non-3GPP network to a 3GPP network.

35

NSN677-1002,

Docket No. HW708564

[0248] In Step I, after the UE is handed over or switched from the non-3GPP network to the

3GPP network, the MME or the PDN GW registers a new RAT Type of the UE with the

HSS/AAA server.

[0249] In Step II, if the HSS/AAA server determines that the RAT type of the UE registered

last time is inconsistent with that of the UE registered this time, the HSS/AAA server determines

whether to send the cancel location message to a non-3GPP GW (to notify the non-3GPP GW to

detach the UE from the non-3GPP network) according to the handover or change of the UE in the

access network, or according to the handover or change of the UE in the access network and the

terminal capability of the UE, or according to the handover or change of the UE in the access



information of the operator. If yes, the HSS/AAA server sends the cancel location message to the

non-3GPP GW. The detailed process thereof can be known with reference to the descriptions of

the above embodiment.

[0250] FIG. 10 shows a fifth example of the method for user detachment when a handover or



[0251] In step 1001, the UE accesses a 3GPP access network through the serving GW and the

PDN GW.

[0252] In step 1002, the UE triggers a handover or switching from the 3GPP network to the

non-3GPP network.

[0253] In step 1003, the MME sends a handover or switching request (HO Request) message

to a non-3GPP GW.

[0254] In this step, as for a WLAN system, the non-3GPP GW is an EPDG; as for a Wimax

system, the non-3GPP GW is an ASN GW; and as for a CDMA system, the non-3GPP GW is an

AGW.

[0255] In Step 1004, the non-3GPP GW performs a resource create procedure.

[0256] In this step, the resource create procedure includes performing the processes of user

authentication and PMIP tunnel binding.


36

NSN677-1002,

Docket No. HW708564

[0258] In step 1006, the MME sends an HO command message to the UE, and commands the

UE to hand over or switch to an access network of the non-3GPP network.

[0259] In step 1007, the UE sends an access request message to the non-3GPP GW, and is

handed over or switched to the non-3GPP network.


[0261] Steps 1001-1008 and the process of the handover or switching of the UE from a 3GPP

network to a non-3GPP network in the prior art implement functions similar to that of steps

201-207 in FIG. 2.


[0263] In step 1010, the MME returns an HO complete Ack message to the non-3GPP GW.

[0264] Step 1010 further includes: determining, by the MME, whether to delete the MM

context of the UE (that is, to detach the UE from the 3GPP network) according to the handover

or change of the UE in the access network, or according to the handover or change of the UE in

the access network and the terminal capability of the UE, or according to the handover or change

of the UE in the access network and the access policy information of the operator, or according to

the handover or change of the UE in the access network, the terminal capability of the UE, and

the access policy information of the operator; if yes, the MME deletes the MM context of the UE;

otherwise, the process ends. Specifically, the determination process includes the following four

circumstances.


handover or change of the UE in the access network, in which if the MME determines that the

UE is handed over or switched from the 3GPP network to the non-3GPP network, the MME

deletes the MM context of the UE; otherwise, the MME does not delete the MM context of the

UE.


handover or change of the UE in the access network and the terminal capability of the UE, in

which if the MME determines that the UE is handed over or switched from the 3GPP network to

the non-3GPP network, and the terminal capability of the UE is "single radio capability", the

MME deletes the MM context of the UE; if the MME determines that the terminal capability of

the UE is "multi radio capability", the MME does not delete the MM context of the UE.

37

NSN677-1002,

Docket No. HW708564


handover or change of the UE in the access network and the access policy information of the

operator, in which if the MME determines that the UE is handed over or switched from the 3GPP

network to the non-3GPP network, and the access policy information of the operator is "single

radio access", the MME deletes the MM context of the UE; if the MME determines that the

access policy information of the operator is "multi radio access", the MME does not delete the

MM context.


handover or change of the UE in the access network, the terminal capability of the UE, and the

access policy information of the operator, in which if the MME determines that the UE is handed

over or switched from the 3GPP network to the non-3GPP network, the terminal capability of the

UE is "dual radio capability", and the access policy information of the operator is "single radio

access", or if the MME determines that the UE is handed over or switched from the 3GPP

network to the non-3GPP network, the access policy information of the operator is "multi radio

access", and the terminal capability of the UE is "single radio capability", or if the MME


network, the terminal capability of the UE is "single radio capability", and the access policy

information of the operator is "single radio access", the MME deletes the MM context of the UE;

if the MME determines that the terminal capability of the UE is "dual radio capability", and the

access policy information of the operator is "multi radio access", the MME does not delete the


[0269] In step 1011, if the MME finds that the subscription data and the MM context of the

UE are deleted, the MME sends a purge UE message to the HSS/AAA server, and then the






[0272] In this embodiment, the UE is detached after Step 1007, and the detailed process

thereof can be known with reference to the descriptions of the third example of the method for

38

NSN677-1002,

Docket No. HW708564

user detachment.



network.



[0275] In step II, the non-3GPP GW determines whether to delete the MM context of the UE

(that is, to detach the UE from the non-3GPP network) according to the handover or change of

the UE in the access network, or according to the handover or change of the UE in the access

network and the terminal capability of the UE, or according to the handover or change of the UE

in the access network and the access policy information of the operator, or according to the

handover or change of the UE in the access network, the terminal capability of the UE, and the

access policy information of the operator; if yes, the non-3GPP GW deletes the MM context of

the UE. The detailed process thereof can be known with reference to the descriptions of the

above embodiment.

[0276] FIG. 11 shows a sixth example of the method for user detachment when a handover or




[0278] In step 1103, the UE sends a detach request message to the MME, and the detach

request message carries a cause value represented as "detach because of UE's accessing RAT


message is caused by the handover or change of the UE from the 3GPP network to the non-3GPP

network.

[0279] In this step, before the UE sends the detach request message to MME, the process

further includes determining whether to detach the UE from the 3GPP network according to the

handover of the UE in the access network, or according to the handover of the UE in the access

network and the terminal capability of the UE, or according to the handover of the UE in the

access network and the access policy information of the operator, or according to the handover of

the UE in the access network, the terminal capability of the UE, and the access policy

39

NSN677-1002,

Docket No. HW708564

information of the operator. If yes, the UE sends the detach request message to the MME;

otherwise, step 1107 is performed. The terminal capability of the UE and the access policy

information of the operator are obtained by the network elements according to the processes of

FIGS. 3 and 4. Specifically, the determination process includes the following circumstances.

[0280] 1) The UE determines whether to detach the UE from the 3GPP network and whether

to send the detach request message to the MME according to the handover or change of the UE in

the access network, in which the UE determines whether the UE is handed over or switched from

the 3GPP network to the non-3GPP network; if yes, the MM context and bearer resources of the

3GPP network in the UE are deleted, and the detach request message is sent to the MME;

otherwise, step 1107 is performed.



the access network and the terminal capability of the UE, in which if the UE determines that the

UE is handed over or switched from the 3GPP network to the non-3GPP network, and the

terminal capability of the UE is "single radio capability", the MM context and the bearer

resources of the 3GPP network in the UE are deleted, and the detach request message is sent to

the MME; if the UE determines that the terminal capability of the UE is "multi radio capability",

the MM context of the 3GPP network in the UE is not deleted (that is, the UE is not detached

from the 3GPP network), the detach request message is not sent to the MME, and step 1107 is

performed.



the access network and the access policy information of the operator, in which if the UE


network, and the access policy information of the operator is "single radio access", the MM

context and the bearer resources of the 3GPP network in the UE are deleted, and the detach

request message is sent to the MME; if the UE determines that the access policy information of

the operator is "multi radio access", the MM context of network in the UE is not deleted (that is,

the UE is not detached from the 3GPP network), the detach request message is not sent to the

MME, and step 1107 is performed.

40

NSN677-1002,

Docket No. HW708564

[0283] 4) The UE determines whether to detach the UE from the 3GPP network according to

the handover or change of the UE in the access network, the terminal capability of the UE, and

the access policy information of the operator, in which if the UE determines that the UE is

handed over or switched from the 3GPP network to the non-3GPP network, the terminal

capability of the UE is "dual radio capability", and the access policy information of the operator

is "single radio access", or if the UE determines that the UE is handed over or switched from the

3GPP network to the non-3GPP network, the access policy information of the operator is "multi

radio access", and the terminal capability of the UE is "single radio capability", or if the UE


network, the terminal capability of the UE is "single radio capability", and the access policy

information of the operator is "single radio access", the MM context and the bearer resources of

the 3GPP network in the UE are deleted, and the detach request message is sent to the MME. If

the UE determines that the terminal capability of the UE is "dual radio capability", and the access

policy information of the operator is "multi radio access", the MM context of the 3GPP network

in the UE is not deleted (that is, the UE is not detached from the 3GPP network), the detach

request message is not sent to the MME, and step 1107 is performed.

[0284] In step 1104, after the MME receives the detach request message, the MME deletes the

MM context of the UE in the MME, initiates a bearer deletion process, and deletes the bearer

resources used by the UE on the 3GPP network side.

[0285] In this step, the bearer resources used by the UE on the 3GPP network side include the

bearer resources used by the UE in the MME, serving GW, and PDN GW.

[0286] In step 1105, if the MME finds that the subscription data and the MM context of the

UE are deleted, the MME sends a purge UE message to the HSS/AAA server, and then the








41

NSN677-1002,

Docket No. HW708564


network.

[0292] When the UE is handed over from the non-3GPP network to the 3GPP network, the

UE determines whether to detach the UE from the non-3GPP network according to the handover

of the UE in the access network, or according to the handover of the UE in the access network

and the terminal capability of the UE, or according to the handover of the UE in the access

network and the access policy information of the operator, or according to the handover of the

UE in the access network, the terminal capability of the UE, and the access policy information of

the operator. If yes, the UE sends the detach request message to the non-3GPP GW. The detailed

process thereof can be known with reference to the description of the above embodiment.

[0293] It should be noted that, in this embodiment, the serving GW and the PDN GW may be

configured in different entities or in the same entity. When the serving GW and the PDN GW are

configured in the same entity, the messages between the serving GW and the PDN GW are

transmitted in the same entity. The HSS and the AAA server may be configured in different

entities or in the same entity. If the HSS and the AAA server are configured in different entities,

the MME sends the purge UE message to the HSS.


handover or change of the UE from the 3GPP network to the non-3GPP network, after the user

detachment, the process may further include: setting, by the MME of the 3GPP, the state of the

UE to an invalid state. Specifically, the process of setting, by the MME of the 3GPP, the state of

the UE to an invalid state is implemented as follows.

[0295] The MME deletes the subscription date information and the MM context of the UE.

[0296] Alternatively, the MME retains the subscription data information of the UE, but sets

the state of the MME used by the UE to an invalid state.

[0297] Alternatively, the state of the MME used by the UE is set to an invalid value.

[0298] Alternatively, the MME retains the subscription data information of the UE, but sets a

change flag location of the MME used by the UE to a changed state.


handover or switching of the UE from the non-3GPP network to the 3GPP network, after the user

detachment, the process may further include: setting, by the non-3GPP GW of the non-3GPP, the

42

NSN677-1002,

Docket No. HW708564

state of the UE to an invalid state. Specifically, the process of setting, by the non-3GPP GW of

the non-3GPP, the state of the UE to an invalid state is implemented as follows.

[0300] The non-3GPP GW deletes the subscription data information and the MM context of

the UE.

[0301] Alternatively, the non-3GPP GW retains the subscription data information of the user,

but sets the state of the non-3GPP GW used by the UE to an invalid state.

[0302] Alternatively, the address of the non-3GPP GW used by the UE is set to an invalid

value.

[0303] Alternatively, a non-3GPP GW retains the subscription data information of the user,

but sets a change flag position of the non-3GPP GW used by the UE to a changed state.

[0304] FIG. 12 shows a system for user detachment when a handover or change occurs in a

heterogeneous network according to an embodiment of the present invention. The system

includes a UE and a network side.


network side to a target network.


the target network to detach the UE from the source network.

[0307] The UE may include a first handover or change module, and the network side may

include a second handover or change module and a second detachment module.

[0308] The first handover or change module is adapted to enable the UE to be handed over or

switched from the source network to the target network.

[0309] The second handover or change module is adapted to enable the network side to hand

over or switch the UE from the source network to the target network.

[0310] The second detachment module is adapted to enable the network side to detach the UE

from the source network.

[0311] Optionally, the UE includes a first detachment module adapted to detach the UE from

the source network.

[0312] Optionally, the UE includes a first detachment determination module and a second

detachment determination module disposed on the network side.

[0313] The first detachment determination module is adapted to determine whether to detach

43

NSN677-1002,

Docket No. HW708564

the UE from the source network, and if yes, an enable instruction is sent to the first detachment

module to enable the first detachment module.

[0314] The second detachment determination module is adapted to determine whether to

detach the UE from the source network, and if yes, an enable instruction is sent to the second

detachment module to enable the second detachment module. The second detachment

determination module may be disposed in a network element on a network side, such as an MME,

a PDN GW, a serving GW, or an HSS/AAA server.

[0315] The UE further includes a module for sending terminal capability of a UE and a

module for receiving access policy information of an operator, and the network side further

includes a module for receiving the terminal capability of the UE and a module for sending the

access policy information of the operator.

[0316] The module for sending the terminal capability of the UE is adapted to send the

terminal capability of the UE to the network side, and the module for receiving the access policy

information of the operator is adapted to receive the access policy information of the operator

sent by the network side.

[0317] The module for receiving the terminal capability of the UE is adapted to receive the

terminal capability of the UE sent by the UE, and the module for sending the access policy

information of the operator is adapted to send the access policy information of the operator to the

UE.

[0318] Based on the solutions for user detachment when a handover or change occurs in a

heterogeneous network according to the embodiments of the present invention, when the UE is

handed over or switched from the source network on the network side to the target network on

the network side, the source network can detach the UE from the source network, and the UE can

detach the UE from the source network.

[0319] It will be apparent to those skilled in the art that various modifications and variations

can be made to the present invention without departing from the scope of the invention. In view

of the foregoing, it is intended that the present invention cover modifications and variations of

this invention provided that they fall within the scope of the following claims and their

equivalents.

44

NSN677-1002,

Docket No. HW708564

CLAIMS

What is claimed is:

1. A method for detaching a user equipment (UE) when a handover from a 3rd generation

partnership project (3GPP) network to a non-3GPP network occurs, comprising:

receiving, by a mobility management entity (MME) of the 3GPP network, a delete bearer

request sent by a serving gateway (GW) of the 3GPP network which carries a cause information

element (IE), wherein the cause IE indicates the UE handovers from the 3GPP network to the

non-3GPP network;

deleting, by the MME, bearer resources of the UE;

detaching, by the MME, the UE from the 3GPP network when all the bearer resources of

the UE are deleted.

2. The method according to claim 1, wherein the cause IE is set to "UE's accessing RAT

changed from a 3GPP network to a non-3GPP network".

3. The method according to claim 2, further comprising:

setting, by a packet data network gateway (PDN GW), the cause IE to "UE' s accessing

RAT changed from a 3GPP network to a non-3GPP network";

sending, by the PDN GW, the delete bearer request message carrying the cause IE to the

serving GW; and

sending, by the serving GW, the delete bearer request message carrying the cause IE to

the MME.

4. The method according to claim 1, wherein detaching, by the MME, the UE from the

3GPP network further comprises:

detaching, by the MME, the UE from the 3GPP network without sending a detach request

message to the UE.

5. The method according to claim 1, comprising:

45

NSN677-1002,

Docket No. HW708564

detaching, by the MME, the UE from the 3GPP network if a terminal capability of the UE

is single radio capability.


detaching, by the MME, the UE from the 3GPP network if access policy information of

an operator is single radio access.


detaching, by the MME, the UE from the 3GPP network if a terminal capability of the UE

is dual radio capability and access policy information of an operator is single radio access; or if

the terminal capability of the UE is single radio capability and the access policy information of

the operator is dual radio access; or if the terminal capability of the UE is the single radio

capability and the access policy information of the operator is the single radio access.

8. A network device, configured to:

receive a delete bearer request sent by a serving gateway (GW) of a 3GPP network when

a handover from the 3GPP network to a non-3GPP network occurs, wherein the delete bearer

request carries a cause information element (IE) which indicates a user equipment handovers

from the 3GPP network to the non-3GPP network;

delete bearer resources of the user equipment; and

detach the UE from the 3GPP network when all the bearer resources of the UE are

deleted.

9. The network device according to claim 8, wherein the cause IE is set to "UE's

accessing RAT changed from a 3GPP network to a non-3GPP network".

10. The network device according to claim 9, wherein the delete bearer request is sent

from a packet data network gateway to the network device via the serving gateway, wherein the

cause IE is set to "UE's accessing RAT changed from a 3GPP network to a non-3GPP network"

by the packet data network gateway.

46

NSN677-1002,

Docket No. HW708564

11. The network device according to claim 8, wherein the network device is configured

to detach the UE from the 3GPP network without sending a detach request message to the UE.

12. The network device according to claim 8, wherein the network device is configured to

detach the UE from the 3GPP network if a terminal capability of the UE is single radio

capability.


detach the UE from the 3GPP network if access policy information of an operator is single radio

access.


detach the UE from the 3GPP network if a terminal capability of the UE is dual radio capability

and access policy information of an operator is single radio access; or if the terminal capability of

the UE is single radio capability and the access policy information of the operator is dual radio

access; or if the terminal capability of the UE is the single radio capability and the access policy

information of the operator is the single radio access.

47

NSN677-1002,

Docket No. HW708564

ABSTRACT

A method for user detachment when a handover or change occurs in a heterogeneous

network is provided. The method includes: a user equipment (UE) is handed over or switched

from a source network to a target network; a network element on a network side determines

whether to detach the UE from the source network, and if yes, the network element on the

network side detaches the UE from the source network. A system and a device for user

detachment when a handover or change occurs in a heterogeneous network, and another method

for user detachment when a handover or change occurs in a heterogeneous network are also

provided.

48

NSN677-1002,

on-KiPP Access

MME E

Serving PDN AAA

Ciateway Gateway Semer

FIG. 1

6IRAN

c:!:!TRAN

1/12

NSN677-1002,

2/12

Non-3GPP GW

UE

4


change

203Access Request

201

MME Serving

GW PDN GW

HSS/AAA Server

Access the 3GPP network



205b Binding Update

206a Proxy Binding Ack 4

206b Binding Ack

207 Access Accept

208 Delete Bearer Request 4 4


FIG. 2

NSN677-1002,

3/12

UE Network

element on the access side

MME Serving GW

PDN GW

HSS/AAA Server

PCRF

301 Attach Request

302 Autientication process for the UE N

303 Update Location


305Update Location Ack 4

306 Create Bearer Request

307 PCC Rules equest

308 PCC Rules 4

309 Create Bearer Response .

310a Register 4

310b Register 4 *

rovisior

311 Attach Accept 4

312 Bearer establishment request 4

313 Radio Bearer establishment response

FIG. 3

NSN677-1002,

UE Serving GW

PDN

GW HSS/AAA

Server MME

401TAU/RAU Request

402 Update Location


404 Update Location

405 Update Bearer Request

4 406a Register

406b Register 4 ►

407 TAU/RAU Accept 4

Ack

4/12

FIG. 4

NSN677-1002,

5/12

UE Non-3GPP GW

501Access Request

PDN GW HSS/AAA

Server PCRF



503b Binding Update






508b Binding Ack

509 Register

510 Register

511 Access Accept

FIG. 5

NSN677-1002,

Non-3GPP GW MME

PDN GW

Serving GW

HS S/ AAA Server

601 Access the 3GPP network 111.-4

UE

4

602 UE triggers the handover/change

6031Access Request

604 Access authentication process 0-4

605aProxy Binding Update

605b Binding Update

606a Proxy Binding Ack 4

606b Binding Ack

4 607 Access Accept

4 608a Delete Bearer Request 4

608b Delete Bearer Request 608b Binding Revocation Ind 4


609b Delete Bearer Response

610 Detach Request 4

610 Detach Accept

609b Binding Revocation Ack

611 Purge UE

611 Purge UE Ack 4-

6/12

FIG. 6

NSN677-1002,

7/12

UE MME Non-3GPP

GW Servin g GW

PDN GW

HSS/AAA Server

701 Access the 3GPP network


703 Access Request



705b Binding Update


706b Binding Ack

707 Access Accept

708a Delete Bearer Request

708b Delete Bearer Request 708b Binding Revocation Indication


709b Delete Bearer Response 709b Binding Revocation Ack

710 Purge UE

710 Purge UE Ack

FIG. 7

NSN677-1002,

8/12

UE MME Non-

3GPP GW Serving

GW PDN GW

HS S/AAA Server


802 UE triggers the handover/ change

803 Access Request

804 Access authenticatio I 6 rocess

805aProxy Binding Update

805b Binding Update


806b Binding Ack

807Access Accept

808a Detacl Request

808b Detach Request

808c4 Detach Req est 808c Binding Revocation Indication

809a Detac Response

809b Detac Response

809c Detach Response 809c Binding Revocation Ack


811 Purge UE

811 Purge UE Ack

FIG. 8

NSN677-1002,

9/12

UE MME Non-3GPP

GW Serving

GW PDN GW

HS S/AAA Server

901 Access the 3GPP network 4

902 UE triggers handover/cha

the ge

903 Access Request

904 Access authentication process 4

905a Proxy Binding Udate

905b Binding Update

906a Proxy 4

Binding Ack

906b Binding Ack 908 Register 4

907 Access Accept Request . 4 909 Register

Response

910 Cancel Location

911 Cancel Location Ack

912

912

Purge UE

Purge UE Ack


FIG. 9

NSN677-1002,

10/12

PDN GW

Serving GW

HSS/AAA Server

UE


MME

Non-3GPP GW

4

1002 UE triggers the handover

1003 HO Request

1004 Resource Create Procedure

1005 HO Response

1006 HO Command

1007 Access Request

1008 Access Accept 4

1009 HO Complete

1010 HO Complete Ack

1011 Purge UE

1011 Purge UE Ack 4-


FIG. 10

NSN677-1002,

MME Non-

3GPP GW Serving

GW PDN GW

HSS/AAA Server

UE



1103 Detach Request


1105 Purge UE

105 Purge UE Ack

1106 Detach Accept

1107 Access Request

1108 Access Authentication •


1109b Binding Update

11 10a Proxy Binding Ack I

1110b Binding Ack

1111 Access Accept

1 1/1 2

FIG. 11

NSN677-1002,

Module for receiving access


First detachment determination

module

Second detachment determination module

Module for sending terminal capability

of UE

Module for receiving terminal capability of

UE

First handover module

First detachment module

•

Second handover module

Second detachment module

•

UE

Module for sending access policy information of

operator

Network side

4

12/12

FIG. 12

NSN677-1002,

IN THE UNITED STATES PATENT AND TRADEMARK OFFICE

Patent Application No.

Confirmation No.

Applicant: WU et al.

Filed: June 27, 2011

TC/AU:

Examiner:

Docket No.: HW708564 (Client Ref. No. 81356140US16)

Customer No.: 77399

Commissioner for Patents P.O. Box 1450 Alexandria, VA 22313-1450

STATEMENT OF PRE-EXAMINATION SEARCH

Dear Sir:

This Pre-Examination Search Document is provided in support of the Petition for

Accelerated Examination filed herewith.

A pre-examination search was conducted involving U.S. patents and patent application

publications, foreign patents documents and non-patent literatures as indicated below. The

results of the search are provided on an Information Disclosure Statement filed concurrently

herewith.

NSN677-1002,

Docket No. HW708564 Statement of Pre-Examination Search

A. PRE-EXAMINATION SEARCH

1. U.S. Field Search:

Classes/Subclasses Searched:

370/331, 370/332, 370/328, 370/352, 709/229, 455/428, 455/436, 455/437,

455/438, 455/439, 455/442, 455/422.1, 455/560

Date Conducted: May 1, 3 - 6, and 10, 2011.

2. Foreign Field of Search:

IPCs Searched:

HO4Q-007/38, HO4Q-007/20, HO4Q-007/00, GO6F-015/16, HO4L-029/06,

HO4W-036/14, HO4L-012/46, HO4W-004/00, HO4L-012/56, HO4L-029/04,

HO4W-036/00

Date Conducted: May 6 and 10, 2011.

3. Database Searches:

3(a). Database Service: WIPS (US)

Files Searched:

Patent scope: Search US patent and application at http://www.wipsglobal.com/

(the years are selected all). In the following searches, the classes are searched in all class

field (.UC.), and the remaining terms are searched in fulltext.

In the following searches, the "*" is a wildcard for a string of any number of

characters.

Search Logic:

(1) Class/Subclass: 370/331

Ll: ((handover* or hand-over* or (hand* adj over) or handoff* or hand-off* or

mov*) and (delet* or releas*) and detach*) and (370/331).uc.

L2: ((handover* or hand-over* or (hand* adj over) or handoff* or hand-off* or

mov*) and bear* and delet* and (3GPP or non-3GPP)) and (370/331).uc.

2

NSN677-1002,



mov*) and delet* and context and (3GPP or non-3GPP)) and (370/331).uc.


mov*) and resourc* and detach*) and (370/331).uc.


mov*) and detach* and (capability or policy)) and (370/331).uc.

L6: (((source or original) and (target or destination)) and network) and (delet* or

releas*) and detach* and (370/331).uc.

L7: (((source or original) and (target or destination)) and network) and delet* and

context and (3GPP or non-3GPP) and (370/331).uc.


bear and (370/331).uc.

L9: ((mobility adj management adj entity) or MME) and (delet* or releas*) and

detach* and (370/331).uc.










3

NSN677-1002,

























4

NSN677-1002,

























5

NSN677-1002,
























6

NSN677-1002,

























7

NSN677-1002,

























8

NSN677-1002,

























9

NSN677-1002,

























10

NSN677-1002,























(12) Class/Subclass: 455/422.1

11

NSN677-1002,



mov*) and (delet* or releas*) and detach*) and (455/422.1).uc.


mov*) and bear* and delet* and (3GPP or non-3GPP)) and (455/422.1).uc.


mov*) and delet* and context and (3GPP or non-3GPP)) and (455/422.1).uc.


mov*) and resourc* and detach*) and (455/422.1).uc.


mov*) and detach* and (capability or policy)) and (455/422.1).uc.


releas*) and detach* and (455/422.1).uc.


context and (3GPP or non-3GPP) and (455/422.1).uc.


bear and (455/422.1).uc.


detach* and (455/422.1).uc.






12

NSN677-1002,
















3(b). Database Service: WIPS (EPO)

Files Searched: Patent scope: Search EPO patent and application at

http:/,/wwwpsglobal.com/(the years are selected all). In the following searches, the

classes are search in the class field, and the remaining terms are searched in all fields of

the EPO patent application and EPO patent database, the "*" is a wildcard for a string of

any number of characters.

Search Logic:

(1) International Patent Classification (IPC): HO4Q-007/38


13

NSN677-1002,


mov*) and (delet* or releas*) and detach*) and (H04Q-007/38).ipc.


mov*) and bear* and delet* and (3GPP or non-3GPP)) and (H04Q-007/38).ipc.


mov*) and delet* and context and (3GPP or non-3GPP)) and (H04Q-007/38).ipc.


mov*) and resourc* and detach*) and (H04Q-007/38).ipc.


mov*) and detach* and (capability or policy)) and (H04Q-007/38).ipc.


releas*) and detach* and (H04Q-007/38).ipc.


context and (3GPP or non-3GPP) and (H04Q-007/38).ipc.


bear and (H04Q-007/38).ipc.


detach* and (H04Q-007/38).ipc.







14

NSN677-1002,

























15

NSN677-1002,











(4) International Patent Classification (IPC): GO6F-015/16


mov*) and (delet* or releas*) and detach*) and (GO6F-015/16).ipc.


mov*) and bear* and delet* and (3GPP or non-3GPP)) and (GO6F-015/16).ipc.


mov*) and delet* and context and (3GPP or non-3GPP)) and (GO6F-015/16).ipc.


mov*) and resourc* and detach*) and (GO6F-015/16).ipc.


mov*) and detach* and (capability or policy)) and (GO6F-015/16).ipc.


releas*) and detach* and (GO6F-015/16).ipc.


16

NSN677-1002,


context and (3GPP or non-3GPP) and (GO6F-015/16).ipc.


bear and (GO6F-015/16).ipc.


detach* and (GO6F-015/16).ipc.

(5) International Patent Classification (IPC): HO4L-029/06


mov*) and (delet* or releas*) and detach*) and (HO4L-029/06).ipc.


mov*) and bear* and delet* and (3GPP or non-3GPP)) and (HO4L-029/06).ipc.


mov*) and delet* and context and (3GPP or non-3GPP)) and (HO4L-029/06).ipc.


mov*) and resourc* and detach*) and (HO4L-029/06).ipc.


mov*) and detach* and (capability or policy)) and (HO4L-029/06).ipc.


releas*) and detach* and (HO4L-029/06).ipc.


context and (3GPP or non-3GPP) and (HO4L-029/06).ipc.


bear and (HO4L-029/06).ipc.


detach* and (HO4L-029/06).ipc.

17

NSN677-1002,


(6) International Patent Classification (IPC): HO4W-036/14


mov*) and (delet* or releas*) and detach*) and (H04W-036/14).ipc.


mov*) and bear* and delet* and (3GPP or non-3GPP)) and (H04W-036/14).ipc.


mov*) and delet* and context and (3GPP or non-3GPP)) and (H04W-036/14).ipc.


mov*) and resourc* and detach*) and (H04W-036/14).ipc.


mov*) and detach* and (capability or policy)) and (H04W-036/14).ipc.


releas*) and detach* and (H04W-036/14).ipc.


context and (3GPP or non-3GPP) and (H04W-036/14).ipc.


bear and (H04W-036/14).ipc.


detach* and (H04W-036/14).ipc.




18

NSN677-1002,

























19

NSN677-1002,

























20

NSN677-1002,

























21

NSN677-1002,

























22

NSN677-1002,


3(c). Database Service: WIPO

Files Searched: Search International Patent Applications at

http://www.wipo.int/pctdb/en/. In the following searches, the classes are search in the

class field, and all remaining terms are searched in any field of the WIPO patent

application database.

Search Logic:


Ll: ((handover* or hand-over* or "hand* over" or handoff* or hand-off* or mov*)

and (delet* or releas*) and detach*) and (H04Q-007/38).ipc.

L2: ((handover* or hand-over* or "hand* over" or handoff* or hand-off* or mov*)

and bear* and delet* and (3GPP or non-3GPP)) and (H04Q-007/38).ipc.


and delet* and context and (3GPP or non-3GPP)) and (H04Q-007/38).ipc.


and resourc* and detach*) and (H04Q-007/38).ipc.


and detach* and (capability or policy)) and (H04Q-007/38).ipc.







L9: ("mobility management entity" or MME) and (delet* or releas*) and detach*

23

NSN677-1002,


and (H04Q-007/38).ipc.



















and (H04Q-007/20).ipc.



24

NSN677-1002,


















and (H04Q-007/00).ipc.

(4) International Patent Classification (IPC): GO6F-015/16


and (delet* or releas*) and detach*) and (GO6F-015/16).ipc.


and bear* and delet* and (3GPP or non-3GPP)) and (GO6F-015/16).ipc.


25

NSN677-1002,


and delet* and context and (3GPP or non-3GPP)) and (GO6F-015/16).ipc.


and resourc* and detach*) and (GO6F-015/16).ipc.


and detach* and (capability or policy)) and (GO6F-015/16).ipc.


releas*) and detach* and (GO6F-015/16).ipc.


context and (3GPP or non-3GPP) and (GO6F-015/16).ipc.


bear and (GO6F-015/16).ipc.


and (GO6F-015/16).ipc.



and (delet* or releas*) and detach*) and (HO4L-029/06).ipc.


and bear* and delet* and (3GPP or non-3GPP)) and (HO4L-029/06).ipc.


and delet* and context and (3GPP or non-3GPP)) and (HO4L-029/06).ipc.


and resourc* and detach*) and (HO4L-029/06).ipc.


26

NSN677-1002,


and detach* and (capability or policy)) and (HO4L-029/06).ipc.








and (HO4L-029/06).ipc.



and (delet* or releas*) and detach*) and (H04W-036/14).ipc.


and bear* and delet* and (3GPP or non-3GPP)) and (H04W-036/14).ipc.


and delet* and context and (3GPP or non-3GPP)) and (H04W-036/14).ipc.


and resourc* and detach*) and (H04W-036/14).ipc.


and detach* and (capability or policy)) and (H04W-036/14).ipc.




27

NSN677-1002,






and (H04W-036/14).ipc.



















28

NSN677-1002,





















and (H04W-004/00).ipc.



29

NSN677-1002,

























30

NSN677-1002,

























31

NSN677-1002,










and (H04W-036/00).ipc.

3(d). Database Service: SIPO

Files Searched:

Search Chinese Patent Applications at http://www.sipo,gov.cnizliil. In the

following searches, all terms are searched in abstract field of the SIPO patent database.

Search Logic:


and (delet* or releas*) and detach*)


and bear* and delet* and (3GPP or non-3GPP))


and delet* and context and (3GPP or non-3GPP))


and resourc* and detach*)


and detach* and (capability or policy))

32

NSN677-1002,



releas*) and detach*


context and (3GPP or non-3GPP)


bear


3(e). Database Service: Google

File Searched:

Google Scholar (Non Patent Literature),

littp://scholar.google.com/advanced scholar search?hi,en&lr.

In the following searches, all terms of keywords are searched in all fields of the

Google Scholar database, wherein the "*" is a wildcard for a strong of any number of

characters.

Search Logic:

Ll: (delet* or releas*) and detach*

L2: delet* and bear

L3: bear* and delet* and (3GPP or non-3GPP)

L4: delet* and context and (3GPP or non-3GPP)

L5: resourc* and detach*

3(f). Database Service: 3GPP

33

NSN677-1002,


File Searched:

3GPP website: http://www.3gpp.org

In the following searches, all terms of are searched in FTP site in Specs field, the

3GPP (3rd Generation Partnership Project) website collects all the protocols of the 3GPP,

wherein the "*" is a wildcard for a strong of any number of characters.

Search Logic:

Ll: (delet* or releas*) and detach*

L2: delet* and bear

L3: bear* and delet* and (3GPP or non-3GPP)

L4: delet* and context and (3GPP or non-3GPP)

L5: resourc* and detach*

34

NSN677-1002,


B. SEARCH DIRECTED TO THE INVENTION

The pre-Examination search was directed to the claimed invention, encompassing

all the features of the claims and giving the claims their broadest reasonable

interpretation.

C. SEARCH DIRECTED TO THE DISCLOSURE

No disclosed features that are unclaimed at this time are currently seen as features

that may be claimed later.

D. SEARCH REPORT FROM FOREIGN PATENT OFFICE

The current U.S. Application is the U.S. national phase application of

international application No. PCT/CN2008/071842. A search report from the Chinese

Patent Office for PCT patent Application No. PCT/CN2008/071842 is provided herewith.

Since the search report was written in Chinese, Application provides an English

translation here.

The search report from the Chinese Patent Office is provided herewith. Since the search

report was written in Chinese, Application provides an English translation here.

The search report from the European Patent Office is provided herewith.

35

NSN677-1002,


PATENT COOPERXTION TREATY

t4.r7z ATIANAL.,,sSEARCHINI3 mumlune To;

PCT AlOP I in)81

1:04"

301.S,Pernale Nikiing,No.17 Road,Efiidian Diatiet,Beijing>PA.,Clim

WRITTEN COMM OF TEM RMENATIONAL SEARCHING AuTuoury

(a :Rai: 43 bisM

BEANOMST) :.PMENT&TRADEMARK AGENT LTD.

20'Nov, 2006 M.1 I.2008) ...................... ..

Si t3

FOR. Atfallitat ACTION

p7f:;iptii$11 2 Wow

...

tr4h1W:SY•

. ...

TWITtc0ii:M4 . a;;;;;;14;:r1 V.....,,••••••

PCTICRZOOSA rTI g4:1 3 ha. 200R,31 20(4) ....... PAkite akStigitatW OKI IN Itigh KtOiv,iS*1 :::$$$s:f2ssXim IN:::

7.;"4

Nitittity t:etitzieotOntio,RMI

07 Aug„ :244)7(07,08,2(Xr1)

Attkii:MIt

HUME1 TECTINOUXIIES CO,,t3D: ...a.aftemaaw wieeeeeee.,,,,,WWWWWWV.

. . . . . . ................... ••••••••••••••••,,,,,,,,,

i.,1„40k0 twtsiot, fsigiogiatio koMag tIto ftibs$Mit

ars No. Omit; of it* ol.M0m Pskxitty

Wit ickf <0003; latigh iky,0-4. otr.t14.yt, Masestats,s;:%,:m.sp 834 tia.intitir.41Arii$oi.iW

0 Itao by ittsittM0o. fj gm. N. iutt.lskAi getV3.<0 SiMkt io4:W..1 MOO* 'nista IA 11xYA*.y,

E.V.itt044P0 attr)i 30;:t: gia•SM`..8 Oge,Sks 40(SiiiegMIS

'ti -eigokin kitM$:0 ttm.*: :1::AraarimtW Cat&i.qt ikarissItktIS Cao ::;:zt•SM•14::::.;•.:4

2. MOVER ALI:10N

If a eMtmoit immoatiottat kmaioimgok i$ made.. Itzi$ »Ilk* $41Z: itv i'ami.iiMmkt NI is. witiett otgt.e ittii$Amikme .ft:Apk.wy iscarnisfi'alg rttliVse") :;gopt tbst thi$ (Itm$ pm. ms$#;$, krVMM witmitt dogkim, at Atailmie, Aim: It10 m$:$f.$M rm4..eso IN:StikOlatSt PEA 00tilk.4 &it A35i0 64idga. wii*ist.oiisiioas of V4 httmlokott.1 SmeM.v A0.10tily br$ mmitImMi.

g.*.,,* 5tmitt•Wt:..%$$$ktm.-$.1. ay tai: a air ttm via Mot of dm: W.gAt,. tt0Argf0tta iii froAtil tai af3 s3f##t R3 C3 }TEAa wig* o414::iis XC s3 F. 0I3giut.titmwri$0, 100 mmAmota,. Imtx$>•.4sk: 4t0eMitoo of '~tom itsg, gamrst 2tnairl dikkUPCTMAt71.$ ,Or WIZet t4itLaht i fed a:;: Alktima Nita Iota,

Ea , .FirtAtc:PCTIWIM.

Por fm4mt sitma,

Mommet oloilicts ottkIntt$ of dm1$:A.K.'..N Am oompirlim oftm$ opitttm Rateritioti offIt.ox

no :slavw..4matils.pmpr:y i maki.zu. xigm wopt

LIE:$.kriezt, actitm, Wait 1 (WM zip'' ms (2u 0.100a) WU Shkaang.

IHOoo$ 6-1.062411507

.rom §-4:.1x..-z:..i,foow rkmaotplia len)

36

NSN677-1002,

Docket No. HW708564

worm ommoN OF WC. INTERN ATIONAL SEARCUING MaittiliTTY

iebrmariomi aggiestiori PCMC.N20(igt071842

RON Na 1 Basis cat3 et opistitel

With iegmi re din hengnnge„ this opinion het: 'bme esisrMisW imh,'

filo inienstinnai .vpliention Ss.t. itwigange iu wh5th 3 is i3 o? a toinsistion tbo itsZterissioniA apPtiottnrs wi!nsib fits Innwsge of a tininiintitnt futnisiral lbs.! tiutpinposen eis.tnntratissnai MX:4 k2 €s} mil 73344

This **isle has. bsssi mssibases I kik? Nft:ANant 'OM radifk**31 3,4 t)bNiVilg :mistake iswsr r writ:41SM. to tiiin Mates:in" mass Rae itg:ii!i& 4iTh1.1(0)

With mgarki to any rantimirle =Nor 30a$81* add ettiosese disclosed is thn international afrfrgi;:sirion and amemnry ris the slairnest ovation ism itana nstriblisisetti on the basis of

o, typo a minicia€ vaputnetlisnsig

oblo:o)MnssrS so tits soltsertas

b .1,mm* of untresiel aaa Tsti:w

0 it dec.tnwtsie form

rr. tb.ite fiiinOrnish44 rtitnintmnisr 66,,itgarratiomil 0p,Ocati4.14 0:5 -Kw

n tppit„,„i!:.b...tuttumgw.,..ow spptination izi 4.es>trorsis', lbws 0 I:jookiku/ s.sabwwaltly Aurbcseisy rho .s-oirposste

g..f;kfia,tya, mat. that aystrO 8hs a..M.B VOSPiri or. ovy 4:xviagm mz:Vot §2.}:ae &vets isak: igesi or oraiii$W, the. nquimei Ntatrilma-$ the information in tip hmmino #s witibirorni tofrim is isininio4 Kt. tsar h. Ors;

splissnisna tiled Er d:**3 DO go boA-soriske appliow•:ion as Oat as! pinta first %tres.: ihrttinheal,

Aingneesi erstonergs:

ftw Tcrex s imm N :€) 21)D7)

Statement of Pre-Examination Search

37

NSN677-1002,


WitVITEN MINION OF TM eftens— doe. INTRRNAstn(riAL igt.AltailiNGAUTUORITY PC.VeN2(3081073. 842

RatosedsteektamtnederRuk43.4iv.10tOrithrtordrantreth„riaihult:ivet(143 ktsi.tanthieii441A1"14tY; 0;0a:et:Sod o?„phmatiosszl sopptsvitat. aattrotot

WeeeeeM

ifionentaku

Mhos 143

Claim Nesna

Ch$hm _2-15: 18-22, :34-23

, 1,- 2, If3* I

Claim None

••••••••••••HAVWV,

i.tat.i.e.ne end *pier:at-ions Rafertme it sevit to tho fallowing .c.Nizrigum RIL2dV402.9663AI ir1Rfe02006:33881441 DI -,:iieeiests a ;settled Mid ChWiffN for 4Witchiel; EkSttfi).xk :41ErIlOO:

fa dis<:Imai a nothod far tetablishing connection iv the hetenkkvmeout 116tVOrit:

1.13 diteltnt,g itethi)d .MM} terrefeal Enr evitching end .r:eletetieg ;irk coutteetice 1e: the. railtiesele 34ate I t y (31)

goolt of tho dia.:mons DI, D3 end DI does rot disclose ell int features to :to oce of tledise I, 1.6, 21 24 and 40 tharafore 2;3 ood; tht critaria set fair in OA KT Assail:le 33(3), ir.tolve ottifeity.

g000rdine;iy, tho depan•rktnt. claim 3-13 of Otis; 1„ the depeadent. €7-22 t3 an* the dettetntitnt claim 24 &:f oiejs* 23, the tte:tasaknt. 0,3e.sd, 26-29 of title aad the depectiattt claim at: claim 30 met the csriterie set telt in the XI' ArticIe 33 (2), involve novnitts„ OTeltriiill }MIKIS)

4octetoot Di diotinaos a ratthnd fce• switthiag attleark seesine (tee the descraptine Put 8, lint 11-vege 44. shim inelssfed taer tan:noel seitohet to a kargat ;IV:A=1*k o &oureo netwo,rc,

serviee melt:ft enntrol wit ,affiges ahat1atr the eetterk toold be suitohed. iii. does not disclose stm.h e feature that a notettek aide unit seperetos the neer terfidttiI from the mina r.etwart.ilowewer, this feature it well-iaown

tht 63.t. It$31:111: On in And the soli-tease technalagp, the 41,1We:et-wetter elais .1 p.4.nrione to filo Allied . ft

par.ean in the art, eta eltifs 1 6Teff3 lltA WIVE the criteria sat oict tha At-ricia 33 (3). dtat net in.,-41re et nsenti.se atm

The adtlitis„aittl„ .feetttre (.4:‘ claim 3 7:5 *NZ:1-.1W= tilt *Nalvt.. 333 14. tit* %/ni'Ant-Nil tfti11101.0..t.Y.

eicife 2 ehich cites- elaits 1 it Oita:16st to the skilled person in the art, tharefera fii itlG 2 dootk aot aatet th.e akqterio set ont tht Article 33 (3), lVot‘";: ?..4S :11EVenti3'V

&It tit*iHSt thsCiotvt Ss s 'si.lcsd far ovitilive rArtAnr.it t:14.30 the description Asp C. lne ..".}age 14, line 14-; fit.awe 4) ehioh .inolzpdes the nser ter.elnal rfiltiZiat?s: tip $WitCh t ti* target. network frail the 3Onrce otfaenis; the .service stitch. teetsvl unit jinitsif nitether the neteorh wralti he estitthed• 4t9t WA Olt:clove oath feettrre '016 Etraiitgli it: separate, f.rott the IIEIMV :hi, f?.zatitre qpirt-icaordo in tho art, ilmod on J a end the well-itfaxst ttwhaoleo, the sahjeat-wotter Ftf el5i% ift Cb'iMiXS V.? Og? ptrson it the ert, aa claim 16 &tee te. Site. tilt irrin3ria. sot out the. PCT Artiote :13 (3), dote not itrpoixt RL ineantiee twA.

'Th aviditionol 11:Ai.M.V i? it eel-iv:0X: '..kht art, ba;Ofi 1).1 end the et13"ktowo tenhhniorf, the ath.:itut-esettex- ef. :anis, 17 eitich cites cIftin 16 if4 OtAdtP.;Zi. EV the et:Ailed. person the 3.):t, therefore claim

e t •f. t Arrt 3), &es otst ifnalse insentive step: 10 e ia ( Tha datment dienitzen &it' fta: twitching fteteur}: settica (ntt the tittveitilisii .nN3e lite 11-

14, lint 14; figure 4), nifich includes: that; the user terminal twitches to the target network free; a scone catenris; the terwite :mita mut or the network tide jtalget whether iha tmtioark wetild ;F•mitthed• dnrz h1A: ffiss<asse ditth iF Tea3:l$33$ that thiE eatiKelf. skit- unit sepetat,tg eat stsor ter:eineI .frm the snerce netoork. fifAeser,

tiiac feaMtra well-kr:owe Ira the att. Used ;so PI end the wel.1--ktem Mtn nub:Nut-atter cinin obwieva to the Allied perm ie the 2Wt., $.3! cloin 23 done not wet the orlterie tot tot tha K3".krticie

33 (3), duee ;:fSi; 1M'OtYt

Pnent i'Cif:SA/237(33;;;MI An :if

38

NSN677-1002,


WRITFEN OPINION OV ME LNTERNATIONALRENRCHINGAUTEMITY

----,-- Intenwiehal .K.903eWee

PCntN2.00S./07184.2

Sapp}omelet Oat

eaee the epe.se s. f. 3i3):' i.tt: the re.c.emling b(me in mkt enPnel.eat.

-Ceetienetion No,. V the. e:5t";..ik-M3t.S. 174: flu, dg$ nikient-mtten of clef= 25 el.el are eot. thvieee to the skilled

pexeen in the art, en then trial a• we, thenritere i-A3t AFfi. a Paartiale 33 (2), ineolre Imentiva atepe.

?p,inse‹.1 to the denasemite. V?. W, the althjeet-eaotter.s. el:elm 24, 24-233 $04 31-3'3

er:e ant aL.c.W.* to. the sktiie.:i wane. la the aieee elenze aett ;M: r)iCt in the PC? Article

leveh,a inventive etews, ImuoTlaI appllability.

an.amon t2 :1:90.3t applleahint a the: invent:inn, e.;.ainn 1-,?;?.meet Cite eriter'le eet el;t le the. PCT Artiele

Rwnr, ldske.,B7(K.Glemeeral Bea-51:43.g 'ZOO?)

39

NSN677-1002,


Partial Translation of First Chinese Office Action of Chinese Application

No. 200710137568.8

Mailing Date: July 17, 2009

1. The Applicant has made amendments to Claim 5 in the amended documents submitted on

June 8, 2009. The amended Claim 5 has disclosed two parallel technical solutions concerning a

handover or change between a 3rd-generation partnership project (3GPP) network and a non-

3GPP network. However, the two parallel technical solutions are not disclosed in the original

claims and specification. In addition, the term "indication information" disclosed in Claim 5 is

not disclosed in the original claims and specification, either. Moreover, the amended technical

solution cannot be directly and undoubtedly obtained from the disclosure of the original claims

and specification. Therefore, the amendments go beyond the scope of the disclosure of the

original claims and specification, and Claim 5 fails to meet the provisions of Article 33 of the

Patent Law of the PRC. The Applicant shall note that, as regards the technical solution "the

network element on the network side is a mobility management entity (MME) of the source

network," the specification has only disclosed that, only when a handover or change occurs from

a 3GPP network to a non-3GPP network and the source network is the 3GPP network, the MME

exists in the source network, and moreover, it is a "cause information element (IE)" that indicates

a user equipment (UE) is handed over or switched from the 3GPP network to the non-3GPP

network; and as regards the technical solution "the network element on the network side is a non-

3GPP gateway (GW) of the source network," the specification has only disclosed that, only when

a handover or change occurs from a non-3GPP network to a 3GPP network and the source

network is the non-3GPP network, the non-3GPP GW exists in the source network, and moreover,

it is the "cause IE" that indicates the UE is handed over or switched from the non-3GPP network

to the 3GPP network.

2. The Applicant has added Independent Claim 19 in the amended documents submitted on

June 8, 2009. However, the added independent claim is not disclosed in the original claims and

specification. Moreover, according to the disclosure of the original claims and specification,

persons skilled in the art cannot directly and undoubtedly obtain the technical solution claimed in

Claim 19. Therefore, the amendments go beyond the scope of the disclosure of the original

claims and specification, and Claim 19 fails to meet the provisions of Article 33 of the Patent

40

NSN677-1002,


Law of the PRC. The Applicant shall note that, the added independent claim is the generalization

of the process of user detachment in the embodiments of the present invention, which does not

disclose how to trigger the user detachment , and such generalized amendments are not allowed.

3. The Applicant has added Dependent Claims 20, 22, and 23 in the amended documents

submitted on June 8, 2009. However, the term "indication information" disclosed in these claims

is not disclosed in the original claims and specification. Moreover, the amended technical

solutions cannot be directly and undoubtedly obtained from the disclosure of the original claims

and specification. Therefore, the amendments go beyond the scope of the disclosure of the

original claims and specification, and Claims 20, 22, and 23 fail to meet the provisions of Article

33 of the Patent Law of the PRC. The Applicant shall note that, the specification has only

disclosed indicating the user by the "cause IE."

4. The Applicant has added Dependent Claims 21, 22, 23, and 24 in the amended documents

submitted on June 8, 2009. However, the terms "MME of the source network" and "non-3GPP

GW of the source network" disclosed in these claims are not disclosed in the original claims and

specification. The original claims and specification have only disclosed that, only when the

source network is a 3GPP network, the MME exists in the source network, and only when the

source network is a non-3GPP network, the non-3GPP GW exists in the source network.

Moreover, according to the disclosure of the specification, persons skilled in the art cannot

directly and undoubtedly obtain the technical solutions claimed in Claims 21, 22, 23, and 24.

Therefore, the amendments go beyond the scope of the disclosure of the original claims and

specification, and Claims 21, 22, 23, and 24 fail to meet the provisions of Article 33 of the Patent

Law of the PRC.

5. Claim 1 seeks to protect a method for user detachment when a handover or change occurs

in a heterogeneous network. Reference Document 1 (US2006/0146803A1) has disclosed a

method for performing handoff of a UE from a Wireless Local Area Network (WLAN) network

to a Universal Mobile Telecommunication System (UMTS) network, and has specifically

disclosed the following contents (referring to Reference Document 1, the Abstract, the

specification, paragraphs 0045-0052 and 0058-0065, and FIGs. 3-4): when performing packet

exchange with the WLAN network, the UE triggers handoff from the current WLAN network to

a Ultimate Radio Access Network (UTRAN), then the UE performs pre-registration to the

UTRAN, and after receiving a Pre-Registration Response message, the UE performs detachment

41

NSN677-1002,


from the WLAN network. Upon comparison, the distinguishing technical feature between the

technical solution claimed in Claim 1 and the contents disclosed in Reference Document 1 lies in

that, the handover of the UE is known, and the source network determines whether to detach the

UE from the source network, and detaches the UE from the source network. Based on the

distinguishing technical feature, it can be determined that the technical problem to be actually

solved in Claim 1 is to perform determination before the detachment by the network. However,

in the mobile communication field, the handover performed by the UE requires the combined

operation of the network and the terminal. Therefore, persons skilled in the art can easily think of

knowing the handover of the UE by the network. In addition, the detachment is not required

under all circumstances. For example, the detachment is not required to be performed when the

handover is performed on a dual mode mobile terminal. Therefore, in order to perform different

processing according to different circumstances, persons skilled in the art can easily think of

performing the determination before the detachment. Moreover, initiating the detachment by the

user and initiating the detachment by the network are common manners for initiating the

detachment in this field. Since Reference Document 1 has disclosed that the UE initiates the

detachment process, persons skilled in the art can easily think of initiating the detachment by the

network. Therefore, the distinguishing technical feature is a common technical means in this

field. It is obvious for persons skilled in the art to achieve the technical solution claimed in Claim

1 based on Reference Document 1 in combination with the common technical means. Claim 1

neither has prominent substantive features nor represents a notable progress, and fails to have the

inventive step set forth in Paragraph 3 of Article 22 of the Patent Law of the PRC.

6. Claims 2 and 3 define Claim 1. However, part of the technical features in the

characterizing portions of Claims 2 and 3 have been disclosed in Reference Document 1

(referring to Reference Document 1, the Abstract, the specification, paragraphs 0052 and 0065,

and FIGs. 3-4): the UE performs handoff from the WLAN network (belonging to the non-3GPP

network) to the UMTS network (belonging to the 3GPP network), and is detached from the

WLAN network after performing the pre-registration. In addition, in the mobile communication

field, the handover performed by the UE requires the combined operation of the network and the

terminal. Therefore, persons skilled in the art can easily think of knowing the handover of the UE

by the network. Given that Claim 1 upon which Claims 2 and 3 are dependent fails to have the

inventive step, Claims 2 and 3 also fail to have the inventive step set forth in Paragraph 3 of

42

NSN677-1002,


Article 22 of the Patent Law of the PRC.

7. Claim 4 defines Claim 1. However, the characterizing portion of Claim 4 is a common

manner for user detachment in the mobile communication field. Given that Claim 1 upon which

Claim 4 is dependent fails to have the inventive step, Dependent Claim 4 also fails to have the

inventive step set forth in Paragraph 3 of Article 22 of the Patent Law of the PRC.

8. Claims 6-7 and 10-11 all define Claim 3. However, the characterizing portions of Claims

6-7 and 10-11 are common procedures for user detachment in the mobile communication field.

Given that Claim 3 upon which Claims 6-7 and 10-11 are dependent fails to have the inventive

step, Claims 6-7 and 10-11 all fail to have the inventive step set forth in Paragraph 3 of Article

22 of the Patent Law of the PRC.

9. Claims 8 and 9 both define Claim 3. However, during the handover in a heterogeneous

network, usually, the registration of the target network is performed and the location is updated.

In addition, after the handover is performed, the source network usually deletes bearer resources

occupied by the handed over user. Given that Claim 3 upon which Claims 8 and 9 are dependent

fails to have the inventive step, Dependent Claims 8 and 9 also fail to have the inventive step set

forth in Paragraph 3 of Article 22 of the Patent Law of the PRC.

10. Claim 12 defines Claim 4. However, in the mobile communication field, after the

handover is performed, the source network usually deletes bearer resources occupied by the

handed over user. Given that Claim 4 upon which Claim 12 is dependent fails to have the

inventive step, Dependent Claim 12 also fails to have the inventive step set forth in Paragraph 3

of Article 22 of the Patent Law of the PRC.

11. Claims 13-17 all define Claim 3 or 12. The characterizing portions of Claims 13-17

relate to how to obtain the terminal capability of the UE or the access policy of the network.

However, the user sends terminal capability information to the network when the user accesses

the network or the location is updated, or the terminal capability information of the user is

transmitted between network elements when necessary, and the access policy is transmitted

between network units when necessary, both of which are common technical means in this field.

Given that Claim 3 or 12 upon which Claims 13-17 are dependent fails to have the inventive step,

Claims 13-17 fail to have the inventive step set forth in Paragraph 3 of Article 22 of the Patent

Law of the PRC.

12. Claim 18 defines Claim 7. However, in the mobile communication field, a "cause" IE is

43

NSN677-1002,


added in some messages to represent the cause value of a certain operation, which is a common

technical means. Given that Claim 7 upon which Claim 18 is dependent fails to have the

inventive step, Claim 18 also fails to have the inventive step set forth in Paragraph 3 of Article


13. Claim 25 seeks to protect a method for user detachment when a handover or change

occurs in a heterogeneous network. Reference Document 1 (US2006/0146803A1) has disclosed

a method for performing handoff of a UE from a WLAN network to a UMTS network, and has

specifically disclosed the following contents (referring to Reference Document 1, the Abstract,

the specification, paragraphs 0045-0052 and 0058-0065, and FIGs. 3-4): when performing packet


a UTRAN, then the UE performs pre-registration to the UTRAN, and after receiving a Pre-

Registration Response message, the UE performs detachment from the WLAN network. Upon

comparison, the distinguishing technical feature between the technical solution claimed in Claim

25 and the contents disclosed in Reference Document 1 lies in that, the UE determines whether

to detach the UE from the source network. Based on the distinguishing technical feature, it can

be determined that the technical problem to be actually solved in Claim 25 is to perform

determination before the detachment. However, in the mobile communication field, the

detachment is not required under all circumstances. For example, the detachment is not required

to be performed when the handover is performed on a dual mode mobile terminal. Therefore, in

order to perform different processing according to different circumstances, persons skilled in the

art can easily think of performing the determination before the detachment. Therefore, the

distinguishing technical feature is a common technical means in this field. It is obvious for

persons skilled in the art to achieve the technical solution claimed in Claim 25 based on

Reference Document 1 in combination with the common technical means. Claim 25 neither has

prominent substantive features nor represents a notable progress, and fails to have the inventive

step set forth in Paragraph 3 of Article 22 of the Patent Law of the PRC.

14. Claim 26 defines Claim 25. The content in the characterizing portion of Claim 26 has

been disclosed in Reference Document 1 (referring to Reference Document 1, the Abstract, the

specification, paragraphs 0045-0052 and 0058-0065, and FIGs. 3-4): the UE triggers handoff

from the current WLAN network to a UTRAN and then performs the handoff to the UTRAN.

Given that Claim 25 upon which Claim 26 is dependent fails to have the inventive step,

44

NSN677-1002,


Dependent Claim 26 also fails to have the inventive step set forth in Paragraph 3 of Article 22 of

the Patent Law of the PRC.

15. Claims 27 and 28 define Claim 25, and define a process of user detachment. However,

the characterizing portions of Claims 27 and 28 relate to a common process of user detachment

between the 3GPP network and the non-3GPP network in this field. Given that Claim 25 upon

which Claims 27 and 28 are dependent fails to have the inventive step, Dependent Claims 27 and

28 also fail to have the inventive step set forth in Paragraph 3 of Article 22 of the Patent Law of

the PRC.

16. Claim 29 defines Claim 25. However, it is well known to persons skilled in the art that

the UE is in an invalid state after the UE is detached from the network. In addition, the mobility

management network is usually used for performing operations such as managing the user state

and updating the state. Given that Claim 25 upon which Claim 29 is dependent fails to have the

inventive step, Claim 29 also fails to have the inventive step set forth in Paragraph 3 of Article


17. Claim 31 defines Claim 27. However, part of the content in the characterizing portion of

Claim 31 has been disclosed in Reference Document 1 (referring to Reference Document 1, the

Abstract, the specification, paragraphs 0052 and 0065, and FIGs. 3-4): the UE performs handoff

from the WLAN network (belonging to the non-3GPP network) to the UMTS network

(belonging to the 3GPP network), and is detached from the WLAN network after performing the

pre-registration. In addition, in the mobile communication field, the detachment is not required

under all circumstances. For example, the detachment is not required to be performed when the

handover is performed on a dual mode mobile terminal. Therefore, in order to perform different

processing according to different circumstances, persons skilled in the art can easily think of

performing the determination before the detachment. Further, the occupied bearer and Packet

Data Protocol (PDP) context usually need to be deleted for the detachment of the network. Given

that Claim 27 upon which Claim 31 is dependent fails to have the inventive step, Claim 31 also

fails to have the inventive step set forth in Paragraph 3 of Article 22 of the Patent Law of the

PRC.

18. Claim 32 defines Claim 27 or 28. However, in the mobile communication field, a

"cause" IE is added in some messages to represent the cause value of a certain operation, which

is a common technical means. Given that Claim 27 or 28 upon which Claim 32 is dependent fails

45

NSN677-1002,


to have the inventive step, Claim 32 also fails to have the inventive step set forth in Paragraph 3


19. Claim 33 defines Claim 29. However, the characterizing portion of Claim 33 relates to

common manners for setting the user state in this field. Given that Claim 29 upon which Claim

33 is dependent fails to have the inventive step, Claim 33 also fails to have the inventive step set


20. Claim 34 seeks to protect a system for user detachment when a handover or change


a system for performing handoff of a UE from a WLAN network to a UMTS network, and has





Registration Response message, the UE performs detachment from the WLAN network. Upon

comparison, the distinguishing technical feature between the technical solution claimed in Claim

34 and the contents disclosed in Reference Document 1 lies in that, the network side detaches the

UE from the source network. However, initiating the detachment by the user and initiating the

detachment by the network are common manners for initiating the detachment in this field. Since

Reference Document 1 has disclosed that the UE initiates the detachment process, persons

skilled in the art can easily think of initiating the detachment by the network. Therefore, the

distinguishing technical feature is a common technical means in this field. It is obvious for





21. Claim 35 defines Claim 34. However, part of the content in the characterizing portion of

Claim 35 has been disclosed in Reference Document 1 (referring to Reference Document 1, the

Abstract, the specification, paragraphs 0045-0052 and 0058-0065, and FIGs. 3-4): when

performing packet exchange with the WLAN network, the UE triggers handoff from the current

WLAN network to a UTRAN, then the UE performs pre-registration to the UTRAN, and after

receiving a Pre-Registration Response message, the UE performs detachment from the WLAN

46

NSN677-1002,


network, and performs access to the target network. Based on the above, both the UE and the

network side disclosed in Reference Document 1 have the functions of performing handover and

performing detachment. Further, it is a common technical means in this field to adopt

independent functional modules to perform corresponding functions. Therefore, persons skilled

in the art can easily think of adopting independent functional modules to respectively perform

the handover function and the detachment function. Given that Claim 34 upon which Claim 35 is

dependent fails to have the inventive step, Dependent Claim 35 also fails to have the inventive


22. Claim 36 seeks to protect a device for user detachment when a handover or change







Registration Response message, the UE performs detachment from the WLAN network, and

performs an access process to the UTRAN. Upon comparison, the distinguishing technical

features between the technical solution claimed in Claim 36 and the contents disclosed in

Reference Document 1 lie in that, (1) the network side detaches the UE from the source network;

and (2) Claim 36 discloses the second handover or change module and the second detachment

module. However, initiating the detachment by the user and initiating the detachment by the

network are common manners for initiating the detachment in this field. Since Reference

Document 1 has disclosed that the UE initiates the detachment process, persons skilled in the art

can easily think of initiating the detachment by the network. Therefore, the distinguishing

technical feature (1) is a common technical means in this field. As regards distinguishing

technical feature (2), the network side device disclosed in Reference Document 1 is able to

implement the handover and detachment process of the user. Further, it is a common technical

means in this field to adopt independent functional modules to perform corresponding functions.

Therefore, persons skilled in the art can easily think of adopting independent functional modules

to respectively perform the handover function and the detachment function. It is obvious for


47

NSN677-1002,





23. Claim 37 defines Claim 36. However, in the mobile communication field, the user




art can easily think of performing the determination before the detachment. Moreover, it is a

common technical means in this field to adopt independent functional modules to perform

corresponding functions. Given that Claim 36 upon which Claim 37 is dependent fails to have

the inventive step, Dependent Claim 37 also fails to have the inventive step set forth in

Paragraph 3 of Article 22 of the Patent Law of the PRC.

24. Claims 38 and 40 both define Claim 36. However, the user sends terminal capability

information to the network when the user accesses the network and the network unit transmits

access policy information when necessary, both of which are common technical means in this

field. In addition, it is a common technical means in this field to adopt independent functional

modules to perform corresponding functions. Given that Claim 36 upon which Claims 38 and 40

are dependent fails to have the inventive step, Claims 38 and 40 fail to have the inventive step set


25. Claim 39 defines Claim 37. However, the user detachment in the 3GPP or non-3GPP

network is usually performed by an MME, GW, or home subscriber server (HSS) in the network.

In addition, it is a common technical means in this field to adopt independent functional modules

to perform corresponding functions. Given that Claim 37 upon which Claim 39 is dependent fails

to have the inventive step, Claim 39 also fails to have the inventive step set forth in Paragraph 3


26. Claim 41 seeks to protect a device for user detachment when a handover or change






48

NSN677-1002,



Registration Response message, the UE performs detachment from the WLAN network, and

performs an access process to the UTRAN. Upon comparison, the distinguishing technical

feature between the technical solution claimed in Claim 41 and the contents disclosed in

Reference Document 1 lies in the first handover or change module and the first detachment

module. The user terminal disclosed in Reference Document 1 is able to implement the handover

and detachment process of the user. Further, it is a common technical means in this field to adopt

independent functional modules to perform corresponding functions. Therefore, persons skilled

in the art can easily think of adopting independent functional modules to respectively perform

the handover function and the detachment function. It is obvious for persons skilled in the art to

achieve the technical solution claimed in Claim 41 based on Reference Document 1 in

combination with the common technical means. Claim 41 neither has prominent substantive

features nor represents a notable progress, and fails to have the inventive step set forth in


27. Claim 42 defines Claim 41. However, in the mobile communication field, the user




art can easily think of performing the determination before the detachment. Moreover, it is a

common technical means in this field to adopt independent functional modules to perform

corresponding functions. Given that Claim 41 upon which Claim 42 is dependent fails to have

the inventive step, Dependent Claim 42 also fails to have the inventive step set forth in


28. Claims 43 and 44 define Claim 41. However, the user sends terminal capability

information to the network when the user accesses the network and the network unit

transmits access policy information when necessary, both of which are common technical

means in this field. In addition, it is a common technical means in this field to adopt

independent functional modules to perform corresponding functions. Given that Claim 41

upon which Claims 43 and 44 are dependent fails to have the inventive step, Claims 43

and 44 fail to have the inventive step set forth in Paragraph 3 of Article 22 of the Patent

Law of the PRC.

49

NSN677-1002,

Eiropearc Pawn. orkie KIN4 itA9Nr04 fait.rirsowi'

+4* opts zeeS 0 Fez: *40(0)69=9 • 44eS

1 2 7iEP•THisg

HuaWei Technoio,ciers Ltd

eVelgal Na Igw,obtltk 08n 3f336..3 203E252 P4'TiCti2008071.842

1111111 IIII1 I II 01111111 EN 1111. Than, 0.14f116t1.8. Mitsonerlieh & Partner Sostmenstfanne 33 86331 Ntliirif.4-lerr ALLEMAGNE

For rroy toettotroos akiotst Etti*. zacroniktnicotron: Tet...+.:r1 34'04.50

24 02 10


Cormun tort

The extende.d EBropeart SM011 MPOrt enclosed..

The „extr,,,,nefed European seara report includei-5, ptiev_mtIt 3o P,t,tte:62. EPG., nupplementaty European search report (Art. 1W(7) E.PO. and the European :seed* npinion,

Cdpjors. t d000rrient4 Mae ih the Etttopeori searoh report are attanned,

ariditiondi set(s) ot copies ot such cionuments is (are) ersecaseti es lif

Refund at the search toe

if aprJ.NoaWe undei- Articlo t Rules refating tees, a separnt*rl 007imphionten from the Fi.maiving Cecton 'On the refund Of ale worch fee wilt b sera later.

P4i..ere

is

,I;k0

Er* Fexm ri;07k--4

50

NSN677-1002,

EP 08 78: 3835

CI-AnW$CATION TME (IM

INV. HO4W4/00

TRCNNICAL, Frf.1116 SZ.A11:4,,,sq40 an)


SUPPLEMENTARY EUROPEAN SEARCH REPORT

DOCUMENTS CONSIDERED TO BE RELEVANT <A::Itith'i ,-.S:z:,;:zno vivre 3mt0a10, r R§Itsiant

Wrtzlevwfinasa-408 = tt, ClaiM

'Technical specification group &orvices 11-15 an/ svaem aspects; MIS enhancements for E-UTRAN access (Release 8) 3CIPP T 23.401 V1.1.0' 3R0 GENERATION PARTNERSHIP PROJECT (30P12); l TECHNICALSPEUFICATION (TS). XX, XX, [Online) no, 36PP TS 28,401. V1.1.0, 1 July 2007 (2007-07-01), pages 1-78, 002508183

Retrieved from the Internet: q1Rt.www:30pA)rg> [retrieved on 2.008-12-15] * pages 43-47, par. 5,3:8, 5.3.8.1, 5.3,8.2, 5.3.8.3, 5.3.8A, 5.3.9 *

WO 2007/024115 Al (KOREA ELECTRONICS 1-2, TELECOMM [KR]; CHEON KYUNG-YUL [KRL RO 10-13 KMAN -HYUNj I March 2007 (2007-03-01)

abstract * 3-9, * Page 3, line 10 - Ilne 13 * 14-15 * page 9, line 8 - line 13 * * page 9, line 21 - page lit line 19 * * flora 2 *

EP 2 007 1W Al (NOKIA SIEMENS NETWORKS OY a,14 [FIT 24 December 2008 (2008-12-20 * paragraph romal - Paragraph B1005) * * paragraph [ons] - raragraph [U0511 fNore 2 *

The omtmealy rte( hg3g. tvagt NNW c.16. SSE vet rr, cUrn6 vatld arbl 40.0iat$e sly scan ottke soarm„

A

MunIch 11 February 2010 jMoil, Hans-Peter

i AIT OR O (IMO 0(41.11.2ENT9

.x:IxizekNkfictNek,Xii:11.4.1witgicme

Vx; (4Witletry, A • ;;Ra..-..xn;•jakd

aNI—VA.1•4:4•4 Mis.411x,xtklu., dncoansot4

NM .r .z4r eut invarifi•m eNst.01Mu44sgt.

:40:NAL,:!nt Grik:‹11.:#4.1Kwr top.w.uk

. . : 00:1ts0 R,:s swm WItE Tzttkey. C(3172zWIRIStr.fj: tRAVP*11t

3

page 1 of 2

51

NSN677-1002,

Docket No. HW708564


SUPPLEMENTARY EUROPEAN SEARCH REPORT

ApttnENIcctn Fintatrot

EP 08 78 3835

NW, ctirMr

W44,x row Ns*ri.

fWatklini t63 tiaan

DOCUMENTS CONSIDERED TO BE RELEVANT

i t-,'etepey E:7,1ASSFitaTiOn APPLIeirrAC311

c4t3bo: htheze. woroprat.e, wit?.."51.:9WS

A UPP! "3GPP TS 23.402 T1.2.0 q-15 (2007--L7) 3rd Generation Partner hip Projectjechnical Spdcification Group Services and System Aspects;Architecture Enhancements fcr nor-WP accesses (Release 8)°'

13GPF 3.GPF TS 23..402 1 July. 2007 (2007-07-01), pages 1-54, XP00256767 Retrieved from the Internet:

IURLhttp://www.3gpp,orgiftp/Specsihtml-inf 023402.htm› [retrieved on 2010-02-04 * page 8: figures 4.2.1-1 * * page 9; figures 4,2.2-1 * * page 30, paragraph 5.6 - page 33 * * pages 39-52; Annex C.:: Handover Plows *

TECE,INICAL tgara SUMMED (140C#

Ttt* fat iviernergivy smirch wed No teiee Mese an eke Etx5St EM et cUrna EtalkS and available al. Me stet 4 the riaardh.

ilabo .•z? taman $1[4:tia‘a

Munich r:130FiY (EiEliDte:3333E3dTE3

X : pArExutsr4: reat:awk a taws 4.k.net y 3.:arbantArt,t **;*‘*:k N mmbintal NW: WOW

CieKherer0 i$ :he tn1.1,169F A.lejle,.-A,VketNelhh2hlek c?" reith,peOhn .ht.ihkAMIUTh.

. Mt:m*14a tkamtuest

11 February 2010 I Kell, Hans-Peter : adoN nr prixelpfk toxfkateixotbx. invent n : agfan- act pxtiiskall an, nt ;OW 17.e, .:*:?:re

: !*...Ztj !TN, 1:,,,I4c3 Oka Vrsk,..*ting: . ttaMna.:44 t:,4t*It..:.•t tx s>tt Kattaltat

a:EmeEtwath *mmiy.cerasVmdt4n Wtaa**4

page: 2 of 2

52

NSN677-1002,


ANNEX TO THE EUROPEAN SEARCH REPORT ON EUROPEAN PATENT APPLICATION NO. EP 08 Th 3.U,S

This armee rigs tee patent ;amity mameemalatiag W. tee paeans ca le oted eh...we-ma-Waned Etwapeen s*w team The elemeela am es c:N.asaiesti .kr• the Ema:.asen Pateet Orete EuPtilk oz) to Esme‘wanlent Otf no way kat* ges *gage gerdcuiers•weelh miry !we.? rpfirt litx 418.1.11:N04e us infotrpatort.

WO 2007024115 M 01-03-2007 Ep 1938518 Al

11-02-2010

Pubftason rktte

02-07-2008

441)rai ifg &Mat farprt I Pit

AV :trn

•

Pater-elan* Higint ff$} liz

Palent clotrammt

E P 2007160 fit. 24-12-2008 KVE

rth

"ge thftin akiKini thin WIcfnlx : skeiv jrlezrw3 <0 to Empeae Paw Me, /2•V

53

NSN677-1002,


Mahan BUI eitto rg F4.11:3n 11507 shim Agrsgtasliors :t.3 ti bah:, re:

The uxarniniilion is Wing cartiect oat on the foilowinci apptication doeu eats

Descriotion, Pages

-;;;„:1. t'ik:i.lvo.ith entry info a regOnai pii3Se before tho,

Claims; Numbers

tik-td erity into the regiona phase. 0010re the EPO

Drawings, Sheets

fikstltNBtti witty into U mgion pAR,ie before triof PO

ma • ed r`a.mencled" by the appticant

Reference is made to the folIewi:n decurnents; the numbering MI be adhered to in the resit)! the procedure:

D1 "Technical specification group services and system aspects: (3PRS enhancements for EI-LITRA.N access (Reklase, 8) 3GPP TS 23.401 V1.1.8" 8RD GENERATION PARTNERSHIP PROJECT (3GPP), TECHNICA.t.SPEClfiCATIGN (TS), XX, XX, ifT.)nIinel no. 3(..;'iPP TS 28.401 V'.1.0.1 stuIy 20.07 (2007-07-01) . pages 1-78, )Poo25oai53 Retrieved from the Ititernet: LIRL:www.3gop.erg [retrieved on 2008-12-16)

02 WO 2007i024115 Al (KOREA ELECTRONICS TELECOMM [K.R]; CHEON [KR]; HO KWANG-HYUN D I March 2007 (2007-03-01)

EP 2 007 160 Al (NOKIA SIEMENS NETWORKS OY MI) 24 December 2008 (2008-12-24)

2 Clarify, Mide 84 EPC

2.1 Claim

Independent Ctaim 1 does not meet the requi -MSC! ArticIe 84 EPC re..prding clarity for the i0!1+ viriM) reasons:

2.1.1 Independent Claim 1 :mentions in the preamble a 3GPP network and a none-3GPP netwoek. in the. Wowing features di Ctaini I a source network s.nd a target network are mentioned and two method ste4-.* are defined ire which saki source and said target netwetk appew. It ja ot7t4 unclear whether

f).:5)1•11:3

54

NSN677-1002,


01.45.01 . in Anirs144*-1**. ClaS Of i;%:,:rrii 1 5,.' 7 Shoe F AK/kali:i: Ns:: t 2 F< 183 935..5

indeed four differgrit netwOrit.S. are present or whether me source andlor. the target network are of the 3GPP. or non-3‘3PP typo it is noted that originally filed dependent Claim 2 contains a dear formulation..

2_12 Moreover, Claim 1 uses eXpressions such aslionclover or change" and "handing ver or switc dna'. If is totially unclear, whether. 'to handover is different from "to switch' pr "to change" or whether sad atlditional expreSSions are merely redundant and can tie removed.. This objection actually applies to most Of the ether Claims as well.

2.1.3 Moreover, the $ec.'ond feature .intioduces Me term "altedwrzrk_sitiel', is it the 'side of the source network, or the side of the to iigial network, tir We ;de of the 3GPP network or the side of the non-3GPP network? Thls is totally unclear.

2_1.4 )rdependent Claire 1 is totaify silent with respect to .the .fact how it is determined hy the network element whether ttii de.tach the UE, i„e, the critenon/criteris I.V.s6.:d for Chia determination are not present in Claim 1.

2.2 Claim 3:

Dependent Claim 3 does not meet We requirements of Article 84 EPC regarding clarity .for the following ;roasons:

2.2.1 Dependent Claim 3 includes the inconsistent expressions 'bearer sources' (page 52, liner, 13 and 22) and 'bear sourc,es" (page 52, lines 15 and 24). Even if it is assumed that. tile expression "hear sources" is the result of a typing error and that "bearer sources" was intended, the definition e_)t said expression is totally Unclear.

2.3 Claim 8:

independent .Claim 8 does permit meet .the iegthroments of Article 84 .EPC. regarding clarity kr the following: reasons:

2.3,1 Independent Claim 8 is totally silent with respotit to the tact how it is. determined by the UE whether to detach from the source: network, i.e . t criterion/criteria. used for this deterinination are not present in Claim 8.

2.4 Claim 10:

Independent Claim 10 does not meet the requirements of Article. 34 E PC regarding clarity for the folloWihQ reasons.:

2.41 Independent Claim 10 does merely define that the network side is both adapted tiD handover UE {from a source to a target network) and to detach the UE from the source network.. However, .no connection between said two aspects is definet whether The .notion of detaching the LIE. from the source network is related to the handover action. Moreover, Claim 10 •va totaliy. silent

ksn. t 1 .:;.; TR;

55

NSN677-1002,


*atiois es33 A?1ecle3detAlt. Oatii, C.: f?.~74;m. 1 5 L ; Staff? ApsgiClttlw Ner. :lc 3 35 . DC0k, F,stsi8g C.:41,11150cle Sr"

with respect to the tact under viihich circumstances the UE is detached from the source network. i.e. whether .any criterion/criteria are used for determining whether to detach the UE not,

2.5 Claim 12:

€ndependent Ciaim 12 dor s. not meet the requirements of Article 84 EPC regarding clarity for the following reasons:

2,5.1 independent Claim 12 is dilrected ruder:is a device fer user detachment comprising a second tiandovef• En odute and a second detachment rnodute. From Fig.. 12 it is apparent, that the devic& el.airned En Claim 12 is in fact the "nelVorkPlement ofi thertetwork side" mentioned in Claim 1. Conarstent terminology should be used and Claim 12 accordingly revirorded, Moreover; the expression "wi;et.detachment" is inc.orreot since present application deals with UE .detactiment.

2.5,2 independent Claim 12 clues merely define that the device (networli element on the network side) comprises modules which are both adapted to handover a UE (from a seurrx to a target network) arld to detach the fiE, from the SOURM network, However, rill connection between said tic.) as:pects ts i.e. whether the action of detaching the UE from the source network is related to Me handover action, Moreover, Claim 12 is totally sifent with respect kti the fact under vvf-k.h circumstances the UE is detached nom the, source network. i.e. .whether stay onterionjsriteria tart:- used for de.termining •ivtristrier to .detach

UE s. r not

2.6 Claim 14:

Independent Claim 14 does not meet the requirements of Article 84 EPC regarding clarity for the following reasons:

Independent Claim 14 is. directed towards t device for user detachment comPlislog a first handover module and a first detachment modulo. From Fig, 12 Et is apparent., that the device diaimed in Claim 14 is in f a.ct the "iLla.' men toneti in Claim 1. ConSiSMrtt (Willnology should be uaed anfil Claim 14 aCCordingly reworded. Moreover, the expression "user:detachment" is Incorrect since the present application deals with LIE detachment,

2.6.2 thdependent Claim 14 does merely define that the device (UE) comprises. moduies which are both adapted to handover a it E dram a scarce to a target network) and to detach the LYE from the source network: However, no Exinnection between said two aspects is defined, L. whether the, action of detaching the UE from the source network is related to the nandover action. Moreover, laim 14 is totally silent with *SpOC1 to the fact under which circumstances UE is detached from the source network, i.e. whether any eriterionichteria are used for determining whether to detach the LE or not

56

NSN677-1002,


0,30.111 Blatt .Aoracelde-Nr. t);:ito 15E37 meek APPficatt'ean No' r) - ?..35 ri ost.R. rc,..•tou

Nov ay and inverttive Step, Article 52(1), 54(1), (2) and 56 EPC

Reparic Notwithstanding the wxlve clarity objections (Article 84 E PC) and i,nsofar zel said Cleitns can be understood, the ioilmesiing. assessment i > made:

31 Ctaim 1:

3,1,1 The appfitant shouid note that independent Claim 1 does not appeal to be novel (Artiste 54(1) (2) EPC) and to itIvoive an inventive step (Article 56 EPC) ',6s-A-vis document Dl arid is thus incit allowabie according to Article 52

) EPC.

The document Ell is regarded as being the elbsest prior art . to the subject-matter of Claim 1 and shows. an 'method for user. detachment when hartclovvr pLeh,ange occurs between a 3GPP rreta rf,arld non-',:(1)PP .rigtwortr,' (D1, page 45; par: 5,3,84, Met): 1-4) with aii the features as defined in Claim 1 al the qreset-tt European Patent ilapiisation.

handin Over of awitchitu a user equipment from a so§..irm riatw4-K, a target:network ,oiw 45, par, 5.3.8,4, lines 1.4)

- deter:Mining,* a network dement on a network side, whether to dktacti the uE f (11/1 the sopr.n. net,w^rk: if *Felac.."Nr) the LE from the source netwitir (Di. page 45.. par. 5.3.8,4, fines t-4)

Rematk. The Scenario of detaching a from a source network (i.e. update/ remove MM context end deieting the EPS bearers) in response to a 3(3 PP to non-36PP bandover is described as b6ng 'FPS" in Di. "FFS' means "fer further studies" in the context of 30PP standardization documents. This means that it was not yet decided at the time. o generating V1 ,1.0 of 3GPP TS 23.401 whether this Will be indeed imfAerhis,nted, However, We option was already" there.

3.1.2 As a consequence, Claim 1 does net meet the requirements of Article 54(1), (2) EPC in that its subltest-matter tacks .novelty and is thus not allowable (Article 52(1) EPC).

3.1.3 it is further noted Wet even if the App cent. woukt nteripret the disclosure cf Document Di in a siightiy different manner than the exa.minei has done in the above analysis, and based oh his, interpretations wmid come to the conolustc.-in that there are dfletennes between the subject-matter et present

57

NSN677-1002,


Dawn smi. move: •. oato For m :1.507 viciot is,p0cMion No' 09 -78 'A 835 .. 5 Dai.c3 keilaio.,: (..,.oriv:imii,,w,

Claim I and DI which: wouid then e:stabfish novelty (AMOe 54(1)., (2) .EPC), her these differences, even it ti, y could b ads,nowledged as suc# .,. would

only be of so minor nature that they could not be the baste for .establishing the orttsence. of any inventive, step (Article 56 E PO), ae 01 discloses .the same object and the same type of solution as the, presoht appricalori, i,i(•,c1c(airn I would, even with such a difference in interpretation, not meet the tequirements of Article 52(1) and 5:6 E PC.

3.1.4 it s further noted that also the above cited docurne.nt D2 appears to disclose the subjecHnatter c f independent Claim 1 and that therefore' Claim I lurtheimoic_,t lacks novelty and inventive step within the meaning of Article 54 (1), (2) and 56 EPC also vis-a-vis the disclosure of 02.

Reference is made in this respect 10 the foiliowing text passages of 112

02, abstract

(12, page 3, fines 10-13

02, page 9, fines 8-13

02, page 9, finef page t, line 19

02, Fig2

3.2 Claims 10 and 12:

3 The features of independent system Claim 10 and do 0c& Claim 12 correspond to the features of ;ndependent rnefhod Claim 1 and hence the arguments concerning iack .of novelty/inventive step as set out above apply equally to sald Claims 10 and 12, which does ihereipre efso not meet the requirements ot Art cle 54(1), (2) and 56 EPC. 'Claims 10 and 12 are thus not allowable (Article 52(1) EPC).

Claim 8.

3.3.1 The European patent Et ppiicatioa cited as 03 above published on 24,12.2008 was filed on 19.06.2007, .e. prior to the filing date of the present European Application, its content as filed therefore considered to be comprised in the slate el the art :relevant tr.3 the question of novelty, pursuant to Article 541:3) EPC.

This earlier aprAdation shows at the features of independent Claim 8, name y:

3 riVthed tot u:tlet detaOrnant when handdver 01;41:1Qp. r t41ars jtu, Lleterogeneou, ng:twork [0035H00501: Fig.2), comprising:

--inFtirat374_PY a use- e<9uTrri0M, handover r switching from e eouroe Qetwork to a„target nrAwdrk (D3. [0039110040T

58

NSN677-1002,


()MON Slat .A.no*Edry..-Nir: C3a91 F:51'.'M 1 ...E.r Shett Apacaiiol Na. 09 ia3 a35 . 5

N.,tiliso& n'

by the UE, whether to detach the UE from the solgogiletwork‘ if yea, deiachina thetlE. final the source network {D3. [004): Fig.2)

3.3.2 Thus, Da is prejudicial to the noveity of the subjectrmatter of independent Claim 8 of the present application (Article 54(1), 3) EPC).

3.13 Moree,ver, Claim 8 does not meet the requirements of Article 56 EPC regarding inventive step to the following reasoris

3.3.3.1 Document Di discloses that a FOS-initialed iJE. Detach procedure may be. implemented if a LE changes RAT (i.e. hangovers) from 3CIPP to non-30PP (DI, page 45, par. 5-34.4, knee 1-41.

Document Dl also discloses that this Detach procedure may be initiated by a UE, a MME or a HSS (DI, page 43, par 5.32.1, lines 10-14 Document D1 discloses on Dl, ixage 4$, tines 1-2 That death may be required if a UE attaches to a non-3CiPP network. Di furthermore discloses on D1, paw. 44, par. 53,82 how this LIE-initiated Detach procedure is tarried out

The sKilled person - based on this disclosure - would implement a LIE 1, Detach pl-Dce:dwe in the scenario of a 3GPP to non-3GPP handover if rocOred under the circumstances without exercising any inventive activity,

3.3.32 Independent Claim 8 does therefore riot meet the requirements Of Article 56 EPC: Claim 8 is thus rot allowable (Article 52(1) EPC).

3,1 Claim 14

The features of independent device Claim 14 correspond to the features: of independent method Claim 8 and hence the arguments concerning lack of noveltrinventive step as set out above apply equally to said Claim 14, which does therefore also 0 of nice 1 the requirements of Article 54(1). (3) and 56 EPC._ CIatnt 14 is thus not allowable (Article 52(1) EPC).

3.5 Claims 2-7, 9, 11,10, 15:

3.5.1 The additional features cif dependent Claims 2-7, 9, It, 13, 15 appear to and nothing novel (Article 54(1), (2) EPC) arielor nothing of inventive significance (Article Se EPC) to those otalms to which they are appended, as the addltional features Joixciduced by said :dependent claims refer only to rnhior implementing details which are disclosed or obviously derivable from the cited prior art refe.reneDS or fall within the general knowledge of a person sKillee in the art:

3.5.1,1 Claim 2 (first alternative feature lricluded in Claim 2):

59

NSN677-1002,

Docket No. HW708564


Datum Mat awe ;":1: 1,"ortii Sheet Date Ftw.lo4s

Awriekot54,0! Awkallsn i71 7 83 N-111An00

1, Ave 45, par. 5.3,6,4, tines 1-4

2, page 9, line 21 - page 11, line 19 and D2, Fig2

3.5.1„2 Claim 3:

minor implementing detail in the light of DI, pages 43-46,. par 5,18, 5.34. /, 5..3.8.2, 5.3.8,3, 5.3.84

Claim 4:

iMpietnenting detail In the light of D1, page 46, par. 5.a8..4, Fig. _.)a.J.3,4-1.: Message: Cancel Location, irrle4 1-5 -

3.5.1.4 Claims 5-7:

niir/or irriptamenting d fall

3.5.1.5 Maim 9::

Minal. implenx4ntind detail

Claim:11.:

cf. aairn 12

3.5.1,7 Claims 13 and 15:

minor implemenling detail

3.5.2 Hence, the subject matter of dependen Claims 2-7, 9, 13, 15 $ not aliowahle within the meaning of Article 52.01 E

4 ln view of the cited prior ad, it is rot cleat at pte.$ent which part cr the application couid serve as a basis for a ne,,,v, allowable claim Should the appilcant ri.everthetess regard some particular mater as patentable, he is invited to We a new :set Di claims directed :awards such matter with suitable supporting argurnehtti.

The -applicant ishould indicate in the letter of reply the difference af the subject:- matter of the new claim vis-a-vis the state of the art and the zigrtjficanett thereot,

When submitting amendments, the appitn rt ;should atecl, take the, opportunity to attend to the foilowing matter:

5,1 To meet the requirements of Rule 42(1)(13) EPC„ the relevant prior art, t.r . the documents D1 and D2, sticutd be identitied -in the description. and the relevaqt background art disciose.d therein 'should be brielly discussed,

52. Any independent Claim should to hi the proper illvo-part "characterize" form recommended by Rule 43(1) EPC, having a pr: ambie that correctly irelleets the nearest prior art Dl

60

NSN677-1002,


Itgsg atm Ame1M-Nr Da* ef P,)rm 1507 silkm Appksaken No. 08 783 , *au., Fwiti4 uk-onancx

5. The opening pan of the descrip,fion should be brought into agreement with the new Claims to be filed (Rule 42(1)(c) EPC.),

5.4

The features of the claims should be provided with reference signs placed in parentheses to increase the intelltgitaty el the claims (Fttde 437) EPC), This applies to both the preamble arid characterlaing portion (see Guidelines C 1114 4.19).

5.5

Regarding the use of abbreviations (UE:. MME, non-3GPP CAW, PUN GW, RAU) for features repeater.* referred to In €t cat ports of the Claims,

it is necessary to delete the parentheses which enclose those. abbreviations the first Wile they are mentioned (ie,g, 'user equipment 1.1E"or 4mobifty management entity MME"), in order to avoid mi.5nterpreta On as to th6r limiting effect (Article 84 EPC and Guidelines, Cher,Iter

5.6 The general statement in the descriptlon on pages 49/50. par. 103151: " a.t.s' ended thW: the pre6ecrt Lnventin modifIcatns

...Rd tnj,8 inentm>2.1 pnwided thE.-3y fall th.,a fllowlng claim and ther.

ellaitva irit,") implies that the subject-matter for which protection. is sought may be different to that defined by the claims, thereby rendering the scope of the ddims unclear (Article. 84 E PC), This statement should therefore be deteted to remove this inconsistency (Guidelines, Chapter C. 4.4).

5.7 The applicant is requested to effect the amen:tin-Dents by filing replacement pages for only those pages which have been emended, L.Jrinecessary recasting of the description shoutd be avoided. An amended ab,stiact is not required. The applicant should also take account of the requirements of Rule 50(1) EPC. if hand-written amendments are submitted, they should be clearly legible for the printer,

5.8 ln order to facilitate the examinabon of the conformity of the amended application with the requirements of Article 123(2. ) EPC, the applicant is l'iquestKI to, clearly idettly the amendments carried out, irrespective of wnether they concern amendments by, addition., replacement or deletion, and to indicate the passages CA the application as filed on which these amendments are based. Speciai we should be taken to avoid giving rise to further objections by The knadvertent addition of subject-matter (Article 123(2) EPC't

61

NSN677-1002,


E. STATEMENT OF GOOD FAITH

All statements above in support of the petition to make special are based on a good faith

belief that the search was conducted in compliance with the requirements of this rule.

Respectfully submitted,

/John K. Winn/ John K. Winn, Registration No. 58,579 LEYDIG, VOLT & MAYER, LTD. Two Prudential Plaza, Suite 4900 180 North Stetson Avenue Chicago, Illinois 60601-6731 (312) 616-5600 (telephone) (312) 616-5700 (facsimile)

Date: June 27, 2011

62

NSN677-1002,



Confirmation No.



TC/AU:

Examiner:

Docket No. HW708564 (Client Ref. No. 81356140US16)

Customer No.: 77399


ACCELERATED EXAMINATION SUPPORT DOCUMENT

Dear Sir:

This Accelerated Examination Support Document is provided in support of the Petition

for Accelerated Examination filed herewith. The following sections are provided herewith:

A. References from Accompanying IDS begins on page 2 of this paper.

B. Identification of the Limitation of the Claims Disclosed by the Cited References

begins on page 2 of this paper.

C. Detailed Explanation of Patentability begins on page 27 of this paper.

D. Statement of Utility begins on page 28 of this paper.

E. Showing of Support of Each Claim Limitation begins on page 29 of this paper.

F. References that may be Disqualified as Prior Art begins on page 53 of this paper.

NSN677-1002,

Docket No. HW708564 Accelerated Examination Support Document

A. References from Accompanying IDS

This support document is filed concurrently with an Information Disclosure Statement,

which lists the following references:

1. U.S. Patent Publication No. 2009/0286527 (Cheon)

2. U.S. Patent Publication No. 2006/0153124 (Nishi)

3. U.S. Patent Publication No. 2006/0146803 (Bae)

4. U.S. Patent Publication No. 2010/0135245 (Zhu)

5. 3GPP TS 23.401 V1.1.0 (3GPP TS)

B. Identification of the Limitation of the Claims Disclosed by the Cited References

1. U.S. Patent Publication No. 2009/0286527

Independent Claim 1

U.S. Patent Publication No. 2009/0286527 by Cheon (hereinafter "Cheon") describes a

method for supporting a seamless service when a mobile station moves between a 3GPP

network and a non-3GPP network (see Cheon, at Abstract).

Further, Cheon discloses that, at paragraph [0042], when the mobile station 100 of the

3GPP subscriber accessed the 3GPP network 200, the PDP address allocated to the mobile

station 100 is stored at the HLR/AAA 240; at paragraph [0043], the mobile station moves from

the 3GPP network to the non-3GPP network; at paragraphs [0044] and [0045], the IWG 250

receives the PDP address previously allocated by the GGSN 230 from the HLR/AAA 240 and

forms a tunnel 320 to the mobile station 100 by providing the received PDP address to the

mobile station 100; at paragraphs [0049], the GGSN 230 transmits the PDP context delete

request message to the SGSN 220 so as to cancel the GRPS session (see Cheon, at paragraphs

[0038]-[0049], Fig. 1 and Fig. 2).

Independent claim 1 is not anticipated by Cheon at least because Cheon fails to disclose

the steps of: receiving, by a mobility management entity (MME) of the 3GPP network, a delete

bearer request sent by a serving gateway (GW) of the 3GPP network which carries a cause

information element (IE); wherein the cause IE indicates the UE handovers from the 3GPP

2

NSN677-1002,


network to the non-3GPP network; detaching, by the MME, the UE from the 3GPP network

when all the bearer resources of the UE are deleted.

It is obvious to one of ordinary skill in the art that Cheon only related to delete the bear

in the source network, but fails to disclose that the MME receives a delete bearer request which

carries a cause information element (IE); wherein the cause IE indicates the UE handovers from

the 3GPP network to the non-3GPP network. In addition, Choen also fails to disclose that the

MME detaches the UE from the 3GPP network when all the bearer resources of the UE are

deleted.

Dependent Claim 2

Cheon disclosed that at paragraphs [0049], the GGSN 230 transmits the PDP context

delete request message to the SGSN 220 so as to cancel the GRPS session.

Dependent claim 2 is not anticipated by Cheon at least because it depends from claim 1.

Furthermore, Cheon fails to disclose that the cause IE is set to "UE's accessing RAT changed

from a 3GPP network to a non-3GPP network."

Dependent Claim 3




Furthermore, Cheon fails to disclose "setting, by a packet data network gateway (PDN GW),

the cause IE to "UE' s accessing RAT changed from a 3GPP network to a non-3GPP network";


serving GW; and sending, by the serving GW, the delete bearer request message carrying the

cause IE to the MME."

Dependent Claim 4


Furthermore, Cheon fails to disclose "detaching, by the MME, the UE from the 3GPP network

without sending a detach request message to the UE."

3

NSN677-1002,


Dependent Claim 5



if a terminal capability of the UE is single radio capability."

Dependent Claim 6



if access policy information of an operator is single radio access."

Dependent Claim 7



if a terminal capability of the UE is dual radio capability and access policy information of an

operator is single radio access; or if the terminal capability of the UE is single radio capability

and the access policy information of the operator is dual radio access; or if the terminal

capability of the UE is the single radio capability and the access policy information of the

operator is the single radio access."

Independent Claim 8

U.S. Patent Publication No. 2009/0286527 by Cheon (hereinafter "Cheon") describes a

method for supporting a seamless service when a mobile station moves between a 3GPP

network and a non-3GPP network (see Cheon, at Abstract).

Further, Cheon disclosed that, at paragraph [0042], when the mobile station 100 of the

3GPP subscriber accessed the 3GPP network 200, the PDP address allocated to the mobile

station 100 is stored at the HLR/AAA 240; at paragraph [0043], the mobile station moves from

the 3GPP network to the non-3GPP network; at paragraphs [0044] and [0045], the IWG 250

receives the PDP address previously allocated by the GGSN 230 from the HLR/AAA 240 and

forms a tunnel 320 to the mobile station 100 by providing the received PDP address to the

mobile station 100; at paragraphs [0049], the GGSN 230 transmits the PDP context delete

4

NSN677-1002,


request message to the SGSN 220 so as to cancel the GRPS session (see Cheon, paragraphs

[0038]-[0049], Fig. 1 and Fig. 2).

Independent claim 8 is not anticipated by Cheon at least because Cheon fails to disclose

that a network device is configured to receive a delete bearer request sent by a serving gateway

(GW) of a 3GPP network when a handover from the 3GPP network to a non-3GPP network

occurs, wherein the delete bearer request carries a cause information element (IE) which

indicates a user equipment handovers from the 3GPP network to the non-3GPP network; and

detach the UE from the 3GPP network when all the bearer resources of the UE are deleted.

It is obvious to one of ordinary skill in the art that Cheon only related to delete the bear

in the source network, but fails to disclose that the network device is configured to receive a

delete bearer request sent by a serving gateway (GW) of a 3GPP network when a handover

from the 3GPP network to a non-3GPP network occurs, wherein the delete bearer request

carries a cause information element (IE) which indicates a user equipment handovers from the

3GPP network to the non-3GPP network. In addition, Choen also fails to disclose that the

network device is configured to detach the UE from the 3GPP network when all the bearer

resources of the UE are deleted.

Dependent Claim 9

Cheon discloses that at paragraphs [0049], the GGSN 230 transmits the PDP context



Furthermore, Cheon fails to disclose that the cause IE is set to "UE's accessing RAT changed


Dependent Claim 10



Dependent claim 10 is not anticipated by Cheon at least because it depends from claim

9. Furthermore, Cheon fails to disclose that the delete bearer request is sent from a packet data

network gateway to the network device via the serving gateway, wherein the cause IE is set to

5

NSN677-1002,


"UE's accessing RAT changed from a 3GPP network to a non-3GPP network" by the packet

data network gateway."

Dependent Claim 11


8. Furthermore, Cheon fails to disclose the network device is configured to detach the UE from

the 3GPP network without sending a detach request message to the UE.

Dependent Claim 12



the 3GPP network if a terminal capability of the UE is single radio capability.

Dependent Claim 13



the 3GPP network if access policy information of an operator is single radio access.

Dependent Claim 14



the 3GPP network if a terminal capability of the UE is dual radio capability and access policy

information of an operator is single radio access; or if the terminal capability of the UE is

single radio capability and the access policy information of the operator is dual radio access; or

if the terminal capability of the UE is the single radio capability and the access policy


2. U.S. Patent Publication No. 2006/0153124 (Nishi)

Independent Claim 1

6

NSN677-1002,


U.S. Patent Publication No. 2006/0153124 by Nishi (hereinafter "Nishi") describes a

method for how to maintaining consistent network connections when mobile station handovers

from GPRS network to WLAN network.

Further, Nishi disclosed that at steps 1-6, MT enters an GPRS access network, the client

connects to the GPRS access network which provides connectivity to SGSN using a primary

PDP context which is preferably requested by the MT; at steps 7-11, the MT handovers to a

WLAN access network from the GPRS access network, the client connects to the WLAN

access network by a secondary PDP context which has the same IP address with the primary

PDP context; at step 12, the client has two flow paths to the same GGSN with different priority

levels and there is no change in the IP address of the client, thus no effect to the higher layer

protocols; at steps 13-17, when the MT roams out of the WLAN hotspot, M-WSG sends a

delete PDP context request, the GGSN removes the secondary PDP context from its context

table, M-WSG cleans up associated session and GTP context information (see Nishi, at

paragraphs [0044]-[0067], Fig. 2 and Fig. 3).

Independent claim 1 is not anticipated by Nishi at least because Nishi fails to disclose

steps of: receiving, by a mobility management entity (MME) of the 3GPP network, a delete



network to the non-3GPP network; detaching, by the MME, the UE from the 3GPP network


It is obvious to one of ordinary skill in the art that Nishi only discloses: when the MT

roams out of the WLAN hotspot, M-WSG sends a delete PDP context request, the secondary

PDP context which is established when the MT accesses the WLAN. But Nishi fails to disclose

that the MME receives a delete bearer request which carries a cause information element (IE);

wherein the cause IE indicates the UE handovers from the 3GPP network to the non-3GPP

network; the MME delete bearer resources of the UE. In addition, Nishi also fails to disclose

that the MME detach the UE from the 3GPP network when all the bearer resources of the UE

are deleted.

Dependent Claim 2

7

NSN677-1002,


Nishi disclosed that at paragraphs [0063], M-WSG sends a delete PDP context request

with the context parameters.

Dependent claim 2 is not anticipated by Nishi at least because it depends from claiml.

Furthermore, Nishi fails to disclose that the cause IE is set to "UE's accessing RAT changed


Dependent Claim 3



Dependent claim 3 is not anticipated by Nishi at least because it depends from claim 2.

Furthermore, Nishi fails to disclose "setting, by a packet data network gateway (PDN GW), the

cause IE to "UE's accessing RAT changed from a 3GPP network to a non-3GPP network";




Dependent Claim 4


Furthermore, Nishi fails to disclose "detaching, by the MME, the UE from the 3GPP network


Dependent Claim 5


Furthermore, Nishi fails to disclose "detaching, by the MME, the UE from the 3GPP network if

a terminal capability of the UE is single radio capability."

Dependent Claim 6



access policy information of an operator is single radio access."

8

NSN677-1002,


Dependent Claim 7



a terminal capability of the UE is dual radio capability and access policy information of an





Independent Claim 8

U.S. Patent Publication No. 2006/0153124 by Nishi (hereinafter "Nishi") describes a

method for how to maintaining consistent network connections when mobile station handovers

from GPRS network to WLAN network.

Further, Nishi disclosed that at steps 1-6, MT enters an GPRS access network, the client

connects to the GPRS access network which provides connectivity to SGSN using a primary

PDP context which is preferably requested by the MT; at steps 7-11, the MT handovers to a

WLAN access network from the GPRS access network, the client connects to the WLAN

access network by a secondary PDP context which has the same IP address with the primary

PDP context; at step 12, the client has two flow paths to the same GGSN with different priority

levels and there is no change in the IP address of the client, thus no effect to the higher layer

protocols; at steps 13-17, when the MT roams out of the WLAN hotspot, M-WSG sends a

delete PDP context request, the GGSN removes the secondary PDP context from its context

table, M-WSG cleans up associated session and GTP context information (see Nishi, at

paragraphs [0044]-[0067], Fig. 2 and Fig. 3).

Independent claim 8 is not anticipated by Nishi at least because Nishi fails to disclose

that a network device is configured to receive a delete bearer request sent by a serving gateway

(GW) of a 3GPP network when a handover from the 3GPP network to a non-3GPP network

occurs, wherein the delete bearer request carries a cause information element (IE) which

indicates a user equipment handovers from the 3GPP network to the non-3GPP network; and


9

NSN677-1002,


It is obvious to one of ordinary skill in the art that Nishi only discloses: when the MT

roams out of the WLAN hotspot, M-WSG sends a delete PDP context request, the secondary

PDP context which is established when the MT accesses the WLAN. But Nishi fails to disclose

that the network device is configured to receive a delete bearer request sent by a serving

gateway (GW) of a 3GPP network when a handover from the 3GPP network to a non-3GPP

network occurs, wherein the delete bearer request carries a cause information element (IE)

which indicates a user equipment handovers from the 3GPP network to the non-3GPP network.

In addition, Nishi also fails to disclose that the network device is configured to detach the UE

from the 3GPP network when all the bearer resources of the UE are deleted.

Dependent Claim 9




Furthermore, Nishi fails to disclose that the cause IE is set to "UE's accessing RAT changed


Dependent Claim 10




Furthermore, Nishi fails to disclose that the delete bearer request is sent from a packet data




Dependent Claim 11


Furthermore, Nishi fails to disclose the network device is configured to detach the UE from the

3GPP network without sending a detach request message to the UE.

10

NSN677-1002,


Dependent Claim 12



3GPP network if a terminal capability of the UE is single radio capability.

Dependent Claim 13



3GPP network if access policy information of an operator is single radio access.

Dependent Claim 14



3GPP network if a terminal capability of the UE is dual radio capability and access policy





3. U.S. Patent Publication No. 2006/0146803 (Bae)

Independent Claim 1

U.S. Patent Publication No. 2006/0146803 by Bae (hereinafter "Bae") describes a

method for providing fast, seamless handoff during WLAN-UMTS interworking. The method

performs pre-registration and pre-authentication processed before occurrence of handoff in

order to solve the delay problem occurring during handoff from a WLAN network to a UMTS

network (see Bae, at Summary of the invention, and Abstract).

Further, Bae discloses at step 304, the UE 201 delivers a pre-registration Request

message for requesting pre-authentication and pre-registration to an SGSN 208 via a GGSN

209 of a UMTS network 205 through a WLAN AN 210; at step 318, GGSN 209 transmits a

pre-registration Response message to the UE 201 via the WLAN AN 210 to inform the UE 201

of completion of the pre-authentication and pre-registration process; at step 320, the UE 201

11

NSN677-1002,


performs detachment from the WLAN AN 210 through an AP 202, and then performs L2

handoff to the UMTS network 250 (UE movement) (see Bae, at paragraphs [0045]-[0052], and

Fig3).

Independent claim 1 is not anticipated by Bae at least because Bae fails to disclose steps of:

receiving, by a mobility management entity (MME) of the 3GPP network, a delete bearer request

sent by a serving gateway (GW) of the 3GPP network which carries a cause information element

(IE), wherein the cause IE indicates the UE handovers from the 3GPP network to the non-3GPP

network; deleting, by the MME, bearer resources of the UE; detaching, by the MME, the UE


It is obvious to one of ordinary skill in the art that Bae discloses that after completion of the

pre-authentication and pre-registration process, the UE 201 performs detachment from the

WLAN AN 210 through an AP 202, and then performs handoff to the UMTS network 250, but

fails to disclose that the MME receives a delete bearer request which carries a cause information

element (IE); wherein the cause IE indicates the UE handovers from the 3GPP network to the

non-3GPP network; and the MME deletes bearer resources of the UE. In addition, Bae also fails

to disclose the MME detaches the UE from the 3GPP network when all the bearer resources of

the UE are deleted.

Dependent Claim 2

Bae discloses that at step 318, GGSN 209 transmits a pre-registration Response

message to the UE 201 via the WLAN AN 210 to inform the UE 201 of completion of the pre-

authentication and pre-registration process; at step 320, the UE 201 performs detachment from

the WLAN AN 210 through an AP 202 (see Bae, at paragraph [0052]).

Dependent Claim 2 is not anticipated by Bae at least because it depends from claiml.

Furthermore, Bae fails to disclose that the cause IE is set to "UE's accessing RAT changed


Dependent Claim 3



12

NSN677-1002,




Dependent claim 3 is not anticipated by Bae at least because it depends from claim 2.

Furthermore, Bae fails to disclose "setting, by a packet data network gateway (PDN GW), the

cause IE to "UE' s accessing RAT changed from a 3GPP network to a non-3GPP network";




Dependent Claim 4


Furthermore, Bae fails to disclose "detaching, by the MME, the UE from the 3GPP network


Dependent Claim 5


Furthermore, Bae fails to disclose "detaching, by the MME, the UE from the 3GPP network if a

terminal capability of the UE is single radio capability."

Dependent Claim 6


Furthermore, Bae fails to disclose "detaching, by the MME, the UE from the 3GPP network if


Dependent Claim 7


Furthermore, Bae fails to disclose "detaching, by the MME, the UE from the 3GPP network if a

terminal capability of the UE is dual radio capability and access policy information of an



13

NSN677-1002,




Independent Claim 8

U.S. Patent Publication No. 2006/0146803 by Bae (hereinafter "Bae") describes a

method for providing fast, seamless handoff during WLAN-UMTS interworking. The method

performs pre-registration and pre-authentication processed before occurrence of handoff in

order to solve the delay problem occurring during handoff from a WLAN network to a UMTS

network (see Bae, at Summary of the invention, and Abstract).

Further, Bae discloses at step 304, the UE 201 delivers a pre-registration Request

message for requesting pre-authentication and pre-registration to an SGSN 208 via a GGSN

209 of a UMTS network 205 through a WLAN AN 210; at step 318, GGSN 209 transmits a

pre-registration Response message to the UE 201 via the WLAN AN 210 to inform the UE 201

of completion of the pre-authentication and pre-registration process; at step 320, the UE 201

performs detachment from the WLAN AN 210 through an AP 202, and then performs L2

handoff to the UMTS network 250 (UE movement) (see Bae, at paragraphs [0045]-[0052], and

Fig3).

Independent claim 8 is not anticipated by Bae at least because Bae fails to disclose that a

network device is configured to receive a delete bearer request sent by a serving gateway (GW)

of a 3GPP network when a handover from the 3GPP network to a non-3GPP network occurs,

wherein the delete bearer request carries a cause information element (IE) which indicates a user

equipment handovers from the 3GPP network to the non-3GPP network; and detach the UE from

the 3GPP network when all the bearer resources of the UE are deleted.

It is obvious to one of ordinary skill in the art that Bae discloses that after completion of

the pre-authentication and pre-registration process, the UE 201 performs detachment from the

WLAN AN 210 through an AP 202, and then performs handoff to the UMTS network 250, but

fails to disclose that the network device is configured to receive a delete bearer request sent by

a serving gateway (GW) of a 3GPP network when a handover from the 3GPP network to a non-

3GPP network occurs, wherein the delete bearer request carries a cause information element

(IE) which indicates a user equipment handovers from the 3GPP network to the non-3GPP

14

NSN677-1002,


network. In addition, Bae also fails to disclose that the network device is configured to detach

the UE from the 3GPP network when all the bearer resources of the UE are deleted.

Dependent Claim 9






Furthermore, Bae fails to disclose that the cause IE is set to "UE's accessing RAT changed


Dependent Claim 10




the WLAN AN 210 through an AP 202 (paragraph [0052]).


Furthermore, Bae fails to disclose that the delete bearer request is sent from a packet data




Dependent Claim 11


Furthermore, Bae fails to disclose the network device is configured to detach the UE from the


Dependent Claim 12

15

NSN677-1002,





Dependent Claim 13




Dependent Claim 14








4. U.S. Patent Publication No. 2010/0135245

Independent Claim 1

U.S. Patent Publication No. 2010/0135245 by Zhu (hereinafter "Zhu") describes a

method for avoiding resource being released mistakenly during tracking area update or

handover process (see Zhu, at Abstract).

Further, Zhu discloses at step 302, if the target MME determines to select a new

Serving GW, sending notification message to the original MME by the target MME to indicate

that the target MME has selected a new Serving GW; at step 303, after the original MME

determines that Serving GW has changed, sending a request for deleting bearer context to the

old Serving GW by the original MME (see Zhu, at paragraphs [0041]40043], [0058]-[0061],

[0078]-[0082], [0095]40098], Fig. 3, Fig. 4, Fig. 5, and Fig. 6).

Independent claim 1 is not anticipated by Zhu at least because Zhu fails to disclose steps of:

receiving, by a mobility management entity (MME) of the 3GPP network, a delete bearer request

16

NSN677-1002,


sent by a serving gateway (GW) of the 3GPP network which carries a cause information element

(IE), wherein the cause IE indicates the UE handovers from the 3GPP network to the non-3GPP

network; deleting, by the MME, bearer resources of the UE; detaching, by the MME, the UE


It is obvious to one of ordinary skill in the art that Zhu discloses that the target MME

sends a notification message to the original MME when the target MME determines to select a

new Serving GW. The original MME determines that Serving GW has changed after receiving

the notification message, and sends a request for deleting bearer context to the old Serving GW.

But Zhu fails to disclose that the MME receives a delete bearer request which carries a cause


network to the non-3GPP network; and the MME deletes bearer resources of the UE. In addition,

Zhu also fails to disclose the MME detaches the UE from the 3GPP network when all the bearer

resources of the UE are deleted.

Dependent Claim 2

Zhu discloses that at step 302, if the target MME determines to select a new Serving

GW, sending notification message to the original MME by the target MME to indicate that the

target MME has selected a new Serving GW (see Zhu, at paragraphs [0041]-[0043]).

Dependent claim 2 is not anticipated by Ba at least because it depends from claiml.

Furthermore, Zhu fails to disclose that the cause IE is set to "UE's accessing RAT changed


Dependent Claim 3




Dependent claim 3 is not anticipated by Zhu at least because it depends from claim 2.

Furthermore, Zhu fails to disclose "setting, by a packet data network gateway (PDN GW), the

cause IE to "UE's accessing RAT changed from a 3GPP network to a non-3GPP network";


17

NSN677-1002,




Dependent Claim 4


Furthermore, Zhu fails to disclose "detaching, by the MME, the UE from the 3GPP network


Dependent Claim 5


Furthermore, Zhu fails to disclose "detaching, by the MME, the UE from the 3GPP network if

a terminal capability of the UE is single radio capability."

Dependent Claim 6




Dependent Claim 7



a terminal capability of the UE is dual radio capability and access policy information of an





Independent Claim 8

U.S. Patent Publication No. 2010/0135245 by Zhu (hereinafter "Zhu") describes a

method for avoiding resource being released mistakenly during tracking area update or

handover process (see Zhu, at Abstract).

18

NSN677-1002,


Further, Zhu discloses at step 302, if the target MME determines to select a new

Serving GW, sending notification message to the original MME by the target MME to indicate

that the target MME has selected a new Serving GW; at step 303, after the original MME

determines that Serving GW has changed, sending a request for deleting bearer context to the

old Serving GW by the original MME (see Zhu,. at paragraphs [0041]40043], [0058]-[0061],

[0078]-[0082], [0095]40098], Fig. 3, Fig. 4, Fig. 5, and Fig. 6).

Independent claim 8 is not anticipated by Zhu at least because Zhu fails to disclose that a

network device is configured to receive a delete bearer request sent by a serving gateway (GW)

of a 3GPP network when a handover from the 3GPP network to a non-3GPP network occurs,

wherein the delete bearer request carries a cause information element (IE) which indicates a user

equipment handovers from the 3GPP network to the non-3GPP network; and detach the UE from

the 3GPP network when all the bearer resources of the UE are deleted.

It is obvious to one of ordinary skill in the art that Zhu discloses that the target MME

sends a notification message to the original MME when the target MME determines to select a

new Serving GW. The original MME determines that Serving GW has changed after receiving

the notification message, and sends a request for deleting bearer context to the old Serving GW.

But Zhu fails to disclose that the network device is configured to receive a delete bearer request

sent by a serving gateway (GW) of a 3GPP network when a handover from the 3GPP network

to a non-3GPP network occurs, wherein the delete bearer request carries a cause information

element (IE) which indicates a user equipment handovers from the 3GPP network to the non-

3GPP network. In addition, Zhu also fails to disclose that the network device is configured to


Dependent Claim 9





Furthermore, Zhu fails to disclose that the cause IE is set to "UE's accessing RAT changed


19

NSN677-1002,


Dependent Claim 10





Furthermore, Zhu fails to disclose that the delete bearer request is sent from a packet data




Dependent Claim 11


Furthermore, Zhu fails to disclose the network device is configured to detach the UE from the


Dependent Claim 12




Dependent Claim 13




Dependent Claim 14






20

NSN677-1002,




5. 3GPP TS 23.401 V1.1.0 (3GPP TS)

Independent Claim 1

3GPP TS 23.401 V1.1.0 (hereinafter "3GPP TS") describes a detach procedure for

detaching the UE when the UE accesses the EPS through E-UTRAN. Three detach procedures

are provided in 3GPP TS: UE-Initiated Detach Procedure, MME-initiated Detach Procedure, and

HSS-Initiated Detach Procedure (see 3GPP TS, Section 5.3.8.1, 5.3.8.2, 5.3.8.3, 5.3.8.4, 5.3.9,

Figure 5.3.8.2, Figure 5.3.8.3-1 and Figure 5.3.8.4-1).

Further, Section 5.3.8.2 of 3GPP TS discloses UE-Initiated Detach Procedure, wherein

the UE sends NAS message Detach Request to the MME, the MME sends Delete Bearer Request

to the Serving GW and a Detach Accept to the UE, and release the S 1 -MME signalling

connection for the UE by sending S1 Release Command to the eNodeB with Cause =Detach.

Section 5.3.8.3 of 3GPP TS discloses MME-initiated Detach Procedure, wherein the

MME initiated detach procedure, the MME may not send the detach request message to the UE

in case of implicit detach, and the MME may explicitly detach the UE by sending a Detach

Request message to the UE. And the MME sends the Delete Bearer Request Message to the

Serving GW.

Section 5.3.8.4 of 3GPP TS discloses HSS-Initiated Detach Procedure, wherein the HSS

initiates a detach procedure to update the subscriber's MM context at the MME and to delete

the EPS bearer because that the UE'S accessing RAT is changed from 3GPP to Non-3GPP.The

MME informs the UE, and sends a Delete Bearer Request message to the Serving GW.

Independent claim 1 is not anticipated by 3GPP TS at least because 3GPP TS fails to

disclose steps of: receiving, by a mobility management entity (MME) of the 3GPP network, a

delete bearer request sent by a serving gateway (GW) of the 3GPP network which carries a

cause information element (IE); wherein the cause IE indicates the UE handovers from the

3GPP network to the non-3GPP network; deleting, by the MME, bearer resources of the UE;

detaching, by the MME, the UE from the 3GPP network when all the bearer resources of the

UE are deleted.

21

NSN677-1002,


Obviously, 3GPP TS only disclose a detach procedure, In the UE-Initiated Detach

Procedure, it is the UE that decides to detach from the network, so the UE send a detach request

to the MME, so the MME does not need to make a decision whether to detach the UE, and just

need to send the Delete Bearer Request Message to the Serving GW to delete the Bear. In the

MME-initiated Detach Procedure, the MME initiated detach procedure, the MME decide to

detach a UE, and then sends the Delete Bearer Request Message to the Serving GW to delete

the bear. In the HSS-initiated Detach Procedure, HSS makes the decision to detach the UE, and

told the MME to detach the UE. But 3GPP TS fails to disclose that MME receives a delete


information element (IE), wherein the cause IE indicates the UE handovers from the 3GPP

network to the non-3GPP network, and deletes bearer resources of the UE. 3GPP TS also fail to

disclose that the MME delete the bear resources of the UE first, and then decide to detach the

UE from the 3GPP network when all the bear resources of the UE have been deleted.

Dependent Claim 2

3GPP TS discloses that at step 2 of Section 5.3.8.2, at step 2 of Section 5.3.8.3 and at

step 3 of Section 5.3.8.4, the active EPS bearers in the Serving GW regarding this particular UE

are deactivated by the MME sending Delete Bearer Request to the Serving GW.

Dependent claim 2 is not anticipated by 3GPP TS at least because it depends from

claiml. Furthermore, 3GPP TS fails to discloses that the cause IE is set to "UE's accessing

RAT changed from a 3GPP network to a non-3GPP network."

Dependent Claim 3

3GPP TS disclosed that at step 2 of Section 5.3.8.2, at step 2 of Section 5.3.8.3 and at



Dependent claim 3 is not anticipated by 3GPP TS at least because it depends from claim

2. Furthermore, 3GPP TS fails to disclose "setting, by a packet data network gateway (PDN

GW), the cause IE to "UE's accessing RAT changed from a 3GPP network to a non-3GPP

network"; sending, by the PDN GW, the delete bearer request message carrying the cause IE to

22

NSN677-1002,


the serving GW; and sending, by the serving GW, the delete bearer request message carrying

the cause IE to the MME."

Dependent Claim 4


1. Furthermore, 3GPP TS fails to disclose "detaching, by the MME, the UE from the 3GPP

network without sending a detach request message to the UE."

Dependent Claim 5


1. Furthermore, 3GPP TS fail to disclose "detaching, by the MME, the UE from the 3GPP

network if a terminal capability of the UE is single radio capability."

Dependent Claim 6



network if access policy information of an operator is single radio access."

Dependent Claim 7



network if a terminal capability of the UE is dual radio capability and access policy information

of an operator is single radio access; or if the terminal capability of the UE is single radio

capability and the access policy information of the operator is dual radio access; or if the

terminal capability of the UE is the single radio capability and the access policy information of

the operator is the single radio access."

Independent Claim 8

3GPP TS 23.401 V1.1.0 (hereinafter "3GPP TS") describes a detach procedure for

detaching the UE when the UE accesses the EPS through E-UTRAN. Three detach procedures

are provided in 3GPP TS: UE-Initiated Detach Procedure, MME-initiated Detach Procedure, and

23

NSN677-1002,


HSS-Initiated Detach Procedure (see 3GPP TS, at Section 5.3.8.1, 5.3.8.2, 5.3.8.3, 5.3.8.4, 5.3.9,

Figure 5.3.8.2, Figure 5.3.8.3-1 and Figure 5.3.8.4-1).

Further, Section 5.3.8.2 of 3GPP TS discloses UE-Initiated Detach Procedure, wherein

the UE sends NAS message Detach Request to the MME, the MME sends Delete Bearer Request

to the Serving GW and a Detach Accept to the UE, and release the S 1-MME signalling

connection for the UE by sending S1 Release Command to the eNodeB with Cause =Detach.

Section 5.3.8.3 of 3GPP TS discloses MME-initiated Detach Procedure, wherein the

MME initiated detach procedure, the MME may not send the detach request message to the UE

in case of implicit detach, and the MME may explicitly detach the UE by sending a Detach

Request message to the UE. And the MME sends the Delete Bearer Request Message to the

Serving GW.

Section 5.3.8.4 of 3GPP TS discloses HSS-Initiated Detach Procedure, wherein the HSS

initiates a detach procedure to update the subscriber's MM context at the MME and to delete

the EPS bearer because that the UE'S accessing RAT is changed from 3GPP to Non-3GPP.The

MME informs the UE, and sends a Delete Bearer Request message to the Serving GW.

Independent claim 8 is not anticipated by 3GPP TS at least because 3GPP TS fail to

disclose that a network device is configured to receive a delete bearer request sent by a serving

gateway (GW) of a 3GPP network when a handover from the 3GPP network to a non-3GPP

network occurs, wherein the delete bearer request carries a cause information element (IE)

which indicates a user equipment handovers from the 3GPP network to the non-3GPP network;

delete bearer resources of the user equipment; and detach the UE from the 3GPP network when

all the bearer resources of the UE are deleted.

Obviously, 3GPP TS only disclose a detach procedure, In the UE-Initiated Detach

Procedure, it is the UE that decides to detach from the network, so the UE send a detach request

to the MME, so the MME does not need to make a decision whether to detach the UE, and just

need to send the Delete Bearer Request Message to the Serving GW to delete the Bear. In the

MME-initiated Detach Procedure, the MME initiated detach procedure, the MME decide to

detach a UE, and then sends the Delete Bearer Request Message to the Serving GW to delete the

bear. In the HSS-initiated Detach Procedure, HSS makes the decision to detach the UE, and told

the MME to detach the UE. But 3GPP TS fails to disclose that a network device is configured to

receive a delete bearer request sent by a serving gateway (GW) of a 3GPP network when a

24

NSN677-1002,


handover from the 3GPP network to a non-3GPP network occurs, wherein the delete bearer

request carries a cause information element (IE) which indicates a user equipment handovers

from the 3GPP network to the non-3GPP network; delete bearer resources of the user equipment.

3GPP TS also fail to disclose that a network device is configured to detach the UE from the

3GPP network when all the bearer resources of the UE are deleted.

Dependent Claim 9

3GPP TS discloses that that at step 2 of Section 5.3.8.2, at step 2 of Section 5.3.8.3 and

at step 3 of Section 5.3.8.4, the active EPS bearers in the Serving GW regarding this particular

UE are deactivated by the MME sending Delete Bearer Request to the Serving GW.


8. Furthermore, 3GPP TS fail to disclose that the cause IE is set to "UE's accessing RAT

changed from a 3GPP network to a non-3GPP network."

Dependent Claim 10

3GPP TS disclosed that at step 2 of Section 5.3.8.2, at step 2 of Section 5.3.8.3 and at




claim 9. Furthermore, 3GPP TS fail to disclose that the delete bearer request is sent from a

packet data network gateway to the network device via the serving gateway, wherein the cause

IE is set to "UE's accessing RAT changed from a 3GPP network to a non-3GPP network" by

the packet data network gateway."

Dependent Claim 11


claim 8. Furthermore, 3GPP TS fail to disclose the network device is configured to detach the

UE from the 3GPP network without sending a detach request message to the UE.

Dependent Claim 12

25

NSN677-1002,




UE from the 3GPP network if a terminal capability of the UE is single radio capability.

Dependent Claim 13



UE from the 3GPP network if access policy information of an operator is single radio access.

Dependent Claim 14



UE from the 3GPP network if a terminal capability of the UE is dual radio capability and

access policy information of an operator is single radio access; or if the terminal capability of

the UE is single radio capability and the access policy information of the operator is dual radio

access; or if the terminal capability of the UE is the single radio capability and the access

policy information of the operator is the single radio access.

26

NSN677-1002,


C. Detailed Explanation of Patentability

1. 35 U.S.C. §102

Applicant respectfully submits that for at least the reasons set forth above, none of Cheon,

Nishi, Bae, Zhu and 3GPP TS 23.401 anticipates any of now pending claims 1-14 of the

present patent application under 35 U.S.C. § 102 (a)-(g) at least because none of these

references discloses each and every limitation of any of now pending claims 1-14.

2. 35 U.S.C. §103(a)

Applicant respectfully submits that none of Cheon, Nishi, Bae, Zhu and 3GPP TS 23.401

either standing alone or in combination, renders claims 1-14 of the present patent application

obvious under 35 U.S.C. §103(a) at least because none of these references discloses or suggests

a method, a corresponding apparatus and a corresponding computer readable medium for

implementing the method. The method includes: receiving, by a mobility management entity

(MME) of the 3GPP network, a delete bearer request sent by a serving gateway (GW) of the

3GPP network which carries a cause information element (IE), wherein the cause IE indicates

the UE handovers from the 3GPP network to the non-3GPP network; deleting, by the MME,

bearer resources of the UE; detaching, by the MME, the UE from the 3GPP network when all

the bearer resources of the UE are deleted. Moreover, no suggestion or impetus in the art to

modify any of the identified references to include the features of the invention that the

references are lacking.

3. 35 U.S.C. § 103(c)

Applicant respectfully submits that none of Cheon, Nishi, Bae, Zhu and 3GPP TS 23.401

can be disqualified under 35 U.S.0 § 103(c).

27

NSN677-1002,


D. Statement of Utility

The present invention, as set forth in independent claim 1 and claim 8 may be used to

receive, by a mobility management entity (MME) of a 3GPP (3rd generation partnership

project) network, a delete bearer request sent by a serving gateway (GW) of the 3GPP network

which carries a cause information element (IE), wherein the cause IE indicates the user

equipment (UE) handovers from the 3GPP network to the non-3GPP network; delete, by the

MME, bearer resources of the UE; and detach, by the MME, the UE from the 3GPP network


28

NSN677-1002,


E. Showing of Support of Each Claim Limitation

The following table provides references to the disclosure for each limitation of Claims 1-

14. Although this table refers to selected sections of the disclosure for each limitation,

additional sections may also provide further support for the claim limitations.

Table 1. Support from present application

CLAIM LIMITITION SUPPORT

1. A method for detaching a user At least paragraphs [0154], [0158], [0159]

equipment (UE) when a handover from a 3rd and Fig.6.

generation partnership project (3GPP) network In step 608a, the PDN GW sends a delete

to a non-3GPP network occurs, comprising: bearer request message to the serving GW, and

receiving, by a mobility management then the serving GW sends the received delete

entity (MME) of the 3GPP network, a delete bearer request message to the MME, and adds

bearer request sent by a serving gateway (GW) a cause IE in the delete bearer request message

of the 3GPP network which carries a cause to indicate the reason of the deletion, and the

information element (IE), wherein the cause IE MME deletes the bearer resources.

indicates the UE handovers from the 3GPP Step 608a or step 608b further includes

network to the non-3GPP network; the following: the MME deletes the bearer

deleting, by the MME, bearer resources of resources after receiving the delete bearer

the UE; request message. If the MME finds that all

detaching, by the MME, the UE from bearer resources of the UE are deleted, the

the 3GPP network when all the bearer MME further determines whether to delete an

resources of the UE are deleted. MM context (i.e., detaching the UE from the

3GPP network) and whether to send a detach

request message to the UE. Specifically, the

process includes the following circumstances.

1) The MME makes the following

determination according to the cause IE carried

in the delete bearer request. The MME

determines whether the cause IE carried in the

29

NSN677-1002,

Docket No. HW708564

Accelerated Examination Support Document

received delete bearer request message is

represented as "UE's accessing RAT changed

from a 3GPP network to a non-3GPP

network"; if yes, the MME deletes the MM

context of the UE, and does not send the detach

request message to the UE; otherwise, the

MME sends the detach request message to the

UE and notifies the UE to delete the MM

context and the bearer resources of the 3GPP

network in the UE.

2. The method according to claim 1,

wherein the cause IE is set to "UE's accessing

At least paragraph [0155].

In this step, as for the bearer deletion

RAT changed from a 3GPP network to a non- caused by the handover or switching of the

3GPP network". UE from the 3GPP network to the non-3GPP

network, the PDN GW sets the cause IE as

"UE's accessing RAT changed from a 3GPP

network to a non-3GPP network".


further comprising:

At least paragraphs [0154] and [0155].

In step 608a, the PDN GW sends a delete

setting, by a packet data network gateway bearer request message to the serving GW, and

(PDN GW), the cause IE to "UE' s accessing then the serving GW sends the received delete

RAT changed from a 3GPP network to a non- bearer request message to the MME, and adds

3GPP network"; a cause IE in the delete bearer request message

sending, by the PDN GW, the delete to indicate the reason of the deletion, and the

bearer request message carrying the cause IE to MME deletes the bearer resources.

the serving GW; and In this step, as for the bearer deletion

sending, by the serving GW, the delete caused by the handover or switching of the

bearer request message carrying the cause IE UE from the 3GPP network to the non-3GPP

to the MME. network, the PDN GW sets the cause IE as


30

NSN677-1002,

Docket No. HW708564




wherein detaching, by the MME, the UE from

the 3GPP network further comprises:

detaching, by the MME, the UE from

the 3GPP network without sending a detach

request message to the UE.



determination according to the cause IE

carried in the delete bearer request. The

MME determines whether the cause IE

carried in the received delete bearer request

message is represented as "UE's accessing

RAT changed from a 3GPP network to a non-

3GPP network"; if yes, the MME deletes the

MM context of the UE, and does not send the

detach request message to the UE.


comprising:

detaching, by the MME, the UE from the

3GPP network if a terminal capability of the

UE is single radio capability.



determination according to the IE carried in

the delete bearer request and the terminal

capability of the UE. If the MME determines

that the IE carried in the received delete

bearer request message is represented as


network to a non-3GPP network", and the

MME knows that the terminal capability of

the UE is "single radio capability", the MME

deletes the MM context of the UE.


comprising:


3GPP network if access policy information of





the delete bearer request and the access

policy information of the operator. If the

MME determines that the IE carried in the

31

NSN677-1002,

Docket No. HW708564





network", and the MME knows that the

access policy information of the operator is

"single radio access", the MME deletes the



comprising:



detaching, by the MME, the UE from the determination according to the IE carried in

3GPP network if a terminal capability of the the delete bearer request, the terminal

UE is dual radio capability and access policy capability of the UE, and the access policy

information of an operator is single radio information of the operator. If the MME

access; or if the terminal capability of the UE determines that the IE carried in the received

is single radio capability and the access policy delete bearer request message is represented

information of the operator is dual radio as "UE's accessing RAT changed from a

access; or if the terminal capability of the UE 3GPP network to a non-3GPP network", the

is the single radio capability and the access terminal capability of the UE is "dual radio

policy information of the operator is the single capability", and the access policy information

radio access. of the operator is "single radio access", or if

the MME determines that the IE carried in the




network", the access policy information of

the operator is "multi radio access", and the

terminal capability of the UE is "single radio

capability", or if the MME determines that

the IE carried in the received delete bearer

request message is represented as "UE's

32

NSN677-1002,

Docket No. HW708564


accessing RAT changed from a 3GPP

network to a non-3GPP network", the


capability", and the access policy information

of the operator is "single radio access", the

MME deletes the MM context of the UE.

8.A network device, configured to: At least paragraphs [0154], [0158], [0159]

receive a delete bearer request sent by a and Fig.6.

serving gateway (GW) of a 3GPP network In step 608a, the PDN GW sends a delete

when a handover from the 3GPP network to a bearer request message to the serving GW, and

non-3GPP network occurs, wherein the delete then the serving GW sends the received delete

bearer request carries a cause information bearer request message to the MME, and adds

element (IE) which indicates a user equipment a cause IE in the delete bearer request message

handovers from the 3GPP network to the non- to indicate the reason of the deletion, and the

3GPP network; MME deletes the bearer resources.

delete bearer resources of the user Step 608a or step 608b further includes

equipment; and the following: the MME deletes the bearer

detach the UE from the 3GPP network resources after receiving the delete bearer

when all the bearer resources of the UE are request message. If the MME finds that all

deleted. bearer resources of the UE are deleted, the

MME further determines whether to delete an

MM context (i.e., detaching the UE from the









33

NSN677-1002,

Docket No. HW708564






detach request message to the UE; otherwise,

the MME sends the detach request message

to the UE and notifies the UE to delete the

MM context and the bearer resources of the


9. The network device according to claim At least paragraph [0155].

8, wherein the cause IE is set to "UE's In this step, as for the bearer deletion

accessing RAT changed from a 3GPP network caused by the handover or switching of the

to a non-3GPP network". UE from the 3GPP network to the non-3GPP




10. The network device according to At least paragraphs [0154] and [0155].

claim 9, wherein the delete bearer request is In step 608a, the PDN GW sends a delete

sent from a packet data network gateway to the bearer request message to the serving GW, and

network device via the serving gateway,


then the serving GW sends the received delete

bearer request message to the MME, and adds

RAT changed from a 3GPP network to a non- a cause IE in the delete bearer request message

3GPP network" by the packet data network to indicate the reason of the deletion, and the

gateway. MME deletes the bearer resources.


caused by the handover or switching of the

UE from the 3GPP network to the non-3GPP




34

NSN677-1002,

Docket No. HW708564


11. The network device according to

claim 8, wherein the network device is

configured to detach the UE from the 3GPP

network without sending a detach request

message to the UE.












12. The network device according to At least paragraph [0160].

claim 8, wherein the network device is 2) The MME makes the following

configured to detach the UE from the 3GPP determination according to the IE carried in

network if a terminal capability of the UE is the delete bearer request and the terminal

single radio capability. capability of the UE. If the MME determines











network if access policy information of an the delete bearer request and the access

operator is single radio access. policy information of the operator. If the



35

NSN677-1002,

Docket No. HW708564











network if a terminal capability of the UE is the delete bearer request, the terminal

dual radio capability and access policy capability of the UE, and the access policy




















36

NSN677-1002,

Docket No. HW708564







Table 2. Support from parent application Serial No. 12/479,216
























37

NSN677-1002,

Docket No. HW708564












network in the UE.











further comprising:













38

NSN677-1002,

Docket No. HW708564






















comprising:

















comprising:









39

NSN677-1002,

Docket No. HW708564











comprising:























40

NSN677-1002,

Docket No. HW708564
































41

NSN677-1002,

Docket No. HW708564


































42

NSN677-1002,

Docket No. HW708564







message to the UE.















network if a terminal capability of the UE is

single radio capability.
















network if access policy information of an

operator is single radio access.







43

NSN677-1002,

Docket No. HW708564
































44

NSN677-1002,

Docket No. HW708564








Table 3. Support from Chinese Priority Document No.CN 200710137568.8























45

NSN677-1002,

Docket No. HW708564













network in the UE.











further comprising:












46

NSN677-1002,

Docket No. HW708564























comprising:

















comprising:







47

NSN677-1002,

Docket No. HW708564


an operator is single radio access. policy information of the operator. If the










comprising:






















48

NSN677-1002,

Docket No. HW708564
































49

NSN677-1002,

Docket No. HW708564


































50

NSN677-1002,

Docket No. HW708564








message to the UE.















network if a terminal capability of the UE is

single radio capability.
















network if access policy information of an

operator is single radio access.






51

NSN677-1002,

Docket No. HW708564
































52

NSN677-1002,

Docket No. HW708564









F. References that may be Disqualified as Prior Art

None of the references cited herein can be disqualified as prior art under 35 U.S.C.

103(c) as amended by the Cooperative Research and Technology Enhancement (CREATE) Act.

Conclusion

In view of this Accelerated Support Document, Applicant respectfully requests that the

Examiner grant the Petition for Accelerated Examination in the above-captioned patent

application. Applicant respectfully submits that the claims of the above-captioned patent

application are in condition for allowance, and respectfully request that the Examiner allow the

claims of the above-captioned patent application to issue in a U.S. patent.


/John K. Winn/ John K. Winn, Registration No. 58,579 LEYDIG, VOLT & MAYER, LTD. Two Prudential Plaza, Suite 4900 180 North Stetson Avenue Chicago, Illinois 60601-6731 (312) 616-5600 (telephone) (312) 616-5700 (facsimile)

Date: June 27, 2011

53

NSN677-1002,



Confirmation No.



TC/AU:

Examiner:

Docket No.: HW708564 (Client Reference No. 81356140US16)

Customer No.: 77399


INFORMATION DISCLOSURE STATEMENT

Pursuant to 37 CFR 1.97 and 1.98, the references listed on the enclosed Form PTO-1449 and/or Substitute Form PTO-1449 ("Form 1449") are submitted for consideration by the Examiner in the examination of the above-identified patent application.

The full consideration of the references in their entirety by the Examiner is respectfully requested and encouraged. Also, it is respectfully requested that the references be entered into the record of the present application and that the Examiner initial the appropriate area on the enclosed Form 1449, thereby indicating the Examiner's consideration of each of the references.

The submission of the references listed on the Form 1449 is for the purpose of providing a complete record and is not a concession that the references listed thereon are prior art to the invention claimed in the patent application. The right is expressly reserved to establish an invention date earlier than the above-identified filing date in order to remove any reference submitted herewith as prior art should it be deemed appropriate to do so.

Further, the submission of the references is not to be taken as a concession that any reference represents art that is relevant or analogous to the claimed invention. Accordingly, the right to argue that any reference is not properly within the scope of prior art relevant to an examination of the claims in the above-identified application is also expressly reserved.

The Information Disclosure Statement is being filed:

within any one of the following time periods: (a) within three months of the filing date of a national application other than a continued prosecution application under 37 CFR 1.53(d); (b) within three months of the date of entry of the national stage as set forth in 37 CFR 1.491 of an international application; (c) before the mailing date

Page 1 of 4

NSN677-1002,

Application No. TBD Information Disclosure Statement

of a first Office Action on the merits; or (d) before the mailing of a first Office Action after the filing of a request for continued examination under 37 CFR 1.114.

❑ Note: This submission includes the Statement under 37 CFR 1.704(d) (see "Statement under 37 CFR 1.704(d)" below), such that no reduction in patent term adjustment is warranted by the filing of this Information Disclosure Statement.

❑ after (a), (b), (c) or (d) above, but before the mailing date of a final action under 37 CFR 1.113, a Notice of Allowance under 37 CFR 1.311, or an action that otherwise closes prosecution in the application, and includes one of:

❑ the Statement under 37 CFR 1.97(e) (see "Statement under 37 CFR 1.97(e)" below).


— or —

❑ the fee of $180 set forth in 37 CFR 1.17(p) (see "Fees" below).

❑ on or after the mailing date of a final action under 37 CFR 1.113 or a Notice of Allowance under 37 CFR 1.311, or an action that otherwise closes prosecution in the application, and on or before payment of the issue fee, and includes the Statement under 37 CFR 1.97(e) (see "Statement under 37 CFR 1.97(e)" below), and the fee of $180 as set forth in 37 CFR 1.17(p) (see "Fees" below).

❑ on or after the mailing date of a Notice of Allowance under 37 CFR 1.311, and on or before payment of the issue fee, and within thirty days of receiving each item of information contained in the Information Disclosure Statement, and includes the Statement under 37 CFR 1.704(d) (see "Statement under 37 CFR 1.704(d)" below), and the fee of $180 as set forth in 37 CFR 1.17(p) (see "Fees" below). NOTE: This is for original applications except applications for a design patent, filed on or after May 29, 2000, wherein a paper containing only an Information Disclosure Statement in compliance with 37 CFR 1.97 and 1.98 is being filed.

Citation to Other Patent Applications

❑ The following U.S. patent applications are hereby brought to the attention of the Examiner. The U.S. patent applications claim subject matter that may be considered by the Examiner to be similar to the subject matter claimed in the above-identified patent application. Accordingly, these U.S. patent applications and/or the prosecution pertaining thereto may include information considered to be material to the prosecution of the above-identified patent application. Since the Examiner has electronic access to the prosecution histories of these U.S. patent applications, copies of prosecution materials therefrom are not provided herewith, but will be promptly provided if the Examiner so desires and requests same.

Page 2 of 4

NSN677-1002,

Application No. TBD

Information Disclosure Statement

U.S. APPLICATIONS STATUS (check one)

U.S. APPLICATIONS U.S. FILING DATE Patented Pending Never Issued: Abandoned/Expired

1.

2. 3.

Copies of the References

• Copies of any U.S. patents and published patent applications that are listed on the accompanying Form 1449 are not enclosed herewith. Copies of any other references identified on the accompanying Form 1449 are enclosed herewith.

• For each reference not in the English language, attached is at least one of the following: (a) an English translation in whole or in part or (b) a concise statement of relevance in the form of, for example, an English language counterpart, an English-language abstract, or an English-language version of the search report or action by a foreign patent office in a counterpart foreign application indicating the degree of relevance found by the foreign office.

❑ The references listed on the enclosed Form 1449 were previously identified in the parent application(s) of the present application, and copies of the references were furnished at that time. Accordingly, additional copies of the references are not submitted herewith, so as not to burden the file with duplicate copies of references. The Examiner is respectfully requested to carefully review the references in accordance with the requirements set out in the Manual of Patent Examining Procedure. In accordance with 37 CFR 1.98(d), the details of the parent application(s) relied upon for an earlier filing date under 35 USC 120 in which copies of the references were previously furnished are set out below:


U.S. APPLICATIONS U.S. FILING DATE Patented Pending Abandoned

1.

2. 3.

Statement under 37 CFR 1.97(e)

❑ The undersigned hereby states that each item of information contained in the Information Disclosure Statement was first cited in any communication from a foreign patent office in a counterpart foreign patent application not more than three months prior to the filing of the Information Disclosure Statement.

❑ The undersigned hereby states that no item of information contained in the Information Disclosure Statement was cited in a communication from a foreign patent office in a counterpart foreign patent application, and, to the knowledge of the undersigned after making reasonable inquiry, no item of information contained in the Information Disclosure Statement was known to any individual designated in

Page 3 of 4

NSN677-1002,

Application No. TBD Information Disclosure Statement

37 CFR 1.56(c) more than three months prior to the filing of the Information Disclosure Statement.

Statement under 37 CFR 1.704(d)

❑ The undersigned hereby states that each item of information contained in the Information Disclosure Statement was first cited in any communication from a foreign patent office in a counterpart application and that this communication was not received by any individual designated in 37 CFR 1.56(c) more than thirty days prior to the filing of the Information Disclosure Statement.

Fees

El No fee is owed by the applicant(s). ❑ Charge Deposit Account No. 12-1216 in the amount of $180.00 (37 CFR 1.17(p)).

Authorization to Charge Additional Fees

• If any additional fees are owed in connection with this communication, please charge Deposit Account No. 12-1216.

Instructions as to Overpayment

• Credit Account No. 12-1216. ❑ Refund

/John K. Winn/ John K. Winn, Reg. No. 58,579 LEYDIG, VOIT & MAYER, LTD. Two Prudential Plaza, Suite 4900 180 North Stetson Avenue Chicago, Illinois 60601-6731 (312) 616-5600 (telephone) (312) 616-5700 (facsimile)

Date: June 27, 2011

Page 4 of 4

NSN677-1002,

Please type a plus sign (+) inside this box

Substitute for form 1449A/B/PTO

INFORMATION DISCLOSURE STATEMENT BY APPLICANT

(Use as many sheets as necessary)

Complete if Known Application Number

Filing Date June 27, 2011 First Named Inventor WU, Wenfu Group Art Unit

Examiner Name

Sheet 1 of 1 Attorney Docket Number HW708564

U.S. PATENT DOCUMENTS

Examiner Initials

Doc. No.

U.S. Patent Document

Name of Patentee or Applicant Date of Publication Filing Date If Appropriate

Application or Patent Number

Kind Code

A A 2009/0286527 Al Cheon et al. November 19, 2009 A B 2006/0153124 Al Kant et al. July 13, 2006 A C 2006/0146803 Al Bae et al. July 6, 2006 A D 2010/0135245 Al Zhu et al. June 3, 2010

FOREIGN PATENT DOCUMENTS

Examiner Initials

Doc. No.

Foreign Patent Document

Name of Patentee or Applicant Date of

Publication Translation * Office


Kind Code

OTHER - NON PATENT LITERATURE DOCUMENTS

Examiner Initials

Doc. No.

Include name of the author (in CAPITAL LETTERS), title of the article (when appropriate), title of the item (book, magazine, journal, serial, symposium, catalog, etc.), date, page(s), volume-issue number (s), publisher, city and/or country where published.

Translation *

A E

"3GPP TS 23.401 — 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; GPRS enhancements for E-UTRAN access (Release 8)," July 2007, Version 1.1.0, 3rd Generation Partnership Project, Valbonne, France.

Examiner Signature Date Considered

" If the reference is not in English, then at least one of the following is provided: (a) an English translation in whole or in part or (b) a concise statement of relevance in the form of, for example, an English language counterpart, an English-language abstract, or an English-language version of the search report or action by a foreign patent office in a counterpart foreign application indicating the degree of relevance found by the foreign office.

NSN677-1002,

Electronic Patent Application Fee Transmittal

Application Number:

Filing Date:

Title of Invention: METHOD, SYSTEM, AND DEVICE FOR USER DETACHMENT WHEN A

HANDOVER OR CHANGE OCCURS IN HETERGENEOUS NETWORK

First Named Inventor/Applicant Name: Wenfu WU

Filer: John Knox Winn/Leanna Bultema

Attorney Docket Number: HW708564

Filed as Large Entity

Utility under 35 USC 111(a) Filing Fees

Description Fee Code Quantity Amount Sub-Total in

USD($)

Basic Filing:

Utility application filing 1011 1 330 330

Utility Search Fee 1111 1 540 540

Utility Examination Fee 1311 1 220 220

Pages:

Claims:

Miscellaneous-Filing:

Petition:

Petition fee- 37 CFR 1.17(h) (Group III) 1464 1 130 130

NSN677-1002,


USD($)

Patent-Appeals-and-Interference:

Post-Allowance-and-Post-Issuance:

Extension-of-Time:

Miscellaneous:

Total in USD ($) 1220

NSN677-1002,

Electronic Acknowledgement Receipt

EFS ID: 10394902

Application Number: 13169619

International Application Number:

Confirmation Number: 2286


HANDOVER OR CHANGE OCCURS IN HETERGENEOUS NETWORK


Customer Number: 77399


Filer Authorized By: John Knox Winn


Receipt Date: 27-JUN-2011

Filing Date:

Time Stamp: 16:20:30

Application Type: Utility under 35 USC 111(a)

Payment information:

Submitted with Payment yes

Payment Type Deposit Account

Payment was successfully received in RAM $1220

RAM confirmation Number 2966

Deposit Account 121216

Authorized User

The Director of the USPTO is hereby authorized to charge indicated fees and credit any overpayment as follows:

Charge any Additional Fees required under 37 C.F.R. Section 1.17 (Patent application and reexamination processing fees)

Charge any Additional Fees required under 37 C.F.R. Section 1.19 (Document supply fees)

NSN677-1002,

Charge any Additional Fees required under 37 C.F.R. Section 1.21 (Miscellaneous fees and charges)

File Listing:

Document

Number Document Description File Name

File Size(Bytes)/

Message Digest

Multi

Part /.zip

Pages

(if appl.)

1 Transmittal of New Application Application_Transmittal.pdf

140388

no 2

1c9a29a3abc05f4cd52649bc7948cb1e1af8

7bdd

Warnings:

Information:

2 Application Data Sheet ADS.pdf

1032121

no 5

e61121e8d84411144ca3c9a5eb466a816771

8713

Warnings:

Information:

3 Petition for 12-month Accelerated Exam PetitionforSpecialStatus.pdf

971989

no 4

652111e8d5db534430139de27346c66dadb

4a1a7

Warnings:

Information:

4 Oath or Declaration filed ParentDeclaration.pdf

208674

no 4

9effa6753eb113b6fd4c66c195d8c44afbef6

bad

Warnings:

Information:

5 Translation of Foreign Priority

Documents CN_Translation.pdf

500478

no 60

9c75690060d0a976333db0578b1Oe18987e

93261

Warnings:

Information:

6 Translation of Foreign Priority

Documents PCT_Translation.pdf

449484

no 80

18af396803d0562d76d264f778c78988bca

e8e88

Warnings:

Information:

7 Application.pdf

631067

yes 60

2549789f45cacb3677ea7ab1a27a21c7Oce2

efOe

Multipart Description/PDF files in zip description

Document Description Start End

Specification 1 44

Claims 45 47

NSN677-1002,

Abstract 48 48

Drawings-only black and white line drawings 49 60

Warnings:

Information:

8 Statement of preexamination search

Pre-

Examination_Search_Documen

t.pdf

2069486

no 62

ab8cea48c90d6c3e5e18899556a741f660a

2454c

Warnings:

Information:

9 Examination support document AESD.pdf

234801

no 53

818554e671bbd9cd167803496aa6fabaf316

2e82

Warnings:

Information:

10 Transmittal Letter IDS_1.pdf

39762

no 4

941cfcd8650636865d71cd91840e0bbe8f0

720e

Warnings:

Information:

11 Information Disclosure Statement (IDS)

Form (5E308) 1449Form_1.pdf

23615

no 1

925156e695d9c523796flae5317f957508a0

8ec95

Warnings:

Information:

This is not an USPTO supplied IDS fillable form

12 Non Patent Literature 3GPPTS23401_Version110_ July

2007.pdf

4349379

no 78

7500928926402c8b3e838062f6a2464a345

2a6a8

Warnings:

Information:

13 Fee Worksheet (5E306) fee-info.pdf

36935

no 2

a01012d5f4daa661ffe9e04c7a54c4a57848

1979

Warnings:

Information:

Total Files Size (in bytes): 10688179

NSN677-1002,

This Acknowledgement Receipt evidences receipt on the noted date by the USPTO of the indicated documents, characterized by the applicant, and including page counts, where applicable. It serves as evidence of receipt similar to a Post Card, as described in MPEP 503.

New Applications Under 35 U.S.C. 111 If a new application is being filed and the application includes the necessary components for a filing date (see 37 CFR 1.53(b)-(d) and MPEP 506), a Filing Receipt (37 CFR 1.54) will be issued in due course and the date shown on this Acknowledgement Receipt will establish the filing date of the application.

National Stage of an International Application under 35 U.S.C. 371 If a timely submission to enter the national stage of an international application is compliant with the conditions of 35 U.S.C. 371 and other applicable requirements a Form PCT/DO/E0/903 indicating acceptance of the application as a national stage submission under 35 U.S.C. 371 will be issued in addition to the Filing Receipt, in due course.

New International Application Filed with the USPTO as a Receiving Office If a new international application is being filed and the international application includes the necessary components for an international filing date (see PCT Article 11 and MPEP 1810), a Notification of the International Application Number and of the International Filing Date (Form PCT/RO/105) will be issued in due course, subject to prescriptions concerning national security, and the date shown on this Acknowledgement Receipt will establish the international filing date of the application.

NSN677-1002,

UNITED STATES PATENT AND TRADEMARK OFFICE

UNITED STATES DEPARTMENT OF COMMERCE United States Patent and Trademark Office Address: COMMISSIONER FOR PATENTS

P.O.Box 1450 Alexandria, VirgLnia 22313-1450 www.uspto.gov

AP NUMBER PLICATION I

371(c)

FILIN

DATE G or I G

UNIT I

IT FIL FEE RECD I ATTY.DOCKET.NO ITOT CLAIMS I IND CLAIMS

13/169,619

06/27/2011

2617

77399 Leydig, Voit & Mayer, Ltd (for Huawei Technologies Co., Ltd) Two Prudential Plaza Suite 4900 180 North Stetson Avenue Chicago, IL 60601

1090 HW708564 14 2

CONFIRMATION NO. 2286

FILING RECEIPT

l imiallooliCIIII0I11111111111111111

Date Mailed: 07/01/2011

Receipt is acknowledged of this non-provisional patent application. The application will be taken up for examination in due course. Applicant will be notified as to the results of the examination. Any correspondence concerning the application must include the following identification information: the U.S. APPLICATION NUMBER, FILING DATE, NAME OF APPLICANT, and TITLE OF INVENTION. Fees transmitted by check or draft are subject to collection. Please verify the accuracy of the data presented on this receipt. If an error is noted on this Filing Receipt, please submit a written request for a Filing Receipt Correction. Please provide a copy of this Filing Receipt with the changes noted thereon. If you received a "Notice to File Missing Parts" for this application, please submit any corrections to this Filing Receipt with your reply to the Notice. When the USPTO processes the reply to the Notice, the USPTO will generate another Filing Receipt incorporating the requested corrections

Applicant(s) Wenfu WU, Shanghai, CHINA; Weihua HU, Shanghai, CHINA; Shanhan WANG, Shanghai, CHINA;

Assignment For Published Patent Application HUAWEI TECHNOLOGIES CO., LTD., Shenzhen, CHINA

Power of Attorney: The patent practitioners associated with Customer Number 85854

Domestic Priority data as claimed by applicant This application is a CON of 12/479,216 06/05/2009 which is a CON of PCT/CN2008/071842 07/31/2008

Foreign Applications (You may be eligible to benefit from the Patent Prosecution Highway program at the USPTO. Please see http://www.uspto.gov for more information.) CHINA 200710137568.8 08/07/2007

If Required, Foreign Filing License Granted: 06/29/2011

The country code and number of your priority application, to be used for filing abroad under the Paris Convention, is US 13/169,619

Projected Publication Date: 10/06/2011

Non-Publication Request: No

Early Publication Request: No page 1 of 3

NSN677-1002,

Title


Preliminary Class

455

PROTECTING YOUR INVENTION OUTSIDE THE UNITED STATES

Since the rights granted by a U.S. patent extend only throughout the territory of the United States and have no effect in a foreign country, an inventor who wishes patent protection in another country must apply for a patent in a specific country or in regional patent offices. Applicants may wish to consider the filing of an international application under the Patent Cooperation Treaty (PCT). An international (PCT) application generally has the same effect as a regular national patent application in each PCT-member country. The PCT process simplifies the filing of patent applications on the same invention in member countries, but does not result in a grant of "an international patent" and does not eliminate the need of applicants to file additional documents and fees in countries where patent protection is desired.

Almost every country has its own patent law, and a person desiring a patent in a particular country must make an application for patent in that country in accordance with its particular laws. Since the laws of many countries differ in various respects from the patent law of the United States, applicants are advised to seek guidance from specific foreign countries to ensure that patent rights are not lost prematurely.

Applicants also are advised that in the case of inventions made in the United States, the Director of the USPTO must issue a license before applicants can apply for a patent in a foreign country. The filing of a U.S. patent application serves as a request for a foreign filing license. The application's filing receipt contains further information and guidance as to the status of applicant's license for foreign filing.

Applicants may wish to consult the USPTO booklet, "General Information Concerning Patents" (specifically, the section entitled "Treaties and Foreign Patents") for more information on timeframes and deadlines for filing foreign patent applications. The guide is available either by contacting the USPTO Contact Center at 800-786-9199, or it can be viewed on the USPTO website at http://www.uspto.gov/web/offices/pac/doc/general/index.html.

For information on preventing theft of your intellectual property (patents, trademarks and copyrights), you may wish to consult the U.S. Government website, http://www.stopfakes.gov. Part of a Department of Commerce initiative, this website includes self-help "toolkits" giving innovators guidance on how to protect intellectual property in specific countries such as China, Korea and Mexico. For questions regarding patent enforcement issues, applicants may call the U.S. Government hotline at 1-866-999-HALT (1-866-999-4158).

LICENSE FOR FOREIGN FILING UNDER

Title 35, United States Code, Section 184

Title 37, Code of Federal Regulations, 5.11 & 5.15

GRANTED

The applicant has been granted a license under 35 U.S.C. 184, if the phrase "IF REQUIRED, FOREIGN FILING LICENSE GRANTED" followed by a date appears on this form. Such licenses are issued in all applications where

page 2 of 3

NSN677-1002,

the conditions for issuance of a license have been met, regardless of whether or not a license may be required as set forth in 37 CFR 5.15. The scope and limitations of this license are set forth in 37 CFR 5.15(a) unless an earlier license has been issued under 37 CFR 5.15(b). The license is subject to revocation upon written notification. The date indicated is the effective date of the license, unless an earlier license of similar scope has been granted under 37 CFR 5.13 or 5.14.

This license is to be retained by the licensee and may be used at any time on or after the effective date thereof unless it is revoked. This license is automatically transferred to any related applications(s) filed under 37 CFR 1.53(d). This license is not retroactive.

The grant of a license does not in any way lessen the responsibility of a licensee for the security of the subject matter as imposed by any Government contract or the provisions of existing laws relating to espionage and the national security or the export of technical data. Licensees should apprise themselves of current regulations especially with respect to certain countries, of other agencies, particularly the Office of Defense Trade Controls, Department of State (with respect to Arms, Munitions and Implements of War (22 CFR 121-128)); the Bureau of Industry and Security, Department of Commerce (15 CFR parts 730-774); the Office of Foreign AssetsControl, Department of Treasury (31 CFR Parts 500+) and the Department of Energy.

NOT GRANTED

No license under 35 U.S.C. 184 has been granted at this time, if the phrase "IF REQUIRED, FOREIGN FILING LICENSE GRANTED" DOES NOT appear on this form. Applicant may still petition for a license under 37 CFR 5.12, if a license is desired before the expiration of 6 months from the filing date of the application. If 6 months has lapsed from the filing date of this application and the licensee has not received any indication of a secrecy order under 35 U.S.C. 181, the licensee may foreign file the application pursuant to 37 CFR 5.15(b).

page 3 of 3

NSN677-1002,

PATENT APPLICATION FEE DETERMINATION RECORD Substitute for Form PTO-875

Application or Docket Number

13/169,619

APPLICATION AS FILED - PART I (Column 1) (Column 2)

FOR NUMBER FILED NUMBER EXTRA

BASIC FEE (37 CFR 1.16(a), (b), or (c)) N/A N/A

SEARCH FEE (37 CFR 1.16(k), (i), or (m)) N/A N/A

EXAMINATION FEE (37 CFR 1.16(o), (p), or (q)) N/A N/A

TOTAL CLAIMS (37 CFR 1.16(0) 14 minus 20=

INDEPENDENT CLAIMS (37 CFR 1.16(h)) 2 minus 3 =

APPLICATION SIZE FEE (37 CFR 1.16(s))

If the specification and drawings exceed 100 sheets of paper, the application size fee due is $270 ($135 for small entity) for each additional 50 sheets or fraction thereof. See 35 U.S.C. 41(a)(1)(G) and 37 CFR 1.16(s).

MULTIPLE DEPENDENT CLAIM PRESENT (37 CFR 1.16(j))

* If the difference in column 1 is less than zero, enter "0" in column 2.

APPLICATION AS AMENDED - PART II

SMALL ENTITY OR

OR

OTHER THAN SMALL ENTITY

RATE($) FEE($) RATE($) FEE($)

N/A N/A 330

N/A N/A 540

N/A N/A 220

x 52 = 0.00

x 220 = 0.00

0.00

0.00

TOTAL TOTAL 1090

(Column 1) (Column 2) (Column 3)

OTHER THAN SMALL ENTITY OR SMALL ENTITY

AM

EN

DM

EN

T A

CLAIMS REMAINING

AFTER AMENDMENT

HIGHEST NUMBER

PREVIOUSLY PAID FOR

PRESENT EXTRA

Total (37 CFR 1.16(i))

Minus =

Independent (37 CFR 1.16(h))

Minus .

Application Size Fee (37 CFR 1.16(s))

FIRST PRESENTATION OF MULTIPLE DEPENDENT CLAIM (37 CFR 1.16(j))

RATE($) ADDITIONAL

FEE($)

OR

OR

OR

TOTAL ADD'L FEE

OR

RATE($) ADDITIONAL

FEE($)

x

x

TOTAL ADD'L FEE

(Column 1) (Column 2) (Column 3)

AM

EN

DM

EN

T B

CLAIMS REMAINING

AFTER AMENDMENT

HIGHEST NUMBER

PREVIOUSLY PAID FOR

PRESENT EXTRA

Total (37 CFR 1.16(i))

Minus =

Independent (37 CFR 1.16(h))

Minus =

Application Size Fee (37 CFR 1.16(s))

FIRST PRESENTATION OF MULTIPLE DEPENDENT CLAIM (37 CFR 1.16(j))

RATE($) ADDITIONAL

FEE($) RATE($)

ADDITIONAL FEE($)

OR

OR

OR

x

x

TOTAL ADD'L FEE

TOTAL ADD'L FEE

* If the entry in column 1 is less than the entry in column 2, write "0" in column 3. "" If the "Highest Number Previously Paid For" IN THIS SPACE is less than 20, enter "20".

""" If the "Highest Number Previously Paid For" IN THIS SPACE is less than 3, enter "3". The "Highest Number Previously Paid For (Total or Independent) is the highest found in the appropriate box in column 1.

OR

NSN677-1002,

1060034752 2010-05.25 17,19,36

A PTOISB/80 (11-08)

Approved for use through 11/30/2011. OMB 0651-0035 U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE

Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of Information unless It displays a valid OMB control number.

POWER OF ATTORNEY TO PROSECUTE APPLICATIONS BEFORE THE USPTO

I hereby revoke all previous powers of attorney given in the application identified in the attached statement under 37 CFR 3.73(b). I hereby appoint:

Ell Practitioners associated with the Customer Number:

OR

77399

1-1 Practitioner(s) named below (if more than ten patent practitioners are to be named, then a customer number must be used):

Name Registration Number

,-A Name Registration Number

,1

r .:t p.

--, ,

as a .torney(s) or agent(s) to represent the undersigned be any and all patent applications assigned p_aiy to the undersigned attached to this form in accordance with 37 CFR 3.73(b).

ore the United S according

ates Patent and Trademark Office (USPTO) in connection with to the USPTO assignment records or assignment documents

Please change the correspondence address for the application identified in the attached statement under 37 CFR 3.73(b) to:

0 The address associated with Customer Number: 77399

OR

JFirm or

— Individual Name Address

City State " Zip

Ccuntry

Telephone Email

•

Assignee Name and Address:

Huawei Technologies Co., Ltd. Huawei Administration Building, Bantian, Longgang District, Shenzhen, Guangdong 518129, P. R. China

A copy of this form, together with a statement under 37 CFR 3.73(b) (Form PTO/SB/96 or equivalent) is required to be filed in each application in which this form is used. The statement under 37 CFR 3.73(b) may be completed by one of the practitioners appointed in this form if the appointed practitioner is authorized to act on behalf of the assignee, anci must identify the application in which this Power of Attorney is to be filed.

SIGNATURE of Assignee of Record The individual whose signature and title is supplied below is authorized to act on behalf of the assignee

Signature Date 46k Mogul WIO

Name UN Yafang Telephone 075548357800 Title President This collection of information is required by 37 CFR 1.31, 1.32 and 1.33. The information Is required to obtain or retain a benefit by the public which is to file (and by the USPTO to process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.11 and 1.14. This collection is estimated to take 3 minutes to ccmplete, including gathering, preparing, and submitting the completed application form to the USPTO. Time will vary depending upon the individual case. Any comments on the amount of time you require to complete this form and/or suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S. Patent and Trademark Office, U.S. Department of Commerce, P.O. Box 1450, Alexandria, VA 22313-1450, DO NOT SEND FEES OR COMPLETED FORMS To THIS ADDRESS. SEND TO: Commissioner for Patents, P.O. Box 1450, Alexandria, VA 22313-1450.

If you need assistance In completing the form, call 1-800-PTO-9199 and select option 2.

NSN677-1002,

Yafang Sun Name

DELEGATION OF AUTHORITY UNDER 37 C.F.R.§ 1.34

Effective this date, I authorize:

John B. Conklin Registration No. 30,369; Dimitry Kapmar Registration No. 62,998; John K. Winn Registration No. 58,579; Philip M. •Pippenger Registration No. 46,055; and Mark Joy Registration No. 35,562

to exercise full authority in United States in which HuAwEJ TECHNOLOGIES CO., L'w., of Fluawei Administration Building, Bantian, Longgang District, Shenzhen, 518129, Guangdong, P.R. China, is an applicant or has ownership interest with respect to the following:

• Signing original, associate or substitute powers of attorney before the United States;

• Signing assignee's consent to changes in inventorship;

• Signing papers required from an assignee in connection with an application for reissue and/or reexamination of a patent;

• Signing terminal disclaimers including, but not limited to, terminal disclaimers to obviate obviousness-type double patenting rejections; and

• Signing all documents before the United States Patent and Trademark Office that can be signed by an assignee in patent matter.

President Title

Feb. 1, 2011 ignature Date

NSN677-1002,


EFS ID: 10471592








Filer: John B. Conklin/Leanna Bultema

Filer Authorized By: John B. Conklin


Receipt Date: 07-JUL-2011

Filing Date: 27-JUN-2011




Submitted with Payment no

File Listing:

Document Number

Document Description File Name File Size(Bytes)/ Message Digest

Multi Part /.zip

Pages (if appl.)

1 Assignee showing of ownership per 37

CFR 3.73(b). 3_73b.pdf

423444

no 2

66576667789119e8018739a1f58c8d9ee49

c28cb

Warnings:

Information:

NSN677-1002,

2 Power of Attorney GENERAL_POA.pdf

78551

no 1

4e17d5a8b448a41c596fe7be270e9e12cc3

a64fd

Warnings:

Information:

44406

3 Miscellaneous Incoming Letter DelegationofA u .pdtfhority_Huawei

no 1

eaa090a8a58a649574711bOacOfcc82f5d33

28d4

Warnings:

Information:






NSN677-1002,

STATEMENT UNDER 37 CFR 3.73(b)

Applicant/Patent Owner: WU et al.

Application No./Patent No.: 13/169,619 Filed/Issue Date: June 27, 2011

Titled: METHOD, SYSTEM, AND DEVICE FOR USER DETACHMENT WHEN A HANDOVER OR CHANGE OCCURS IN HETEROGENEOUS NETWORK

Huawei Technologies Co., Ltd. a corporation

(Name of Assignee) (Type of Assignee, e.g., corporation, partnership, university, government agency, etc.

states that it is:

1. X the assignee of the entire right, title, and interest in;

2. 0 an assignee of less than the entire right, title, and interest in (The extent (by percentage) of its ownership interest is %); or

3. 0 the assignee of an undivided interest in the entirety of (a complete assignment from one of the joint inventors was made)

the patent application/patent identified above, by virtue of either:

A. X An assignment from the inventor(s) of the patent application/patent identified above. The assignment was recorded in the United States Patent and Trademark Office at Reel 022788 , Frame 0564 , or for which a copy therefore is attached.

OR

B. 0 A chain of title from the inventor(s), of the patent application/patent identified above, to the current assignee as follows:

1. From: To:

The document was recorded in the United States Patent and Trademark Office at

, Frame , or for which a copy thereof is attached.

2. From: To:


Reel , Frame , or for which a copy thereof is attached.

3. From: To:


Reel , Frame , or for which a copy thereof is attached.

0 Additional documents in the chain of title are listed on a supplemental sheet(s).

ri As required by 37 CFR 3.73(b)(1)0), the documentary evidence of the chain of title from the original owner to the assignee was, or concurrently is being, submitted for recordation pursuant to 37 CFR 3.11.

[NOTE: A separate copy (La, a true copy of the original assignment document(s)) must be submitted to Assignment Division in accordance with 37 CFR Part 3, to record the assignment in the records of the USPTO. See MPEP 302.08]

The undersigned (whose title is supplied below) is authorized to act on behalf of the assignee.

/John B. Conklin/ July 7, 2011

Signature Date

John B. Conklin Attorney of Record

Printed or Typed Name Title

Reel


U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it displays a valid OMB control number.

This collection of information is required by 37 CFR 3.73(b). The information is required to obtain or retain a benefit by the public which is to file (and by the USPTO to process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.11 and 1.14. This collection is estimated to take 12 minutes to complete, including gathering, preparing, and submitting the completed application form to the USPTO. Time will vary depending upon the individual case. Any comments on the amount of time you require to complete this form and/or suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S. Patent and Trademark Office, U.S. Department of Commerce, P.O. Box 1450, Alexandria, VA 22313-1450. DO NOT SEND FEES OR COMPLETED FORMS TO THIS ADDRESS. SEND TO: Commissioner for Patents, P.O. Box 1450, Alexandria, VA 22313-1450.

If you need assistance in completing the form, call 1-800-PTO-9199 and select option 2.

NSN677-1002,




1. The information on this form will be treated confidentially to the extent allowed under the Freedom of Information Act (5 U.S.C. 552) and the Privacy Act (5 U.S.0 552a). Records from this system of records may be disclosed to the Department of Justice to determine whether disclosure of these records is required by the Freedom of Information Act.



4. A record in this system of records may be disclosed, as a routine use, to a contractor of the Agency having need for the information in order to perform a contract. Recipients of information shall be required to comply with the requirements of the Privacy Act of 1974, as amended, pursuant to 5 U.S.C. 552a(m).




8. A record from this system of records may be disclosed, as a routine use, to the public after either publication of the application pursuant to 35 U.S.C. 122(b) or issuance of a patent pursuant to 35 U.S.C. 151. Further, a record may be disclosed, subject to the limitations of 37 CFR 1.14, as a routine use, to the public if the record was filed in an application which became abandoned or in which the proceedings were terminated and which application is referenced by either a published application, an application open to public inspection or an issued patent.


NSN677-1002,

06/27/2011 Wenfu WU 13/169,619


HW708564

CONFIRMATION NO. 2286 POA ACCEPTANCE LETTER

1111111111111111111111111CIIII0I111!1411,11111111111111111111111



PO. Box 1450 Alexandria, Virginia 22313-1450 www.uspto.gov

APPLICATION NUMBER

FILING OR 371(C) DATE

FIRST NAMED APPLICANT

ATTY. DOCKET NO./TITLE


NOTICE OF ACCEPTANCE OF POWER OF ATTORNEY

This is in response to the Power of Attorney filed 07/07/2011.

The Power of Attorney in this application is accepted. Correspondence in this application will be mailed to the above address as provided by 37 CFR 1.33.

/ddinh/

Office of Data Management, Application Assistance Unit (571) 272-4000, or (571) 272-4200, or 1-888-786-0101

page 1 of 1

NSN677-1002,

06/27/2011 Wenfu WU 13/169,619


HW708564

CONFIRMATION NO. 2286 POWER OF ATTORNEY NOTICE

1111111111111111111111111CIIII0I111!14111,11111111111111111111111




APPLICATION NUMBER





NOTICE REGARDING CHANGE OF POWER OF ATTORNEY

This is in response to the Power of Attorney filed 07/07/2011.

• The Power of Attorney to you in this application has been revoked by the assignee who has intervened as provided by 37 CFR 3.71. Future correspondence will be mailed to the new address of record(37 CFR 1.33).

/ddinh/

Office of Data Management, Application Assistance Unit (571) 272-4000, or (571) 272-4200, or 1-888-786-0101

page 1 of 1

NSN677-1002,

EXAMINER

ART UNIT

PAPER NUMBER

2617

NOTIFICATION DATE

DELIVERY MODE

07/20/2011

ELECTRONIC



P.O. Box 1450 Alexandria, Virginia 22313-1450 www.uspto.gov

APPLICATION NO. FILING DATE

FIRST NAMED INVENTOR

ATTORNEY DOCKET NO. CONFIRMATION NO.

13/169,619

06/27/2011

Wcnfu WU

HW708564

2286

77399 7590 07/20/2011

Leydig, Voit & Mayer, Ltd (for Huawei Technologies Co., Ltd) Two Prudential Plaza Suite 4900 180 North Stetson Avenue Chicago, IL 60601

Please find below and/or attached an Office communication concerning this application or proceeding.

The time period for reply, if any, is set in the attached communication.

Notice of the Office communication was sent electronically on above-indicated "Notification Date" to the following e-mail address(es):

[email protected] [email protected]

PTOL-90A (Rev. 04/07)

NSN677-1002,


Commissioner for Patents United States Patent and Trademark Office

P.O. Box 1450 Alexandria, VA 22313-1450

www.usoto.aov

Leydig, Voit & Mayer, Ltd (for Huawei Technologies Co., Ltd) Two Prudential Plaza Suite 4900 180 North Stetson Avenue Chicago IL 60601

In re Application of: WU, WENFU, et al.

Serial No.: 13/169,619 Filed: June 27, 2011

Title: METHOD, SYSTEM, AND DEVICE FOR USER DETACHMENT WHEN A HANDOVER OR CHANGE OCCURS IN HETEROGENEOUS NETWORK

DECISION ON PETITION TO MAKE SPECIAL FOR NEW APPLICATION UNDER 37 C.F.R. § 1.102 & M.P.E.P. §

708.02

The petition to make the application special filed June 27, 2011 is GRANTED.

The application is eligible for accelerated examination and the petition complies with the conditions for granting the application special status pursuant to the "Change to Practice for Petitions in Patent Applications to Make Special and for Accelerated Examination" published June 26, 2006, in the Federal Register. (71 Fed. Reg. 36323).

The prosecution of the instant application will be conducted expeditiously according to the following guidelines.

1. The application will be docketed to an examiner and taken up for action within two weeks of the date of this decision.

2. Restriction Practice: If the examiner determines that the claims are not directed to a single invention, a telephone request to elect one single invention will be made pursuant to MPEP 812.01. As a prerequisite to the grant of this petition, the applicant has agreed to make an oral election, by telephone, without traverse. If the applicant refuses to make an election without traverse, or the examiner cannot reach the applicant after a reasonable effort, the

NSN677-1002,

Application Serial No. 13/169,619 2 Decision on Petition

examiner will treat the first claimed invention (invention defined by claim 1) as having being constructively elected without traverse for examination.

3. Office action: If it is determined that, after appropriate consultation, there is a potential rejection or any other issue to be addressed, the examiner will telephone the applicant and arrange an interview to discuss and resolve the issue. An Office action, other than a Notice of Allowance and Fee(s) Due (Notice of Allowance), will not be issued unless either: 1) an interview was conducted but did not result in agreed to action that places the application in condition for allowance, or, 2) a determination is made that an interview would be unlikely to result in the application being placed in condition for allowance, and 3) an internal conference has been held to review any rejection of any claim.

4. Time for Reply: An Office action other than a Notice of Allowance or a final Office action will set a shortened statutory period of one month or thirty days, whichever is longer, for reply with no extension of time available under 37 CFR 1.136(a). Failure to timely file a reply within this non-extendible period for reply will result in the abandonment of the application.

5. Reply by Applicant: . A timely reply to an Office action other than the Notice of Allowance must be submitted electronically via EFS or EFS-web and limited to addressing the rejections, objections and requirement made. Any amendment that attempts to: 1) add claims which would result in more than three pending independent claims or more than twenty pending total claims; 2) present claims not encompassed by the pre-examination search or an updated accelerated examination support document; or 3) present claims that are directed a non-elected invention or an invention other than that previously claimed and examined in the application, will be treated as not fully responsive and will not be entered:

For any amendment to the claims (including any new claim) that is not encompassed by the accelerated examination support document, applicant must provide an updated accelerated examination support document that encompasses the amended or new claims at the time of filing of the amendment.

To proceed expeditiously with the examination, it is recommended that a reply with amendments made to any claim or with any new claim being added be accompanied by an updated accelerated examination support document or a statement explaining how the amended or new claim is supported by the original accelerated examination support document.

6. Information Disclosure Statement (IDS): Any IDS filed during prosecution must be submitted electronically via EFS or EFS-web, accompanied by an updated accelerated examination support document, and be in compliance with 37 CFR 1.97 and 1.98.

NSN677-1002,

Application Serial No. 13/169,619 3 Decision on Petition

7. Post-Allowance Processing: To expedite processing of the allowed application into a patent, the applicant must: 1) pay the required fees within one month of the date of the Notice of Allowance, and 2) not file any post allowance papers not required by the Office. In no event may the issue fee be paid and accepted later than three months from the date of the Notice of Allowance.

8. After-Final and Appeal Procedures: To expedite prosecution, after receiving the final Office action, applicant must: 1) promptly file a notice of appeal, an appeal brief and appeal fees; and 2) not request a pre-appeal brief conference.

Any amendment, affidavit or other evidence filed after final Office action must comply with applicable rules and the requirements outlined in numbered paragraphs 5 and 6 above.

On appeal, the application will proceed according to normal appeal procedures. After appeal, the application will again be treated special.

9. Proceedings Outside the Normal Examination Process: If the application becomes involved in a proceeding that is outside the normal examination process (e.g., a secrecy order, national security review, interference proceeding, petitions under 37 CFR 1.181, 182 or 183), the application will be treated special before and after such proceeding.

10. Final Disposition: The twelve month goal of this accelerated examination procedure ends with a final disposition. The mailing of a final Office action, a Notice of Allowance, the filing of a Notice of Appeal, or the filing of a Request for Continued Examination (RCE) is the final disposition.

If, during prosecution, a paper is not filed electronically using EFS-web, a reply is filed but is not fully responsive, the application is involved in an appeal, or a proceeding outside normal examination process, the application will still be examined expeditiously, however, the final disposition may occur more than twelve months from the filing of the application.

Any inquiry regarding this decision should be directed to Ken Wieder, Quality Assurance Specialist, at (571) 272-2986.

/Kenneth A. Wieder/

Kenneth A. Wieder Quality Assurance Specialist Technology Center 2600 Communications

NSN677-1002,





Complete if Known Application Number 13/169,619 Filing Date June 24, 2011 First Named Inventor WU, Wenfu Group Art Unit 2617 Examiner Name NGUYEN, David Q


OLU.S. PATENT DOCUMENTS

Examiner Initials

Doc. No.




Kind Code

A F 2008/0304454 Al Zhong et al. December 11, 2008


Examiner Initials

Doc. No.


Name of Patentee or Applicant Date of Publication Translation* Office Application or

Patent Number Kind Code

A G EP 1713207 Al Huawei Tech. Co., Ltd. October 18, 2006 A H EP 2007160 Al Nokia Siemens Networks Oy December 24, 2008

A I WO 2007/024115 Al Electronics and Telecommunications Research Institute

March 1, 2007

A J WO 2006/029663 Al Matasushita Electric Inc. Co., Ltd. March 23, 2006 A K WO 2006/088331 Al LG Electronics Inc. August 24, 2006 A L CN 1881919 A Huawei Tech. Co., Ltd. December 20, 2006 (b) A M CN 1878389 A Huawei Tech. Co., Ltd. December 13, 2006 (b)


Examiner Initials

Doc. No.


Translation *

A N 1St Office Action in corresponding Russian Application No. 2009142607 (July 31, 2008).

(a)

A 0 1st Office Action in corresponding Chinese Application No. 200710137568.8 (July 17, 2009).

(a)

A P Written Opinion of the International Searching Authority in corresponding PCT Application No. PCT/CN2008/071842 (November 20, 2008).

A Q International Search Report in corresponding PCT Application No. PCT/CN2008/071842 (November 20, 2008).

A R Extended European Search Report in corresponding European Application No. 08783835.5 (February 24, 2010).

A S

"3GPP TS 23.060 - 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS); Service description; Stage 2 (Release 8)," June 2008, Version 8.1.0, 3rd Generation Partnership Project, Valbonne, France.

AT "3GPP TS 23.401 - 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; GPRS enhancements for E-UTRAN access (Release 8)," Version 1.1.1, 3rd Generation Partnership Project, Valbonne, France.

A U

"3GPP TS 23.402 — 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture Enhancements for non-3GPP accesses (Release 8)," June 2007, Version 1.1.0, 3rd Generation Partnership Project, Valbonne, France.

A V

"3GPP TS 23.402 — 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture Enhancements for non-3GPP accesses (Release 8)," July 2007, Version 1.2.0, 3rd Generation Partnership Project, Valbonne, France.



NSN677-1002,








Examiner Initials

Doc. No.


Translation "

A W

"3GPP TS 29.213 - 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control signalling flows and QoS parameter mapping; (Release 8)," May 2008, Version 8.0.0, 3rd Generation Partnership Project, Valbonne, France.

AX Image File Wrapper in corresponding US Application No. 12/479,216 (July 27, 2011).



NSN677-1002,

iii 1111 (19)

Europaisches Patentamt

European Patent Office

Office europeen des brevets (11) EP 1 713 207 Al

(84) Designated Contracting States: AT BE BG CH CY CZ DE DK EE ES Fl FR GB GR HU IE IS IT LI LT LU MC NL PL PT RO SE SI SK TR

(30) Priority: 02.02.2004 CN 200410000476 09.04.2004 CN 200410033722

(71) Applicant: Huawei Technologies Co., Ltd. Longgang District, Shenzhen, Guangdong 518129 (CN)

(72) Inventors: • ZHANG, Wenlin,

Huawei Administration Building Shenzhen, Guangdong 518129 (CN)

• ZHANG, Hai, Huawei Administration Building Shenzhen, Guangdong 518129 (CN)

(74) Representative: Thun, Clemens Mitscherlich & Partner Sonnenstrasse 33 80331 Munchen (DE)

MtIOC,,Ngttilies WftlItif.A10 tress Ilkszkaircattke rmaz.,:q fton me new Vltimi Nlobik• CA-2.14.itmt- tmtsg: isi0'wo06,. nod i:I:M(1:041W

Wt.AN eitffkrelli ViztAttd, Ni.obi;e t,-.:Nturhuhit.ation NdiwNiss.

5(YE

Thr wi,AN no.wf.11:: kutistm

Oxithc,..acstion alt WEAN

r,

Aa490 NiAwork authe46- clexiisit Dimtelurt: to Om 14orsv., zht, WI -AN W'..4:6-,a M015ik

WIAX No.sv or), celovIzmla• clIA•arttuvtion cathi hit itzetc:$

Wweete the, %V IA ;1..1d mrrz,pevAirts,F tNhe3 Mobitn NOworksxawnii:seta the, n=ccisat a4ee m inan.a4ktil

Fig. 5

(12) EUROPEAN PATENT APPLICATION published in accordance with Art. 158(3) EPC

(43) Date of publication: 18.10.2006 Bulletin 2006/42

(21) Application number: 05700469.9

(22) Date of filing: 21.01.2005

(51) Int Cl.: HO4L 12/28 (200"1)

(86) International application number: PCT/CN2005/000095

(87) International publication number: WO 2005/076532 (18.08.2005 Gazette 2005/33)

(54) THE INTERACTIVE METHOD FOR RE-SELECTING THE OPERATION NETWORK BY THE WIRELESS AREA NETWORK WLAN USER TERMINAL

(57) The present invention discloses an interactive method for a WLAN UE accessing a new operation net-work, which comprises: when the WLAN UE which has accessed a Visited Mobile Communication Network needs to re-select another Visited Mobile Communica-tion Network to access, the WLAN UE sending authen-tication information to a Home Network of the WLAN UE through a WLAN Access Network and the Visited Mobile Communication Network newly selected by the WLAN UE; after receiving the authentication information, the Home Network of the WLAN UE authenticate the WLAN UE according to the authentication information via the Visited Mobile Communication Network newly selected by the WLAN UE, and sending an access instruction to the WLAN Access Network through the Visited Mobile Communication Network; and On receiving the access instruction, the WLAN Access Network completing dis-connection and/or access between the WLAN UE and the corresponding Visited Mobile Communication Net-works. The method enables a WLAN UE to reselect an-other Visited Mobile Communication Network after ac-cessing a Visited Mobile Communication Network.

Printed by Jouve, 75001 PARIS (FR)

NSN677-1002,

1 EP 1 713 207 Al

2

Description

Field of the Technology

[0001] The present invention relates to operation net-work selection technology, and more specifically relates to a method for a User Equipment (UE) in Wireless Local Area Network (WLAN) reselecting a new operation net-work.

Background of the Invention

[0002] As users' requirements on the wireless access rate are becoming higher and higher, WLAN which is able to provide a higher wireless access rate of data in a relatively small area has emerged as the times require. WLAN involves various kinds of techniques, the most extensively used technical standard of which is IEEE 802.11 b, which uses the frequency band of 2.4GHz and the data transmission rate of which is up to 11Mbps. Oth-er technical standards using the same frequency band include IEEE 802.11g and Bluetooth, wherein, the data transmission rate of IEEE 802.11g is up to 54Mbps. Other new standards of WLAN, such as IEEE 802.11 a and ETSI BRAN Hiperlan2, use the frequency band of 5GHz, and the transmission rate of which can be up to 54 Mbps as well. [0003] Although WLAN involves various kinds of wire-less access techniques, most WLAN techniques utilize IP data packets for data transmission. The specific WLAN access technique adopted by a wireless IP network is usually transparent to the upper IP level. Such a wireless IP network is usually configured with Access Points (AP) for implementing wireless access of a WLAN UE, and with controlling and connecting devices for implementing IP data transmission. [0004] Along with the appearance and development of WLAN, the inter-working of WLAN with various wireless mobile communication networks, such as GSM, CDMA, WCDMA, TD-SCDMA, and CDMA2000 has become the focus of research. In accordance with the 3GPP (3rd Gen-eration Partner Project) standards, a WLAN UE is not only able to connect with Internet and Intranet via the access network of WLAN, but also able to connect with the home network and the visited network of a 3GPP system via the WLAN Access Network. To be specific, when accessing locally, the WLAN UE is able to connect to the 3GPP Home Network via the WLAN Access Net-work, as shown in Figure 2; when in case of roaming, the WLAN UE is able to connect to the Visited Network of the 3GPP system via the WLAN Access Network. And as some entities of the 3GPP Visited Network are con-nected with some corresponding entities of the 3GPP Home Network, for instance, the 3GPP Authentication, Authorization and Accounting (AAA) Proxy in the 3GPP Visited Network is connected with the 3GPP AAA Server in the 3GPP Home Network, the WLAN Access Gate (WAG) in the 3GPP Visited Network is connected with

the Packet Data Gateway (PDG) in the 3GPP Home Net-work, and etc., as shown in Figure 1. Wherein, Figure 1 and Figure 2 respectively illustrate the architecture of an inter-working network of a WLAN system and a 3GPP

5 system under roaming and non-roaming circumstances. [0005] As shown in Figure 1 and Figure 2, a 3GPP system primarily comprises Home Subscriber Server (HSS)/ Home Location Register (HLR), 3GPP AAA Serv-er, 3GPP AAA Proxy, WAG, PDG, Charging Gateway

10 (CGw)/Charging information Collecting Function (CCF) and Online Charging System (OCS). WLAN UEs, WLAN access network, and all the entities of the 3GPP system together construct a 3GPP-WLAN inter-working network, which can be used as a WLAN service system. In this

15 service system, 3GPP AAA Server is in charge of the authentication, authorization, and accounting of a WLAN UE, collecting the charging information sent from the WLAN access network and sending the charging infor-mation to the charging system; the PDG is in charge of

20 the transmission of the user's data from the WLAN Ac- cess Network to the 3GPP network or other packet switching networks; and the charging system is in charge of receiving and recording the user's charging informa-tion sent from the network, and the OCS takes charge of

25 instructing the network to periodically send online charging information in accordance with the expenses of the online charged users, meanwhile collecting statistics and controlling the network. [0006] In the case of non-roaming, when a WLAN UE

30 desires to access the Internet/Intranet directly, the WLAN UE can access to the Internet/Intranet via the WLAN Ac-cess Network after an authentication process with an AAA server (AS) via the WLAN Access Network. If the WLAN UE desires to access the services of 3GPP PS

35 domain as well, it should further request the services of Scenario 3 from the 3GPP Home Network, which com-prises: the WLAN UE sends a Service Authorization Re-quest of Scenario 3 to the AS of the 3GPP Home Network, and the AS performs authentication and authorization to

40 the Service Authorization Request, if the authentication and authorization are successful, the AS sends an Ac-cess Permission Message to the WLAN UE and assigns a corresponding PGD for the WLAN UE. After establish-ing a tunnel with the assigned PDG, the WLAN UE can

45 access 3GPP PS domain services. At the same time, CGw/CCF and OCS records accounting information ac-cording to the use of network by the WLAN UE. In case of roaming, if a WLAN UE desires to access the Internet/ Intranet directly, the WLAN UE will make a request to the

50 3GPP Home Network via the 3GPP Visited Network for accessing the Internet/Intranet. If the WLAN UE desires to access 3GPP PS domain services requesting a Sce-nario 3 services as well, the WLAN UE needs to initiate a Service Authentication procedure via the 3GPP Visited

55 Network to 3GPP Home Network, and similarly, the procedure is also implemented between the WLAN UE and the AS of the 3GPP Home Network. After the authenti-cation procedure succeeds, the AS assigns a corre-

2

NSN677-1002,

3 EP 1 713 207 Al

4

sponding Home PGD for the WLAN UE, and after a tunnel with the assigned PDG is established via the WAG of 3GPP access network, the WLAN UE can access 3GPP PS domain services.

Step 404-405: After receiving the packet sent from the WLAN UE, the WLAN Access Network finds that the network selection information in the packet does not belong to the Mobile Communication Network

[0007] In 3GPP-WLAN inter-working networks, if a WLAN UE connects with multiple 3GPP Visited Net-

5 currently connected with the WLAN Access Network, and then sends a network notification signaling con-

works, which refer to a plurality of Mobile Communication taining the information of all the Mobile Communica- Networks, there are two schemes, as shown in Figure 3 and Figure 4 respectively, for the WLAN UE selecting a proper Mobile Communication Network to access ac- 10

tion Networks connected with it to the WLAN UE.

Step 406-407: On receiving the signaling, the WLAN cording to its own requirements. Figure 3 represents a UE reselects a Mobile Communication Network to successful process illustrating the WLAN UE directly se- access according to the information of the Mobile lecting a Mobile Communication Network to access, which comprises:

Communication Networks contained in the informa-tion signaling, and then sends a User Identity Re-

15 sponse packet carrying the selection information of Step 301-303: After establishing a wireless connec- the newly selected network to the WLAN Access Net- tion between the WLAN UE and a WLAN Access work. Network, the network or the WLAN UE initiates an access authentication procedure, the WLAN Access Step 408-409: These steps are exactly the same as Network sends a User Identity Request packet to the 20 Step 305-306. WLAN UE; and after receiving the request packet, the WLAN UE returns a User Identity Response [0009] It can be seen from above schemes, there has packet carrying network selection information to the been a relative consummate flow fora WLAN UE to select WLAN Access Network. Here, the network selection an access network in 3GPP-WLAN inter-working net- information refers to the information of the Mobile 25 works, however, when a WLAN Access Network con- Communication Network connected with the WLAN nects with a plurality of VPLMN at the same time, and network and also to be accessed by the current after a certain WLAN UE has accessed one of these WLAN UE; the access authentication procedure be-tween the WLAN Access Network and the WLAN

VPLMN networks through the WLAN Access Network, the WLAN UE may need to disconnect the VPLMN net-

UE is based on an Expandable Authentication Pro- 30 work it currently connects and reselect another VPLMN tocol (EAP) procedure. In general, the network se- network connected with the WLAN Access Network due lection information is carried in a User Identity Field to different reasons, such as charge, range of access defined by a Network Access Identity (NAI) format. service and so on; or the current WLAN UE expects to

access Service A through VPLMNI and access Service Step 304-306: After receiving the packet sent from 35 B through VPLMN2 at the same time. No specific scheme the WLAN UE, the WLAN Access Network judges whether the network selection information in the packet belongs to the Mobile Communication Net-work currently connected with the WLAN, if yes, the

is proposed at present to resolve the above problems.

Summary of the Invention

WLAN Access Network determines a 3GPP AAA ao [0010] In view of the above description, the main object Agent or a 3GPP AAA Server of the Mobile Commu- of the present invention is to provide a method for a WLAN nication Network selected by the WLAN UE accord- UE reselecting a mobile communication network, making ing to NAI, and then sends the user identity and an the WLAN UE reselect another Visited Mobile Commu- Access Authentication Request to the determined nication Network to access after accessing one Visited 3GPP AAA Agent or 3GPP AAA Server, making 45 Mobile Communication Network. 3GPP AAA Agent or 3GPP AAA Server authenticate [0011] To obtain the above object, the technical to the currently accessing WLAN UE; if the authen- scheme of the present invention is implemented as fol- tication is passed, the subsequent access procedure lows: will be accomplished.

50 A method for a WLAN UE accessing a new mobile [0008] Figure 4 represents a process illustrating a communication network, which comprises: WLAN UE reselecting a Mobile Communication Network to access according to the sent network selection infor- when the WLAN UE which has accessed a Vis- mation when the first selection fails, which comprises: ited Mobile Communication Network needs to

55 re-select another Visited Mobile Communica- Step 401-403: These steps are exactly the same as tion Network to access, the WLAN UE sends Step 301-303. authentication information to a Home Network

of the WLAN UE through a WLAN Access Net-

3

NSN677-1002,

5 EP 1 713 207 Al

6

Mobile Communication Network that the WLAN UE has accessed, and disconnects the connection be-tween the WLAN UE and the Visited Mobile Com-munication Network that the WLAN UE has ac-

5 cessed.

work and the Visited Mobile Communication Network newly selected to access by the WLAN UE;

on receiving the authentication information via the new selected Visited Mobile Communication Network, the Home Network of the WLAN UE authenticates the WLAN UE, and sends an ac-cess instruction to the WLAN Access Network through the new selected Visited Mobile Com-munication Network; and

on receiving the access instruction, the WLAN Access Network completes disconnection and/or access between the WLAN UE and the 15

corresponding Visited Mobile Communication Networks.

[0012] There are several alternative methods to implement the above method, which are as follows: 20

10

In the third case, before the Home Network authen-ticates the WLAN UE, the method further comprises: the Home Network judging whether to permit the WLAN UE to access the Visited Mobile Communi-cation Network newly selected by the WLAN U E, and if permitted, continues to authenticate the WLAN UE from the Visited Mobile Communication Network newly selected by the WLAN UE; if not permitted, the step of sending an access in-struction comprises: the Home Network sends an Access Rejection message to the WLAN Access Network via the Visited Mobile Communication Net-work newly selected by the WLAN UE; and

The step of corn pleting disconnection and/or access between the WLAN UE and the corresponding Vis-ited Mobile Communication Networks comprises the WLAN Access Network returning the Access Rejec-

25 tion message to the WLAN UE.

In the first case, before the Home Network authen-ticates the WLAN UE, the method further comprises: the Home Network of the WLAN UE sends a Discon-nection message to the Visited Mobile Communica-tion Network that the WLAN UE has accessed, and disconnects the connection between the WLAN UE and the Visited Mobile Communication Network that the WLAN UE has accessed; the step of sending an access instruction comprises: 30

the Home Network sends an Access Permission message or an Access Rejection message to the WLAN Access Network through the Visited Mobile Communication Network newly selected by the WLAN UE; and

35

the step of completing disconnection and access be-tween the WLAN UE and the corresponding Visited Mobile Communication Networks comprises: the WLAN Access Network judges whether the Access Permission message is received, if so, establishes 40

a connection between the WLAN UE and the Visited Mobile Communication Network newly selected by the WLAN UE, and completes the access of the WLAN UE to the Visited Mobile Communication Net-work newly selected by the WLAN UE; otherwise, 45

returns the Access Rejection message to the WLAN UE.

In the second case, before the Home Network au-thenticates the WLAN UE, the method further com- 50

prises: judging whether the WLAN UE is permitted to access more than one Visited Mobile Communi-cation Networks simultaneously, and if so, the Home Network of the WLAN UE determines whether to send a Disconnection message to the Visited Mobile 55

Communication Network that the WLAN UE has ac-cessed; otherwise, the Home Network of the WLAN UE sends a Disconnection message to the Visited

[0013] Wherein, the step of judging further comprises: determining whether to permit the WLAN UE to access more than one Visited Mobile Communication Networks simultaneously, and if permitted, judges whether to per-mit the WLAN UE to access the Visited Mobile Commu-nication Network newly selected by the WLAN UE; and otherwise, the WLAN UE is considered not to be permit-ted to access to the Visited Mobile Communication Net-work newly selected. [0014] The Access Rejection message further carries a piece of information indicating the reason of rejection. [0015] In the fourth case, after the authentication to the WLAN UE is successful, the step of sending an ac-cess instruction comprises: the Home Network sends an Access Permission message to the WLAN Access Net-work via the Visited Mobile Communication Network newly selected by the WLAN UE; the step of completing disconnection and/or access be-tween the WLAN UE and the corresponding Visited Mo-bile Communication Networks comprises: according to the received Access Permission message, the WLAN Access Network establishes a connection between the WLAN UE and the Visited Mobile Communication Net-work newly selected by the WLAN UE, and completes the access of the WLAN UE and the Mobile Visited Com-munication Network newly selected by the WLAN UE. [0016] Wherein, while sending the Access Permission message to the Visited Mobile Communication Network newly selected by the WLAN UE, the Home Network sends a Disconnection message to the Visited Mobile Communication Network that the WLAN UE has ac-cessed;

4

NSN677-1002,

7

EP 1 713 207 Al 8

[0017] The step of completing disconnection and/or access between the WLAN UE and the corresponding Visited Mobile Communication Networks further com-prises: disconnecting the connection between the WLAN UE and the Visited Mobile Communication Network that the WLAN UE has accessed. [0018] In the present scheme, before sending the Dis-connection message to the WLAN Access Network via the Visited Mobile Communication Network that the WLAN UE has accessed, the method further comprises: judging whether to permit the WLAN UE to access more than one Visited Mobile Communication Networks simul-taneously, if so, the Home Network of the WLAN UE de-termines whether a Disconnection message to be sent to the Visited Mobile Communication Network that the WLAN UE has accessed if necessary; otherwise, the Home Network sends the Disconnection message to the WLAN Access Network via the Visited Mobile Commu-nication Network that the WLAN UE has accessed. [0019] In the present scheme, the method further com-prises: implementing re-authentication for the WLAN UE via the Visited Mobile Communication Network that the WLAN UE has accessed; and/or sending advertisement information to inform the WLAN UE that more than one connection existis in the WLAN UE; or doing nothing. [0020] In the fifth case, after the authentication is suc-cessful, the step of sending an access instruction com-prises: the Home Network sending an Access Permission message to the WLAN Access Network via the Visited Mobile Communication Network newly selected by the WLAN UE; the step of completing disconnection and/or access be-tween the WLAN UE and the corresponding Visited Mo-bile Communication Networks comprises: according to the received Access Permission message, the WLAN Access Network establishes a connection between the WLAN UE and the Visited Mobile Communication Net-work newly selected by the WLAN UE, completes the access of the WLAN UE and the Mobile Visited Commu-nication Network newly selected by the WLAN UE, and disconnect the connection between the WLAN UE and the Mobile Visited Communication Network that the WLAN UE has accessed. [0021] Wherein, after the WLAN Access Network com-pletes the access of the WLAN UE and the Mobile Visited Communication Network newly selected by the WLAN UE, the method further comprises: judges whether to per-mit the WLAN UE to access more than one Visited Mobile Communication Networks simultaneously, if so, the WLAN Access Network determines whether a Discon-nection message to be sent to the Visited Mobile Com-munication Network that the WLAN UE has accessed; otherwise, disconnects the connection between the WLAN UE and the Mobile Visited Communication Net-work that the WLAN UE has accessed. [0022] In the above schemes, the WLAN UE is permit-ted to access more than one Visited Mobile Communi-cation Networks simultaneously, and no Disconnection

message needs to be sent to the Visited Mobile Commu-nication Network that the WLAN UE has accessed, the method further comprises: implements re-authentication for the WLAN UE via the Visited Mobile Communication

5 Network that the WLAN UE has accessed; and/or sending advertisement information to inform the WLAN UE that more than one connection existing in the WLAN UE; or doing nothing. [0023] Where, the step of sending an access instruc-

10 tion comprises: sending a notification to the WLAN UE via one of the existing connections, or sending a notifi-cation to the WLAN UE through the newly established connection. The notification comprises total numbers of the current connections, and/or specific selection infor-mation of the connections. [0024] In the above schemes, a threshold of the max-imum number of the permitted simultaneous connections of the WLAN UE is preset; if the WLAN UE is permitted to access more than one Visited Mobile Communication

20 Networks simultaneously, the method further comprising: judging whether the number of the current simulta-neous connections exceeds the threshold of the maxi-mum number of the simultaneous connections, if not ex-ceed, continuing with subsequent operations; otherwise,

25 rejecting the authentication request of the current connection directly, or performing the authentication request of current connection and informing the current WLAN UE to select and remove one or more than one existing connections.

30 [0025] In above scheme, when the authentication for the authentication request from the newly selected Vis-ited Mobile Communication Network implemented by the Home Network succeeds, the step of completing discon-nection and/or access between the WLAN UE and the

35 corresponding Visited Mobile Communication Networks comprises:

c1. the WLAN Access Network judges whether the Access Permission message from the Visited Mobile

40 Communication Network newly selected by the WLAN UE is received first, if so, proceeds to Step c2; if the Disconnection message is received first, proceeds to Step c3;

45 c2. collects and sends charging information to the Visited Mobile Communication Network that the WLAN UE has accessed, and disconnects the con-nection between the WLAN UE and the Visited Mo-bile Communication Network that the WLAN UE has

50 accessed; and at the same time, establishes a connection between the WLAN UE and the Visited Mo-bile Communication Network newly selected by the WLAN UE, and completes the access of the WLAN UE and the Visited Mobile Communication Network

55 newly selected by the WLAN UE and then completes the current re-selection process;

c3. collects and sends charging information to the

5

NSN677-1002,

9 EP 1 713 207 Al

10

Visited Mobile Communication Network that the WLAN UE has accessed, and disconnects the con-nection between the WLAN UE and the Visited Mo-bile Communication Network that the WLAN UE has accessed, then waits for the Access Permission message from the Visited Mobile Communication Network newly selected by the WLAN UE; and after receiving the Access Permission message, estab-lishes a connection between the WLAN UE and the Visited Mobile Communication Network newly se-lected by the WLAN UE, and completes the access of the WLAN UE and the Visited Mobile Communi-cation Network newly selected by the WLAN UE.

[0026] Where, the method further comprising before Step c3: judging whether the received Disconnection message is a Disconnection message generated by a successful authentication, if so, waiting for the Access Permission message from the Visited Mobile Communi-cation Network newly selected by the WLAN UE, and after receiving the Access Permission message, collect-ing and sending charging information to the Visited Mo-bile Communication Network that the WLAN UE has ac-cessed, and disconnecting the connection between the WLAN UE and the Visited Mobile Communication Net-work that the WLAN UE has accessed; and at the same time, establishing a connection between the WLAN UE and the Visited Mobile Communication Network newly selected by the WLAN UE, and completing the access of the WLAN UE and the Visited Mobile Communication Network newly selected by the WLAN UE; otherwise, continuing with Step c3. [0027] In above scheme, when the authentication for the authentication request from the newly selected Vis-ited Mobile Communication Network implemented by the Home Network fails, the step of sending an access in-struction comprises: the Home Network sends a Discon-nection message to the WLAN Access Network via the Visited Mobile Communication Network that the WLAN UE has accessed, and sends an Access Rejection mes-sage to the WLAN Access Network via the Visited Mobile Communication Network newly selected by the WLAN UE; the step of completing disconnection and access be-tween the WLAN UE and the corresponding Visited Mo-bile Communication Networks comprises: the WLAN Ac-cess Network disconnects the connection between the WLAN UE and the Visited Mobile Communication Net-work that the WLAN UE has accessed according to the received Disconnection message and returns the Access Rejection message to the WLAN UE according to the received Access Rejection message. [0028] In above scheme, when the authentication for the WLAN UE from the newly selected Visited Mobile Communication Network implemented by the Home Net-work fails, the step of sending an access instruction com-prises: the Home Network sends an Access Rejection message to the WLAN Access Network via the Visited Mobile Communication Network newly selected by the

WLAN UE; the step of completing disconnection and/or access between the WLAN UE and the corresponding Visited Mobile Communication Networks comprises: the WLAN Access Network returns the Access Rejection

5 message to the WLAN UE according to the received Ac- cess Rejection message. [0029] In above scheme, when the authentication for the WLAN UE from the newly selected Visited Mobile Communication Network implemented by the Home Net-

10 work fails, the step of sending an access instruction comprises: the Home Network sends an Access Rejection message to the WLAN Access Network via the Visited Mobile Communication Network newly selected by the WLAN UE, and sends a Re-authentication Request to

15 the WLAN Access Network via the Visited Mobile Com- munication Network that the WLAN UE has accessed; the step of completing disconnection and access be-tween the WLAN UE and the corresponding Visited Mo-bile Communication Networks comprises: the WLAN Ac-

20 cess Network returns the Access Rejection message to the WLAN UE according to the received Access Rejec-tion message, and implements a re-authentication pro-cedure to the Re-authentication Request from the Visited Mobile Communication Network that the WLAN UE has

25 accessed. [0030] In above scheme, when the authentication for the WLAN UE from the newly selected Visited Mobile Communication Network implemented by the Home Net-work fails, the step of sending an access instruction corn-

30 prises: the Home Network sends a Re- authentication Request message to the WLAN Access Network via the Visited Mobile Communication Network newly selected by the WLAN UE; the step of completing disconnection and access between the WLAN UE and the correspond-

35 ing Visited Mobile Communication Networks comprises: the WLAN Access Network implements a re-authentica-tion procedure to the Re-authentication Request from the Visited Mobile Communication Network newly selected by the WLAN UE.

40 [0031] In above scheme, when receiving the Access Permission message from the newly selected Visited Mo-bile Communication Network, the step of completing dis-connection and access between the WLAN UE and the corresponding Visited Mobile Communication Networks

45 comprises: the WLAN Access Network informs the Vis-ited Mobile Communication Network newly selected by the WLAN UE to complete resource distribution and pa-rameter configuration, and the WLAN Access Network establishes a connection between the WLAN UE and the

5° newly selected Visited Mobile Communication Network, and sets the state of the connection as non-activation; and after disconnecting the connection between the WLAN UE and the Visited Mobile Communication Net-work that the WLAN UE has accessed, activates the es-

55 tablished connection between the WLAN UE and the newly selected Visited Mobile Communication Network at once. [0032] In above scheme, the Visited Mobile Commu-

6

NSN677-1002,

11 EP 1 713 207 Al

12

nication Network is a middle operation network connect-ing the WLAN UE and its Home Network, or the Home Network of the WLAN UE. [0033] In above scheme, the step of authenticating the authentication information comprises: an AAA Server of the Home Network implements authentication for the au-thentication request form the Visited Mobile Communi-cation Network newly selected by the WLAN UE. [0034] The interactive method for a WLAN UE re-se-lecting an operation network according to the present invention introduces only a little modification to the AAA Server in the Home Network of current WLAN UE, and enables the AAA Server to cooperate with the existing selection procedure of a WLAN PLM N to accomplish the Visited Mobile Communication Network re-selection by the WLAN UE. [0035] In the technical scheme disclosed by the present invention, the WLAN Access Network can direct-ly implement authentication and access procedure with the new Visited Mobile Communication Network without disconnecting the connection with the former Visited Mo-bile Communication Network, thus the connection time of disconnecting the WLAN UE and external services is shortened or even eliminated, and a smooth re-selection procedure of Visited Communication Network is realized. Moreover, the present invention also provides a WLAN UE establishing multiple connections through different PLMNs, which may not only improve the satisfaction of clients, but also increase the accuracy of charging and subsequently protect the profit of operators. [0036] In addition, the present invention just introduces a few small modifications or adds relatively a little function demand to each network entity, such as the WLAN UE, the WLAN Access Network and the AAA Server, which has little effect on the existing process flow. Therefore, the present invention not only can realize the re-selection function of accessed operation network for WLAN UE but also has very strong practicability. Moreover, the present invention has multiple implementation substi-tutes, thus the implementation of the present invention can be very flexible.

Brief Description of the Drawings

[0037]

Figure 1 is a schematic diagram illustrating a network structure of an inter-working network of a WLAN and a 3GPP system in the case of roaming;

Figure 2 is a schematic diagram illustrating a network structure of an inter-working network of a WLAN and 3GPP system in the case of non-roaming;

Figure 3 is a flow chart illustrating the process of a WLAN UE selecting a Mobile Communication Net-work to access according to an embodiment of the present invention;

Figure 4 is a flow chart illustrating the process of a WLAN UE selecting a Mobile Communication Net-work to access according to another embodiment of the present invention;

5 Figure 5 is a flow chart illustrating the method ac-cording to the present invention;

Figure 6 is a flow chart illustrating the method ac- 10 cording to a specific embodiment of the present in-

vention;

Figure 7 is a schematic diagram illustrating the struc-ture of a network in which a WLAN connected with

15 a plurality of visited networks.

Detailed Description of the Invention

[0038] In order to make the object, the technical 20 scheme and the advantages of the present invention

clearer and more obvious, the present invention will be described in detail hereinafter with reference to embod-iments and accompanying drawings. [0039] The basic idea of the present invention is: a

25 WLAN UE needing to reselect a Visited Mobile Commu- nication Network, initiate an authentication process to the Home Network of the WLAN UE via a WLAN Access Network and the newly selected Visited Mobile Commu-nication Network, which is reselected by the WLAN UE

30 and connected with the present WLAN; and after receiving the authentication request, the Home Network deter-mines whether to disconnect the connection between the WLAN UE initiated request and the former Visited Mobile Communication Network according to the correlative au-

35 thentication information stored in advance, authentica-tion result and the circumstances of whether the current WLAN UE is permitted to have more than one connection simultaneously; and determines whether to set up a con-nection between the WLAN UE initiated request and the

40 new Visited Mobile Communication Network. Thus the access of the WLAN UE to the reselected new Visited Mobile Communication Network is completed. Here, the correlative authentication information stored in advance refers to user subscription information, network access

45 rules set in advance and so on. [0040] In the present invention, the precondition of a WLAN UE implementing network reselection is that the WLAN UE has currently accessed a Visited Mobile Com-munication Network. Here, the Visited Mobile Commu-

50 nication Network currently accessed can be an access network, which is called a middle operation network, con-necting the WLAN UE and its Home Network, such as a VPLMN; it also can be an HPLMN of the current WLAN UE. Wherein, the entity implementing authentication in

55 the Home Network of the WLAN UE can be an AAA Serv- er, more over, in 3GPP-WLAN inter-working network, the entity is a 3GPP AAA Server. [0041] There are several reasons for a WLAN UE re-

7

NSN677-1002,

13

EP 1 713 207 Al 14

selecting a Visited Communication Operation Network, for example, the charge of the currently accessed Visited Mobile Communication Network is higher than that of an-other Visited Mobile Communication Network, in this case the WLAN UE may desire to switch from the cur-rently accessed Visited Mobile Communication Network to the another Visited Mobile Communication Network. In another case, the currently accessed Visited Mobile Communication Network has some restriction for the WLAN UE to access Internet, and the WLAN UE may desire to switch from the currently accessed Visited Mo-bile Communication Network to another Visited Mobile Communication Network. In still another case, the cur-rently accessed Visited Mobile Communication Network can not provide the interaction ability with certain services in PLMN, but another Visited Mobile Communication Net-work can provide such ability; or in still another case, although the charge of the currently accessed Visited Mobile Communication Network is relatively cheap, while the data transmission rate of it is slow, and highspeed access is needed in practical applications, thus the WLAN UE may need to reselect a more expensive Visited Mobile Communication Network with a higher-speed da-ta rate. For example, the switch mentioned above can be a switch from its HPLMN to a VPLMN, or a switch from VPLMN1 to VPLMN2, or a switch from a VPLMN to the HPLMN. [0042] If the current WLAN UE is permitted to support multiple connections simultaneously, for example, the WLAN UE accesses HPLMN through two different VPLMN, VPLMN1 and VPLMN2 simultaneously, then the WLAN UE can access Internet using VPLMNI with a cheaper charging; while for SMS service that is not supported by VPLMNI, the WLAN UE can adopt VPLMN2 supporting SMS service at the same time. Un-der this circumstance, VPLMN1 and VPLM N2 charge the WLAN UE respectively according to the services imple-mented, and the WLAN UE can select either VPLMN1 or VPLMN2 to access a certain service making use of different NAI identities. Here, the multiple connections supported simultaneously can be connections with HPLMN and VPLMN, or connections with different VPLMNs: VPLMNI, VPLMN2... VPLMNn. [0043] As shown in Figure 5, the process of a WLAN UE reselecting a Mobile Communication Network ac-cording to the present invention comprises the following steps:

Step501: On determining a reselected Visited Mobile Communication Network, the WLAN UE needing to select a new Visited Network initiates an access au-thentication process to the WLAN Access Network, and sends the information of the newly selected Vis-ited Mobile Communication Network to the WLAN Access Network. Wherein, the information of the newly selected Visited Mobile Communication Net-work can be carried in the request message and sent to the WLAN Access Network directly; alternatively,

it can also be sent to the WLAN Access Network through response packet during an EAP procedure between the WLAN Access Network and the WLAN UE.

5 Step 502: On receiving the request of the WLAN UE, the WLAN Access Network initiates an authentica-tion request to the Home Network of the current WLAN UE via the Visited Mobile Communication

10 Network newly selected to access by the WLAN UE.

Step 503: On receiving the authentication request, the Home Network implements an authentication op-eration for the authentication request from the Visited

15 Mobile Communication Network newly selected by the current WLAN UE, and sends an access instruc-tion to the WLAN Access Network through different Visited Mobile Communication Networks, that is, through the accessed Visited Mobile Communica-

20 tion Network and the newly selected Visited Mobile Communication Network.

Step 504: On receiving the access instruction sent from the Home Network of the WLAN UE, the WLAN

25 Access Network completes disconnection and/or access process between the WLAN UE and the corre-sponding Visited Mobile Communication Network according to the access instruction.

30 [0044] The Visited Mobile Communication Network mentioned in the present invention can be a Mobile Com-munication Network or other Cable Communication Op-eration Networks. Hereinafter, the implementation pro-cedure of the method according to the present invention

35 will be illustrated in more detail taking a Mobile Commu- nication Network as an example, and the implementation procedures of other Communication Networks are basi-cally similar to that of the Mobile Communication Net-work.

40 [0045] The specific implementation procedure of a WLAN UE reselecting a Mobile Communication Network is shown in Figure 6, which comprises the following steps:

Step 601: The WLAN UE needing to reselect a new 45 Access Network determines a newly selected Mobile

Communication Network to access; then the WLAN UE sends an Access Authentication Request to the WLAN Access Network, expressing that the WLAN UE needs to access the new Mobile Communication

50 Network. For example, selecting VPLMN2 while already connecting with VPLMN1 indicates that the WLAN UE desires to access HPLMN via the new VPLMN2, if the newly selected network is HPLMN, it means the WLAN UE desires to access HPLMN

55 directly. Here, the WLAN UE can select to switch from an existing connection to a new connection, and it can also select to support two or a plurality of connections simultaneously according to network

8

NSN677-1002,

15

EP 1 713 207 Al 16

ability and/or subscription information.

[0046] Wherein, the 3GPP Mobile Communication Network currently accessed by the WLAN UE can be a Visited Network or a Home Network of the WLAN UE.

Step 602: After the WLAN Access Network receives the Access Authentication Request, an access au-thentication procedure is implemented between the WLAN Access Network and the WLAN UE, i.e. an EAP procedure is taken, more specifically: the WLAN Access Network sends a Request UID packet to the WLAN UE; and on receiving the request pack-et, the WLAN UE sends a UID Response packet con-taining the information of the newly selected Mobile Communication Network to the WLAN Access Net-work. In the same way, the information of a Mobile Communication Network can be set in the UID field with the NAI format.

Step 603: Via the Mobile Communication Network newly selected by the current WLAN UE, the WLAN Access Network sends the Access Authentication Request to the Home Network of the current WLAN UE to implement authentication, which specifically comprises: the WLAN Access Network sends the Access Authentication Request to an AAA Agent of the new Mobile Communication Network; and after receiving the request, the AAA Agent sends an au-thentication request to the AAA Server in the Home Network of the WLAN UE, and subsequently the au-thentication procedure is implemented by the AAA Server.

Step604-606: On receiving the authentication re-quest, the Home Network of the WLAN UE deter-mines whether the request is an authentication re-quest from the newly selected Mobile Communica-tion Network according to the information in the re-quest, if the request is an authentication request via the newly selected Mobile Communication Network the Home Network implements an authentication op-eration to the authentication request from the Mobile Communication Network newly selected by the cur-rent WLAN UE, and sends an access instruction to the WLAN Access network through different Mobile Communication Networks, i.e. through the accessed Mobile Communication Network and the newly se-lected Mobile Communication Network; and after re-ceiving the Home Network access instruction from the current WLAN UE, the WLAN Access Network completes a disconnection and an access operation between the WLAN UE and corresponding Mobile Communication Networks.

[0047] The information in the request in Step 604 refers to address information of a VPLMN or a VPLMN ID or other. For example: since the Home Network stores all

the information of the currently accessed Mobile Com-munication Network, the Home Network can judge whether the source address in the request is the same as the address of the currently accessed Mobile Com-

5 munication Network. And if the two addresses are not the same, it means that the request is an authentication request from a newly selected Mobile Communication Network. [0048] In fact, an alternative case in Step 604 is that

10 the Home Network does not need to judge whether the request is an authentication request from the newly se-lected Mobile Communication Network, and it imple-ments authentication to the received authentication re-quest directly.

15 [0049] In Step 604, before implementing the authentication, the Home Network can first judge whether the current WLAN UE is permitted to access multiple con-nections simultaneously. Wherein, the judgment is based on the data configured in advance by the operators or

20 the data of the user subscription information. The data configured may include that whether the network permits the WLAN UE to have multiple connections, whether the network permits users with certain characteristics to have multiple connections or whether the network forbids us-

25 ers with other certain characteristics to have multiple connections; in addition, whether multiple connections to cer-tain VPLMNs are forbidden, if so, a list of VPLMNs under these circumstances is needed. If the judgment is imple-mented according to each user, the corresponding pa-

30 rameters are needed in the user subscription information, which may include whether the user permits multiple con-nection accesses from different VPLMNs, whether the permitted multiple connections comprise HPLMN, and the maximum number of the permitted simultaneous con-

35 nections and so on. [0050] If the current WLAN UE is permitted to access only one VPLMN connection simultaneously, the process done to the newly selected network in Step 605 and 604 can actually be divided into two cases:

40

In one case, the Home Network sends a Disconnec-tion message to the former Mobile Communication Network and disconnects the former connection be-tween the former Mobile Communication Network

45 and the current WLAN UE, then implements authentication to the authentication request from the new Mobile Communication Network. In this case, the WLAN Access Network determines whether to ac-cess the new Mobile Communication Network ac-

50 cording to the authentication result. And next completes subsequent operations, and then completes the current flow of reselecting a network. That is, if the authentication fails, an Access Failure message will be returned to the WLAN UE, which may contain

55 failure reasons; if the authentication succeeds, the WLAN Access Network will set up a normal connec-tion between the WLAN UE and the new Mobile Communication Network, establishes a correspond-

9

NSN677-1002,

17 EP 1 713 207 Al

18

ing charging relationship between the WLAN Access Network and the new Mobile Communication Net-work, and thus completes the procedure of the WLAN UE reselecting a Mobile Communication Net-work.

In the other case, the Home Network implements authentication to the authentication request from the new Mobile Communication Network directly, and determines the Mobile Communication Network to be finally accessed by the current WLAN UE accord-ing to the authentication result and corresponding authentication information, and then the Home Net-work sends an authentication result to the WLAN Access Network; the WLAN Access Network com-pletes the subsequent disconnection and/or access operations according to the received signaling indi-cations. In this case, the subsequent operations of the WLAN Access Network can be further divided into three cases:

a) The authentication implemented by the Home Network to the authentication request from the new Mobile Communication Network fails. In this case, the Home Network should differenti-ate whether the failure is a failure of an authen-tication to the current WLAN UE, which can be judged with respect to the failure reasons. If the failure is a failure of an authentication to the cur-rent WLAN UE, the Home Network may reject to set up a connection between the WLAN UE and the new Mobile Communication Network, and at the same time may disconnect the con-nection between the WLAN UE and the former Mobile Communication Network. Alternatively, the Home Network can also only reject to set up a connection between the WLAN UE and the new Mobile Communication Network; in view of another substitute, the Home Network can also reject to set up a connection between the WLAN UE and the new Mobile Communication Net-work and at the same time request the former Mobile Communication Network to implement authentication to the current WLAN UE once again. Otherwise, the Home Network can only reject to set up a connection between the WLAN UE and the new Mobile Communication Network, and keep the connection between the WLAN UE and the former Mobile Communication Network. Al-ternatively, the Home Network can also imple-ment authentication to the authentication re-quest from the new Mobile Communication Net-work once again.

b) The Home Network judges whether the au-thentication request via the new Mobile Com-munication Network is permitted to pass accord-

ing to the network access rules or user subscrip-tion information set in advance, and if it is not permitted, the Home Network sends an authen-tication failure message to the new Mobile Com-

5 munication Network, and keeps the connection between the WLAN UE and the former Mobile Communication Network. For example, the net-work access rule set in advance includes that accessing another Mobile Communication Net-

10 work simultaneously after accessing one Mobile Communication Network is not permitted, and then the authentication request via the new Mo-bile Communication Network will not be permit-ted to pass. For another example, the user sub-

15 scription information indicates that accessing more than one Access Network simultaneously is not permitted, and then the authentication re-quest from the new Mobile Communication Net-work will not be permitted to pass. That is, the

20 Home Network can forbid the WLAN UE to access two Mobile Communication Networks si-multaneously according to the practical situation of the WLAN UE.

25 c) The authentication to the WLAN UE succeeds. In this case, the Home Network sends an Access Permission message to the new Mo-bile Communication Network, and then sends a Disconnection message to the former Mobile

30 Communication Network. Specifically, the Home Network can send the Access Permission message first and then send the Disconnection message. Alternatively, it can also send the Ac-cess Permission message and the Disconnec-

35 tion message at the same time. Or, the Home Network can only send the Access Permission message to the new Mobile Communication Network.

40 [0051] According to the above Case c, accordingly, the process of the WLAN Access Network also comprises three cases:

c1) If the WLAN Access Network receives the Ac- 45 cess Permission message from the new Mobile

Communication Network first, the WLAN Access Network collects charging information and sends the charging information to the former Mobile Commu-nication Network, and then disconnects the network

50 connection between the current WLAN UE and the former Mobile Communication Network; at the same time, the WLAN Access Network sets up a normal network connection between the current WLAN UE and the new Mobile Communication Network, and

55 establishes a corresponding charging relationship with the new Mobile Communication Network, and the subsequent charging information should be sent to the new Mobile Communication Network and thus,

10

NSN677-1002,

19 EP 1 713 207 Al

20

the network reselecting operation of the WLAN UE is completed.

c2) If the WLAN Access Network receives the Dis-connection message from the former Mobile Com-munication Network, the WLAN Access Network can collect the charging information and send the charg-ing information to the former Mobile Communication Network directly, then disconnects the current WLAN UE and the former Mobile Communication Network, and next waits for the authentication result from the new Mobile Communication Network. After receiving the authentication result, the WLAN Ac-cess Network sets up a normal network connection between the current WLAN UE and the new Mobile Communication Network and establishes a corre-sponding charging relationship with the new Mobile Communication Network, thus the subsequent charging information is to be sent to the new Mobile Communication Network and then the network rese-lecting operation of the WLAN UE is completed. The WLAN Access Network can also wait for authen-tication result from the new Mobile Communication Network first; and after receiving the authentication result, the WLAN Access Network collects the charg-ing information and sends it to the former Mobile Communication Network, and then disconnects the network connection between the current WLAN UE and the former Mobile Communication Network, At the same time, the WLAN Access Network sets up a normal network connection and a corresponding charging relationship for the current WLAN UE and the new Mobile Communication Network, thus the subsequent charging information is to be sent to the new Mobile Communication Network and then com-pletes the network reselecting operation of the WLAN UE.

c3) If the WLAN Access Network receives the Dis-connection signaling generated due to authentica-tion failure, the WLAN Access Network first collects the charging information and sends it to the former Mobile Communication Network, then disconnects the network connection between the current WLAN UE and the former Mobile Communication Network, and then waits for authentication result from the new Mobile Communication Network; if the Access Per-mission message is received, the corresponding op-erations will be implemented according to Case c1; and if the authentication result is not received, tries to implement the authentication process once again.

[0052] If the current WLAN UE is permitted to access multiple VPLMN connections simultaneously, for exam-ple, the current WLAN UE sets up a connection of WLAN-VPLMNI-HPLMN, and at the same time, it also sets up a connection of WLAN-VPLMN2-PLMN. Here, the Home Network or the WLAN Access Network of the current

WLAN UE will determine whether to disconnect the ex-isting connection according to the user subscription in-formation, network setting or user selection. If it deter-mines not to disconnect the existing connection, on one

5 hand, the AAA will judge whether the connection is within the range of the multiple connections, and if so, the AAA will implement normal authentication and access authen-tication operations for the new connection and indicate WLAN to access the WLAN UE after the authentication

10 is successful. On the other hand, it also needs to implement an operation of affirming the existing connection is continued to be used. This operation can be completed in more than one ways, for example, a) implements a re-authentication to the WLAN UE through the Mobile Com-munication Network that the current WLAN UE has ac-cessed; b) indicates the current WLAN UE that there are multiple connections exist in itself, here the indication can be sent through established connections, the new established connection or any other connections be-

20 tween the network and the WLAN UE, and the total number of the current connections and/or specific con-nection selection such as a list of selected and accessed VPLMN and so on can be indicated in the indication in-formation; c) does nothing.

25 [0053] If a threshold of the number of multiple connections is set in advance and after the new connection to be established by the WLAN UE is established, the number of connections exceeds the threshold of the max-imum number of multiple connections, the request of the

30 new connection will be rejected; or the user will be prompted to select a connection to be removed, i.e. select a connection to be removed among the current estab-lished connections. Here, the network can disconnect the corresponding accessed Visited Mobile Communica-

35 tion Network or reject the newly selected Visited Mobile Communication Network according to user's response, and the network also can appoint a connection to be re-moved and let the user affirm. [0054] In the above schemes, the step of disconnect-

40 ing the connection between the Mobile Communication Network and the WLAN UE further comprises: discon-necting the service connection, settling accounts of charging information and so on, the specific process is exactly the same as the existing procedure of discon-

45 necting connection between the WLAN UE and the Mo-bile Communication Network connected with the WLAN UE. [0055] In the above schemes, after receiving the Ac-cess Permission message from the new Mobile Commu-

50 nication Network, the WLAN Access Network can first do each preparative operation of the WLAN UE and the new Mobile Communication Network, such as the new Mobile Communication Network completing resource distribu-tion, parameters configuration and so on, and the set up

55 a connection between the WLAN UE and the new Mobile Communication Network, whose connection state is set as non-activation. After disconnecting the connection be-tween the WLAN UE and the accessed Mobile Commu-

11

NSN677-1002,

21 EP 1 713 207 Al

22

nication Network, the established connection between the WLAN UE and the new Mobile Communication Net-work is to be activated at once, thus the time of discon-necting the user service connection can be reduced. [0056] Figure 7 shows a circumstance of a certain WLAN Access Network connecting three VPLMNs simul-taneously. Suppose a WLAN UE has accessed VPLMN1 through the WLAN Access Network, and now the WLAN UE wants to switch from VPLMN1 to VPLMN2. Wherein, VPLMNI corresponds to a former 3GPP AAA Agent and VPLMN2 corresponds to a new 3GPP AAA Agent. Now, the process of the WLAN UE reselecting a Mobile Com-munication Network to access will be illustrated in more detail hereinafter with reference to several embodiments and Figure 7.

Embodiment 1:

[0057] In this embodiment, after receiving the authen-tication request from VPLMN2, the Home Network im-plements an authentication operation directly; more over, after the authentication succeeds, the Home Networkfirst sends an Access Permission message to VPLMN2 and then sends a Disconnection message to VPLMNI. Ac-cordingly, the WLAN Access Network will receive the Ac-cess Permission message first. In addition, in the present embodiment, the current WLAN UE is permitted to ac-cess only one connection simultaneously; in this case, the process of the WLAN UE reselecting a Mobile Com-munication Network comprises the following steps:

Step 11: The current WLAN UE determines that it needs to access VPLMN2, and affirms the domain name or identity of VPLMN2.

Step 12: the WLAN UE sends an access authenti-cation request to the WLAN Access Network without affecting the existing connection with VPLMN1, i.e. the WLAN UE sends an Authentication Start Packet EAPoL-Start to the WLAN Access Network.

Step 13-14: On receiving the access authentication request, the WLAN Access Network initiates an ac-cess authentication procedure, i.e. an EAP proce-dure, between the WLAN Access Network and the WLAN UE. Specifically, the WLAN Access Network sends a User Identity Packet EAPoL-Request [Iden-tity] to the WLAN UE to request the user name of the current WLAN UE; after receiving the request pack-et, the WLAN UE returns a User Identity Response Packet EAPoL-Response [Identity] to the WLAN Ac-cess Network, which carries a user identity field with NAI format. Wherein, the user identity field carries network selection information; the packet can also carry identity information to identify this information is for network reselection.

Step 15: The WLAN Access Network confirms that

the current WLAN UE select to access VPLMN2 ac-cording to an address information or identity infor-mation of VPLMN2 in the request, and VPLMN2 con-nects with the present WLAN, then the WLAN Ac-

5 cess Network forwards the access authentication request from the WLAN UE to VPLMN2 and then the access authentication request is forwarded to the Home Network of the WLAN UE, and next the au-thentication procedure is implemented by the Home

10 Network, specifically, all the authentication operations are completed by an AAA Server in the Home Network.

Step 16: After the Home Network of the current 15 WLAN UE receives the authentication request, since

the current WLAN UE connects with VPLMN1, the corresponding connection information exists in the Home Network, the Home Network judges and con-firms that the authentication request from VPLMN2

20 is an authentication request from a newly selected Mobile Operation Network according to the existing information or Mobile Communication Network iden-tity carried in the authentication request, and then the Home Network implements authentication for the

25 authentication request from VPLMN2 directly. In this step, the Home Network also needs to judge whether the current WLAN UE is permitted to access multiple VPLMNs simultaneously, if so, the Home Network can disconnect or keep the former connec-

30 tion in the subsequent steps; otherwise, the former connection will be disconnected. In the present em-bodiment, the current WLAN UE is not permitted to access multiple VPLMNs, so VPLMNI and the WLAN UE will be disconnected in subsequent steps.

35

Step 17: If the authentication to the WLAN UE fails, an Access Rejection message will be sent to VPLMN2; or alternatively a re-authentication mes-sage will be sent to VPLMN1 and an Access Rejec-

40 tion message will be sent to VPLMN2 by the Home Network. After receiving the Access Rejection mes-sage from VPLMN2, the WLAN network informs the WLAN UE initiating the current request that the au-thentication fails, and then completes the current

45 process of network reselection. Wherein, the Access Rejection message carries reasons of rejection, for example, a rejection reason value. If the Home Network confirms to reject the authen-tication request of the current WLAN UE since it is

50 from VPLMN2 according to the network access rules or user subscription information set in advance, for example, access rules of accessing more than one Mobile Communication Network by the WLAN UE simultaneously being not permitted, or accessing

55 VPLMN2 by the WLAN UE being not permitted and soon, the Home Network sends an Access Rejection message to VPLMN2, and the connection between the Home Network and VPLMN1 will not be affected.

12

NSN677-1002,

23

EP 1 713 207 Al 24

After receiving the Access Rejection message from VPLMN2, the WLAN Access Network informs the WLAN UE that the authentication of reselecting Mo-bile Communication Network fails, and then com-

tication request from VPLMN2, the Home Network im-plements authentication operation directly and the au-thentication succeeds; more over, after the authentica-tion succeeds, the Home Network sends an Access Per-

pletes the current process of network reselection. 5 mission message to VPLMN2 and at the same time sends If the authentication to the WLAN UE by the Home a Disconnection message to VPLMNI; and then the Network succeeds, proceeds to Step 18. In the WLAN Access Network receives the Disconnection mes- present embodiment, suppose that the authentica- sage first. In the present embodiment, the current WLAN tion for the WLAN UE by the Home Network suc- UE is permitted to access only one connection or the ceeds. 10 WLAN UE indicates to switch from an existing connection

to a new connection. In this case, the procedure of the Step 18: The Home Network sends an Access Per- WLAN UE reselecting a Mobile Communication Network mission message to VPLMN2, and since according in the present embodiment is basically the same as that to the network access rules or user subscription in- in Embodiment 1, while Step 38 and 39 are different from formation, the WLAN UE is permitted to access only one connection simultaneously, the Home Network sends a Disconnection message to VPLMN1 later.

15 Step 18 and 19 of Embodiment 1.

Step 31-37: These steps are exactly the same as that of Step 11-17 according to Embodiment 1.

Step 19: After receiving the Access Permission mes-sage from VPLMN2 first, the WLAN Access Network 20 Step 38: The Home Network sends an Access Per- collects charging information and then sends it to mission message to VPLMN2 and at the same time VPLMNI, and next disconnects the connection be-tween the current WLAN UE and VPLMNI; and at the same time, the WLAN Access Network sets up

sends a Disconnection message to VPLMNI.

Step 39: After first receiving the Disconnection mes- a normal network connection between the WLAN UE 25 sage from VPLMNI, the WLAN Access Network and VPLMN2, and establishes corresponding charg- waits for the Access Permission message from ing relationship with VPLMN2 and thus the subse- VPLMN2, and after receiving the Access Permission quent charging information will be sent to VPLMN2, and the process of operation network reselection of

message, the WLAN Access Network collects charg-ing information and sends it to VPLMN1, and then

the WLAN UE is completed. 30 disconnects the connection between the current WLAN UE and VPLMNI; next, the WLAN Access

Embodiment 2: Network sets up a normal network connection for the WLAN UE and VPLMN 2, and establishes a corre-

[0058] In this embodiment, after receiving the authen- sponding charging relationship with VPLMN2 and tication request from VPLMN2, the Home Network im- 35 thus the subsequent charging information will be plements authentication operation directly; and after the sent to VPLMN2, and the process of operation net- authentication succeeds, the Home Network sends an work reselection of the WLAN UE is completed. Access Permission message to VPLMN2 and at the same time sends a Disconnection message to VPLMN1; Embodiment 4: and then, the WLAN Access Network receives the Ac- 40

cess Permission message first. In the present embodi- [0060] In this embodiment, after receiving the authen- ment, the current WLAN UE is permitted to access only tication request from VPLMN2, the Home Network im- one connection or the WLAN UE indicates to switch from plements authentication operation directly and the au- an existing connection to a new connection. In this case thentication succeeds; more over, after and the authen- the procedure of the WLAN UE reselecting a Mobile Com- 45 tication succeeds, the Home Network sends an Access munication Network according to the present embodi- Permission message to VPLMN2 and at the same time ment is basically the same as that of Embodiment 1, but sends a Disconnection message to VPLMNI; the WLAN Step 28 is different from Step 18 of Embodiment 1. Access Network receives the Disconnection message

generated due to authentication failure. In the present Step 21-27: These steps are exactly the same as 50 embodiment, the current WLAN UE is permitted to ac- that of Step 11-17 according to Embodiment 1. cess only one connection or the WLAN UE indicates to Step 28: The Home Network sends an Access Per- switch from an existing connection to a new connection. mission message to VPLMN2 and at the same time In this case, the procedure of the WLAN UE reselecting sends a Disconnection message to VPLMNI. a Mobile Communication Network in the present embod-

Embodiment 3:

55 invent is basically the same as that in Embodiment 1, while Step 48 and 49 are different from Step 18 and 19 of Embodiment 1.

[0059] In this embodiment, after receiving the authen-

13

NSN677-1002,

25 EP 1 713 207 Al

26


Step 48: The Home Network sends an Access Per-

and VPLMNI, but does not disconnect the wireless connection between the current WLAN UE and VPLMN1; and then implements authentication to the authentication request from VPLMN2.

mission message to VPLMN2 and at the same time 5 sends a Disconnection message to VPLMN1. Step 58: After receiving the authentication result

from VPLMN2, the WLAN Access Network judges Step 49: After the WLAN Access Network receiving whether the authentication is successful, if the au- the Disconnection message from VPLMN1, and the thentication is successful, the WLAN Access Net- reason value carried in the message indicates that 10 work establishes a signaling relationship, a charging one Mobile Communication Network needs to be dis- relationship and an authentication relationship be- connected because of repeated connection, then the tween the current WLAN UE and VPLMN2, and sets WLAN Access Network collects charging informa- up a service connection between the current WLAN tion first and sends it to VPLMNI, next, disconnects UE and VPLMN2, completing the network reselec- the connection between the current WLAN UE and 15 tion process. Otherwise, the WLAN Access Network VPLMN1, and then waits for the authentication result informs the current WLAN UE that the authentication from VPLMN2; after receiving the Access Permis- is a failure and the authentication failure message sion message from VPLM N2, the WLAN Access Net-work sets up a normal network connection for the

may carry the failure reason value.

WLAN UE and VPLMN2, and then establishes a cor- 20 Embodiment 6: responding charging relationship with VPLMN2 and thus the subsequent charging information will be [0062] In this embodiment, the current WLAN UE is sent to VPLMN2, and the process of operation net- permitted to access multiple VPLMNs according to its work reselection of the WLAN UE is completed. user subscription information, and VPLMN2 selected by Here, if the authentication result from VPLMN2 is not 25 the WLAN UE is the second VPLMN the WLAN UE wants received, the WLAN Access Network may try to im- to access. After receiving the authentication request from plement authentication once again, and times of try- VPLMN2, the Home Network implements authentication ing or a period of time for trying over again can be directly and the authentication succeeds. And after the set in advance, if the times of trying or the period of authentication succeeds, the Home Network confirms time for trying set in advance is reached, the authen- 30 that the current WLAN UE is permitted to implement mul- tication fails. tiple-connection access by judgment, and then the Home

Network sends an Access Permission message to Embodiment 5: VPLMN2; after that the WLAN Access Network activates

the connection from the WLAN UE to VPLMN2 and dis- [0061] In the present embodiment, after receiving the 35 tributes the data of the WLAN UE to VPLMNI orVPLMN2 authentication requestfrom VPLMN2, the Home Network according to different IP address or NAI used by the sends a Disconnection message to VPLMN1 first, and WLAN UE. The WLAN UE sends corresponding service then implements authentication for the authentication re- data to different VPLMNs according to the selection of quest from VPLMN2. In this embodiment, the current the user or the user application program. Thus the pro- WLAN UE is permitted to access only one connection 40 cedure of the WLAN UE reselecting Mobile Communica- simultaneously or the WLAN UE indicates to switch from tion Network according to the present embodiment is ba- an existing connection to a new connection. In this case, the procedure of the WLAN UE reselecting a Mobile Com-

sically the same as that in Embodiment 1, except that Step 68 and 69 are different from Step 18 and 19 of Em-

munication Network comprises the following steps: bodiment 1. 45

Step 51-56: These steps are exactly the same as Step 61-67: These steps are exactly the same as that of Step 11-16 according to Embodiment 1. that of Step 11-17 according to Embodiment 1.

Step 57: The Home Network sends a Disconnection Step 68: Since the current WLAN UE is permitted to message to VPLMN1 requesting to disconnect the 50 access multiple connections simultaneously, at the connection between VPLMN1 and the current WLAN time the Home Network sends an Access Permission UE; after receiving the Disconnection message sent message to VPLMN2, it does not need to send a from the Home Network and through VPLNM1, the Disconnection message to VPLMN1. WLAN Access Network disconnects with VPLMNI, which specifically comprises: collects charging infor- 55 Step 69: After receiving the Access Permission mes- mation and then sends it to VPLMNI, disconnects sage from VPLM N2, the WLAN Access Network sets the network connection, signaling connection and up a normal network connection for the WLAN UE service connection between the current WLAN UE and VPLMN2 and establishes a corresponding

14

NSN677-1002,

27

EP 1 713 207 Al 28

charging relationship with VPLMN2, thus the subse-quent charging information will be sent to VPLMNI or VPLMN2 according to user identity information, here, the user identity information includes NAI, IP address and so on. For example, if the user data use an IP address belonging to VPLMNI, the corre-sponding charging information will be sent to VPLMNI; if the identity of user data is of VPLMN2, the corresponding charging information will be sent to VPLMN2, and the process of the WLAN UE sup-porting multiple VPLMN networks is completed. Here, if the authentication result from VPLMN2 is not received, the WLAN Access Network may try to im-plement authentication once again, and times of try-ing or a period of time for trying can be set in advance. If the times of trying or the period of time for trying set in advance is reached, the authentication fails.

Embodiment 7:

[0063] In this embodiment, the current WLAN UE is permitted to access multiple VPLMNs according to the user subscription information and a threshold of the max-imum connection number simultaneously is set in ad-vance, VPLMNn selected by the WLAN UE is the nth VPLMN the WLAN UE wants to access, and n exceeds the threshold of the maximum connection number simul-taneously of the WLAN UE set in advance, after receiving the authentication request from VPLMNn, the Home Net-work can reject directly and explains in the rejection rea-son that the reason of rejection is access limit, and certain existing connections need to be removed by the WLAN UE; the Home Network can also directly accept the au-thentication request currently received and indicates the WLAN UE to select a connections to be removed after the authentication succeeds.


Step 78: The Home Network judges whether the nth

connection exceeds the threshold of the maximum connection number simultaneously of the WLAN UE, if dose not exceed, proceeds to the steps described in Step 68 and 69 of Embodiment 6; otherwise, the Home Network selects to reject or accept the request and implement authentication according to user sub-scription information or network configuration, and then indicates the WLAN UE to remove a certain existing connection.

Embodiment 8:

[0064] In the present embodiment, the current WLAN UE is permitted to access multiple VPLMNs simultane-ously according to the user subscription information, but the WLAN UE expects to switch from a certain existing connection to anther new connection. In this case, the

existing connection can be deleted first, and then a new connection is established, as described in Embodiment 4; alternatively, a new connection can be tried to set up first, an if the new connection is set up successfully, the

5 former connection deleted then, as described in Embod- iment 1,2 and 3; and in view of another substitute, while the new connection is set up, indicates the network in signaling the former connection to be deleted. [0065] What are mentioned above are just some rela-

10 tively preferred embodiments of the present invention, which are not intended to limit the protection range of the invention.

15 Claims

1. An interactive method for a Wireless Local Area Net-work (WLAN) User equipment (UE) accessing a new communication network, comprising:

20

when the WLAN UE accessing a first Visited Mo-bile Communication Network needs access a second Visited Mobile Communication Network, the WLAN UE sending authentication informs-

25 tion to a Home Network where the WLAN UE locates via a WLAN Access Network and the second Visited Mobile Communication Network; upon receiving the authentication information, the Home Network authenticating the WLAN UE

30 according to the authentication information and sending an access instruction to the WLAN Ac-cess Network via the second Visited Mobile Communication Network; and completing disconnection and/or access be-

35 tween the WLAN UE and the corresponding Vis- ited Mobile Communication Networks.

2. The method according to claim 1, wherein, before the Home Network authenticates the WLAN UE, fur-

40 ther comprising: the Home Network of the WLAN UE sending a Disconnection message to the Visited Mo-bile Communication Network that the WLAN UE has accessed, and disconnecting the connection be-tween the WLAN UE and the Visited Mobile Com-

45 munication Network that the WLAN UE has accessed; the step of sending the access instruction comprises: the Home Network sending an Access Permission message or an Access Rejection message to the

50 WLAN Access Network via the Visited Mobile Com- munication Network newly selected by the WLAN UE; and the step of completing disconnection and/or access between the WLAN UE and the corresponding Vis-

55 ited Mobile Communication Networks comprises: the WLAN Access Network judging whether the Ac-cess Permission message is received, if so, estab-lishing a connection between the WLAN UE and the

15

NSN677-1002,

29 EP 1 713 207 Al

30

Visited Mobile Communication Network newly se-lected by the WLAN UE, and completes the access of the WLAN UE to the Visited Mobile Communica-tion Network newly selected by the WLAN UE; oth-erwise, forwarding the Access Rejection message to the WLAN UE.

3. The method according to claim 2, wherein, before the Home Network authenticates the WLAN UE, fur-ther comprising: judging whether the WLAN UE is permitted to access more than one Visited Mobile Communication Networks simultaneously, if so, the Home Network of the WLAN UE determining wheth-er to send a Disconnection message to the Visited Mobile Communication Network that the WLAN UE has accessed; otherwise, the Home Network of the WLAN UE sending a Disconnection message to the Visited Mobile Communication Network that the WLAN UE has accessed, and disconnecting the con-nection between the WLAN UE and the Visited Mo-bile Communication Network that the WLAN UE has accessed.

4. The method according to claim 1, wherein, before the Home Network authenticates the WLAN UE, fur-ther comprising: the Home Network judging whether to permit the authentication for the authentication re-quest from the Visited Mobile Communication Net-work newly selected by the WLAN UE, and if permit-ted, continuing with the authentication operation for the authentication request from the Visited Mobile Communication Network newly selected by the WLAN UE; if not permitted, the step of sending an access in-struction comprises:

the Home Network sending an Access Rejection message to the WLAN Access Network via the Visited Mobile Communication Network newly selected by the WLAN UE; and the step of completing disconnection and/or ac-cess between the WLAN UE and the corre-sponding Visited Mobile Communication Net-works comprises: the WLAN Access Network forwarding the Access Rejection message to the WLAN UE.

5. The method according to claim 4, wherein, the step ofjudging further comprising: judging whether to per-mit the WLAN UE to access more than one Visited Mobile Communication Network simultaneously, if permitted, judging whether to permit to authenticate the authentication request from the second Visited Mobile Communication Network; and if not permit to authenticate the authentication request, the authen-tication to the authentication request from the second Visited Mobile Communication Network is consid-ered not to be permitted.

6. The method according to claim 2 or 4, wherein, the Access Rejection message further carries a piece of information indicating the reason of rejection.

5 7. The method according to claim 1, wherein, after the authentication to the WLAN UE succeeds, the step of sending an access instruction comprises: the Home Network sending an Access Permission mes-sage to the WLAN Access Network via the Visited

10 Mobile Communication Network newly selected by the WLAN UE; the step of completing disconnection and/or access between the WLAN UE and the corresponding Vis-ited Mobile Communication Network comprises: ac-

15 cording to the received Access Permission message, the WLAN Access Network establishes a con-nection between the WLAN UE and the Visited Mo-bile Communication Network newly selected by the WLAN UE, and completes the access of the WLAN

20 UE and the Visited Mobile Communication Network newly selected by the WLAN UE.

8. The method according to claim 7, wherein, while sending the Access Permission message to the Vis-

25 ited Mobile Communication Network newly selected by the WLAN UE, the Home Network sends a Dis-connection message to the WLAN Access Network via the Visited Mobile Communication Network that the WLAN UE has accessed;

30 the step of completing disconnection and/or access between the WLAN UE and the corresponding Vis-ited Mobile Communication Networks further com-prising: disconnecting the connection between the WLAN UE and the Visited Mobile Communication

35 Network that the WLAN UE has accessed.

9. The method according to claim 7, wherein, before sending the Disconnection message to the WLAN Access Network via the Visited Mobile Communica-

40 tion Network that the WLAN UE has accessed further comprising: judging whether to permit the WLAN UE access more than one Visited Mobile Communica-tion Network simultaneously, if so, the Home Net-work of the WLAN UE determining whether a Dis-

45 connection message be sent to the Visited Mobile Communication Network that the WLAN UE has ac-cessed according to the selection of the users; oth-erwise, the Home Network sending the Disconnec-tion message to the WLAN Access Network via the

50 Visited Mobile Communication Network that the WLAN UE has accessed.

10. The method according to claim 7, wherein, the meth-od further comprising: implementing re-authentica-

55 tion for the WLAN UE via the Visited Mobile Com- munication Network that the WLAN UE has ac-cessed; and/or sending advertisement information to inform the WLAN UE that more than one connec-

16

NSN677-1002,

31

EP 1 713 207 Al 32

tion existing in the WLAN UE; or doing nothing.

11. The method according to claim 1, wherein, after the authentication to the WLAN UE succeeds, the step

whether the number of the current simultaneous con-nections exceeds the threshold of the maximum number of the simultaneous connections, if not, con-tinuing with subsequent operations; otherwise, re-

of sending an access instruction comprises: the 5 jecting the authentication request of the current con- Home Network sending an Access Permission mes- nection directly, or performing the authentication re- sage to the WLAN Access Network via the Visited quest of current connection and informing the current Mobile Communication Network newly selected by WLAN UE to disconnect one or more than one ex- the WLAN UE; isting connection. the step of completing disconnection and/or access 10

between the WLAN UE and the corresponding Vis- 15. The method according to claim 14, wherein, the ited Mobile Communication Networks comprises: af- method further comprising: after informing the ter receiving the Access Permission message, the WLAN UE to disconnect one or more than one con- WLAN Access Network establishing a connection nection, the network disconnecting a corresponding between the WLAN UE and the Visited Mobile Com- 15 accessed Visited Mobile Communication Network or munication Network newly selected by the WLAN rejecting the Visited Mobile Communication Network UE, completes the access of the WLAN UE and the newly selected by the WLAN UE according to the Visited Mobile Communication Network newly se-lected by the WLAN UE, and disconnecting the con-nection between the WLAN UE and the Visited Mo-bile Communication Network that the WLAN UE has accessed.

20

correlative selection information.

16. The method according to claim of 7, 8 or 9, wherein, when the authentication to the WLAN UE succeeds, the step of ompleting disconnection and access be-tween the WLAN UE and the corresponding Visited

12. The method according to claim 11, wherein, after the Mobile Communication Networks comprises: WLAN Access Network completing the accessing 25

the WLAN UE and the Visited Mobile Communica- c1. the WLAN Access Network judging whether tion Network newly selected by the WLAN UE, fur-ther comprising: judging whether the WLAN UE is

the Access Permission message from the Visit-ed Mobile Communication Network newly se-

permitted to access to more than one Visited Mobile Communication Network simultaneously, and if so, the WLAN Access Network determining whether to

30

lected by the WLAN UE is received first, if so, proceeding to Step c2; if the Disconnection mes-sage is received first, proceeding to Step c3;

send the Disconnection message to the Visited Mo- c2. collecting and sending charging information bile Communication Network that the WLAN UE has to the Visited Mobile Communication Network accessed; otherwise, disconnecting the connection that the WLAN UE has accessed, and discon- between the WLAN UE and the Visited Mobile Com- 35 necting the connection between the WLAN UE munication Network that the WLAN UE has ac- and the Visited Mobile Communication Network cessed. that the WLAN UE has accessed; and establish-

ing a connection between the WLAN UE and the 13. The method according to claim 3, 9 or 12, wherein,

when the WLAN UE is permitted to access more than 40

Visited Mobile Communication Network newly selected by the WLAN UE, and completes the

one Visited Mobile Communication Network simul- access of the WLAN UE and the Visited Mobile taneously, and the Home Network of the WLAN UE Communication Network newly selected by the determining not to send a Disconnection message WLAN UE and then completes the current re- to the Visited Mobile Communication Network that selection process; the WLAN UE has accessed, the method further 45 c3. collecting and sending charging information comprising: re-authenticating the WLAN UE via the to the Visited Mobile Communication Network Visited Mobile Communication Network that the that the WLAN UE has accessed, and discon- WLAN UE has accessed; and/or sending a piece of necting the connection between the WLAN UE advertisement information to inform the WLAN UE and the Visited Mobile Communication Network that more than one connection exists; or doing noth- 50 that the WLAN UE has accessed, waiting for the ing. Access Permission message from the Visited

Mobile Communication Network newly selected 14. The method according to claim 3, 5, 9 or 12, wherein,

a threshold of the maximum number of the permitted by the WLAN UE; and after receiving the Access Permission message, establishing a connection

simultaneous connections of the WLAN UE is preset; 55 between the WLAN UE and the Visited Mobile if the WLAN UE is permitted to access more than Communication Network newly selected by the one Visited Mobile Communication Networks simul- WLAN UE, and completes the access of the taneously, the method further comprising: judging WLAN UE and the Visited Mobile Communica-

17

NSN677-1002,

33

EP 1 713 207 Al 34

tion Network newly selected by the WLAN UE.

17. The method according to claim 16, wherein, the method further comprising before Step c3: judging whether the received Disconnection message is generated due to a successful authentication, if so, waiting for the Access Permission message from the Visited Mobile Communication Network newly se-lected by the WLAN UE, and after receiving the Ac-cess Permission message, collecting and sending charging information to the Visited Mobile Commu-nication Network that the WLAN UE has accessed, and disconnecting the connection between the WLAN UE and the Visited Mobile Communication Network that the WLAN UE has accessed; and es-tablishing a connection between the WLAN UE and the Visited Mobile Communication Network newly selected by the WLAN UE, and completing the ac-cess of the WLAN UE and the Visited Mobile Com-munication Network newly selected by the WLAN UE; otherwise, continuing with Step c3.

18. The method according to claim 1, 7, 8, 9, 11 or 12, wherein, when the authentication to the WLAN UE fails, the step of sending the access instruction com-prises:

the Home Network sending a Disconnection message to the WLAN Access Network via the Visited Mobile Communication Network that the WLAN UE has accessed, and sends an Access Rejection message to the WLAN Access Net-work via the Visited Mobile Communication Net-work newly selected by the WLAN UE; the step of completing disconnection and/or ac-cess between the WLAN UE and the corre-sponding Visited Mobile Communication Net-works comprises: the WLAN Access Network disconnecting the connection between the WLAN UE and the Visited Mobile Communica-tion Network that the WLAN UE has accessed according to the received Disconnection mes-sage and forwarding the Access Rejection mes-sage to the WLAN UE according to the received Access Rejection message.

19. The method according to claim 1, 7, 8, 9, 11 or 12, wherein, when the authentication to the WLAN UE fails, the step of sending an access instruction com-prises:

the Home Network sending an Access Rejection message to the WLAN Access Network via the Visited Mobile Communication Network newly selected by the WLAN UE; the step of completing disconnection and/or ac-cess between the WLAN UE and the corre-sponding Visited Mobile Communication Net-

works comprises: the WLAN Access Network forwarding the Access Rejection message to the WLAN UE according to the received Access Re-jection message.

5

20. The method according to claim 1, 7, 8, 9, 11 or 12, wherein, when the authentication to the WLAN UE fails, the step of sending an access instruction com-prises:

10

the Home Network sending an Access Rejection message to the WLAN Access Network via the Visited Mobile Communication Network newly selected by the WLAN UE, and sending a Re-

15 authentication Request to the WLAN Access Network via the Visited Mobile Communication Network that the WLAN UE has accessed; the step of completing disconnection and/or ac-cess between the WLAN UE and the corre-

20 sponding Visited Mobile Communication Net- works comprises: the WLAN Access Network forwarding the Access Rejection message to the WLAN UE according to the received Access Re-jection message, and re-authenticating to the

25 Re-authentication Request from the Visited Mo- bile Communication Network that the WLAN UE has accessed.

21. The method according to claim 1, 7, 8, 9, 11 or 12, 30 wherein, when the authentication to the WLAN UE

fails, the step of sending an access instruction com-prises:

the Home Network sending a Re-authentication 35 Request message to the WLAN Access Network

via the Visited Mobile Communication Network newly selected by the WLAN UE; the step of completing disconnection and/or ac-cess between the WLAN UE and the corre-

40 sponding Visited Mobile Communication Net- works comprises: the WLAN Access Network re-authenticating the Re-authentication Re-quest from the Visited Mobile Communication Network newly selected by the WLAN UE.

45

22. The method according to claim 1, wherein, when re-ceiving the Access Permission message from the newly selected Visited Mobile Communication Net-work, the step of completing disconnection and/or

50 access between the WLAN UE and the corresponding Visited Mobile Communication Networks com-prises: the WLAN Access Network informing the Vis-ited Mobile Communication Network newly selected by the WLAN UE to complete resource distribution

55 and parameter configuration the WLAN Access Net- work establishing a connection between the WLAN UE and the newly selected Visited Mobile Commu-nication Network, and setting the state of the con-

18

NSN677-1002,

35 EP 1 713 207 Al 36

nection as non-activation; and after disconnecting the connection between the WLAN UE and the Visited Mobile Communication Network that the WLAN UE has accessed, activating the established connection between the WLAN UE 5 and the newly selected Visited Mobile Communica-tion Network at once.

23. The method according to claim 1, wherein, the Vis-ited Mobile Communication Network is a middle op- 10

eration network connecting the WLAN UE and its Home Network, or the Home Network of the WLAN UE.

24. The method according to claim 1 or 23, wherein, the 15

Communication Network is a Mobile Communication Network.

25. The method according to claim 1, wherein, the step of authenticating the WLAN UE comprises: 20

an AAA Server in the Home Network authenti-cating to the authentication request from the Vis-ited Mobile Communication Network newly selected by the WLAN UE. 25

26. The method according to claim 13, wherein, the step of sending a piece of advertisement information com-prises: sending a notification to the WLAN UE via one of the existing connections, or sends a notifica- 30

tion to the WLAN UE through the newly established connection.

27. The method according to claim 26, wherein, the no-tification comprises the total number of the current 35

connections, and/or specific selection information of the connections.

40

45

50

55

NSN677-1002,

ry+rMr«rN41,1..0w11, «ww.0,«4•Mf ...I

CG WC:CP

30 PP Visited Network

3GPP Home Network

3GPP AA A Agent

W LAN Access Network erricludirkg or not including

middle network )

Internet/Intranet

Ws/Wc

3GPP AAA Server

CGw/CCF

EP 1 713 207 Al

Fig. 1

20

NSN677-1002,

WLAN Atvess Network I (including or um including

middle network)

EP 1 713 207 Al

F g. 2

21

NSN677-1002,

EP 1 713 207 Al

*IAN LIE. WLAN Access Network 3GPP AAA Proxy 3GPP AAA Server

301 sets up s WLAN access connection

302. user identity request

303. sends user identity (carrying network selection

Information)

304. determines the network selection information in N AI belongs to the present

Mobile Communication Network

305. determines a 3GPP AAA Agent Server of the Mobile Cornmanicatirm Network

selected by the WLAN LIE according to NA!

306. sends the user identity and an Access Authentionion Request

Fig. 3

4

22

NSN677-1002,

EP 1 713 207 Al

WLAN LIE MAN Aceess Network 3GP,P AAA Prw;: 30PP AAA Server

401 sets up a MAN usass iainneetion

user a entity' and an ACt45S

402. user identity request

403. sends user identity (carrying network selection

informaloo)

404, determines, the.oetwork seks:rion informatirm iri"NAI does not Won to the }reseal Mohile

Communication Network

405. sends a network nob tleation silnating

ids the

)

4C6 reselisgs a Mot>ile Communication Network to aer.ess accurding to the

information

407. sCtidS user identity (carrying new network

selection frithrmation

408. deternmes a 36PP AAA Agent Server of the Mobie Contrramication

y th e WE t.l Network selected b k: arcording toNAI

409. se AttatntICV1 Ret:NeW.

Fig. 4

23

NSN677-1002,

EP 1 713 207 Al

The Wl..AN tiE needing, to reselect a network initiates an access authentication procedure to the WLAN Access betwork

502 -v

c WLAN Access Network initiates an authentication procedure to th Home Network of the Wi.,AN tl E via the new Visited Mobile

COIYttntlf on Network

503

The Home Network authernicate the authentioation request ilom the new Visited Mobile Communication Network„ and sends an access instruction to

the KLAN Access Network via different Visited Mobile Communication Networks

WLAN Visited Mobile Network completes disconnection and for access haw= the WEAN UE and corresponding Visited Mobile Communication

Networks according to the received access instruction

Fig. 5

24

NSN677-1002,

V WI-AN Access Network completes disconnection and /or access between

the NYLAN HE and corresponding Visited Mobile Communication Network.s according to received access instruction

Fig. 6

EP 1 713 207 Al

60

WLAN needing to reseloct a network Mitt access inahentication procedure to the WLAN Acces rk

602

The WEAN HE and the WLAN Access Network initiates an access authentication procedure , and sends the information of the Visited Mobile

Cominunitwion Network to ihe WEAN Access Network

6

The WI—AN Access Network sends the authenticatim request to the Home Network of the 'LAN HE via the Visited Mobile Commttmt tton Netowrk

newly selected by the WEAN HE to implement authentication

The Home Network of the %IAN HE determines the autheritica align request belongs to the new selected Visited Mobile Communication

Network

605 V

The Home: Network implements authentication to the authentication request from the new Visited Mobile C`OM311unication Network , and sends an access instruction to the WEAN Access Network via different Visited

Mobile Communication Network s

25

NSN677-1002,

EP 1 713 207 Al

Fig. 7

26

NSN677-1002,

1-27

1-27

Da% °A"TiliPt4t$114 4301i0rW starch k - h. 4.,kiv0 45)

Authorized ollicer

Telephone No. 86- 10-62084554

EP 1 713 207 Al

INTERNATIONAL SEARCH REPORT Inturnational application No.

PCTICS2005100005

A. CLASSIFICATION OF simian' MNITER

1PCli H041,12/28 According to IntiTtrational Parent Clessiiitvtiort (WC) or to both national classification enti

B. FIELDS SEARCHED

Minimum docuraentation searched (class:flea:ion system followed 1,y classification symbols)

1PC7: 1104L12114,12,24,12/28

Doctrine:station searched other than mintrnum dc.icunientation to the extent that such doentriaftits arc included in the fields sestelted

Electronic data base consulted donna the international search (name of data base and, where practicable, search terms used)

WP1, Eponoc, MS ( g • Rigii ft-1R • !IttR, Man.

authentioninc,aufhotiant+.select+ )

C. DOCUMENTS CONSIDERED 70 BE RELEVANT

Category* Citation of document, with indication, where appropriate, of the tekvant passages Relevant to claim No.

A 0%11416241A ( (1111WE—N) 111.7EIT TEC001.0CrY CO LTD) 07.May 2003(07.05.2003) the whole document

CNI429005 A ( (1441S-41) SHANT114A1 NO 2 INST llitINGXING 09...1o12003(0.07.2003) the whole document

C.141.319296A ( (SONY SONY CORP) 24.0et 2001(24.102001) the whole document

US2003169713A1 ( (,tivzrr ) AT & T CORP (1.110144) 1110 F1 )

11.5, 2003(11.09.2003) the whole document

111 Purthe documents are listed in the continuation of Dox C. E Sec patent family annex.

Special categories of cited documents:

document defining the general state of the art which is not considered to be of purticuler relevance

earlier application or patent hut published on or after die international filing date

declaims which sissy throw doubts on priority claim (S) or which is cited to establish the publication date of another citation or other special reason (as specified)

document teferting to an oral disclosure, use, exhibition ar other means

"P" document published prior to the internatikund .filing date but later than the priority date claimed

Date of the actual completion of the international search

13.Apr 2005 (13.04.2005)

Name and mailing address of the ISA/CH The State Intellectual Pror.:etty0Ifitra, die P.R.China ii Xitucherg Rd., timer Bridge. 'fit:khan District, Beijing, China lt10088 Facsimile No. :6-10-6:013451

Poem PCIVISA1210 (second sheet) (April 2005)

laws-document published alter the international filing date or priority dots and not in conflict with the application but cited to understand the principle or theory underlying the invention

"X" document of particular relevance; the claimed invention =no; be considered novel or cannot be considered to involve en inventive step when the document is taker: alone

"Y.. document of particular relevance; the claimed invention cannot he considered to involve ass inventive step when the domanent is combined with one or more other such documents, such combination being obvious to a person skilled in the at t

" LQ document member of the seine patent fismily

27

NSN677-1002,

1nternazional application No.

PCT/CN. 20051000095

INTERNATIONAL SEARCH REPORT Inibrrnation on patent family members

Patent Runily Publication Date Puhneation Date 'Patent Doeurnenta referred in the Ilvort

07.05.2003 nom

09.01.2003 none

.24.10.2001 none

11.09.2003 C.A2413944 Al

CNI:116241A

CN1429005 A

CN1319296 A

US2003169713A1 12.06.2003

EP 1 713 207 Al

Vann PCVISA /210 (patent family annex) (April 2005)

28

NSN677-1002,

1111111111111111

(11) EP 2 007 160 Al

(19) Europaisches Patentamt


Office europeen des brevets

11111111

II

(84) Designated Contracting States: AT BE BG CH CY CZ DE DK EE ES Fl FR GB GR HU IE IS IT LI LT LU LV MC MT NL PL PT RO SE SI SK TR Designated Extension States: AL BA HR MK RS

• Li, Changhong 02140 Espoo (FI)

• Punz, Gottfried Dr. 1080 Wien (AT)

• Wolfner, Gyorgy 1144 Budapest (HU)

(71) Applicant: Nokia Siemens Networks Oy 02610 Espoo (FI)

(72) Inventors: • Forsberg, Dan

00210 Helsinki (FI)

(74) Representative: Bruglachner, Thomas E. Nokia Siemens Network GmbH & Co. KG Patentabteilung Postfach 80 17 60 81541 Miinchen (DE)

208

Parameter [209 mapping -

I 210

211

: 212

(12) EUROPEAN PATENT APPLICATION

(43) Date of publication:

(51) Int CI.: 24.12.2008 Bulletin 2008/52

HO4Q 7/38 (2006- 01)

(21) Application number: 07012010.0

(22) Date of filing: 19.06.2007

(54) Method and device for performing a handover and communication system comprising such device

(57) A method and a device are provided for performing a handover of a first instance from a first network to a second network, the method comprising the steps of (a) a security transfer message is sent to a second in-

Fig.2

stance (HSS, AAA Server); (b) the second instance proc-esses security parameters; and (c) the second instance initiates an authentication based on the security param-eters processed.

201

UE

202

3GPP Access

203

(Ur)Trusted Non-3GPP

Access

204

PDN-GW

205

HSS / MA Server

206a

206b

207

Printed by Jouve, 75001 PARIS (FR)

NSN677-1002,

1 EP 2 007 160 Al

2

Description

[0001] The invention relates to a method and to a de-vice for performing a handover and a communication sys-tem comprising such a device. [0002] According to document 3GPP TS 23.402 V1.0.0 (2007-05), the mobility management procedures specified to handle mobility between 3GPP and non 3GPP accesses shall include mechanisms to minimize the handover latency due to authentication and authori-zation for network access. This applies to User Equip-ments (UEs) either supporting simultaneous radio trans-mission capability or not supporting it. [0003] Fig.1 corresponds to Fig.4.2.1-1 of 3GPP TS 23.402 visualizing a non-roaming architecture for non-3GPP accesses within an Evolved Packet System (EPS). [0004] For a detailed description of Fig.1 reference is made to 3GPP TS 23.402, in particular in combination with the documents as cited therein. [0005] Some of the reference points as shown in Fig. 1 can be summarized as follows:

S2a: It provides the user plane with related control and mobility support between trusted non 3GPP IP access and a Gateway.

S2b: It provides the user plane with related control and mobility support between an Evolved Pack-et Data Gateway (ePDG) and the Gateway.

S2c: It provides the user plane with related control and mobility support between the UE and the Gateway. This reference point is implemented over trusted and/or untrusted non-3GPP Ac-cess and/or 3GPP access.

S5: It provides user plane tunneling and tunnel management between a Serving Gateway and a Packet Data Network Gateway (PDN GW). It is used for Serving GW relocation due to UE mobility and in case the Serving GW needs to connect to a non collocated PDN GW for the required PDN connectivity.

S6a: This interface is defined between a Mobility Management Entity (MME) and a Home Sub-scriber Server (HSS) for authentication and au-thorization.

S6c: It is the reference point between the PDN Gate- way in the HPLMN and a 3GPP AAA server for mobility related authentication, if needed. This reference point may also be used to retrieve and request storage of mobility parameters.

S7: It provides transfer of (QoS) policy and charging rules from a PCRF to Policy and Charging En-forcement Point (PCEF).

SGi: It is the reference point between the PDN Gate- way and the packet data network. Packet data network may be an operator external public or private packet data network or an intra operator

5 packet data network, e.g. for provision of IMS services. This reference point corresponds to Gi and Wi functionalities and supports any 3GPP and non-3GPP access systems.

10 Wa* :

It connects the Untrusted non-3GPP IP Access with the 3GPP AAA Server/Proxy and trans-ports access authentication, authorization and charging-related information in a secure man-ner.

15

Ta":

It connects the Trusted non-3GPP IP Access with the 3GPP AAA Server/Proxy and trans-ports access authentication, authorization, mo-bility parameters and charging-related informa-

20

tion in a secure manner.

Wm": This reference point is located between 3GPP AAA Server/Proxy and an Evolved Packet Data Gateway (ePDG) and is used for AAA signaling

25 (transport of mobility parameters, tunnel authentication and authorization data).

Wn*: This is the reference point between the Untrust- ed Non-3GPP IP Access and the ePDG. Traffic

30 on this interface for a UE initiated tunnel has to be forced towards ePDG.

Wx*:

This reference point is located between 3GPP AAA Server and HSS and is used for transport

35

of authentication data.

[0006] An approach to minimize handover latency for the target network access is to change the architecture as shown in Fig.1 and to provide new interfaces, e.g.,

40 between the Mobility Management Entity (MME) and the AAA-Server. [0007] Such solution, however, disadvantageously leads to a tight interworking structure comprising com-plex interfaces with different security mechanism to cope

45 with. [0008] The problem to be solved is to overcome the disadvantages as stated before and to provide an ap-proach that allows improved handover latency in partic-ular in combination with existing 3GPP architecture.

50 [0009] This problem is solved according to the features of the independent claims. Further embodiments result from the depending claims. [0010] In order to overcome this problem, a method for performing a handover of a first instance from a first

55 network to a second network comprising the following steps:

(a) a security transfer message is sent to a second

2

NSN677-1002,

3

EP 2 007 160 Al 4

instance (HSS, AAA Server); (b) the second instance processes security param-eters, (c) the second instance initiates an authentication based on the security parameters processed.

[0011] Hence, based on the security parameters proc-essed at the second instance, the authentication of the handover can be achieved much faster than without such processing of security parameters. [0012] This allows a significant reduction of handover latency. [0013] In an embodiment, the method further compris-es the steps:

the first instance determines a deterioration of the connection to the first network; the first instance scans for further connections; the first instance requests a handover to the second network.

[0014] Hence, the first instance may recognize, e.g. a deterioration of a signal strength to the first network and hence it may initiate a handover to the second network that has been passively scanned by said first instance. [0015] In another embodiment, the step (b) comprises:

evaluating parameters in order to determine and/or obtain said security parameters; mapping of security parameters; derivation of security parameters; calculation of security parameters.

[0016] Hence, there are several possibilities to proc-ess security parameters. In particular, existing parame-ters (that have been negotiated for the connection with the first network) may be mapped to security parameters that can be utilized for the second network. This is in particular useful if the second network can be trusted. [0017] In a further embodiment, the initiation of the au-thentication comprises at least a transfer of a security context, in particular an EAP success information. [0018] Such information can be used to significantly simplify the handover process and hence to reduce la-tency time associated with such a handover process. [0019] In a next embodiment, the first instance is of the following type:

a user equipment; a mobile terminal; a mobile computer; a mobile network element.

[0020] The first instance may in particular be the user equipment (UE) initiating the handover as described, in particular the authentication based on the processed se-curity parameters. [0021] It is also an embodiment that the first network

and/or the second network is of the following type:

a WiMAX network; an I-WLAN network;

5 a 3GPP access network; in general a trusted non-3GPP access network; in general a non-trusted non-3GPP access network.

[0022] Pursuant to another embodiment, the first net- /0 work and the second network are of different type.

[0023] Hence, different possibilities of connections be-tween (non) 3GPP access networks (trusted or non-trust-ed) can occur. [0024] According to an embodiment, the security

15 transfer message is sent from the first instance, in particular the user equipment. Furthermore, the security transfer message can be sent from a 3GPP access node, in particular if the handover should be executed from a 3GPP access network to a non-3GPP access network.

20 [0025] According to another embodiment, the security transfer message is a security context transfer message, in particular a security context transfer request. [0026] A security context transfer message or request may comprise a target network and an identifier of a user

25 equipment as parameters. [0027] In yet another embodiment, the second in-stance is of the following type:

an authentication, authorization and accounting 30 server (AAA Server);

a home subscriber server (HSS).

[0028] Both such components separately or in combi-nation thereof may be utilized for processing security pa-

35 rameters as described herein. Furthermore, the second instance may then initiate a simplified authentication process and thereinafter the handover with reduced la-tency time. [0029] The problem as stated above is also solved by

40 a device for data processing comprising a processor unit that is arranged and/or equipped such that the method as described herein is executable on said processor unit. [0030] Furthermore, the problem stated above can be solved by a device for initiating a handover of a first in-

45 stance from a first network to a second network comprising a processor unit that is arranged such that the method as described herein can be run on said processor unit. [0031] Moreover, the problem as stated supra is solved by a device for initiating a handover of a first instance

50 from a first network to a second network comprising:

a first unit for receiving a security transfer message; a second unit for processing security parameters; a third unit for initiating an authentication based on

55 the security parameters processed.

[0032] It is to be noted that said first, second and third units may be functional entities that can be realized in

3

NSN677-1002,

5 EP 2 007 160 Al

6

various ways, i.e. as one or several block(s) of hardware and/or as one or several pieces of software running on one or more devices. [0033] According to an embodiment, the device is

an authentication, authorization and accounting server and/or a home subscriber server.

[0034] The problem stated above is also solved by a communication system comprising the device as de-scribed herein. [0035] Embodiments of the invention are shown and illustrated in the following figures:

Fig.2 shows a message sequence chart illustrating a handover from a 3GPP access network to a (non)-trusted non-3GPP access network;

Fig.3 shows a message sequence chart illustrating a handover from a trusted non-3GPP access net-work to a 3GPP access network;

Fig.4 shows a non-roaming architecture for non- 3GPP access with an Evolved Packet System utilizing a path through the architecture for se-curity context transfer from non-3GPP access networks to 3GPP access networks;

Fig.5 shows a non-roaming architecture for non- 3GPP access with an Evolved Packet System utilizing a path through the architecture for se-curity context transfer from 3GPP access net-works to non-3GPP access networks;

Fig.6 shows a device for initiating an authentication, in particular for initiating a handover.

[0036] Fig.2 shows a message sequence chart illus-trating a handover from a 3GPP Access to a trusted non-3GPP Access. This Fig.2 is also applicable for the hando-ver from a 3GPP Access to a non-trusted non-3GPP Ac-cess. [0037] It is to be noted that the term "Access" herein also refers to an access network or to an access node. [0038] Fig.2 comprises a User Equipment UE 201, the 3GPP Access 202, the Trusted Non-3GPP Access 203, a Packet Data Network Gateway PDN-GW 204 and a Home Subscriber Server HSS or an Authentication, Au-thorization and Accounting Server (AAA Server) 205. [0039] Arrows 206a and 206b indicate that the User Equipment UE 201 is connected to the PDN-GW 204 and hence a connection via 3GPP access is established. [0040] Sending a message 207 to the 3GPP Access 202, the User Equipment UE 201 indicates to the 3GPP Access 202 that a signal relating to the established con-nection deteriorates and that the User Equipment UE 201 wants to change the network connection. Hence, by

sending this message 207 the User Equipment UE 201 may trigger a change of network thereby also indicating a destination network to which it wants to be handed over. [0041] Prior to sending such message 207 the User

5 Equipment UE 201 may (permanently) scan for other networks available. Such networks may be of different types, in particular 2G, 3G networks or Wireless LANs or World-wide I nteroperabi lity for Microwave Access (WiMAX) net-works, or any other access networks which are integrated

/o with 3GPP's EPS. [0042] A message 208 is sent from the 3GPP Access 202 to the HSS/ASS Server 205 requesting a security context transfer indicating a target network (TargetNet) and an identification or identifier of the User Equipment

15 UE 201 (UE id). The message 208 can be as follows:

Sec Ctx Transfer (TargetNet, UE id)

[0043] A Mobility Management Entity MME (see Fig. 20 1) transfers the security context to the HSS/AAA Server

205 via the PDN-GW 204. The HSS may in particular insert actual security vectors for the user of the AAA Serv-er. [0044] In a block 209, a parameter mapping, in partic-

25 ular a processing of security parameters is conducted. Such processing may comprise an evaluation of param-eters in order to determine and/or to obtain security pa-rameters, a mapping of (security) parameters, a deriva-tion of security parameters or a calculation of security

30 parameters. [0045] The HSS/AAA Server 205 can use the vectors and/or key material provided for a fast re-authentication (e.g., fast Extensible Authentication Protocol for UMTS Authentication and Key Agreement (EAP-AKA) re-au-

35 thentication) or no authentication (e.g., utilizing key material as provided, skipping an EAP authentication). [0046] It is to be noted that such (re-)authentication can be network dependent and in particular separately predefined according to distinct networks.

40 [0047] A message 210 is sent from the HSS/AAA Serv- er 205 to the trusted non-3GPP Access 202. The mes-sage may be as follows:

Sec Ctx Transfer (UE id, derived keys) 45

thereby indicating an identification of a User Equipment (here: the User Equipment UE 201) and derived keys as provided by the parameter mapping 209. [0048] The derived keys may in particular be based on

50 security vectors, e.g., a cipher key (CK), an integrity key (IK) or a key used in an LTE (KASME). Without (re)-au-thentication, security parameters may be sent to the tar-get trusted non-3GPP Access 203 (if required) by an equivalent of an EAP-AKA success message including

55 the key material. [0049] An arrow 211 indicates that the User Equipment UE 201 detaches from the 3GPP Access 202. [0050] An arrow 212 indicates that the User Equipment

4

NSN677-1002,

7 EP 2 007 160 Al

8

UE 201 attaches to the trusted non-3GPP Access (net-work) using the (same) security parameters as provided to the target trusted non-3GPP access network. [0051] It is to be noted that no explicit synchronization is required, i.e. it is assumed that the detachment from 3GPP access and attachment to trusted non-3GPP ac-cess has in total a higher latency than the security context transfer. [0052] Fig.3 shows a message sequence chart illus-tration of a handover from a trusted non-3GPP Access to a 3GPP Access, in particular an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and/or a Release 8 3GPP Access network. [0053] Fig.3 comprises a User Equipment UE 301, the 3GPP Access 302, the Trusted Non-3GPP Access 303, a Packet Data Network Gateway PDN-GW 304 and a Home Subscriber Server HSS or an Authentication, Au-thorization and Accounting Server (AAA Server) 305. [0054] Arrows 306a and 306b indicate that the User Equipment UE 301 is connected to the PDN-GW 304 and hence a connection with the trusted non-3GPP access is established. [0055] In a message 307, the User Equipment UE 301 sends a Sec Ctx Transfer Request (Target Network Id) i.e., a security context transfer request message com-prising a target network identification, to the HSS/AAA Server 305. Such message 307 can be in particular sent via non-3GPP access NW and subsequently via Ta* and/or Wa* reference points (see Fig.1); in this case a link specific message from the User Equipment UE 301 to the authenticator entity in the non-3GPP access net-work, e.g., an EAP message, may be used. [0056] In a block 308 a parameter mapping, in partic-ular a processing of security parameters is conducted. Such processing may comprise an evaluation of param-eters in order to determine and/or to obtain security pa-rameters, a mapping of (security) parameters, a deriva-tion of security parameters or a calculation of security parameters. [0057] The HSS/AAA Server 305 may obtain 3GPP security parameters based on an authentication vector that is currently used in the Trusted Non-3GPP Access network 303. [0058] It is to be noted that the HSS/AAA Server 305 may be aware of the authentication vectorthat is currently being used - in particular if I-WLAN is utilized. [0059] A message 309 is sent from the HSS/AAA Serv-er 305 to the 3GPP Access 302, in particular to an MME, which is the authenticator in 3GPP access, as follows:

Sec Ctx Transfer (UE id, derived keys) thereby indicating an identification of a User Equip-ment (here: the User Equipment UE 301) and de-rived keys as provided by the parameter mapping 308. The MME is determined before by the HSS/AAA Server 306.

[0060] Based on the current authentication vector, the HSS may generate key material, e.g. a key used in an LTE (KASME) to be used in the Mobility Management En-tity (MME). If such approach is not admissible, the au-

5 thentication will have to be executed. [0061] An arrow 310 indicates that the User Equipment UE 301 attaches to the 3GPP Access (network) using the security parameters as provided. [0062] The MME and the User Equipment UE 301 may

10 use the keys for further appliance in an LTE environment (e.g., AS and NAS specific keys may be derived). Fig.4 shows a non-roaming architecture for non-3GPP access with an Evolved Packet System utilizing a path 501 through the architecture for security context transfer

15 from non-3GPP access networks to 3GPP access net-works; [0063] Fig.5 shows a non-roaming architecture for non-3GPP access with an Evolved Packet System utiliz-ing a path 601 through the architecture for security con-

20 text transfer from 3GPP access networks to non-3GPP access networks; [0064] Fig.6 shows a device for initiating an authenti-cation, in particular within the process of the handover. Such a device 700 may in particular be an authentication,

25 authorization and accounting server (AAA Server) and/or a home subscriber server (HSS). [0065] The device 700 comprises a First Unit 701 for receiving a security transfer message 704 and a Second Unit 702 for processing security parameters. The device

30 700 further comprises a Third Unit 703 for initiating an authentication 705 based on the security parameters processed. Such authentication 705 may occur during execution of a handover thereby utilizing the security pa-rameters processed and reducing the processing time

35 required for the handover.

Abbreviations (in alphabetical order):

[0066] 40

AAA Authentication, Authorization and Ac- counting

EAP Extensible Authentication Protocol EAP-AKA EAP for UMTS Authentication and Key

45 Agreement ePDG Evolved Packet Data Gateway EPS Evolved Packet System E-UTRAN Evolved UTRAN GW Gateway

50 HPLMN Home Public Land Mobile Network HSS Home Subscriber Server I-WLAN Interworking WLAN MME Mobility Management Entity PCEF Policy and Charging Enforcement Func-

55 tion PCRF Policy Control and Charging Rules Func-

tion PDN Packet Data Network

5

NSN677-1002,

9

EP 2 007 160 Al 10

UE UTRAN

WiMAX

WLAN

Claims

User Equipment Universal Terrestrial Radio Access Net-work Worldwide Interoperability for Microwave Access Wireless Area Network

- a WiMAX network; - an I-WLAN network; - a 3GPP access network; - in general a trusted non-3GPP access network;

5 - in general a non-trusted non-3GPP access network.

7. The method according to any of the preceding claims, wherein the security transfer message is sent

10 from the first instance.

8. The method according to any of the preceding claims, wherein the security transfer message is sent from a 3GPP access node.

15

9. The method according to any of the preceding claims, wherein the security transfer message is a security context transfer message, in particular a se-curity context transfer request.

20

10. The method according to any of the preceding claims, wherein the second instance is of the follow-ing type:

25 - an authentication, authorization and accounting server; - a home subscriber server.

11. The method according to any of the preceding 30 claims, wherein the first network and the second net-

work are of different type.

12. A device for data processing comprising a processor unit that is arranged such that the method according

35 of any of the preceding claims is executable on said processor unit.

13. A device for initiating a handover of a first instance from a first network to a second network comprising

40 a processor unit that is arranged such that the method according to any of the claims 1 to 11 can be run on said processor unit.

14. A device for initiating a handover of a first instance 45 from a first network to a second network comprising:

- a first unit for receiving a security transfer mes-sage; - a second unit for processing security parame-

50 ters; - a third unit for initiating an authentication based on the security parameters processed.

15. The device according to any of claims 12 to 14, said 55 device is

- an authentication, authorization and account-ing server and/or

1. A method for performing a handover of a first in-stance from a first network to a second network com-prising the following steps:

(a) a security transfer message is sent to a sec-ond instance (HSS, AAA Server); (b) the second instance processes security pa-rameters; (c) the second instance initiates an authentica-tion based on the security parameters proc-essed.

2. The method according to claim 1, comprising the following steps prior to step (a):

- the first instance determines a deterioration of the connection to the first network; - the first instance scans for further connections; - the first instance requests a handover to the second network.

3. The method according to any of the preceding claims, wherein the step (b) comprises:

- evaluating parameters in order to determine and/or obtain said security parameters; - mapping of security parameters; - derivation of security parameters; - calculation of security parameters.

4. The method according to any of the preceding claims, wherein the initiation of the authentication comprises at least a transfer of a security context, in particular an EAP success information.

5. The method according to any of the preceding claims, wherein the first instance is of the following type:

- a user equipment; - a mobile terminal; - a mobile computer; - a mobile network element.

6. The method according to any of the preceding claims, wherein the first network and/or the second network is of the following type:

6

NSN677-1002,

11 EP 2 007 160 Al 12

- a home subscriber server.

16. Communication system comprising the device ac-

cording to any of claims 12 to 15. 5

10

15

20

25

30

35

40

45

50

55

NSN677-1002,

\Wn*

S2a S2c

HPLMN

r

HSS

Wx*

C2G/3G

SGSN

S I -MME

E-UTRAN

S3

S10

S I -U

II

Serving

Gateway

SGi

S2b

ePDG

Rx+

Operator's IP Services

(e.g. IMS, PSS

etc.)

S6c

Wm*

3GPP AAA Server

PDN Gateway

S7

S5

S4 S6a

MME

PCRF

Tan UE

Untrusted Non-3GPP IP

Access

Trusted Non-3GPP IP

Access

Non-3GPP

Network Trusted/Unt ted* Non-3GP P Access

or ' P Access Wa*

Fig.1

IN 0

91.

LO

O Z

d3

* Untrusted non-3GPP access requires ePDG in the data

NSN677-1002,

206a 206b

207 >

208

Fig.2 201

UE

I I

202

3GPP Access

203

(Uri)Trusted Non-3GPP

Access 1

204

PDN-GW

>

205

HSS / AM Server

1209

>1 1

IN 0

91.

LO

O Z

d3

Parameter mapping

210 <

NSN677-1002,

Fig.3 301

302

303

304

305

1 I 307

UE

. , < 1

1 3GPP Access

(Ur)Trusted Non-3GPP

Access

i

PDN-GW

1 HSS /

AAA Server

Parameter mapping -

I I

306a

306b

1 I I

I

I

I

I

I I I I I

I I

I I I I I I I I

309

1 1 1 1 1 1

X308

IN 0

91.

LOO

Z d

3

NSN677-1002,

HPLMN

Trusted Non-3GPP IP

Access

r

Was

Non-3GPP

Networks/ Trusted/Unt

Non-3GP Or

UE

II

ePDG 3GPP AAA Server

HSS

Wx*

SGi

S2b

Rx+


(e.g. IMS, PSS

etc.)

S6c

7

S10 Serving

Gateway

S5

PDN Gateway

S I-U 501

Wm*

S2a S2c

S3

S4 S6a 2G/3G

SGSN

SI-MME

E-UTRAN

MME

PCRF

Fig.4

IN 0

91.

LO

O Z

d3


NSN677-1002,

Non-3GPP

Network sled*

P Access P Access

Trusted/Un

Non-3GP

or

Wn*

r

ETrusted Non-3GPP IP

Access

Untrusted Non-3GPP IP

601/

601

Wa*

Ta*

S3 Rx+

HSS

Wx*

S4 S6a

rving

S5 S I -U S6c

S2b

II

601

S2c

Wm*

3GPP AAA

Server

S7

SI 0

S2a ePDG

SGi

PDN way


(e.g. IMS, PSS

etc.)

PCRF

MME

2G/3G

SGSN

SI-MME

E-UTRAN

HPLMN

UE

Fig.5

IN 0

91.

LO

O Z

d3


NSN677-1002,

Initiate Authentication 705

First Unit 701

Second Unit 702

Third Unit 703

Fig.6

700

Security Transfer Message 704

IN 0

91.

LO

O Z

d3

NSN677-1002,

1

2 0

EP 2 007 160 Al

European Patent

Office EUROPEAN SEARCH REPORT

Application Number

EP 07 01 2010


Category Citation of document with indication, where appropriate, of relevant passages

Relevant to claim

CLASSIFICATION OF THE APPLICATION (IPC)

X EP 1 662 726 A (SAMSUNG ELECTRONICS CO LTD 1,14 INV. [KR]) 31 May 2006 (2006-05-31) H04Q7/38

Y * paragraphs [0001], [0030] * 2-13,15, 16

* paragraph [0037] - paragraph [0040] * * paragraph [0050] - paragraph [0052] * * figures 2,4 *

X WO 2007/049936 A (SAMSUNG ELECTRONICS CO 1,14 LTD [KR]; RAJAVELSAMY R [IN]; JEEDIGUNTA VENKAT) 3 May 2007 (2007-05-03)

Y * paragraphs [0001], [0009] - paragraph 2-13,15, [0013] * 16 * paragraph [0038] - paragraph [0048] * * paragraph [0058] - paragraph [0066] * * paragraph [0112] - paragraph [0119] * * figures 2,3,6 *

X EP 1 311 136 A (LUCENT TECHNOLOGIES INC 1,14 [US]) 14 May 2003 (2003-05-14) * abstract * TECHNICAL FIELDS

* paragraph [0009] - paragraph [0010] * SEARCHED (IPC)

* paragraph [0023] - paragraph [0024] * H040 * figure 1 * HO4L

Y WO 2005/027559 A (DOCOMO COMM LAB EUROP 1,14 GMBH [DE] ; WANG HU [DE]) 24 March 2005 (2005-03-24) * page 3, line 21 - page 4, line 11 * * page 5, line 1 - line 20 * * page 12, line 1 - line 11 * * page 12, line 20 - page 14, line 23 * * page 15, line 20 - line 30 * * figures 4,5 *

-/--

The present search report has been drawn up for all claims

Plane of search Date of completion of the search Fxaminel

Munich 19 November 2007 Rosenauer, Hubert

CATEGORY OF CITED DOCUMENTS T theory or principle underlying the invention E : earlier patent document, but published on, or

X : particularly relevant if taken alone after the filing date Y : particularly relevant if combined with another D : document cited in the application

document of the same category L : document cited for other reasons A : technological background O: non-written disclosure & : member of the same patent family, corresponding P : intermediate document document

14

NSN677-1002,

0

O 0

EP 2 007 160 Al


EUROPEAN SEARCH REPORT Application Number

EP 07 01 2010


Category Citation of document with indication, where appropriate, of relevant passages

Relevant to claim

CLASSIFICATION OF THE APPLICATION (IPC)

Y US 2004/218605 Al (GUSTAFSSON EVA [SE] ET AL) 4 November 2004 (2004-11-04) * paragraph [0052] * * paragraph [0056] - paragraph [0070] *

* figures 3-5 *

1,14

TECHNICAL FIELDS SEARCHED (IPC)

The present search report has been drawn up for all claims

Place of search

Munich

Date of completion of the search

19 November 2007

Examiner

Rosenauer, Hubert

CATEGORY OF CITED DOCUMENTS T : theory or principle underlying the invention E : earlier patent document, but published on, or

X : particularly relevant if taken alone after the filing date Y : particularly relevant it combined with another D : document cited in the application

document of the same category L : document cited for other reasons A : technological background 0 : non-written disclosure & : member of the same patent family, corresponding P : intermediate document document

15

NSN677-1002,

if>

0_ OC OC O

EP 2 007 160 Al

ANNEX TO THE EUROPEAN SEARCH REPORT ON EUROPEAN PATENT APPLICATION NO. EP 07 01 2010

This annex lists the patent family members relating to the patent documents cited in the above-mentioned European search report. The members are as contained in the European Patent Office EDP file on The European Patent Office is in no way liable for these particulars which are merely given for the purpose of information.

19-11-2007

Patent document cited in search report

Publication date

Patent family me ITIber(s)

Publication date

EP 1662726 A 31-05-2006 KR 20060059064 A 01-06-2006 US 2006146803 Al 06-07-2006

WO 2007049936 A 03-05-2007 KR 20070046012 A 02-05-2007

EP 1311136 A 14-05-2003 NONE

WO 2005027559 A 24-03-2005 AU 2003258718 Al 06-04-2005 AU 2003294788 Al 06-04-2005 WO 2005027557 Al 24-03-2005 JP 2007515827 T 14-06-2007

US 2004218605 Al 04-11-2004 NONE

0 en For more details about this annex : see Official Journal of the European Patent Office, No. 12/82

16

NSN677-1002,

12 I

320 300

3GPP Network

230

Huv244.

WIG

Network

Packet Data

SGSN

220

Mobile Station

Mobile Station

210

UTRAN

Non-3GPP Network In

O

(12) INTERNATIONAL APPLICATION PUBLISHED UNDER THE PATENT COOPERATION TREATY (PCT)

(19) World Intellectual Property Organization International Bureau

(43) International Publication Date 1 March 2007 (01.03.2007)

III III 11111111 11101 11111 11111 1110 II II 111111 1 1111 11111 111111111111111E1111111111111 1111 1111

(10) International Publication Number WO 2007/024115 Al PCT

(51) International Patent Classification: HO4L 12/46 (2006.01)

(21) International Application Number: PCT/KR2006/003349

(22) International Filing Date: 24 August 2006 (24.08.2006)

(25) Filing Language: Korean

(26) Publication Language: English

(30) Priority Data: 10-2005-0078824 26 August 2005 (26.08.2005) KR 10-2006-0080075 23 August 2006 (23.08.2006) KR

(71) Applicant (for all designated States except US)• ELEC-TRONICS AND TELECOMMUNICATIONS RE-SEARCH INSTITUTE [KR/KR]; 161, Gaj eong-dong, Yuseong-gu, Daejeon 305-350 (KR).

(72) Inventors; and (75) Inventors/Applicants (for US only): CHEON,

Kyung-Yul [KR/KR]; 161, Gajeong-dong, Yuseong-gu, Daejeon 305-350 (KR). RO, Kwang-Hyun [KR/KR]; 161, Gajeong-dong, Yuseong-gu, Dacjeon 305-350 (KR). SHIN, Jae-Wook [KR/KR]; 161, Gajeong-dong, Yuseong-gu, Daejeon 305-350 (KR). KWON, Hye-Yeon [KR/KR] ; 161, Gajeong-dong, Yuseong-gu, Daejeon 305-350 (KR). SHIN, Hyung-Cheol [KR/KR]; 161, Gajeong-dong, Yuseong-gu, Daejeon 305-350 (KR). JUNG, Kwang-Ryul [KR/KR]; 161, Gaj eong-dong, Yuseong-gu, Daejeon 305-350 (KR). HWANG, You-Sun

[KR/KR]; 161, Gajeong-dong, Yuseong-gu, Dae-jeon 305-350 (KR). PARK, Ae-Soon [KR/KR]; 161, Gajeong-dong, Yuseong-gu, Daejeon 305-350 (KR).

(74) Agent: YOU ME PATENT & LAW FIRM; Seolim bldg., 649-10, Yoksam-dong, Kangnam-ku, Seoul 135-080 (KR).

(81) Designated States (unless otherwise indicated, for every kind of national protection available): AE, AG, AL, AM, Al, AU, AZ, BA, BB, BG, BR, BW, BY, BZ, CA, CH, CN, CO, CR, CU, CZ, DE, DK, DM, DZ, EC, EE, EG, ES, FT, GB, GD, GE, GH, GM, I-IN, I-1R, HU, ID, IL, IN, IS, JP, KE, KG, KM, KN, KP, KZ, LA, LC, LK, LR, LS, LT, LU, LV, LY, MA, MD, MG, MK, MN, MW, MX, MY, MZ, NA, NG, NI, NO, NZ, OM, PG, PH, PL, PT, RO, RS, RU, SC, SD, SE, SG, SK, SL, SM, SV, SY, TJ, TM, TN, TR, TT, TZ, UA, UG, US, UZ, VC, VN, ZA, ZM, ZW.

(84) Designated States (unless otherwise indicated, for every kind of regional protection available): ARIPO (BW, GH, GM, KE, LS, MW, MZ, NA, SD, SL, SZ, TZ, UG, ZM, ZW), Eurasian (AM, AZ, BY, KG, KZ, MD, RU, TJ, TM), European (AT, BE, BG, CH, CY, CZ, DE, DK, EE, ES, FL FR, GB, GR, HU, IE, IS, IT, LT, LU, LV, MC, NL, PL, PT, RO, SE, SI, SK, TR), OAPI (BF, BJ, CF, CG, CI, CM, GA, GN, GQ, GW, ML, MR, NE, SN, TD, TG).

Published: with international search report

For two-letter codes and other abbreviations, refer to the "Guid-ance Notes on Codes and Abbreviations" appearing at the begin-ning of each regular issue of the PCT Gazette.

(54) Title: AN APPARATUS AND A METHOD FOR SERVICE CONTINUITY BETWEEN UMTS NETWORK AND WLAN NETWORK

200

420

100

(57) Abstract: Service continuity is provided between a 3GPP network and a non-3GPP network. When a mobile station having accepted service in the 3GPP network moves to the non-3GPP network or returns from the non-3GPP network to the 3GPP network, an interworking gateway is interworked with a GGSN through a universal tunnel using a packet data network, and accordingly a mobile subscriber may accept seamless service.

NSN677-1002,

WO 2007/024115

PCT/KR2006/003349

AN APPARATUS AND A METHOD FOR SERVICE CONTINUITY

BETWEEN UMTS NETWORK AND WLAN NETWORK

5 BACKGROUND OF THE INVENTION

(a) Field of the Invention

The present invention relates to a service continuity apparatus and

method for providing a seamless service between a universal mobile

communication system network and wireless local area network. More

10 particularly, the present invention relates to a service continuity apparatus

and method for performing a handover without breaking a service between

a 3GPP network and non-3GPP network.

(b) Description of the Related Art

A universal mobile telecommunication system (hereinafter, referred

15 to as 'UMTS') presently includes a third generation mobile

telecommunication system developed by a framework known as an

international mobile communication standard-2000 (IMT-2000).

The third generation mobile communication system had been

designed to provide multimedia communication. It has a high data speed

20 so that it can increase public and private network information access and

service and provide flexible telecommunication. Such a third generation

mobile communication system has been studied regarding standard

technologies by a 3rd Generation Partnership Project (3GPP) by

1

NSN677-1002,

WO 2007/024115 PCT/KR2006/003349

standardization institutions or enterprises of many countries. Hereinafter,

a system or network provided by the 3GPP, that is, the standardization

institutions, is referred to as "3GPP system" or "3GPP network". In

addition, a system (e.g., wireless local area network) or network not

5 provided by the 3GPP, that is, the standardization institutions, for example,

is referred to as "non-3GPP system" or "non-3GPP network".

The UMTS has a drawback in that a spectrum is largely consumed

and data rate is low in comparison with the wireless local area network

(hereinafter, referred to as 'WLAN'). Accordingly, a system and method

10 for utilizing WLAN bands is required so as to supplement a bandwidth of

UMTS and improve efficiency thereof.

A conventional release 6-based 3GPP UMTS has provided an

inter-network loaming structure for utilizing the WLAN in the 3GPP UMTS

network and non-3GPP network. That is, it is described for a 3GPP

15 subscriber to accept services such as 3GPP network authentication,

authorization, and charging, and then to accept service of the 3GPP when

the 3GPP subscriber accesses to the WLAN. Accordingly, a mobile

station may accept a packet service though the 3GPP network even when

it accesses the WLAN.

20 However, according to such a conventional structure, when the

mobile station having accessed the 3GPP network moves in the WLAN

while accepting a service or otherwise, the mobile station cannot use a

previously-used address in a moved network. That is, since the mobile

2

NSN677-1002,

WO 2007/024115 PCT/KR2006/003349

station must accept a new address from a gateway GPRS support node

(GGSN) or a packet data gateway (PDG) of a newly moved network when

it moves between networks, the mobile station cannot accept seamless

service.

5 The above information disclosed in this Background section is only

for enhancement of understanding of the background of the invention and

therefore it may contain information that does not form the prior art that is

already known in this country to a person of ordinary skill in the art.

SUMMARY OF THE INVENTION

10 The present invention has been made in an effort to provide a

service continuity apparatus and method having advantages of supporting

a seamless service when a mobile station moves between a well known

3GPP UMTS network and a non-3GPP network.

An exemplary embodiment of the present invention provides a

15 service continuity apparatus for supporting service continuity between a

universal mobile communication system network and a wireless local area

network. The service continuity apparatus includes a first node for

transmitting a data packet to a mobile station in the universal mobile

communication system network; a second node for performing a wireless

20 gate function between the first node and the packet data network and

allocating a first address to the mobile station through the first node so as

to communicate data with the packet data network; and an interworking

gateway for generating tunneling with the second network through the

3

NSN677-1002,

WO 2007/024115 PCT/KR2006/003349

packet data network and providing a seamless service to the mobile station

using the first address when the mobile station moves from the universal

mobile communication system network to the wireless local area network.

At this time, the interworking gateway generates tunneling with the

5 second node through the packet data network and provides a seamless

service to the mobile station using the first address when the mobile station

returns from the wireless local area network to the universal mobile

communication system network.

Another embodiment of the present invention provides a service

10 continuity method for supporting service continuity between a universal

mobile communication system network and a wireless local area network.

The service continuity includes (a) a first node performing a wireless gate

function of an inter-packet data network by allocating a first address for

communicating data with the packet data network to the mobile station

15 accessed to the universal mobile communication system network and

recoding the allocated first address on an authentication server;

(b) an interworking gateway receiving a tunnel establishment

request message from the mobile station moved from the universal mobile

communication system network to the wireless local area network;

20 (c) the interworking gateway performing user authentication and

authorization and receiving the recoded first address from the

authentication server by being interworked with the authentication server;

(d) the interworking gateway generating tunneling with the first

4

NSN677-1002,

WO 2007/024115 PCT/KR2006/003349

node through the packet data network; and

(e) the interworking gateway transmitting a tunnel establishment

response message including the received first address to the mobile

station.

5 In addition, yet another embodiment of the present invention

provides (a) a first node for transmitting a packet in a service area of the

universal mobile communication system network receiving a PDP context

activation request message from a mobile station, the mobile station

having returned from the wireless local area network to the universal

10 mobile communication system network;

(b) the first node transmitting a PDP context generation request

message to a second node, the second node for performing a wireless

gate to a node packet data network;

(c) the second node receiving a PDP address from an

15 authentication server the PDP address being previously allocated to the

mobile station accessed to the universal mobile communication system

network so as to perform a data communication with the packet data

network;

(d) the second node generating tunneling to an interworking

20 gateway through the packet data network; and

(e) the first node transmitting a PDP context activation response

message to the mobile station using the received PDP address.

5

NSN677-1002,

WO 2007/024115 PCT/KR2006/003349


FIG. 1 is a schematic diagram of an interworking system between a

3GPP network and a non-3GPP network for supporting a seamless service

according to an exemplary embodiment of the present invention.

5 FIG. 2 is a flowchart for showing how a mobile station moves from a

3GPP network to a non-3GPP network according to an exemplary

embodiment of the present invention.

FIG. 3 is a flowchart for showing how a mobile station moves from a

non-3GPP network to a 3GPP network according to an exemplary

10 embodiment of the present invention.



according to another exemplary embodiment of the present invention.

DETAILED DESCRIPTION OF THE EMBODIMENTS

15 In the following detailed description, only certain exemplary

embodiments of the present invention have been shown and described,

simply by way of illustration. As those skilled in the art would realize, the

described embodiments may be modified in various different ways, all

without departing from the spirit or scope of the present invention.

20 Accordingly, the drawings and description are to be regarded as illustrative

in nature and not restrictive. Like reference numerals designate like

elements throughout the specification. When it is described that an

element is coupled to another element, the element may be directly

6

NSN677-1002,

WO 2007/024115 PCT/KR2006/003349

coupled to the other element or coupled to the other element through a

third element.

In addition, composition elements shown in the drawings may be

implemented by hardware, software, or a combination thereof, and may be

5 realized by at least one programmed universal device including a

processor, a memory, and input/output interfaces.

Now a service continuity apparatus and method for supporting

service continuity between a 3GPP network and a non-3GPP network

according to an exemplary embodiment of the present invention will be

10 described.



according to an exemplary embodiment of the present invention. The

system shown in FIG. 1 is one example. Accordingly, respective

15

elements known to a person of ordinary skill in the art may be described

briefly to impart understanding of an exemplary embodiment of the present

invention.

In FIG. 1, a mobile station 100 is defined as a general mobile

terminal having a dual mode of 3GPP and non-3GPP. A 3GPP network

20 200 is defined as a general universal mobile communication system

(UMTS) network, and a non-3GPP network 300 is defined as all the

wireless local area networks excluding the 3GPP network. For example,

the non-3GPP network 300 includes the IEEE 602.16, Hyper LAN, Wibro,

7

NSN677-1002,

WO 2007/024115 PCT/KR2006/003349

and Personal Area Network (PAN).

As shown in FIG. 1, the 3GPP network 200 includes a UTRAN 210,

a SGSN 220, a GGSN 230, an HLR/AAA 240, and an interworking gateway

250.

5 The URRAN UMTS (Terrestrial Radio Access Network) 210 is a

wireless access network for performing a wireless-related function, and

includes a node B (not shown) and a wireless network controller (RNC) (not

shown).

The SGSN (Serving GPRS Support Node: 220) is a node for

10 performing a data packet transmission to the mobile station in a service

area, and has packet routing and transmission, mobility management, local

link management functions. In addition, the SGSN 220 includes a location

register for storing user location information (cell, visitor location register,

and the like) and user profile, in which the user is registered in the SGSN.

15 The GGSN (Gateway GPRS Support Node: 230) performs a

wireless gateway function between the SGSN 220 and the packet data

network (PDN). That is, the GGSN 230 transmits all the data to the

packet data network, in which the data is transmitted/received in the packet

data network. At this time, the GGSN 230 allocates a Packet Data

20 Protocol (PDP) address through the SGSN 220 to the mobile station 100

such that the mobile station 100 may perform data communication with the

packet data network. An HLR/AAA 240 stores the PDP address allocated

by the GGSN 230.

8

NSN677-1002,

WO 2007/024115 PCT/KR2006/003349

The HLR/AAA 240 stores a home location of the mobile station 100

and the PDP address allocated by the GGSN 230, and performs an

authentication to the mobile station.

An interworking gateway (hereinafter referred to as 'IWG') 250 is for

5 performing a seamless service between the 3GPP network and the

non-3GPP network, and is connected to the GGSN 230 through a universal

tunnel 420 passing through the packet data network 400.

According to an exemplary embodiment of the present invention,

when the mobile station 100 moves from the 3GPP network to the

10 non-3GPP network, GGSN 230, the IWG 250 receives the PDP address

previously allocated by the GGSN 230 from the HLR/AAA 240 and forms a

tunnel 320 to the mobile station 100 by providing the received PDP

address to the mobile station 100.

In FIG. 1, the packet data network 400 may be defined as a

15 packet-based network including both of the Internet and intranet, and the

GGSN 230 and IWG 250 according to an exemplary embodiment of the

present invention respectively includes interfaces 11 and 12 for interworking

with the packet data network 400.

Now, how to interwork a service between the 3GPPnetwork and the

20 non-3GPP network is described with reference to FIG. 2 and FIG. 3.

FIG. 2 is a flowchart for showing how a mobile station moves from a

3GPP network to a non-3GPP network according to an exemplary


9

NSN677-1002,

WO 2007/024115 PCT/KR2006/003349

First, when the mobile station 100 of the 3GPP subscriber accesses

the 3GPP network 200, the GGSN 230 allocates a PDP address to the

mobile station (S10). At this time, the PDP address allocated by the

GGSN 230 is stored at the HLR/AAA 240.

5 When the mobile station 100 accesses the non-3GPP network 300,

the non-3GPP network 300 allocates a local address to the mobile station

100, in which the local address is for communicating data with the

non-3GPP network 300 (S20).

The mobile station 100 then transmits a tunnel establishment

10 request message to the IWG 250 (S30). When the IWG 250 receives the

tunnel establishment request message from the mobile station 100, it

performs user authentication and authorization by being interworked with

the HLR/AAA 240 (S40) and then receives the previously-allocated PDP

address from the HLR/AAA 240.

15 When the IWG 250 receives the PDP address, it cooperates with

the GGSN 230 and establishes the tunnel 420 passing through the packet

data network 400 (S50). At this time, so as to establish a

security-ensured tunnel, it obtains tunnel establishment information from

the HLR/AAA 240.

20 After the IWG 250 has established a tunnel by cooperating with the

GGSN 230, the IWG 250 transmits a tunnel establishment response

message including the PDP address obtained from the HLR/AAA 240 to

the mobile station 100, and accordingly generates a tunnel 320 to the

10

NSN677-1002,

WO 2007/024115 PCT/KR2006/003349

mobile station 100.

The GGSN 230 performs mobile station-link packet buffering as

soon as it receives the tunnel establishment request message from the

IWG 250, and transmits the buffered packet to the mobile station when the

5 tunnel establishment is finished, and "the mobile station-link packet" is

referred to as a packet transmitted to the mobile station herein.

The mobile station 100 may accept a seamless service with respect

to all packet data transmitted to the 3GPP network using the generated

tunnel 320 by means of the GGSN 230 and IWG 250.

10 In addition, the GGSN 230 may recycle radio resources by

canceling a previously formed GRPS session using the same. That is, the

GGSN 230 transmits the PDP context delete request message to the

SGSN 220 so as to cancel the GRPS session (S70) and the SGSN 220

transmits the PDP context delete response message to the GGSN 230

15 (S80), and accordingly the given GRPS session is cancelled and the radio

resource is recycled

At this time, if the PDP context delete request message is not used,

the SGSN 220 may cancel the given session by operating a timer (Mobile

Reachable Timer) after a predetermined time.

20 FIG. 3 is a flowchart for showing how a mobile station moves from a

non-3GPP network to a 3GPP network according to an exemplary


As described with reference to FIG. 2, when the mobile station 100

11

NSN677-1002,

WO 2007/024115 PCT/KR2006/003349

subscribed in the 3GPP network accesses the non-3GPP network 300, the

mobile station 100 receives a local address allocated by the non-3GPP

network 300 and the PDP address previously allocated from the IWG 250.

When the mobile station 100 returns to the 3GPP network, the

5 mobile station 100 starts an access to the SGSG 220 (S110) and the

mobile station 100 transmits a PDP context activation request message to

the SGSN 220 (S120).

The SGSN 220 transmits a PDP context generation request

message to the GGSN 230 (S130), and the GGSN 230 performs user

10 authentication and authorization by being interworked with the HLR/AAA

240 and then receives the PDP address previously allocated from the

HLR/AAA 240 (S140).

When the GGSN 230 has received the PDP address, it establishes

a tunnel 420 passing through the packet data network 400 by cooperating

15 with the IWG (S150). So as to establish a security-ensured tunnel, the

GGSN 230 obtains the tunnel establishment information from the HLR/AAA

240.

The GGSN 230 then transmits a PDP context generation response

message including the PDP address to the SGSN 220 (S160) and the

20 SSGN 220 transmits a PDP context activation response message including

the PDP address to the mobile station 100 (S170).

Though these steps, the mobile station 100 may accept a seamless

service even if it moves from the non-3GPP network 200 to the 3GPP

12

NSN677-1002,

WO 2007/024115 PCT/KR2006/003349

network.

According to the first exemplary embodiment of the present

invention as shown in FIG. 1, the IWG 250 is disposed in a 3GPP home

network. However, the IWG 250 may be disposed in a 3GPP visitor

5 network 500 as shown in FIG. 4. Elements in Fig. 4 that are the same or

similar to those illustrated in FIG. 1 have the same or similar reference

numerals. These elements may not be described for brevity of

description.

As shown in FIG. 4, the 3GPP visitor network 500 additionally

10 includes an AAA proxy 540 when the IWG 250 is disposed in the 3GPP

visitor network 500. The AAA proxy 540 performs user authentication and

authorization by interworking the IWG 250 with the HLR/AAA 240 of the

3GPP home network, receives the PDP address from the HLR/AAA 240,

and transmits the same to the IWG 250.

15 As described above, according to an exemplary embodiment of the

present invention, when the mobile station moves from the 3GPP network

to the non-3GPP network or it returns from the non-3GPP network to the

3GPP network, it may accept a seamless service by generating a universal

tunnel passing through the packet data network by means of the

20 interworking gateway and the GGSN.

The recording medium may include all types of recording media

that a computer can read, for example an HDD, a memory, a CD-ROM, a

magnetic tape, and a floppy disk, and it may also be realized in a carrier

13

NSN677-1002,

WO 2007/024115 PCT/KR2006/003349

wave (e.g., Internet communication) format.

While this invention has been described in connection with what is

presently considered to be practical exemplary embodiments, it is to be

understood that the invention is not limited to the disclosed embodiments,

5 but, on the contrary, is intended to cover various modifications and

equivalent arrangements included within the spirit and scope of the

appended claims.

As described above, according to an exemplary embodiment of the

present invention, the mobile station may accept a seamless service even

10 if it moves between the 3GPP network and the non-3GPP network.

15

20

14

NSN677-1002,

WO 2007/024115 PCT/KR2006/003349

WHAT IS CLAIMED IS:

1. A service continuity apparatus for supporting service

continuity between a universal mobile communication system network and

5 a wireless local area network, the service continuity apparatus comprising:

a first node for transmitting a data packet to a mobile station in a

service area of the universal mobile communication system network;

a second node for performing a wireless gate function between the

first node and the packet data network and allocating a first address to the

10 mobile station through the first node so as to communicate data with the

packet data network; and

an interworking gateway for generating tunneling with the second

network through the packet data network and providing a seamless service

to the mobile station using the first address when the mobile station moves

15 from the universal mobile communication system network to the wireless

local area network.

2. The service continuity apparatus of claim 1, wherein the

interworking gateway forms a tunnel with the mobile station using the first

20 address.


interworking gateway generates tunneling with the second node through

15

NSN677-1002,

WO 2007/024115 PCT/KR2006/003349

the packet data network and provides a seamless service to the mobile

station using the first address when the mobile station returns from the

wireless local area network to the universal mobile communication system

network.

5

4. The service continuity apparatus of any one of claim 1 to

claim 3, wherein the first node is given as an SGSN (Serving GPRS

Support Node), and the second node is given as a GGSN (Gateway GPRS

Support Node).

10

5. The service continuity apparatus of claim 4, wherein the first

address is a PDP (Packet Data Protocol) address.


15 interworking gateway includes an interface for interworking with the packet

data network.


interworking gateway receives the first address allocated by the second

20 node from an authentication server.


interworking gateway is disposed in a visitor network of the universal

16

NSN677-1002,

WO 2007/024115 PCT/KR2006/003349

mobile communication system network, and the visitor network of the

universal mobile communication system includes a proxy authentication

server for performing user authentication and authorization by being

interworked with the authentication server.

5

9. A service continuity method for supporting service continuity

between a universal mobile communication system network and a wireless

local area network, the service continuity method comprising:

(a) a first node performing a wireless gate function of an

10

inter-packet data network allocating a first address for communicating data

with the packet data network to the mobile station accessed to the

universal mobile communication system network, and recording the

allocated first address on an authentication server;

(b) an interworking gateway receiving a tunnel establishment

15

request message from the mobile station having moved from the universal

mobile communication system network to the wireless local area network;

(c) the interworking gateway performing a user authentication and

authorization and receiving the recorded first address from the

authentication server by being interworked with the authentication server;

20

(d) the interworking gateway generating a tunneling with the first

node through the packet data network; and

(e) the interworking gateway transmitting a tunnel establishment

response message including the received first address to the mobile

17

NSN677-1002,

WO 2007/024115 PCT/KR2006/003349

station.

10. The service continuity method of claim 9, further

comprising:

5 the first node transmitting a PDP context delete request message to

a second node the second node being for transmitting a data packet to the

mobile station in a service area of the universal mobile communication

system network; and

the second node canceling a session by transmitting a PDP context

10 delete response message to the first node.

11. The service continuity method of claim 9 or claim 10,

wherein the first node is given as a GGSN (Gateway GPRS Support Node).

15 12. The service continuity method of claim 11, wherein the first

address is given as a PDP (Packet Data Protocol) address.

13. A service continuity method for supporting service continuity

between a universal mobile communication system network and a wireless

20 local area network, the service continuity method comprising:

(a) a first node for transmitting a packet in a service area of the

universal mobile communication system network receiving a PDP context

activation request message from a mobile station, the mobile station

18

NSN677-1002,

WO 2007/024115 PCT/KR2006/003349

having returned from the wireless local area network to the universal

mobile communication system network;

(b) the first node transmitting a PDP context generation request

message to a second node, the second node for performing a wireless

5 gate function to a node packet data network;

(c) the second node receiving a PDP address from an

authentication server, the PDP address being previously allocated to the

mobile station accessed to the universal mobile communication system

network so as to perform data communication with the packet data

10 network;

(d) the second node generating tunneling to an interworking

gateway through the packet data network; and

(e) the first node transmitting a PDP context activation response

message to the mobile station using the received PDP address.

15

14. The service continuity method of claim 13, wherein the first

node is given as an SGSN (Serving GPRS Support Node), and the second

node is given as a GGSN (Gateway GPRS Support Node).

19

NSN677-1002,

240

HLR/AAA

MG Mobile Station

320 300

Mobile Station

210

UTRAN SGSN GGSN

3GPP Network

220 230

Non-3GPP Network

250

1<

12

FIG.1

l lt

ZO

/LO

OZ

OM

200

6t£

£0

0/9

00Z

ILM

/13

cl

NSN677-1002,

240 220 250 230 100 300

FIG.2

l ltZ

O/L

OO

Z O

M

Non 3GPP Network MS GGSN SGSN

PDP Address Allocation(S10)

Non 3GPP Network Access S20 and Local Address Allocation

Tunnel establishment Request(S30)

Authentication, Authorization( 40)

funnel Setup Procedure(S50)

Tunnel establishment Response(S60)

Delete PDP Context Request(S10)

Delete PDP Context Response(S80)

E

6t£

£00/9

00Z

ILM

/13cl

NSN677-1002,

100 220 240 250

MS SGSN IWG

2:1

GGSN HLR/AAA

FIG.3

l lt

ZO

/LO

OZ

OM

6t£

£0

0/9

00

ZIL

M/ 1

3cl

Try Access(S110)

Activate PDP Context Request(S120)

Create PDP Context Request

Authentication, Authorization(S140)

PDP Address

Tunnel Setup Procedure(S150)

Create PDP Context Response(S160)

Activate PDP Context Response(S170)

NSN677-1002,

Mobile Station

320 300 500

290

3GPP Home Netwrok

220

SGSN

490

420

Non-3GPP Network

Mobile Station

100

12

l lt

ZO

/ LO

OZ

OM

FIG.4

6t£

£00/9

00Z

ILM

/13cl

NSN677-1002,

INTERNATIONAL SEARCH REPORT International application No. PCT/KR2006/003349

A. CLASSIFICATION OF SUBJECT MATTER

HO4L 12/46(2006.01)i

According to International Patent Classification (IPC) or to both national classification and IPC

B. FIELDS SEARCHED

Minimum documentation searched (classification system followed by classification symbols)

IPC H04L 12/46

Documentation searched other than minimum documentation to the extent that such documents are included in the fields searched orean Patents and applications for inventions since 1975 Korean Utility models and applications for Utility models since 1975

Electronic data base consulted during the intertnational search (name of data base and, where practicable, search terms used) cKIPASS(KIPO internal), IEEE Xplorc

C. DOCUMENTS CONSIDERED TO BE RELEVANT

Category* Citation of document, with indication, where appropriate, of the relevant passages Relevant to claim No.

US20040076179 A1(Stcphcn Kaminski) 22 April 2004 See the abstract and claims 1, 6

US20050080884 A1( KONINKLIJKE PHILIPS ELECTRONICS N.V.) 14 April 2005 See the abstract and claims 1, 17

W02005027563 Al( MATSUSHITA ELECTRIC INDUSTRIAL CO., LTD.) 24 March 2005 See the whole document

n Further documents are listed in the continuation of Box C. See patent family annex.

A

A

A

1-14

1-14

1-14

Special categories of cited documents: document defining the general state of the art which is not considered to be of particular relevance

"E" earlier application or patent but published on or after the international filing date document which may throw doubts on priority claim(s) or which is cited to establish the publication date of citation or other special reason (as specified) document referring to an oral disclosure, use, exhibition or other means

upu document published prior to the international filing date but later than the priority date claimed

later document published after the international filing date or priority date and not in conflict with the application but cited to understand the principle or theory underlying the invention document of particular relevance; the claimed invention cannot be considered novel or cannot be considered to involve an inventive step when the document is taken alone

uyu document of particular relevance; the claimed invention cannot be considered to involve an inventive step when the document is combined with one or more other such documents,such combination being obvious to a person skilled in the art

11&11 document member of the same patent family

Date of the actual completion of the international search

28 NOVEMBER 2006 (28.11.2006)

Date of mailing of the international search report

28 NOVEMBER 2006 (28.11.2006) Name and mailing address of the ISA/KR

Korean Intellectual Property Office 920 Dunsan-dong, Sco-gu, Dacjcon 302-701, Republic of Korea

Facsimile No. 82-42-472-7140

Authorized officer

Kim, Yun Bae

Telephone No. 82-42-481-5766

Form PCT/ISA/210 (second sheet) (April 2005)

NSN677-1002,

INTERNATIONAL SEARCH REPORT Information on patent family members

International application No.

PCT/KR2006/003349

Patent document cited in search report

Publication date

Patent family member(s)

Publication date

US20040076179 Al 22.04.2004 EP01411670 Al 21.04.2004

US20050080884A1 14.04.2005 EP01472850 Al 03.11.2004 JP17516546 Al 02.06.2005 KR1020040074135 A 21.08.2004 W02003065682 Al 07.08.2003

W02005027563 Al 24.03.2005 GB2406022 Al 16.03.2005

Form PCT/ISA/210 (patent family annex) (April 2005)

NSN677-1002,

HETEROGENEOUS NETWORK AND METHOD FOR HANDOVER BETWEEN HETEROGENEOUS NETWORKS

Also published as:

EP1986461 (A1)

• CN1881919 (A)

• CN100488142 (C)

VI W02007093110 (A1)

Publication number: US2008304454 (A1)

Publication date: 2008-12-11 Inventor(s): ZHONG HUI [CN]; WANG SHU [CN]; LIU YUAN [CN] Applicant(s):

HUAWEI TECH CO LTD [ON] + Classification:

- international: H04W36/00; H04W36/14; 1-104W36/36 - European:

H0407/38H8; H0.4W36/00P2

Application number: US20080193594 20080818

Priority number(s): CN20061033773 20060218; W02007CN00174 20070117

Abstract of US 2008304454 (Al)

A heterogeneous network includes a terminal side and a network side. The network side includes an original PoA and handover candidate PoAs. The terminal side is used to select the handover candidate PoAs, initiate a media independent handover request, terminate a connection with the original PoA, and establish a connection with the handover candidate PoAs. The original PoA is used to terminate the connection with the terminal side according to the media independent handover request initiated by the terminal side. The handover candidate PoAs is used to establish the connection with the terminal side according to the media independent handover request initiated by the terminal side. A method for handover between heterogeneous networks initiated by the terminal side and the network side based on the 802.21 architecture is also provided, which improves the processing of the handover process.

Data supplied from the espacenet database — Worldwide

NSN677-1002,

[19] itil.PAMI:11:11:1Z11-RnZR

[51 ] Int. Cl.

HO4L 12/28 (2006. 01 )

fi

[12] af111i41111El1tli`J--FiAli111

HO4L 29/06 (2006. 01 )

[21 El] 200610033773. 5

[43]i.t.:F El 2006 /f 12 20 H [11] ):1.;9+-'4 CN 1881919A

[22] H 2006. 2. 18

[21] 200610033773. 5

[71] EP 4PYv ljt*h- Pkiz ithii1 518129 r 'tiR,1)11 Ell EoR EFI 4-r

[n] *NIA 4 !W RN A

fR*M-*-1 3 X 1A 11 lei VIA 6 X

[54] afftr,

KAM- M-Oi4kni7

[57 40W

*aomTry—#444gwvrAtm*ibhm, ietrri/J-mmto-F- n: a kR DA tilt

MIH njP )2A-0j1KRill*A PoA; b, 44191.1

MTH TIIP)2'aWa474KX-WA-1,A*4V-MPJ4-1,1W iyj PoA FA 802. 21

fil7, 11`71t144411 K'>4 VJ h fu AN, Miin71114Vii<PW4CAU, T -P14*

NSN677-1002,

200610033773.5

1:3

1/ 3A-

1 —4'A-41.1MiLt-ip7 4n `j ffrit0 8,4*-1077-

a, 4-0!'J *+1J MIH A fi AiVf--034AilitAA.A PoA;

b. i'4L4,01 MIH AP.% A__-1/X*7t*-0J4.3ti-A-44:4-0345t5ii M- irtj -/-J43t

PoA.

2, 4MA-ix.41*-4 1 hi-it0 , 4101A --T- A-12 -P-W a A-4 t4-*:

al *4'1911 MIH A it MIH kJ-JO PoA

a2. .4-4401 MIH Mir *likfifl-t0-ft- tit4t-W4MA.it PoA,

3, 4M 4A411*--* 2 fiA-i_ , 44+4114---T- t-irtz al -11-4*ti*:

*WPM MIH 4R-Vi*AtX1.t0*4-44.-A-1*-4t3t*14-Atit.444t44--A-ric

.t444-1-47 MIHF It MIH MIHF

MIHF, A-4 A-4 MIH ti PoA , *4411 MIH A P. 4AJILIVFx-It-

MIH Jj 0 RDA t

tILAtifol MIH I#IP f7 MIH tfiL*X--11,-.V4-itO PoA O'ft , MIH

ta4-8-0(.4tCfritO PoA Witt.

4, trt.44-49.41J-A-4 3 A-l_t0 , -)Et4+4J1,0-1-- fi#4:0 P0A 4-St 8,4S-M

tt-A 4124;f;ig -*V 4.1=4;i;-1):. -1Z EL* 141-7- QoS v,t&t lit

5, 4R-4)X-4x.411-**- 2 fiA-Itir5 , 4c4+,1114- --T- 17 tig al 44* 8A-:

4401 MIH Ifl P 4t0A-*AtA.it0t31.4-gi1=14-0-hA414-A**34-A--441c.a.

14-1/Fq4 MIH 1i-Aa-Art#N-XA MIH MIH4-SAArt#4-001L4

4911 MIHF 41-A- MIH tgi70 PoA * R ;

4911 MIH A /7 AM MIH 4,11,LALfg-iti-4firritO PoA MIH -ft;

A~i. Wok:0 PoA

6, fL4/k441J-A-sg 1 fiA-410 , -9--Vrtla 8A-:

b1 PoA 4Mg*ACR1 MIH )1 fir A-0 MIH -014k*Ptelit.-+-itsgif514-

NSN677-1002,

200610033773.5

f4 441 V2/3X

Ait.4-t-i5L01 PoA ;

b2. AiLfrei PoA *>I tE,m-fj Tiff PoA ,

111 MIH I#J fir A_ MIH -Or/A*4-,

b3, tILAt-ffriti6-WAAit PoA3t11, c, , MIH ono

7, 4MiXiq-A-4 6 4-1tiVI'>t-, bl -11-4*ti*:

*4; PoA MIH -1)1A4734164-Lit4i41-11--W4A R 44; PoA ,

41-2'4 It tit-*AtiVtiritiX PoA 1a 4; P0A 4-4/k MIH

H-A-4 A .tit it*3tiXj 41 %J ff

12 b2 CA-140.4-AtiVtIt3X0 PoA ,W4git4,-ThVOttX.A

1! -rifr PoA =1T 1 PoA Witt;

1 tit b3 L4:.i3;43' Alit. PoA X -W4MA *it*, PoA I.

IcliiA5L-11--W491; -074.5V)t -ii4J Pit 44 1(37

8, 4MA4411-R--* 1 Pfritifej;-A-, 444-filAt 4ft-t fr4it a -t_iffi4i LM:

511!-& Tiff PoA 41-411:934-Ag. HA

9, 414A4x411-A-4 1 ffriVit 44+431A-T--, 4 t b

4#0 PoA MIHF1,157R. PoA MIHF MIH -0J 4i1A -+ PoA

45h-lft,1-1-4-%41- A.it*),t0 *OA LO-A_gi1 PoA taig- tffl

; PoA +2.4.44044-$Vg-ht 4-4- a A _EA-Xit-WA EJ PE, A,

10. -034k 44+43141-, 046-4P27 4)-

a, PoA ittA*A.A-074A MIH I1 ft A-M- f;-jA-0Yg Viit*-0743A4CAA N

PoA;

b. 2 PoA frfi MIH l J /' XAVV*AA-W4A-4144-0:L41-0)4A5MitO

-0) R.A. PoA.

11, 4Mg411- 10 FiritA -VA a -11-44c

al PoA MIH A *AR, PoA XitYAUPF*TEM*14--AA-*

NSN677-1002,

200610033773.5

MIHF A. MIH tg)7&55,1*-+, MIH fieiJO PoA

if9R. PoA PoA MIH P A-4/MAJT5i-It-A- MIH tit)) rj PoA *

41tt ;

a2, , PoA j MIH /f) MIH 1tta#N44-fiAit0 PoA Oitt,

MIH PoA Witt;

a3, PoA efq*jk-AA MIH -0;43t4n116-ft-it*-±t.4-1--034Aq T PoA

-SA '12 t(-1 ti5C PoA 41,11, i1%±Eit.PhicIAI:VA-it*OAit.

PoA 'fitt

12, 4Mig-ix.4q -A-4 10 fi4-4M 4#4.11-0-1- ti" -"At a -11-4.

a1 A PoA 1 MIH ?A-1(9 MIH -Matlig..#7§Xit MIH tied7kA1A+,

MIH tER_4-51.67-ititw 41-* MIH fit:970 PoA

a2 A PoA MIH #1,1A-- rfq MIH 4t--,NAL#E--44fiAitO PoA *WA,

MIH PoA

a3, PoA V:(ACtit MIH -074&*14(flit -4-4±41,11-0343tq T PoA

itsni; 4*-Igt-it4t0 PoA ititA 14..t=1 Ph •Rit

PoA -Mt

13, 4R-4-49.411*-4 10 fifritf-i7 414411-At 4 47 tit b -X-4*

b1, iff P0A4M-1€r'- PoA MIH MIH ina497464-t.4+1-4147

firrit0-034kAit PoA iff4iVcr*Afp,fil

b2, A-1-41.0 -W45tRit. PoA ,(5) A(A4401M1H

MIH

b3, PoA -2LA4A-0

14, tOgix41*--4 13 fifritO 4444i1A---T" 413 4,1.-44Z b2

-a. `j PoA 4M %I ft*. is PoA 1 14 PoA

; 413 -tfrit b3 Alt PoA tajMLA' A_ -03-4sA4A iez(-4

).A AIX 5L-4--W4k.

NSN677-1002,

200610033773.5

—#4-A -0k

tt,K4311.

4c%A. '3110XL/144 M4--ik*4jA,, -11-444A, 4)3Am)

*21440 P1M-, it12802.11t.XtrtifLAAAPI 802.16

iX5t5C0 Cf=C,17. 3GPP ( *74- 4301,t-ft-- 44;%It4t-R4VAla )

, F A *-1,,L4Foli-0-•KiLlik4-itg -FAT

J&A-4-44 Ft) .4 4k+4-1*. 802.21 04x. N A.0 , IEE

E ( k)44- XJC0 802.21 (4**-WCIL4-)-01-9.A.-

444 Ti2 ja M Wit t4X4A-*_t_ - J;AIA44-t,

-0743t ht3 44;%*. 'CA 1- AitA irt7**--1151 it-li-4k.,3t14--074k0A-417 SCP:-51

-W4k04FW_L- 4/L41, 4*A_ytilt-**-i2 Atiit-4-AM Nig-040g

Mg4s-it4t-Atl*-4A, gbta-w

, Iliztk*-444 f4-1)11 -tn4A4 0-4it-ty-0 ko

802.21 4C.` 'c#'] MkorE MIHF ( C4c.fc,*-0)45t.xh )

44c. MIHF 4k;t3utnit*OvAA0247-)/4-11-A4oRittm,-Azo0-ihtffli-thsisc#,

0ivITF, A-on,A;AXittitglialth*24#3-kftsio MIHF AZA 111 iv eft PI) 1

ham=, MIHF _LA--1/Eft-W4A)A A.f-4M1b4tI MIH ttrAnfP_L -F

o MIHF A-- 041i14-a+, tk* T --P-R.119J-1-04 ,

5toist.*-JiR-it-31t_31.--T---K-44c04A.4k,K; MIHF itil-4+-X04-4A_,K4N*04,k

1:1 4-121gc4A-ilt g•th'i5CA,111•11-1firo MIHF T -074AA.4_4L, it -iAM *R.

NSN677-1002,

200610033773.5 F9]11.3 M2/111

VA1A-tc-WAC4-*A-04t,to

802.21 T -i/V*A.A.*-1+A*( MIES ).

( MICS ) 41-,111- AL* ( ) 41=iM*4kA.A ( S

APs ) a kee t -b5414-* : Link_Up ) Link_Down (

PO-

5) Link_Going_Down ) Link_Handover_Imminient

) -Af-; MIH_Capability_Discover ( MIH

#..JJAA) MIH _Poll ( MIH ) MIH Switch ( MIN i ) MIH

_Configure ( MIH MIH_Scan ( MIH 4344) MST-AA-0 fa*:

Data_Rates ( 4* ) . Location_LatLong ( . Networks

_Supported ( ) Quality_of Service ( QoS, SL.4-74k ) *; MIH

F t-4,*.it44“A A-Kk-A% _tc4+4,k 12 AVZ4V41:0 SAPS zt4re`:-//0*-40*,

-firrAo SAPs.

14 ITO 802.21, Y(*Pft.-A-47 A. T --'Ht131;(1- ffi 2 47 PI gi--CYPIAA

802.11 5!1 3GPP2 -W45tie7 :

1 .i.1(41111-1:411A: 0****444kir(i A41.4k* It MI

HF MIHF 1,;-44k.A'Ait-W4.5t-+14- MIH a 3A. ( Ack#44-

fl €L PoA ) 4A- MIH fgh0131-111 irfJ PoA.

2. Tiff MIHF PoA -Vs\-XA fil4t/ft 41-0-4/A-A.0 jsR

X-It -W4kAit PoA,

3, Tit NA IHF0:%. V;(44MA-i-4-4-3T-46.*..45-4)3A

*4.,A 44 if; 4-emit )PL 1:7 Mg4i-111 MIHF.

4.sh! Iff MI HF V.A.-i)34.3Uttip-t4

*IA*,

;51t4 .t1(47'4911AAO -03431A,II. 1-44“c,*-0j4.5tA:a4 tAc

44 A1-0143t AA141-X-111-11-A„ , itt.O;LAt& -W4Ct41- irtJ AA.t Aft-WA

NSN677-1002,

200610033773.5 F9]11.3 M3/111

k3-1---kit-hkIrck-IPA;

irti *ft , 443: i PoA 15,5 *ft gi,t,fmq A„ ;511(4 fp ALA fT J o 11s

Pi; t-17- ACM+ 4rIJ Q 11:, g • Cfl it.*- A444- PW.,=-191'1 , A-AP ,

± fiL4-3Agh 'Kit PoA; n pt, 5A.1,4**t

vit,457.0i v,3-49114xiu MIH gd7X.R1.0t5-A-141,P*.i& PoA 0-11-*41;

*A_ "A it'll 14 irf/A-1-4;t4A---447 4-A tis- -W43A6 - 17,0WAJA_,A1i2M'

.4:ve 117 fIcAtimix7t-03A st_014 gf3-191,JX*M44:****Z-6-0

$;411,1_ 1E1 , 4c%ta)1 -APT a*-*t :

*A-, ffritipti *A- t 4-143 -143-44t:

a.41)11.44*.fr_.*-0J4k MIH If) I'A---it*-0345t4kit4ki.A PoA;

b. *A44'1 MIH kWAA-0/A-i-A---***4-wAsim-ito-074k

*A. PoA.

al, MIH MIH 107 PoALi:,̀--SLIt-41;11g;

a2, 0,-4191q MIH A P 4tOgfikietilt4-1",k,!A.4-*--034.3tAit. PoA,

412 4-siga1 -11-4*Lit:

MIH A--4MX*-4 XiXOttiAli-=14.4-ka.#1f-z--k,t3i44401-A-gt.

MIHF kit MIH tiO7A.g11.4+, MIHF

MIHF, 41,-4 MIH fi0Jot PoAP104 -4941ti, tl-419P1 MIH if)

MIH tiO3flt PoA

MIH If) fir MIH PoA 04-S- , MIH

,tLEFL*X-AAA-fin-itej PoA fit-ft to

NSN677-1002,

200610033773.5 11.3 M4/111

firritA PoA t4t- M ±4,t-A1141=4;i;ig *AV 41,4;izi)2.

QoS if) 'ft, 47;0

4t-t 4-44 al f-f*ta*:

t4-41t1 MIH AP A-- 4R4V4-4A.Ithla-45-v174-***44-sti.4-tatffic-A-4-4Scac

t*44-r43 MIH ti,J3&_01*+, MIH -ft„ta#23- 0) 4-4

MIHF A.T=141-* MIH fiU7 irt7

4-41111 MIH MIH -ft; PoA Witt, MIH it

tfirLA-NO,A.-04-410 PoA 'Mt

-1Et- t b11-4*t4-4-:

PoA 4MA-ti(AMPI MIH l 1 P MIH -W4A4n46.4-t*+-4-41.601

AltiX0 PoA -A-411M-f-ta-Mf4;

b2. Fir itO ALAtit.**-isurfj PoA 5t,A5Z,51-41A PoA FhT ,

MIH is A--& MIH -k)/4,A.-+; b3. Fir izEA +/AMC& PoA t.A114-, ALA MIH

t bl

.44141 PoA it MIR -034k4)34/64-tirt3gitg-t-W4A 1E1 41: PoA 1#r j , it

44i--„ti .47 t4-giAL4A4-034ix PoA iftt ; 1 PoA MIH

PoA ;

t b2 fiA-it0t31-4.4_4f3tiA.0 PoA ttA*-4-MVii- X1,9

PoA PoA ;

Ti' Olt b3 33-z. t1,4-&: ALA f1Ait PoA -074kAiLiff*-, PoA It T:7 TirfOri -W4.3txx --- M.tii4k 1:7 1.19 it-WA gi114- 3t 16 411 •

-tfr-iftt a -Z_TifiZeL: -1I;k511 PoA jfiAiti)30-Ag. HA

412 b

PoA MIHF ifi7/* PoA MIHF tot MIH PoA

NSN677-1002,

200610033773.5 11.3 M 5/11i[

N-kL4-1--A-Pi_40X_IL*)A004/1 L7,44-X51.1 -A- PoA __E-4f-ffitiet3t4-1

a; 34k PoA 41:44c43' 040E4-0 gtt-fk 1:7 if-37 _EA--AA-WAE,,th'si.041V-izo

-074A0 , tit-iv-F-4)-W:

a. A PoA 0A4.1c,*.-.074k MIH Ar--4

PoA;

b. R. PoA MIH I1 PAASA4*fc.A.-0/4A-it*-41-V:LM-0745t5W-1-t0

-0/4kAit4A-AA PoA.

412 a -11-44ct4--g:

al, A PoA 1 MIH ); A--41OA- A PoA kilAtatilas1744-rkttt*-1-t-AALti.

44,4tack*11-474 MIHF MIH 41-* MIH 110)0 PoA

rfiJR, PoA PoA MIH J J P A-4/4-31tatifx-41-A- MIH M.JJ fit PoA

a2, A PoA irt MIH I#a P AE14i MIH' ta*S--itig-M-i-t0 PoA 04tA,

PoA WitA;

a3, PoA iti*A4A.it MIH -W4A4n1/4-ft-i-ri-*/t41-034kA T P0A

ii- 'f ' E7,4-6-4t--it*OtAi5C PoA

PoA

412 a -ft--14ct4t:

al, , PoA 1 MIH ft1/2-141 MIH41,-,M*AAIt MIH giJA..91.4`,

MIH W70 P0A*!'-a -;

a2. A PoA MIH MfrA-M, MIH PoA 01-2A,

MIH -K*Ak#N-gOVA-iirtJ PoA i4t4;

a3, PoA 1610:4A.1t MIH -W4k4n4f3ift-it*-itli--003t 41t PoA

it41-SA LI" L46--Itit4ftitAiX PoA 0:At'itiliAt.i.iic:/ffisit.#0Ait

PoA

-"At 13 -11-44-ti-i:

NSN677-1002,

200610033773.5 F9]11.3 6/11X

bl PoA **A PoA MIH ICJ i MIH -WA*46-4-L4- -+-11,-*_09

ffrit0-034k4it. PoA ;

b2, A-i-t0-0)43tAit PoA c Afa Wg=r41 J PoA wAEk 0;cAt 4911 MIH

MIH -034A-0-.+;

b3, Pfrit0-WA4Ct PoA

-it 12 tig b2 A-1*LO 40Atit4f,tiK PoA 4MIVA-A-M fiVit

PoA 1 .a4Ct PoA Witt; -Igt-t b3 it; Li*: PoA 0.7 *4

.i4(414..MPhia ,t)k_Z-•

*A.E1114kth Tit 802.21 Ali10 i *4 PI gS-19111A.011A 4-A Fit

-0343t0 NIPha T A Ac5AXAO-W4*.A4I, -074,AA4_I0

*A.E91-* -*.ik-P-ii;) 41;%fiR. 54 7 4f-1t* T gt,1

01-" ; Vs1 Ettitiv-bt-074&111.07- it 0

T -0J4,”t- -

eli

111 1 5i MIHF

IN 2 Y3gt.liA-A*44J -W4CA43.

119 3 51/ rVALAMMAA-074k 0 A41 VEJ —;

fl) 4 YJIkitILAMMAA-0n45tirtiAtilli-11,

5 'I/ t 717 4t-491X7t0-W4CA,11

IN 6 ph i FbIt V3-1w1A3k0-034CMIT

T -4`41-444's- Affq 40 FR 11P4*it

NSN677-1002,

200610033773.5 is F9]11.3 M7/11X

+ 802.21ot-j-WAA,4i-cirY7 /011:kAii2da PI

1:11.WALA.e...0-W4CM.k' 3 4%2Rtill 4 M.71( iktAYA 802.11

3GPP 0-0/4U131§i-iXE91-0743t1t41 ):

-1frig 1: STA/UE ( ;7&,14,/#1,P ) g1] iff PoA JkLALYJ

802.11 ) *iI HA ( OVJIP 934-A)-1 )

-,Afg- 2, hf, /-14,1 iitfu.0,13utt.A.4* , 4,4-R,14

STA/UE _LA*11.4-0 M tS-4-k T=7 ( ktek.,13 802.11 4k- ) -krfq-A- MIHF9-c*A.

Link_Going_Down ) Link_Parameters_Change (44.4

**Ott,) 'f , MIHF XttL4-i3"*4-t-ifq MIH L. MIH_Link_Going_Down

_4 MIH_Link_Parameters_Report ( MIH F Q) *44- MIH

fr 4M-1A*4+71-4412-i'Ttitrg*AA-WAA4-Y-. STA/UE *A.A_ PoA ±ice

-fit T *4-1-Ak#, !! PoA g1J40 *414- 0 AAP( A.11) `'ItlWiTz ).

4frig3. STA/UE ± j MIH l? ;A , 4-63t, 0;7 MIHF

Lit MIH_Capability_Discover ( MIN ) MIHF

▪ 4i104.4 MIHF, 4.gett M 440 Xt

MIH 444-kit MIH_Capability_Discover AE:1

STA/UE. itsAL MIHF MIH MIH_Capability_Discover

it 1±1 MIH ifittil.#5/4_040

---44t 4. STA/UE MIH P /tit MIH_Capability_Discover 4-1-511

T MIH tit; 93 PoA §1 4. , 1,2=7 MIH tr-AL # k

MIH_Get_Information(MIH PoA 04Ei fa, , t7.44 -6.M

gg-A -**A-t1404-iAs AR-4-14 Sli%ujt-CfV*1,-II

S-Mt 5. STA/UE ± MIH if] PA-074CAX4P-k4R-A-R.45(0 PoA Mt it

#-W#1*-1,X4kAl PoA,

NSN677-1002,

200610033773.5 is F9]11.3 M8/11X

--1-frAt_ 6. STA/UE MIH A P jt MIH_Handover Initiate ( MIN -WA

47A4 ,f-Lit-i ) gt)*A MIHF, *.1-& MIHF IA114 ( 802.11)

PoA. T STA/UE ti3Lit4k PoA

7. PoA 4L STA/UE AAA MIH_Handover_Initiate A-4%44

, -AMAIXO* PoA MIH_Handover Prepare ( MIH ) it*

itgi-if AO, a PoA 14_Q MIH_Handover Prepare vh/51447-1-7***(3-mv,*

▪ 8, !h-' 1 PoA MIH_Handover Prepare 9f-0212 4*4U413t/fl OR

it. PoA.

9, PoA i MIH_Handover Initiate 444 PoA

47akitE:1 STA/UE.

▪ 10, STA/UE 41/110 MIH I1 P MIH_Switch ( MIH*4-074k )

-+AA-W4k.

4)-Vg 11, STA/UE 491!10 MIH MIH_Handover Commit ( MIN -0)

43ttit ) -0-1-3ggi** MIHF, di*, MIHF PoA MIHF XA-W4k

R.3t, lr PoA ALPI MIH_HandoverCommit -it44f-=14-43.1:=7 STA/UE, 4V4

-01431-44-41t-fi-k312.5i.A.4

-"a 12, -0343tX_7, STA/UE 401 ifr!J MIHF PI

T:7 ( 3G P P ) A_IL0 Link_Handover Imminent ( t3C4--WAgFA“-.414; )

MIHF MIH_Link_Handover_Imminent 411**- MIH ICJ P

-W44 46. -a TT A_ it. PI .449111AAPEA.

4frit 13. STA/UE +2* PoA ( 3GPP ) 42z-- L2

-"Aftt 14, L2 - 11.4,A4.t Si_ , STA/UE 49P10 MIHF =14-011.1 Link_Up *44- ,

-4-X.itxliik MIH_Link_Up ikAPtigi-E.A31. -1AV) 71-z -t-PT I,%c M

PA-4911it A.

-tfra 15. .1kE$1-0 ih IP A.iiitlkiNk

12

NSN677-1002,

200610033773.5

i•A F9]11.3 M 9/11i

-1friftz 16 , PoA irt) MIHF r11 PoA MIHF

MIH Handover Complete ( MIH ->135,A,) A PoA

ksA:141-4t-Sk.40it*A00.4- L0-X3'144- RDA -Lif-O-A tti4 if) 10 ita

-11-i4t 17. PoAF.tciElit4-111- , STA/UE 4-PMN.5-49110 MIHF MIH

P4-i-ecgtj Link Down (t4.4#1 ) 4r, MIH_Link_Down*4-1-,t0)11Eifkgs-EJ*

-9-1f1

a 18. +))4k A.', , STA/UE MIHF 41,2 MIH J#J f7 41- 4k 511

Link_Handover_Complete ( 4- -03 4A ) 4%2

MIH_Link_Handover_Complete 41171z. MIHF. ,4t-PI A. **A*

MIH_Link_Handover_Complete 411-Trit-f-i-tX1-67*-i-k410A-Af12.tti-

IP Atl. A* t t

4--it 19. STA/UE >ri5 MIH ICJ P ilk51) MIH_Switch PA/PL, *.nkt31.4-W4A

YEA.

-131g 20. kbat !:* -Aff-*-1-tvA*-4-0g11-44-taig- ( 3GPP) 1.4t.

21. STA/UE 4c. A PoA ( 802.11) ific**.fik*.*.

*Itii-41,1X0-W4CMI-1112R1- 111 5 4RI. 111 6

1. STA/UE PoA ( ItAt.Y3 802.11 4-1:1 ) *Alt

HA 4-iltA-31-k-iks

-Ng 2. '-/t.A-ik.4.ktilicitig,j5t,t4-4- -fiT44-',5kot, , A

PoA PI ( Y/ 802.11 ) MIHF 11-;- *X

Link_Going_Down Link_Parameters_Change **, MIHF fi MIH

MIH_Link_Going_Down MIH_Link_Parameters_Report **.

&at MIH I J f'4R-4--ilz**7.T1-14g1-211M-A-- -W4CA41. R PoA A,A_

STA/UE > T 40044t- AvAL, STA/UE -1-47-gti4E1*4-t-Oil.Ar3 ( A

IN+ )fl

NSN677-1002,

200610033773.5 i5b RA +.3 10/11i[

3. 2 PoA erti MIH If1 fir AiIIA -0)43tot, 4-6-AsTai(--74ft- MIHF

M I H Ca pabil ity_Discover Tr12-7 I 1±45-,f4 t pl TT O

MIH 444--kit MIH_Capability_Discover

it T=1 p PoA MIHF r(3-1 MIH V- at a a A. it_

MIH_Capability_Discoverit4, MIH

4-44z. 4. hi PoA f1 MIH f#J P it MIH_Capability_Discover _ALI-441 T

MIH h j PoA 1.1 4 , 4 i j MIH t; AL # A.

MIH_Get_Information PoA tagr lPA-Ati

Cfl *it

lit 5. PoA MIH iti,-034kATOVA4R-4/A-.45c0 PoA

-070435c1itA PoA,

lit 6. J. PoA MIH ICJ fr MIH_Handover Initiate -inAir-f*-51*-

MIHF, $ MIHF ( 802.11) STA/UE, i it*

t- T Tt PoA *i5C11.43t OA- PoA

Ifrig7. STA/UE 4.4-40-4-43t01 WKit PoA.

8. STA/UE Alt MIH_Handover Initiate 0070544-141-A.A. PoA 15•(741,-

,tkiti::1 th: Tiff PoA,

t 9. -r, PoPoitil MIH_Handover_lnitiate 063 5gi , gt-i-Mr(7

44- PoA AA MIH_HandoverPrepare ff.e 4k PoA ATLI

MIH_Handover Prepare 4-0:14Viir-, Yrbl

10. STA/UE MIH If] MIH_Switch

11. 407 PoA *10 MIH If1 f' t ai MIH_HandoverCommit **A*.

MIHF, v14**., MIHF A.ItA STA/UE MIHF XA.-0-MtAtiff*. STA

/UE At.PI MIH_HandoverCommit -iff**-4-T*.* G1, a 0A-l143tit44iitlf

ALWAA-A-

NSN677-1002,

200610033773.5 i5b RA +.3 11/11i[

--1,44t 12. -WAX.AVi, 4fr PoA 1911€r'7 MIHF 4.1-xlkii*AW).-44.1=7 ( 3GPP )

A. it, Link_Handover_Imminent 4 4+ I , MIHF 4

MIH_Link_Handover_Imminent MIH /fl P -f-r-Z_ -f)74,1g1144-4. is -L-f-1-17.A STA/UE 4910XittA.

-Ng 13. STA/UE 4-vit PoA ( 3GPP ) ji L2 A--

4--44t 14, L2 A-1-/43t.:9:-fit, lT PoA1010 MIHF *qtA Link_Up

tkitxtJA fJ MIH_Link_Up p A-7 Edt 44 it', vA

STA/UE it1A.ittA.

0-ift 15, ift.,111-0 -1,1J IP .i.11-4k

-tfr-OZ 16. A,1_,17, MIH_Handover Commit it , J1 PoA 7 MIHF

PoA J MIHF 1t MIH_Handover_Complete it4 4 PoA

vA1-1-4.*-11- A.It*%k 00* PoA ?A"

17. PoAi 1E1 tib14-01- STA/UE frrP1-4-19110 MIHF 411 MIH

44-4t511 Link Down MIH_Link_Down *4-1-.MilE14ii4 .21-#1

-tfr 18. -07 4A A; 44- PoA *10 MIHF 412 MIH /fl

Link_Handover_Complete MIH_Link_Handover_Complete MIHF

• **A- IT 17-,(#0 MIH_Link_Handover_Complete i

4-5-40 k

4-0 19. STA/UE fry MIH MIH_Switch viittL tz,..11Mti4-+)74k e-J

4-0. 20. klit Tiff--fri*I7A44-05110- 4- ( 3GPP )

21. STA/UE 411A PoA (802.11) fillti\-Alik*v:

NSN677-1002,

200610033773.5 it HA 4; PH IA 1/69,

16

NSN677-1002,

34$ A/Yli P 4r

*AA Ztkfin% 101/01.#414-t$1 MIH

fitiSIX*

UCH Cellular

Client user 802.11 ME tete. twee Function 802.21 802.11

M111 PPP Mill GRE Function UM'

3

5

6

7

MI3—

Handover Inidateindkatio 4 —

MIN_Swite

MIII-HANDOVE -INITIATE REQ

8 L nk Up.resquest

LCP IPCP PPPgtZ.

200610033773.5

1A3 2/6A-

2

CD-0— AAA&

Ala Link Parameters_Chnnge.int kation Link Ps rameters_Cbange.i dkation

Mill hlnk Parameter Chang!, M1H-LINK-PARAMETERS.CHAN Mill Link Parameter Ch Inge • p 111H-CAPABILITY-DISCOVERY-REQ

• 11111 INFO RESPONM (E.g.,Av illable networks)

NHH-HANDOVER-PREPARE-RSP

II*417,314AAA MTH Handover-takiate.Request

Link Up.response

M1H-HANDOVER- INTIATE RSP 0

#411P/101

MIR Handover Mitiatei dicadon MIII-HANDOVER-COMMIT REQ

MIIII_Hardower Complete.Reqrt

Link—

Teardown.resquest 4

Lk* Teardown.response

611H_Hantrer_Complete.Respor se

MIH_Handover_ nitiate.Responst MIR HANDOVER-COMMII RSP •JVHEI Handover-Comit-Comtirm

0-0— 313cHmA2000NclitA41

(r; tolf0/Z1it —0

9

10

11

12

13

14

15

16

18

19

20

DIR-CAPABH ITY DISCOVERY RSP

M1H-HANDOVER-PREPARE-REQ

Link_ Up —

MIR Link Up(3G PP LCP k Li Up) •

NIB Handova -Commit.Request

14 2

17

NSN677-1002,

11SH MIN 802_11 =PP Min LI- C/MACJPHY Flui:kw Ilsor Famaiss

1014,10.1

!Auk G DirralmlicationdLialc Parameters Claaselaideatiaa 2

MIR 113er Client

■

1A3 3/6A- 200610033773.5

MIH a~ CERAM User Fumed= UMTSLTE

3

111H Liik G r Dewaimlicatima/iIIII Link Parameters Repertinikatia a

MIH Str Discorerreineat

MIH_ E ab Disewer-raPellse ilmmm=mmomm=

&I Get IMkrnsatismreq nest 4

Gd IMiarinatienzeips

MIN liami crInidateraluce

MIR Raisderafreparerequest

11111 Harmloyer Prepare-re:pease

MIH Hand er Imliate.npsase 9 4

19 111H Sake

111 3

18

NSN677-1002,

17 Link Dawaisoication

ink Dews's ikatint

1$ 14111fivirkekrespos44

Link Thi.ilditatiela 1-

301IH Link jipisizatinn Link Up. iDditation 14

31111 MIH aOL11MR? Mn MIB LLCSIACPHY Our Facia tier Funteien

11 m lianiever Coaanitsequest

MIN Iambic Commits

Client

11

UM UM now Yard=

LiskIlandever lamithentiadie than A —

111114.........4.LInkfilasdin er Iesai ea . 1k

Linkilandleer 1 mininentiadir n

12

3 ASL 13

13 31M litaadayer_Completemzmast

1CH lita,11d1OVII Campletvirimosse

L i'ak Handkrrer C4sarNet A

MIH ink Hander --------

L'

*ratios

24

L is& Handily er_C.enpldei li ties

Dawaindiattion

GERM/ VMTStTE

FM 4

200610033773.5

1A3

19

NSN677-1002,

200610033773.5

1A3 5/6A-

Link Goiag_DairsAnlicat ink Paranicten_gbasaasailicatisa 2 4

MIH Lima Geiag_D•wmaial• tion/M111 Link Parannetersiteportinilication ago ow ea mo ow am on No ►

MIH _Cap Sky Dimmocer.reguest

MIH TJses.

11111 Client

Ursa r GM AM

MiTSIMM LIR en_n =FP Ina

Fumble 7Jse r Fundisa LIZIMACJPITY

4 MIH Cap y Discatersespaase

MIH Get afarnamionrapust

vao

4 11121_got nirernuniannap

S

M B Handiner I 4

fiEH HaaiarerJt nine

Handevin,_Priparn

MIR Haadsva. Preparareaparat

IS MIH Switchreinesr

20

NSN677-1002,

AifitrtiWi t - ., 1} Ai542(3caT)

if rwidi...

L ink

Link

; "111

I I 3CPP B Sim MTH Ir.,

i Mill LI.C/MAC/PHY

1

61611_11arm

Ilser

i MIR

Final=

mer Com .......ri

; GER

UM'S

Ink-request

Inunini

ComseiLresperast M li Haserter 4

liandoter

4

'-

tip.iadicataa

..1

Itii

in intikatir

inn

L

Liak Ilandover

4

nk tharrer

Inuninent.ha I

lib 3UP Mt IL'

'till

Csinplett.ragteest

3.4.4tik_

Link Up.indica 4r

irindicat ion

Hataility4

er_Cammp1

ir

4-

Link Downimication.

ilk Faudover

Suritzkratimase

Ilk Link

',4 "tumid

MI litandever 41

111H Hasivrter Compktarapisse

Downatilinatian

Raiiiirver -.1-....7..-4.0..Q.......

Lak

III Lint

E•

........- ...........

Contrkete ' itation

..... Ceaspktaisdicat

.t. t

•

Caen Us

11

12

13

14

15

16

17

16

M1H

nit

21

200610033773.5

1A3 6/6A-

111 6

21

NSN677-1002,

Name and mailing address of the IS.A/CN

The State Intellectual Property Office, the P.R.China 6 Xitucheng Rd., Jimen Bridge, Haidian District, Beijing, China 100088

Facsimile No. 86-10-62019451

Date of completion of this opinion

28 Oct. 2008 (28.10.2008)

Authorized aka

WU Shuang

Telephone No. (86-10)62411507

FOR FURTHER ACTION

see paragraph 2 below

Applicant's or agent's tile reference

080503

PATENT COOPERATION TREATY From the INTERNATIONesd, SEARCHING AUTHORITY

To:

0 100081 PCT

ee• 501/B.:Fortune Building:No.17 Daliushu Road,Haidian Distriet,Beijing,P.R.China.

BEIJING ZBSD PArENT&TRADEMARIC AGENT LTD.

WRITTEN OPINION OF"THE INTERNATIONAL SEARCHING AUTHORITY

(PCT Rule 43 his.1)

Date of mailing

(.:oyhnonzh/year) 20 Nov. 2008 (20.11.2008)

International application No.

PCT/CN2008/071842

International filing date (deryhnrtnthiyear)

31 Jul. 2008(31.07.2008)

Priority date (day/month/year)

07 Aug. 2007(07.08.2007) International Patent Classification (IPC) or both national classification and IPC

HO4Q 7/38 (2006.01)i

Applicant

HUAWEI TECHNOLOGIES CO., LTD. et al,

This opinion contains indications relating to the following items:

IZ Box No. I Basis of the opinion ❑ Box No.II Priority D Box No. al Non-establishment of opinion with regard to novelty, inventive step and industrial applicability

D Box No. IV Lack of unity of invention El Box No. V Reasoned statement under Rule 43 bis.1(a)(i)with regard to novelty, inventive step or industrial applicability;

citations and explanations supporting such statement D Box No.VI Certain documents cited O Box No. VII Certain defects in the international application ❑ Box No.VIII Certain observations on the international applicatior,

2. FURTHER ACTION

If a demand for international preliminary examination is made, this opinion will be considered to be a written opinion of the International Preliminary Examining Authority ("IPEA") except that this does not apply where the applicant chooses an Authority other than this one to be the IPEA and the chosen !PEA has notified the International Bureau under Rule 66.1 bis(b) that written opinions of this International Searching Authority will not be so considered.

If this opinion is, as provided above, considered to be a written opinion of the IPEA, the applicant is invited to submit to the IPEA a written reply together, where appropriate, with amendments, before the expiration of 3 months from the date of mailing of Form PCT/ISA/220 or before the expiration of 22 months from the priority date, whichever expires later.

For further options, see Form PCT/ISA/220.

3. For further details, see notes to Form PCTIISA/220.

Form PCT/ISA/237(cover sheet)(April 2007)

NSN677-1002,

WRITTEN OPINION OF THE INTERNATIONAL SEARCHING AUTHORITY

IInternational application No. PCT/CN2008/071842

Box No. I Basis of the opinion

1. With regard to the language, this opinion has been established on the basis of:

• the international application in the language in which it was filed O a translation of the international application into

furnished for the purposes of international search (Rules 12.3(a) and 23.1(b)).

which is the language of a translation

❑ This opinion has been established taking into account the rectification of an obvious mistake authorized by or notified to this Authority under Rule 91(Rule 43bis(a))

With regard to any nucleotide and/or amino acid sequence disclosed in the international application and necessary to the claimed invention, this opinion has been established on the basis of :

type of material ❑ a sequence listing ❑ table(s) related to the sequence listing

b. format of material ❑ on paper ❑ in electronic form

c. time of filing furnishing ❑ contained in the international application as filed ❑ filed together with the international application in electronic form ❑ furnished subsequently to this Authority for the purposes of search

4. 0 In addition, in the case that more than one version or copy of a sequence listing andfor table relating thereto has been filed or furnished, the required statements that the information in the subsequent or additional copies is identical to that in the application as filed or does not go beyond the application as fried, as appropriate, were furnished.

5. Additional comments:

Form PCT/ISA/237(Box No. I) (April 2007)

NSN677-1002,

WRITTEN OPINION OF THE INTERNATIONAL SEARCHING AUTHORITY

International application No. PCT/CN2008/071842

Box No. V Reasoned statement under Rule 43eis.1(a)(i) with regard to novelty inventive step or industrial applicability; citations and explanations supporting such statement

Statement:

Novelty (N) Claims 1-33 YES

Claims None NO

Inventive step (IS) Claims 3-15, 18-22, 24-33 YES

Industrial applicability (IA)

Claims

Claims

I, 2, 16, 17. 23 NO

1-33 YES

Claims None NO

2. Citations and explanations Reference is made to the following documents: Dl: CN1878389A D2: W02006029663A1 D3: W02006088331A1. Di discloses a method and device for switching network service; D2 discloses a method for establishing connection in the heterogeneous network; D3 discloses a method and terminal for switching and releasing link connection in the multimode mobile terminal. Novelty (N) :

Each of the documents 01, D2 and D3 does not disclose all the features in any one of claims I, 16, 23, 25 and 30 completely, therefore claims 1, 16, 23, 25 and 30 meet the criteria set out in the KT Article :33(2), involve novelty.

Accordingly, the dependent claims 2-15 of claim 1, the dependent claims 17-22 of claim 16, the dependent claims 24 of claim 23, the dependent claims 26-29 of claim 25 and the dependent claims 31-33 of claim 30 meet the criteria set out in the PCT Article 33 (2), involve novelty. INVENTIVE STEP (IS) :

The document Di discloses a method for switching network service (see the description page 8, line 11.-page 14, line 14; figure 4), which includes that: a user terminal switches to a target network from a source network; a service switch control unit judges whether the network would be switched. DI does not disclose such a feature that. a network side unit separates the user terminal from the source network. However, this feature is well-known in the art. Based on Di and the well-known technology, the subject-matter of claim 1 is obvious to the skilled person in the art, so claim I does not meet the criteria set out in the PCT Article 33 (3), does not involve an inventive step.

The additional feature of claim 2 is well-known in the art, based on Di and the well-known technology, the subject-•matter of claim 2 which cites claim 1 is obvious to the skilled person in the art, therefore claim 2 does not meet the criteria set out in the PCT Article 33 (3), does not involve an inventive step.

The document Dl discloses a method for switching network service (see the description page 8, line 11--page 14, line 14; figure 4), which includes that: the user terminal requests to switch to the target network from the source network; the service switch control unit judges whether the network would be switched. Di does not disclose such a feature that the user terminal is separated from the source network, However, this feature is well-known in the art. Based on Dl and the well-known technology, the subject-matter of claim 16 is obvious to the skilled person in the art, so claim 1.6 does not meet the criteria set out in the Pa Article 33 (3), doss not involve an inventive step.

The additional feature of claim 17 is well-known in the art, based on DI and the well-known technology, the subject-matter of claim 17 which cites claim 16 is obvious to the skilled person in the art, therefore claim 17 does not meet the criteria set out in the PC,F Article 33 (3), does not involve an inventive step.

The document Di discloses a device for switching network service (see the description page 8, line li-page 14, line 14; figure 4), which includes that: the user terminal switches to the target network from a source network; the service switch control unit of the network side judges whether the network would be switched. Di does not disclose such a feature that the network side unit separates the user terminal from the source network. However, this feature is well-known in the art. Based on Dl and the well-known technology, the subject-matter of claim 23 is obvious to the skilled person in the art, so claim 23 does not meet the criteria set out in the PCT Article 33 (3), does not involve an inventive step.

• Foam PCT/ISAJ237(Box No. V) (April 2007)

NSN677-1002,

WRITTEN OPINION OF THE international application No.

INTERNATIONAL SEARCHING AUTHORITY

PCT/CN2008/071.842

Sup*Inental Box

In case the space in any of the preceding boxes is not sufficient.

Continuation of: No. V

Based on the documents Dl, D2 and D3, the subject—matters of claims 25 and 30 are not obvious to the skilled

person in the art, so these claims meet the criteria set out in the PCT Article 33 (3), involve inventive step-s.

Based on the documents D1, D2 and D3, the subject-•matters of claims 3--15, 18-22, 24, 26-29 and claims 31-33 are not obvious to the skilled per8on in the art; so these claims meet, the criteria set out in the PCT Article 33 (3)i involVe inventive steps. Industrial applicability

There is no reason to doubt the industrial applicability of the invention, claims 1-33 meet the criteria set out in the PCT Article 33 (4).

Form PCUISAI237(Supplemenral Box) (April 2007)

NSN677-1002,


EFS ID: 10606030








Filer: John B. Conklin/Meghan Corbet



Receipt Date: 27-JUL-2011






File Listing:

Document Number


Multi Part /.zip

Pages (if appl.)

1 Transmittal Letter IDS_2.pdf

40069

no 4

a40e6eabead519e2f0cdflp7d7547e3691ad

efObd

Warnings:

Information:

NSN677-1002,

2 Information Disclosure Statement (IDS)

Form (5E308) 1449Form_2.pdf

31515

no 2

5e3304a3500a85c1d01557ae6149e1d1 bac

86136

Warnings:

Information:

This is not an USPTO supplied IDS fillable form

3 Foreign Reference EP_1713207_A1.pdf

919006

no 28

babel e288536642f4087636f73a63a3cdec2

032f

Warnings:

Information:

4 Foreign Reference EP_2007160_A1.pdf

558786

no 16

325a888c5698ff7a110a603411a9215a6c2a

765

Warnings:

Information:

5 Foreign Reference W0_2007024115_A1.pdf

823688

no 26

36069e4730fcd7797233c50e93433a337c6

d75f2

Warnings:

Information:

6 Foreign Reference CN_1881919_A.pdf

1240260

no 22

dd61edc111a30fcee4bd7446e1872729bcd

97f26

Warnings:

Information:

7 Non Patent Literature RU-OA1_2009142607.pdf

479049

no 11

84de686609665e45738c14de7d4a0576784

a4809

Warnings:

Information:

8 Non Patent Literature CN-OA1_2007101375688.pdf

1322546

no 21

26853330440c900d14f0ac645a8c2f75489d

4aeb

Warnings:

Information:

9 Non Patent Literature PCT-WrittenOpinion.pdf

4264093

no 4

155a5ad503ee1a54d58f4bd568d1182e6a2

1894d

Warnings:

Information:

10 Non Patent Literature EP-EESR_087838355.pdf

669795

no 13

52989662ced37737723d6aa924bea69a1b

ef6926

NSN677-1002,

Warnings:

Information:

11 Non Patent Literature 3GPPTS23060_Version810_Jun

e2008.pdf

2814157

no 259

22a7bba00259cb233edf0b0fdc9e1f70e9c3 5ca4

Warnings:

Information:

12 Non Patent Literature 3GPPTS23401_Version111.pdf

698905

no 78

53cf8b026adf138a3f030c544d8e3d77c2c6 cb42

Warnings:

Information:

13 Non Patent Literature 3GPPTS23402_Version110_Jun

e2007.pdf

720528

no 50

5ce29960916296877776de34a4fdb56cc58 382e2

Warnings:

Information:

14 Non Patent Literature 3GPPTS23402_Version120July _

2007.pdf

2277929

no 54

efd9eae4a8730c4e3b97694466aef8594167 63a1

Warnings:

Information:

15 Non Patent Literature 3GPPTS29213_Version800_May

2008.pdf

507687

no 65

d20c2684754ed360f55f99b5f55fe87edfd6 3279

Warnings:

Information:

16 Non Patent Literature

US-

ImageFileWrapper_12479216

pdf

19314895

no 421

7c7f87d4a0399bd27c9465faad1e4c1bd79 8c2c5

Warnings:

Information:


NSN677-1002,





NSN677-1002,


Patent Application No. 13/169,619

Confirmation No. 2286



TC/AU: 2617

Examiner: NGUYEN, David Q

Docket No.: HW708564 (Client Reference No. 81356140US16)

Customer No.: 77399


INFORMATION DISCLOSURE STATEMENT

Pursuant to 37 CFR 1.97 and 1.98, the references listed on the enclosed Form PTO-1449 and/or Substitute Form PTO-1449 ("Form 1449") are submitted for consideration by the Examiner in the examination of the above-identified patent application.

The full consideration of the references in their entirety by the Examiner is respectfully requested and encouraged. Also, it is respectfully requested that the references be entered into the record of the present application and that the Examiner initial the appropriate area on the enclosed Form 1449, thereby indicating the Examiner's consideration of each of the references.

The submission of the references listed on the Form 1449 is for the purpose of providing a complete record and is not a concession that the references listed thereon are prior art to the invention claimed in the patent application. The right is expressly reserved to establish an invention date earlier than the above-identified filing date in order to remove any reference submitted herewith as prior art should it be deemed appropriate to do so.

Further, the submission of the references is not to be taken as a concession that any reference represents art that is relevant or analogous to the claimed invention. Accordingly, the right to argue that any reference is not properly within the scope of prior art relevant to an examination of the claims in the above-identified application is also expressly reserved.

The Information Disclosure Statement is being filed:

within any one of the following time periods: (a) within three months of the filing date of a national application other than a continued prosecution application under 37 CFR 1.53(d); (b) within three months of the date of entry of the national stage as set forth in 37 CFR 1.491 of an international application; (c) before the mailing date

Page 1 of 4

NSN677-1002,

Application No. 13/169,619 Information Disclosure Statement

of a first Office Action on the merits; or (d) before the mailing of a first Office Action after the filing of a request for continued examination under 37 CFR 1.114.


❑ after (a), (b), (c) or (d) above, but before the mailing date of a final action under 37 CFR 1.113, a Notice of Allowance under 37 CFR 1.311, or an action that otherwise closes prosecution in the application, and includes one of:

❑ the Statement under 37 CFR 1.97(e) (see "Statement under 37 CFR 1.97(e)" below).


— or —

❑ the fee of $180 set forth in 37 CFR 1.17(p) (see "Fees" below).

❑ on or after the mailing date of a final action under 37 CFR 1.113 or a Notice of Allowance under 37 CFR 1.311, or an action that otherwise closes prosecution in the application, and on or before payment of the issue fee, and includes the Statement under 37 CFR 1.97(e) (see "Statement under 37 CFR 1.97(e)" below), and the fee of $180 as set forth in 37 CFR 1.17(p) (see "Fees" below).

❑ on or after the mailing date of a Notice of Allowance under 37 CFR 1.311, and on or before payment of the issue fee, and within thirty days of receiving each item of information contained in the Information Disclosure Statement, and includes the Statement under 37 CFR 1.704(d) (see "Statement under 37 CFR 1.704(d)" below), and the fee of $180 as set forth in 37 CFR 1.17(p) (see "Fees" below). NOTE: This is for original applications except applications for a design patent, filed on or after May 29, 2000, wherein a paper containing only an Information Disclosure Statement in compliance with 37 CFR 1.97 and 1.98 is being filed.

Citation to Other Patent Applications

❑ The following U.S. patent applications are hereby brought to the attention of the Examiner. The U.S. patent applications claim subject matter that may be considered by the Examiner to be similar to the subject matter claimed in the above-identified patent application. Accordingly, these U.S. patent applications and/or the prosecution pertaining thereto may include information considered to be material to the prosecution of the above-identified patent application. Since the Examiner has electronic access to the prosecution histories of these U.S. patent applications, copies of prosecution materials therefrom are not provided herewith, but will be promptly provided if the Examiner so desires and requests same.

Page 2 of 4

NSN677-1002,

Application No. 13/169,619

Information Disclosure Statement


U.S. APPLICATIONS U.S. FILING DATE Patented Pending Never Issued: Abandoned/Expired

1.

2. 3.

Copies of the References

• Copies of any U.S. patents and published patent applications that are listed on the accompanying Form 1449 are not enclosed herewith. Copies of any other references identified on the accompanying Form 1449 are enclosed herewith.

• For each reference not in the English language, attached is at least one of the following: (a) an English translation in whole or in part or (b) a concise statement of relevance in the form of, for example, an English language counterpart, an English-language abstract, or an English-language version of the search report or action by a foreign patent office in a counterpart foreign application indicating the degree of relevance found by the foreign office.

[El The references listed on the enclosed Form 1449 were previously identified in the parent application(s) of the present application, and copies of the references were furnished at that time. Accordingly, additional copies of the references are not submitted herewith, so as not to burden the file with duplicate copies of references. The Examiner is respectfully requested to carefully review the references in accordance with the requirements set out in the Manual of Patent Examining Procedure. In accordance with 37 CFR 1.98(d), the details of the parent application(s) relied upon for an earlier filing date under 35 USC 120 in which copies of the references were previously furnished are set out below:


U.S. APPLICATIONS U.S. FILING DATE Patented Pending Abandoned

1. 12/479,216 June 5, 2009 X 2. 3.

Statement under 37 CFR 1.97(e)

❑ The undersigned hereby states that each item of information contained in the Information Disclosure Statement was first cited in any communication from a foreign patent office in a counterpart foreign patent application not more than three months prior to the filing of the Information Disclosure Statement.

❑ The undersigned hereby states that no item of information contained in the Information Disclosure Statement was cited in a communication from a foreign patent office in a counterpart foreign patent application, and, to the knowledge of the undersigned after making reasonable inquiry, no item of information contained in the Information Disclosure Statement was known to any individual designated in

Page 3 of 4

NSN677-1002,

Application No. 13/169,619 Information Disclosure Statement

37 CFR 1.56(c) more than three months prior to the filing of the Information Disclosure Statement.

Statement under 37 CFR 1.704(d)

❑ The undersigned hereby states that each item of information contained in the Information Disclosure Statement was first cited in any communication from a foreign patent office in a counterpart application and that this communication was not received by any individual designated in 37 CFR 1.56(c) more than thirty days prior to the filing of the Information Disclosure Statement.

Fees

El No fee is owed by the applicant(s). ❑ Charge Deposit Account No. 12-1216 in the amount of $180.00 (37 CFR 1.17(p)).

Authorization to Charge Additional Fees

• If any additional fees are owed in connection with this communication, please charge Deposit Account No. 12-1216.

Instructions as to Overpayment

• Credit Account No. 12-1216. ❑ Refund

/John B. Conklin/ John B. Conklin, Reg. No. 30,369 LEYDIG, VOIT & MAYER, LTD. Two Prudential Plaza, Suite 4900 180 North Stetson Avenue Chicago, Illinois 60601-6731 (312) 616-5600 (telephone) (312) 616-5700 (facsimile)

Date:

Page 4 of 4

NSN677-1002,

ART UNIT

EXAMINER

NGUYEN, DAVID Q

PAPER NUMBER

2617

DATE MAILED: 08/08/2011

77399 7590 08/08/2011


UNITED STA I ES PA I ENT AND TRADEMARK OFFICE



NOTICE OF ALLOWANCE AND FEE(S) DUE




13/169,619 06/27/2011 Wenfu WU HW708564 2286

TITLE OF INVENTION: METHOD, SYSTEM, AND DEVICE FOR USER DETACHMENT WHEN A HANDOVER OR CHANGE OCCURS IN HETEROGENEOUS NETWORK

APPLN. TYPE

SMALL ENTITY

ISSUE FEE DUE I PUBLICATION FEE DUE PREV. PAID ISSUE FEE TOTAL FEE(S) DUE

DATE DUE

nonprovisional

NO $1510 $300 $0 $1810

11/08/2011

THE APPLICATION IDENTIFIED ABOVE HAS BEEN EXAMINED AND IS ALLOWED FOR ISSUANCE AS A PATENT. PROSECUTION ON THE MERITS IS CLOSED. THIS NOTICE OF ALLOWANCE IS NOT A GRANT OF PATENT RIGHTS. THIS APPLICATION IS SUBJECT TO WITHDRAWAL FROM ISSUE AT THE INITIATIVE OF THE OFFICE OR UPON PETITION BY THE APPLICANT. SEE 37 CFR 1.313 AND MPEP 1308.

THE ISSUE FEE AND PUBLICATION FEE (IF REQUIRED) MUST BE PAID WITHIN THREE MONTHS FROM THE MAILING DATE OF THIS NOTICE OR THIS APPLICATION SHALL BE REGARDED AS ABANDONED. THIS STATUTORY PERIOD CANNOT BE EXTENDED. SEE 35 U.S.C. 151. THE ISSUE FEE DUE INDICATED ABOVE DOES NOT REFLECT A CREDIT FOR ANY PREVIOUSLY PAID ISSUE FEE IN THIS APPLICATION. IF AN ISSUE FEE HAS PREVIOUSLY BEEN PAID IN THIS APPLICATION (AS SHOWN ABOVE), THE RETURN OF PART B OF THIS FORM WILL BE CONSIDERED A REQUEST TO REAPPLY THE PREVIOUSLY PAID ISSUE FEE TOWARD THE ISSUE FEE NOW DUE.

HOW TO REPLY TO THIS NOTICE:

I. Review the SMALL ENTITY status shown above.

If the SMALL ENTITY is shown as YES, verify your current SMALL ENTITY status:

A. If the status is the same, pay the TOTAL FEE(S) DUE shown above.

B. If the status above is to be removed, check box 5b on Part B -Fee(s) Transmittal and pay the PUBLICATION FEE (if required) and twice the amount of the ISSUE FEE shown above, or

If the SMALL ENTITY is shown as NO:

A. Pay TOTAL FEE(S) DUE shown above, or

B. If applicant claimed SMALL ENTITY status before, or is now claiming SMALL ENTITY status, check box 5a on Part B - Fee(s) Transmittal and pay the PUBLICATION FEE (if required) and 1/2 the ISSUE FEE shown above.

II. PART B - FEE(S) TRANSMITTAL, or its equivalent, must be completed and returned to the United States Patent and Trademark Office (USPTO) with your ISSUE FEE and PUBLICATION FEE (if required). If you are charging the fee(s) to your deposit account, section "4b" of Part B - Fee(s) Transmittal should be completed and an extra copy of the form should be submitted. If an equivalent of Part B is filed, a request to reapply a previously paid issue fee must be clearly made, and delays in processing may occur due to the difficulty in recognizing the paper as an equivalent of Part B.

III. All communications regarding this application must give the application number. Please direct all communications prior to issuance to Mail Stop ISSUE FEE unless advised to the contrary.

IMPORTANT REMINDER: Utility patents issuing on applications filed on or after Dec. 12, 1980 may require payment of maintenance fees. It is patentee's responsibility to ensure timely payment of maintenance fees when due.

Page 1 of 3 PTOL-85 (Rev. 02/11)

NSN677-1002,

PART B - FEE(S) TRANSMITTAL

Complete and send this form, together with applicable fee(s), to: Mail Mail Stop ISSUE FEE Commissioner for Patents P.O. Box 1450 Alexandria, Virginia 22313-1450

or Fax (571)-273-2885

INSTRUCTIONS: This form should be used for transmitting the ISSUE FEE and PUBLICATION FEE (if required). Blocks 1 through 5 should be completed where appropriate. All further correspondence including the Patent, advance orders and notification of maintenance fees will be mailed to the current correspondence address as indicated unless corrected below or directed otherwise in Block 1, by (a) specifying a new correspondence address; and/or (b) indicating a separate "FEE ADDRESS" for maintenance fee notifications.

CURRENT CORRESPONDENCE ADDRESS (Note: Use Block 1 for any change of address)

77399 7590 08/08/2011


Note: A certificate of mailing can only be used for domestic mailings of the Fee(s) Transmittal. This certificate cannot be used for any other accompanying papers. Each additional paper, such as an assignment or formal drawing, must have its own certificate of mailing or transmission.

Certificate of Mailing or Transmission I hereby certify that this Fee(s) Transmittal is being deposited with the United States Postal Service with sufficient postage for first class mail in an envelope addressed to the Mail Stop ISSUE FEE address above, or being facsimile transmitted to the USPTO (571) 273-2885, on the date indicated below.

(Depositor's name)

(Signature)

(Date)




13/169,619 06/27/2011 Wenfu WU HW708564 2286


APPLN. TYPE

SMALL ENTITY

ISSUE FEE DUE I PUBLICATION FEE DUE PREY. PAID ISSUE FEE TOTAL FEE(S) DUE

DATE DUE

nonprovisional

NO

$1510

$300

$0

$1810

11/08/2011

EXAMINER

ART UNIT

CLASS-SUBCLASS

NGUYEN, DAVID Q

2617

370-331000

1. Change of correspondence address or indication of "Fee Address" (37 CFR 1.363).

❑ Change of correspondence address (or Change of Correspondence Address form PTO/SB/122) attached.

❑ "Fee Address" indication (or "Fee Address" Indication form PTO/SB/47; Rev 03-02 or more recent) attached. Use of a Customer Number is required.

2. For printing on the patent front page, list

(1) the names of up to 3 registered patent attorneys or agents OR, alternatively,

(2) the name of a single firm (having as a member a registered attorney or agent) and the names of up to 2 registered patent attorneys or agents. If no name is listed, no name will be printed.

1

2

3

3. ASSIGNEE NAME AND RESIDENCE DATA TO BE PRINTED ON THE PATENT (print or type)

PLEASE NOTE: Unless an assignee is identified below, no assignee data will appear on the patent. If an assignee is identified below, the document has been filed for recordation as set forth in 37 CFR 3.11. Completion of this form is NOT a substitute for filing an assignment.

(A) NAME OF ASSIGNEE (B) RESIDENCE: (CITY and STATE OR COUNTRY)

Please check the appropriate assignee category or categories (will not be printed on the patent) : ❑ Individual ❑ Corporation or other private group entity ❑ Government

4a. The following fee(s) are submitted:

❑ Issue Fee

❑ Publication Fee (No small entity discount permitted)

❑ Advance Order - # of Copies

4b. Payment of Fee(s): (Please first reapply any previously paid issue fee shown above)

❑ A check is enclosed.

❑ Payment by credit card. Form PTO-2038 is attached.

❑ The Director is hereby authorized to charge the required fee(s), any deficiency, or credit any overpayment, to Deposit Account Number (enclose an extra copy of this form).

5. Change in Entity Status (from status indicated above)

❑ a. Applicant claims SMALL ENTITY status. See 37 CFR 1.27. ❑ b. Applicant is no longer claiming SMALL ENTITY status. See 37 CFR 1.27(g)(2).

NOTE: The Issue Fee and Publication Fee (if required) will not be accepted from anyone other than the applicant; a registered attorney or agent; or the assignee or other party in interest as shown by the records of the United States Patent and Trademark Office.

Authorized Signature Date

Typed or printed name Registration No.

This collection of information is required by 37 CFR 1.311. The information is required to obtain or retain a benefit by the public which is to file (and by the USPTO to process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.14. This collection is estimated to take 12 minutes to complete, including gathering, preparing, and submitting the completed application form to the USPTO. Time will vary depending upon the individual case. Any comments on the amount of time you require to complete this form and/or suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S. Patent and Trademark Office, U.S. Department of Commerce, P.O. Box 1450, Alexandria, Virginia 22313-1450. DO NOT SEND FEES OR COMPLETED FORMS TO THIS ADDRESS. SEND TO: Commissioner for Patents, P.O. Box 1450, Alexandria, Virginia 22313-1450. Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it displays a valid OMB control number.

PTOL-85 (Rev. 02/11) Approved for use through 08/31/2013. OMB 0651-0033 U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE

NSN677-1002,

ART UNIT

EXAMINER

NGUYEN, DAVID Q

PAPER NUMBER

2617

DATE MAILED: 08/08/2011

77399 7590 08/08/2011


UNITED STA IES PA PENT AND TRADEMARK OEEICE






13/169,619

06/27/2011

Wenfu WU

HW708564

2286

Determination of Patent Term Adjustment under 35 U.S.C. 154 (b) (application filed on or after May 29, 2000)

The Patent Term Adjustment to date is 0 day(s). If the issue fee is paid on the date that is three months after the mailing date of this notice and the patent issues on the Tuesday before the date that is 28 weeks (six and a half months) after the mailing date of this notice, the Patent Term Adjustment will be 0 day(s).

If a Continued Prosecution Application (CPA) was filed in the above-identified application, the filing date that determines Patent Term Adjustment is the filing date of the most recent CPA.

Applicant will be able to obtain more detailed information by accessing the Patent Application Information Retrieval (PAIR) WEB site (http://pair.uspto.gov).

Any questions regarding the Patent Term Extension or Adjustment determination should be directed to the Office of Patent Legal Administration at (571)-272-7702. Questions relating to issue and publication fee payments should be directed to the Customer Service Center of the Office of Patent Publication at 1-(888)-786-0101 or (571)-272-4200.

Page 3 of 3 PTOL-85 (Rev. 02/11)

NSN677-1002,




1. The information on this form will be treated confidentially to the extent allowed under the Freedom of Information Act (5 U.S.C. 552) and the Privacy Act (5 U.S.0 552a). Records from this system of records may be disclosed to the Department of Justice to determine whether disclosure of these records is required by the Freedom of Information Act.



4. A record in this system of records may be disclosed, as a routine use, to a contractor of the Agency having need for the information in order to perform a contract. Recipients of information shall be required to comply with the requirements of the Privacy Act of 1974, as amended, pursuant to 5 U.S.C. 552a(m).




8. A record from this system of records may be disclosed, as a routine use, to the public after either publication of the application pursuant to 35 U.S.C. 122(b) or issuance of a patent pursuant to 35 U.S.C. 151. Further, a record may be disclosed, subject to the limitations of 37 CFR 1.14, as a routine use, to the public if the record was filed in an application which became abandoned or in which the proceedings were terminated and which application is referenced by either a published application, an application open to public inspection or an issued patent.


NSN677-1002,

Notice of Allowability

Application No.

13/169,619

Applicant(s)

WU ET AL. Examiner

DAVID Q. NGUYEN

Art Unit

2617

-- The MAILING DATE of this communication appears All claims being allowable, PROSECUTION ON THE MERITS IS herewith (or previously mailed), a Notice of Allowance (PTOL-85) NOTICE OF ALLOWABILITY IS NOT A GRANT OF PATENT RIGHTS. of the Office or upon petition by the applicant. See 37 CFR 1.313

on the (OR REMAINS) or other

and MPEP

been received.

been received

of this

Note reason(s)

be submitted.

Patent

Amendment

header

FOR THE

This

35 U.S.C.

cover sheet with the correspondence address-- CLOSED in this application. If not included

appropriate communication will be mailed in due course. THIS application is subject to withdrawal from issue at the initiative

1308.

§ 119(a)-(d) or (f).

in Application No. .

1. @ This communication is responsive to 06/27/2011.

2. @ The allowed claim(s) is/are 1-14.

3. @ Acknowledgment is made of a claim for foreign priority under

a) A All b) ■ Some*c) ■ None of the:

1. A Certified copies of the priority documents have

2. ■ Certified copies of the priority documents have

of this communication

should

of BIOLOGICAL

have been received in this national stage application from the

to file a reply complying with the requirements application.

the attached EXAMINER'S AMENDMENT or NOTICE OF why the oath or declaration is deficient.

Drawing Review ( PTO-948) attached

/ Comment or in the Office action of

be written on the drawings in the front (not the back) of according to 37 CFR 1.121(d).

MATERIAL must be submitted. Note the DEPOSIT OF BIOLOGICAL MATERIAL.

3. ■ Copies of the certified copies of the priority documents

International Bureau (PCT Rule 17.2(a)).

* Certified copies not received: .

Applicant has THREE MONTHS FROM THE "MAILING DATE" noted below. Failure to timely comply will result in ABANDONMENT THIS THREE-MONTH PERIOD IS NOT EXTENDABLE.

4. ❑ A SUBSTITUTE OATH OR DECLARATION must be submitted. INFORMAL PATENT APPLICATION (PTO-152) which gives

5. ❑ CORRECTED DRAWINGS ( as "replacement sheets") must

(a) ■ including changes required by the Notice of Draftsperson's

1) ■ hereto or 2) ■ to Paper No./Mail Date .

(b) ■ including changes required by the attached Examiner's

Paper No./Mail Date .

Identifying indicia such as the application number (see 37 CFR 1.84(c)) each sheet. Replacement sheet(s) should be labeled as such in the

6. ❑ DEPOSIT OF and/or INFORMATION about the deposit attached Examiner's comment regarding REQUIREMENT

Attachment(s) 1. A Notice of References Cited (PTO-892) 5. ■ Notice of Informal Patent Application

2. ■ Notice of Draftperson's Patent Drawing Review (PTO-948) 6. Interview Summary (PTO-413), 08/02/2011 . Paper No./Mail Date

3. A Information Disclosure Statements (PTO/SB/08), 7. Examiner's Amendment/Comment Paper No./Mail Date

4. ■ Examiners Comment Regarding Requirement for Deposit 8. Examiner's Statement of Reasons for Allowance of Biological Material

9. ■ Other .

/DAVID Q NGUYEN/ Primary Examiner, Art Unit 2617

U.S. Patent and Trademark Office

PTOL-37 (Rev. 08-06)

Notice of Allowability Part of Paper No./Mail Date 20110803

NSN677-1002,

Interview Summary

Application No.

13/169,619

Applicant(s)

WU ET AL.

Examiner

DAVID Q. NGUYEN

Art Unit

2617

All participants (applicant, applicant's representative, PTO personnel):

(1) DAVID Q. NGUYEN. (3)_.

(2) John B. Conklin. (4)

Date of Interview: 02 August 2011.

Type: a)

Exhibit shown If Yes,

c)❑

brief

Telephonic b)❑ Video Conference Personal [copy given to: 1)❑ applicant 2)❑ applicant's representative]

or demonstration conducted: d)❑ Yes e)❑ No. description: .

Claim(s) discussed: All claims.

Identification of prior art discussed: .

Agreement with respect to the claims f)r

Substance of Interview including description reached, or any other comments: Applicant

was reached. g)❑ was not reached. h)❑ N/A.

of the general nature of what was agreed to if an agreement was has amended application as indicated in Examiner's Amendment.

(A fuller description, if necessary, and a copy of the amendments which the examiner agreed would render the claims allowable, if available, must be attached. Also, where no copy of the amendments that would render the claims allowable is available, a summary thereof must be attached.)

THE FORMAL WRITTEN REPLY TO THE LAST OFFICE ACTION MUST INCLUDE THE SUBSTANCE OF THE INTERVIEW. (See MPEP Section 713.04). If a reply to the last Office action has already been filed, APPLICANT IS GIVEN A NON-EXTENDABLE PERIOD OF THE LONGER OF ONE MONTH OR THIRTY DAYS FROM THIS INTERVIEW DATE, OR THE MAILING DATE OF THIS INTERVIEW SUMMARY FORM, WHICHEVER IS LATER, TO FILE A STATEMENT OF THE SUBSTANCE OF THE INTERVIEW. See Summary of Record of Interview requirements on reverse side or on attached sheet.



PTOL-413 (Rev. 04-03)

Interview Summary

Paper No. 20110803

NSN677-1002,

Summary of Record of Interview Requirements

Manual of Patent Examining Procedure (MPEP), Section 713.04, Substance of Interview Must be Made of Record A complete written statement as to the substance of any face-to-face, video conference, or telephone interview with regard to an application must be made of record in the application whether or not an agreement with the examiner was reached at the interview.

Title 37 Code of Federal Regulations (CFR) § 1.133 Interviews Paragraph (b)

In every instance where reconsideration is requested in view of an interview with an examiner, a complete written statement of the reasons presented at the interview as warranting favorable action must be filed by the applicant. An interview does not remove the necessity for reply to Office action as specified in §§ 1.111, 1.135. (35 U.S.C. 132)

37 CFR §1.2 Business to be transacted in writing. All business with the Patent or Trademark Office should be transacted in writing. The personal attendance of applicants or their attorneys or agents at the Patent and Trademark Office is unnecessary. The action of the Patent and Trademark Office will be based exclusively on the written record in the Office. No attention will be paid to any alleged oral promise, stipulation, or understanding in relation to which there is disagreement or doubt.

The action of the Patent and Trademark Office cannot be based exclusively on the written record in the Office if that record is itself incomplete through the failure to record the substance of interviews.

It is the responsibility of the applicant or the attorney or agent to make the substance of an interview of record in the application file, unless the examiner indicates he or she will do so. It is the examiner's responsibility to see that such a record is made and to correct material inaccuracies which bear directly on the question of patentability.

Examiners must complete an Interview Summary Form for each interview held where a matter of substance has been discussed during the interview by checking the appropriate boxes and filling in the blanks. Discussions regarding only procedural matters, directed solely to restriction requirements for which interview recordation is otherwise provided for in Section 812.01 of the Manual of Patent Examining Procedure, or pointing out typographical errors or unreadable script in Office actions or the like, are excluded from the interview recordation procedures below. Where the substance of an interview is completely recorded in an Examiners Amendment, no separate Interview Summary Record is required.

The Interview Summary Form shall be given an appropriate Paper No., placed in the right hand portion of the file, and listed on the "Contents" section of the file wrapper. In a personal interview, a duplicate of the Form is given to the applicant (or attorney or agent) at the conclusion of the interview. In the case of a telephone or video-conference interview, the copy is mailed to the applicant's correspondence address either with or prior to the next official communication. If additional correspondence from the examiner is not likely before an allowance or if other circumstances dictate, the Form should be mailed promptly after the interview rather than with the next official communication.

The Form provides for recordation of the following information: —Application Number (Series Code and Serial Number) —Name of applicant —Name of examiner — Date of interview —Type of interview (telephonic, video-conference, or personal) —Name of participant(s) (applicant, attorney or agent, examiner, other PTO personnel, etc.) —An indication whether or not an exhibit was shown or a demonstration conducted —An identification of the specific prior art discussed — An indication whether an agreement was reached and if so, a description of the general nature of the agreement (may be by

attachment of a copy of amendments or claims agreed as being allowable). Note: Agreement as to allowability is tentative and does not restrict further action by the examiner to the contrary.

—The signature of the examiner who conducted the interview (if Form is not an attachment to a signed Office action)

It is desirable that the examiner orally remind the applicant of his or her obligation to record the substance of the interview of each case. It should be noted, however, that the Interview Summary Form will not normally be considered a complete and proper recordation of the interview unless it includes, or is supplemented by the applicant or the examiner to include, all of the applicable items required below concerning the substance of the interview.

A complete and proper recordation of the substance of any interview should include at least the following applicable items: 1) A brief description of the nature of any exhibit shown or any demonstration conducted, 2) an identification of the claims discussed, 3) an identification of the specific prior art discussed, 4) an identification of the principal proposed amendments of a substantive nature discussed, unless these are already described on the

Interview Summary Form completed by the Examiner, 5) a brief identification of the general thrust of the principal arguments presented to the examiner,

(The identification of arguments need not be lengthy or elaborate. A verbatim or highly detailed description of the arguments is not required. The identification of the arguments is sufficient if the general nature or thrust of the principal arguments made to the examiner can be understood in the context of the application file. Of course, the applicant may desire to emphasize and fully describe those arguments which he or she feels were or might be persuasive to the examiner.)

6) a general indication of any other pertinent matters discussed, and 7) if appropriate, the general results or outcome of the interview unless already described in the Interview Summary Form completed by

the examiner. Examiners are expected to carefully review the applicant's record of the substance of an interview. If the record is not complete and

accurate, the examiner will give the applicant an extendable one month time period to correct the record.

Examiner to Check for Accuracy

If the claims are allowable for other reasons of record, the examiner should send a letter setting forth the examiner's version of the statement attributed to him or her. If the record is complete and accurate, the examiner should place the indication, "Interview Record OK" on the paper recording the substance of the interview along with the date and the examiner's initials.

NSN677-1002,

Application/Control Number: 13/169,619 Page 2

Art Unit: 2617

DETAILED ACTION

EXAMINER'S AMENDMENT

1. An examiner's amendment to the record appears below. Should the changes and/or

additions be unacceptable to applicant, an amendment may be filed as provided by 37 CFR

1.312. To ensure consideration of such an amendment, it MUST be submitted no later than the

payment of the issue fee.

2. Authorization for this examiner's amendment was given in a telephone interview with

John B. Conklin on 08/02/2011.

3. The application has been amended as follow:

8 (Currently Amended). A mobility management entity, configured to: receive a delete

bearer request sent by a serving gateway (GW) of a 3GPP network when a handover from

the 3GPP network to a non-3GPP network occurs, wherein the delete bearer request

carries a cause information element (IE) which indicates a user equipment handovers

from the 3GPP network to the non-3GPP network;

delete bearer resources of the user equipment; and


deleted.

9 (Currently Amended). The mobility management entity according to claim 8, wherein

the cause IE is set to "UE's accessing RAT changed from a 3GPP network to a non-3GPP

network".


the delete bearer request is sent from a packet data network gateway to the mobility

NSN677-1002,


Art Unit: 2617

management entity via the serving gateway, wherein the cause IE is set to "UE's

accessing RAT changed from a 3GPP network to a non-3GPP network" by the packet

data network gateway.


the mobility management entity is configured to detach the UE from the 3GPP network

without sending a detach request message to the UE.


the mobility management entity is configured to detach the UE from the 3GPP network if

a terminal capability of the UE is single radio capability.



access policy information of an operator is single radio access.



a terminal capability of the UE is dual radio capability and access policy information of

an operator is single radio access; or if the terminal capability of the UE is single radio

capability and the access policy information of the operator is dual radio access; or if the

terminal capability of the UE is the single radio capability and the access policy


Allowable Subject Matter

4. Claims 1-14 are allowed.

5. The following is an examiner's statement of reasons for allowance:

NSN677-1002,


Art Unit: 2617

Regarding independent claims 1 and 8, Savolainen et al. (US 2009/0232022 Al);

Vesterinen et al. (US 2008/0188223 Al); Faccin (US 2008/0320149 Al); and Zao et al. (US

2009/0238207 Al) all disclose a mobility management entity, configured to: receive a delete

bearer request sent by a serving gateway (GW) of a 3GPP network when a handover from the

3GPP network to a non-3GPP network occurs, wherein the delete bearer request carries a cause

information element (IE) which indicates a user equipment handovers from the 3GPP network to

the non-3GPP network; the MME sends bearer request message to the gateway servers to delete

bearer resources; the serving gateway deletes bearer resources of the user equipment. However,

the above prior arts of record fail to disclose or render obvious deleting, by the MME, bearer

resources of the user equipment; and detaching, by the MME, the UE from the 3GPP network

when all the bearer resources of the UE are deleted as specified in the claims. Therefore, they are

allowable

Claims 2-7 depend on claim 1. Therefore, they are allowable.

Claims 9-14 depend on claim 8. Therefore, they are allowable.

6. Any comments considered necessary by applicant must be submitted no later than the

payment of the issue fee and, to avoid processing delays, should preferably accompany the issue

fee. Such submissions should be clearly labeled "Comments on Statement of Reasons for

Allowance."

Conclusion

7. Any inquiry concerning this communication or earlier communications from the

examiner should be directed to DAVID Q. NGUYEN whose telephone number is (571)272-

7844. The examiner can normally be reached on 8:30AM-5:30PM.

NSN677-1002,


Art Unit: 2617

If attempts to reach the examiner by telephone are unsuccessful, the examiner's

supervisor, Jinsong Hu can be reached on (571)272-3965. The fax phone number for the

organization where this application or proceeding is assigned is 571-273-8300.

Information regarding the status of an application may be obtained from the Patent

Application Information Retrieval (PAIR) system. Status information for published applications

may be obtained from either Private PAIR or Public PAIR. Status information for unpublished

applications is available through Private PAIR only. For more information about the PAIR

system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR

system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would

like assistance from a USPTO Customer Service Representative or access to the automated

information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.


NSN677-1002,

Notice of References Cited

Application/Control No.

13/169,619

Applicant(s)/Patent Under Reexamination WU ET AL.

Examiner

DAVID Q. NGUYEN

Art Unit

2617 Page 1 of 1


* Document Number Country Code-Number-Kind Code

Date MM-YYYY Name Classification

* A US-2009/0238207 09-2009 Zhao et al. 370/468

* B US-2008/0320149 12-2008 Faccin, Stefano 709/228

* C US-2008/0188223 08-2008 Vesterinen et al. 455/436

* D US-2009/0232022 09-2009 Savolainen et al. 370/254

E US-

F US-

G US-

H US-

I US-

j US-

K US-

L US-

M US-


* Document Number Country Code-Number-Kind Code

Date MM-YYYY Country Name Classification

N

0

P

Q

R

S

T

NON-PATENT DOCUMENTS

* Include as applicable: Author, Title Date, Publisher, Edition or Volume, Pertinent Pages)

U

V

W

X

*A copy of th's reference is not being furnished with this Office action. (See MPEP § 707.05(a).) Dates in MM YYYY format are publication dates. Classifications may be US or foreign.


PTO-892 (Rev. 01-2001)

Notice of References Cited

Part of Paper No. 20110803

NSN677-1002,

111

Index

111 1

of

11111111

Claims

111 11


13169619

Applicant(s)/Patent Under Reexamination

WU ET AL.

Examiner

DAVID Q NGUYEN

Art Unit

2617

A Appeal

0 Objected

N Non-Elected

Interference

Rejected

Cancelled

Allowed

Restricted

in the same order as presented by applicant R.1.47 • Claims renumbered • CPA • T.D. •

CLAIM DATE

Final Original 08/03/2011

1 1 =

2 2 =

3 3 =

4 4 =

5 5 =

6 6 =

7 7 =

8 8 =

9 9 =

10 10 =

11 11 =

12 12 =

13 13 =

14 14 =

U.S. Patent and Trademark Office Part of Paper No.: 20110803

NSN677-1002,

Issue

111 111 1 11111111

Classification

111 11


13169619


WU ET AL.

Examiner

DAVID Q NGUYEN

Art Unit

2617

ORIGINAL INTERNATIONAL CLASSIFICATION

CLASS SUBCLASS CLAIMED NON-CLAIMED

370 331 H 0 4 W 36 / 00 (2009.01.01)

CROSS REFERENCE(S)

CLASS SUBCLASS (ONE SUBCLASS PER BLOCK)

370 468 254 328 352

455 422.1 435 436

Claims renumbered in the same order as presented by applicant CPA M M • T.D. M R.1.47

Final Original Final Original Final Original Final Original Final Original Final Original Final Original Final Original

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

NONE

(Assistant Examiner) (Date)

Total Claims Allowed:

14

/DAVID Q NGUYEN/ Primary Examiner.Art Unit 2617

(Primary Examiner)

08/03/2011

(Date)

O.G. Print Claim(s)

1

O.G. Print Figure

1


Part of Paper No. 20110803

NSN677-1002,

111 111 1

Search

11111111

Notes

111 11


13169619


WU ET AL.

Examiner

DAVID Q NGUYEN

Art Unit

2617

SEARCHED

Class Subclass Date Examiner 370 331 08/03/2011 DN 370 328 08/03/2011 DN 370 352 08/03/2011 DN 370 468 08/03/2011 DN 455 422.1 08/03/2011 DN 455 436 08/03/2011 DN 370 254 08/03/2011 DN

SEARCH NOTES

Search Notes Date Examiner Text search

08/03/2011 DN

INTERFERENCE SEARCH

Class Subclass Date Examiner Text search

08/03/2011 DN

/DAVID Q NGUYEN/ Primary Examiner.Art Unit 2617


Part of Paper No.. 20110803

NSN677-1002,

EAST Search History

EAST Search History

EAST Search History (Prior Art)

Ref #

Hits Search Query DBs Default Operator

Plurals Time Stamp

L1 4 (("20090286527") or ("20060153124") or ("20060146803") or ("20100135245")).PN.

US-PGPUB; USPAT; USOCR

OR OFF 2011/08/03 17:52

S1 1 ("20090097454").PN. USPAT; USOCR

US-PGPUB; OR OFF 2011/08/02 14:18

S2

—:

estimat$3 with (mobile adj phone mobile adj device wireless adj device wireless adj phone wireless adj equipment) with cell with load

US-PGPUB; USPAT; USOCR; FPRS; EPO; JPO; DERWENT; IBMTDB

OR OFF 2011/08/02 14:50

S3 S3 0 count$3 with (mobile adj phone mobile adj device wireless adj device wireless adj phone wireless adj equipment user adj terminal) with number with message same load IBM TDB

US-PGPUB; USPAT; USOCR; FPRS; EPO; JPO; DERWENT;

OR OFF 2011/08/02 14:53

S4 count$3 with (mobile adj phone mobile adj device wireless adj device wireless adj phone wireless adj equipment user adj terminal) with number with message

US-PGPUB; USPAT; USOCR; FPRS; EPO; JPO; DERWENT; I BM_TDB

OR OFF 2011/08/02 14:53

S5 S5 3 estimat$3 with (mobile adj phone mobile adj device wireless adj device wireless adj phone wireless adj equipment user adj terminal) with cell with load IBM TDB


OR OFF 2011/08/02 14:53

S6

...._ ,.:

16determin$3 with (mobile adj phone mobile adj device wireless adj device wireless adj phone wireless adj equipment user adj terminal) with cell with load

US-PGPUB; USPAT; USOCR; FPRS; EPO; JPO; DERWENT; IBM_TDB

OR OFF 2011/08/02 14:54

S7 S7 1 count$3 with (mobile adj phone mobile adj device wireless adj device wireless adj phone wireless adj equipment user adj terminal) with cell with load IBM TDB


OR OFF 2011/08/02 15:12

S8 53 (MME MMNE) same (delet$3 eras$3 disconnect$3) same resource

US-PGPUB; USPAT; USOCR; FPRS; EPO; JPO; DERWENT; I BM_TDB

OR ON 2011/08/03 12:53

S9 S9 22 (MME MMNE) same (detach$3) same resource

US-PGPUB; USPAT; USOCR; FPRS; EPO;

OR ON 2011/08/03 12:54

file:///Cl/Users/dnguyen17/Documents/e-Red%20Folder/13169619/EASTSearchHistory.13169619_AccessibleVersion.htm[8/3/2011 5:59:09 PM]

NSN677-1002,

EAST Search History

JPO; DERWENT; IBM TDB

S10 9 S8 and S9 US- PGPUB; OR ON 2011/08/03 USPAT; USOCR; 12:54 FPRS; EPO; JPO; DERWENT;

IBM TDB

S11 1 ( "20080320149" ) . PN. US- PGPUB; OR OFF 2011/08/03 USPAT; USOCR 13:02

8/ 3/2011 5:59:04 PM

file:///Cl/Users/dnguyen17/Documents/e-Red%20Folder/13169619/EASTSearchHistory.13169619_AccessibleVersion.htm[8/3/2011 5:59:09 PM]

NSN677-1002,





Complete if Known Application Number

Filing Date June 27, 2011 First Named Inventor WU, Wenfu Group Art Unit

Examiner Name



Examiner Initials

Doc. No.




Kind Code

A A 2009/0286527 Al Cheon et al. November 19, 2009 A B 2006/0153124 Al Kant et al. July 13, 2006 A C 2006/0146803 Al Bae et al. July 6, 2006 A D 2010/0135245 Al Zhu et al. June 3, 2010


Examiner Initials

Doc. No.


Name of Patentee or Applicant Date of

Publication Translation * Office


Kind Code


Examiner Initials

Doc. No.


Translation *

A E

"3GPP TS 23.401 — 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; GPRS enhancements for E-UTRAN access (Release 8)," July 2007, Version 1.1.0, 3rd Generation Partnership Project, Valbonne, France.

Examiner Signature /David Nguyen/ Date Considered 08/03/2011 * If the reference is not in English, then at least one of the following is provided: (a) an English translation in whole or in part or (b) a concise statement

of relevance in the form of, for example, an English language counterpart, an English-language abstract, or an English-language version of the search report or action by a foreicn patent office in a counterpart foreign application indicatingthe decree of relevance found by the foreicn office.

ALL 'REFERENCES CONSIDERED EXCEP WHERE LINED TH'ROUGH. /TIN,/

NSN677-1002,

of 1

UNIIED STATES PATENT AND TRADEMARK OFFICE



BIB DATA SHEET CONFIRMATION NO. 2286

SERIAL NUMBER

13/169,619

FILING or 371(c) DATE

06/27/2011

RULE

CLASS

455

GROUP ART UNIT

2617

ATTORNEY DOCKET NO.

HW708564

APPLICANTS Wenfu WU, Shanghai, CHINA; Weihua HU, Shanghai, CHINA; Shanhan WANG, Shanghai, CHINA;

** CONTINUING DATA ************************* This application is a CON of 12/479,216 06/05/2009

which is a CON of PCT/CN2008/071842 07/31/2008

** FOREIGN APPLICATIONS ************************* CHINA 200710137568.8 08/07/2007

** IF REQUIRED, FOREIGN FILING LICENSE GRANTED ** 06/29/2011

Foreign Priority claimed 'Yes U No

35 USG 119(a-d) conditions met V Yes U No

Verified and /DAVID Q NGUYEN/

V rdYld?c=ic'e

DN

STATE OR COUNTRY

CHINA

SHEETS DRAWINGS

12

TOTAL CLAIMS

14

INDEPENDENT CLAIMS

2 Acknowledged Examiners Signature Initials

ADDRESS

Leydig, Voit & Mayer, Ltd (for Huawei Technologies Co., Ltd) Two Prudential Plaza Suite 4900 180 North Stetson Avenue Chicago, IL 60601 UNITED STATES

TITLE


FILING FEE RECEIVED

1090

FEES: Authority has been given in Paper

No. to charge/credit DEPOSIT ACCOUNT

0 All Fees

0 1.16 Fees (Filing)

0 1.17 Fees (Processing Ext. of time) 0 1.18 Fees (Issue) No. for following:

0 Other

0 Credit

BIB (Rev. 05/07).

NSN677-1002,







OLU.S. PATENT DOCUMENTS

Examiner Initials

Doc. No.




Kind Code

A F 2008/0304454 Al Zhong et al. December 11, 2008


Examiner Initials

Doc. No.


Name of Patentee or Applicant Date of Publication Translation* Office Application or

Patent Number Kind Code

A G EP 1713207 Al Huawei Tech. Co., Ltd. October 18, 2006 A H EP 2007160 Al Nokia Siemens Networks Oy December 24, 2008

A I WO 2007/024115 Al Electronics and Telecommunications Research Institute

March 1, 2007

A J WO 2006/029663 Al Matasushita Electric Inc. Co., Ltd. March 23, 2006 A K WO 2006/088331 Al LG Electronics Inc. August 24, 2006 A L CN 1881919 A Huawei Tech. Co., Ltd. December 20, 2006 (b) A M CN 1878389 A Huawei Tech. Co., Ltd. December 13, 2006 (b)


Examiner Initials

Doc. No.


Translation *

A N 1St Office Action in corresponding Russian Application No. 2009142607 (July 31, 2008).

(a)

A 0 1st Office Action in corresponding Chinese Application No. 200710137568.8 (July 17, 2009).

(a)

A P Written Opinion of the International Searching Authority in corresponding PCT Application No. PCT/CN2008/071842 (November 20, 2008).

A Q International Search Report in corresponding PCT Application No. PCT/CN2008/071842 (November 20, 2008).

A R Extended European Search Report in corresponding European Application No. 08783835.5 (February 24, 2010).

A S

"3GPP TS 23.060 - 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS); Service description; Stage 2 (Release 8)," June 2008, Version 8.1.0, 3rd Generation Partnership Project, Valbonne, France.

AT "3GPP TS 23.401 - 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; GPRS enhancements for E-UTRAN access (Release 8)," Version 1.1.1, 3rd Generation Partnership Project, Valbonne, France.

A U

"3GPP TS 23.402 — 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture Enhancements for non-3GPP accesses (Release 8)," June 2007, Version 1.1.0, 3rd Generation Partnership Project, Valbonne, France.

A V

"3GPP TS 23.402 — 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture Enhancements for non-3GPP accesses (Release 8)," July 2007, Version 1.2.0, 3rd Generation Partnership Project, Valbonne, France.

Examiner Signature il d N avi guyen / Date Considered 08/03/2011 " If the reference is not in English, then at least one of the following is provided: (a) an English translation in whole or in part or (b) a concise statement



NSN677-1002,








Examiner Initials

Doc. No.


Translation "

A W

"3GPP TS 29.213 - 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control signalling flows and QoS parameter mapping; (Release 8)," May 2008, Version 8.0.0, 3rd Generation Partnership Project, Valbonne, France.

AX Image File Wrapper in corresponding US Application No. 12/479,216 (July 27, 2011).

Examiner Signature /David Nguyen/ Date Considered 08/03/2011 " If the reference is not in English, then at least one of the following is provided: (a) an English translation in whole or in part or (b) a concise statement



NSN677-1002,


Patent Application No. 13/169,619




TC/AU: 2617

Examiner: NGUYEN, David Q

Docket No.: 1-1W708564 (Client Reference No. 81356140US16)

Customer No.: 77399


APPLICANTS' INTERVIEW SUMMARY

Applicants thank Examiner Nguyen for the courtesy of conducting an interview on

August 2, 2011. The attendees included Examiner Nguyen and Applicants' representative John

Conklin. The discussion focused on the amendment proposed by the Examiner regarding claim

8 and its dependent claims. Applicants agreed to amend the claims as suggested by the

Examiner.


. Conklin, Reg. o. 0,369 LE DIG, VOIT & MAYER, LTD. T • Prudential Plaza, Suite 4900 180 North Stetson Avenue Chicago, Illinois 60601-6731 (312) 616-5600 (telephone) (312) 616-5700 (facsimile)

Date: August 18, 2011

NSN677-1002,


EFS ID: 10768176








Filer: John B. Conklin/Leanna Bultema



Receipt Date: 18-AUG-2011






File Listing:

Document Number


Multi Part /.zip

Pages (if appl.)

1 Applicant summary of interview with

examiner InterviewSummary.pdf

37017

no 1

6c7c3f0e3253fee9e46e41a2a7ff638ce9353

a39

Warnings:

Information:

NSN677-1002,

Total Files Size (in bytes) 37017





NSN677-1002,

Authorized Signature Date August 29, 2011

Registration No. 5 8, 5 7 9 Typed or printed name John K. Winn

(Deponioesimoc)

(Signature)

(Date)

Note: A certificate of mailing can only be used for domestic mailings of the Fee(s) Transmittal. This certificate cannot be used for any other accompanying papers. Each additional paper, such as an assignment or formal drawing, must have its own certificate of mailing or transmission.

Certificate of Mailing or Transmission I hereby certify that this Fee(s) Transmittal is being deposited with the United States Postal Service with sufficient postage for first class mail in an envelope addressed to the Mail Stop ISSUE FEE address above, or being facsimile transmitted to the USPTO (571) 273-2885, on the date indicated below.

PART B - FEE(S) TRANSMITTAL

Complete and send this form, together with applicable fee(s), to: Mail Mail Stop ISSUE FEE Commissioner for Patents P.O. Box 1450 Alexandria, Virginia 22313-1450

or Fax (571)-273-2885

INSTRUCTIONS: This form should he used for transmitting the ISSUE FEE and PUBLICATION FEE (if required). Blocks 1 through 5 should he completed where appropriate. All further correspondence. including the Patent, advance orders and notification of maintenance fees will be mailed to the current correspondence address as indicated unless corrected below or directed otherwise in Block I, by (a) specifying a new correspondence address; and/or (b) indicating a separate "FEE ADDRESS" for maintenance fee notifications.

CURRENT CORRESPONDENCE ADORES. S (Note: Use Block l for any change of

77399 7590 08/08/20L1 Leydig, Voit & Mayer, Ltd (for Huawei Technologies Co., Ltd) Two Prudential Plaza Sui to 4900 180 North Stetson Avenue Chicago, IL 60601

APPLICATION NO. I FILING DATE


IATTORNEY DOCKET NO. CONFIRMATION NO.

13/169,619 06/27/2011 Wenfu WU 11W708564 2286


APPLN. TYPE

SMALL ENTITY I ISSUE FEE DUE IPL13LICATION FEE DUE PREY. PAID ISSUE FEE TOTAL FEE(S) DLE I DATE DUE

nonprovisional

NO

$1510

S300

$0

$1810

11/08/2011

EXAMINER

ART UNIT

CLASS-SUBCLASS

NGUYEN, DAVID Q

2.617

370-331000

1. Change of correspondence address or indication of "Fee Address- (37 CFR 1.363).

[:1,1 Change of correspondence address (or Change of Correspondence Address form PTO/SB/122) attached.

0 "Fee Address" indication (or "Fee Address" Indication form PTO/SB/47; Rev 03-02 or more recent) attached. Use of a Customer Number is required.

2. For printing on the patent front page, list

(1) the names of up to 3 registered patent attorneys or agents OR, alternatively,

(2) the name of a single firm (having as a member a registered attorney or agent) and the names of up to 2 registered patent attorneys or agents. If no name is listed, no name will be printed.

1 Leydig, Voit & Mayer, Ltd.

2

3

3. ASSIGNEE NAME AND RESIDENCE DATA TO BE PRINTED ON THE PATENT (print or type)

PLEASE NOTE; Unless an assignee is identified below, no assignee data will appear on the patent. If an assignee is identified below, the document has been filed for recordation as set forth in' 7 CFR 3.11. Completion of this form is NOT a substitute for filing an assignment.

(B) RESIDENCE: (CITY and STATE OR COUNTRY)

Huawei Technologies Co., Ltd. Shenzhen, China

Please check the appropriate assignee category or categories (will not be printed on the patent) : 0 Individual la Corporation or other private group entity Zi Government

4a. The following fee(s) are submitted: Ell Issue Fee

Publication Fee (No small entity discount permitted)

Advance Order - 4/ of Copies

46. Payment of Fee(s): (Please first reapply any previously paid issue fee shown above)

❑ A check is enclosed.

❑ Payment by credit card. Form PTO-2038 is attached. ra The Director is hereby authorized to charge the required fee(s), any deficiency, or credit any

overpayment, to Deposit Account Number 12 - 1216 (enclose an extra copy of this form).

5. Chnuge in Entity Status (from status indicated above) t=i a. Applicant claims SMALL ENTITY status. See 37 CFR 1.27. ❑ b. Applicant is no longer claiming SMALL ENTITY status. See 37 CFR 1.27(g)(2).

NOTE: The Issue Fee and Publication Fee (if required) will not be accepted from anyone other than the applicant; a registered attorney or agent; or the assignee or other party in interest as shown by the records of die United states Patent and Trademark Office.

This collection of information is required by 37 CFR 1.311. The information is required to obtain or retain a benefit by the public which is to file (and by the USPTO to process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.14. This collection is estimated to take 12 minutes to complete, including gathering, preparing, and submitting the completed application form to the USPTO. Time will way depending upon the individual case. Any comments on the amount of lime you require to complete this form and/or suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S. Patent and Trademark Office, U.S. Department of Commerce, F.O. Box 1450, Alexandria, Virginia 22313-1450. DO NOT SEND FEES OR COMPLETED FORMS TO THIS ADDRESS. SEND TO: Commissioner for Patents, P.O. Box 1450, Alexandria, Virginia 22313-1450. Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it displays a valid OMB control number.

(A) NAME OF ASSIGNEE

PTOL-85 (Rev. 02/11) Approved for use through 08/31/2013. OMB 0651-0033 U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE

NSN677-1002,

Electronic Patent Application Fee Transmittal


Filing Date: 27-Jun-2011






Filed as Large Entity

Utility under 35 USC 111(a) Filing Fees


USD($)

Basic Filing:

Pages:

Claims:

Miscellaneous-Filing:

Publ. Fee- early, voluntary, or normal 1504 1 300 300

Petition:

Patent-Appeals-and-Interference:

Post-Allowance-and-Post-Issuance:

Utility Appl issue fee 1501 1 1510 1510

NSN677-1002,


USD($)

Extension-of-Time:

Miscellaneous:

Total in USD ($) 1810

NSN677-1002,


EFS ID: 10837336









Filer Authorized By: John Knox Winn


Receipt Date: 29-AUG-2011





Submitted with Payment yes

Payment Type Deposit Account

Payment was successfully received in RAM $1810

RAM confirmation Number 4431

Deposit Account 121216

Authorized User

File Listing:

Document Number


Multi Part /.zip

Pages (if appl.)

NSN677-1002,

1 Transmittal Letter 312Amendme

p

n

df

t_Transmittal. 58992

no 1

8940edf858492f7919de538d751aec42c062

fe78

Warnings:

Information:

2 Amendment after Notice of Allowance

(Rule 312) 312Amendment.pdf

34012

no 5

ba8fe663bbf7b0e18e08b5a8d80e8bf9b6b

c56b3

Warnings:

Information:

3 Issue Fee Payment (PTO-85B) IssueFeeTransmittal.pdf

108527

no 1

8cdbef45cc276080577d0bc01be4e3c9ecb

0057b

Warnings:

Information:

4 Fee Worksheet (SB06) fee-info.pdf

32524

no 2

b31 c970c2acd1b2165f01dd3719cc41 b19e

bc5aa

Warnings:

Information:


This Acknowledgement Receipt evidences receipt characterized by the applicant, and including page Post Card, as described in MPEP 503.

New Applications Under 35 U.S.C. 111

on the noted date by the USPTO counts, where applicable.

includes the necessary components 1.54) will be issued in due date of the application.

35 U.S.C. 371

of the indicated documents, It serves as evidence of receipt similar to a

for a filing date (see 37 CFR course and the date shown on this

is compliant with the conditions of 35 acceptance of the application as a

Filing Receipt, in due course.

includes the necessary components for of the International Application Number

subject to prescriptions concerning establish the international filing date of

If a new application is being filed and the application 1.53(b)-(d) and MPEP 506), a Filing Receipt (37 CFR Acknowledgement Receipt will establish the filing

National Stage of an International Application under If a timely submission to enter the national stage of an international application U.S.C. 371 and other applicable requirements a Form PCT/DO/E0/903 indicating national stage submission under 35 U.S.C. 371 will be issued in addition to the

New International Application Filed with the USPTO as a Receiving Office If a new international application is being filed and the international application an international filing date (see PCT Article 11 and MPEP 1810), a Notification and of the International Filing Date (Form PCT/RO/105) will be issued in due course, national security, and the date shown on this Acknowledgement Receipt will the application.

NSN677-1002,

By n K. Winn, Reg. No. 58,579

FORM P10-1083

In re Application of: WU et al. Application No. 13/169,619 Confirmation No. 2286 Filed: June 27, 2011

PATENT Attorney Docket No. HW708564



Sir:

Transmitted herewith is an AMENDMENT AFTER ALLOWANCE in the subject application.

0 Small entity status is claimed for this application under 37 CFR 1.27.

EA Petition for an extension of time for the period noted below, as well as for any additional period necessary to render the present submission timely. Please charge Deposit Account No. 12-1216 for the appropriate petition fee.

O Other:

Z Please charge Deposit Account No. 12-1216 in the total amount indicated below.

SMALL ENTITY OTHER THAN A SMALL

ENTITY

TIME EXTENSION PETITION FEE none $ 0.00 $ 0.00

subtract time extension fee previously paid none ($ 0.00) ($ 0.00)

CLAIM FEE

CLAIMS REMAINING

AFTER AMENDMENT

HIGHEST NUMBER

PREVIOUSLY PAID FOR

EXTRA CLAIMS

PRESENT RATE

ADD'L CLAIM

FEE RATE

ADD'L CLAIM FEE

TOTAL 14 MINUS 14 = 0 x 26 = $ x 52 = $0.00

INDEPENDENT 2 MINUS 2 = 0 x 110 = $ x 220 = $0.00

FIRST PRESENTATION OF MULTIPLE CLAIM + 195 = $ + 390 = $0.00 •

OTHER FEES AS DESCRIBED: $ $0.00

TOTAL AMOUNT TO BE CHARGED TO DEPOSIT ACCOUNT TOTAL $ TOTAL $0.00

El The Commissioner is hereby authorized to charge any deficiencies in the following fees associated with this communication or credit any overpayment to Deposit Account No. 12-1216. El Any filing fees under 37 CFR 1.16 for the presentation of extra claims. El Any patent application processing fees under 37 CFR 1.17.


LEYDIG, VOIT & MAYER, LTD. Two Prudential Plaza, Suite 4900 180 North Stetson Avenue Chicago, Illinois 60601-6731 (312) 616-5600 (telephone) (312) 616-5700 (facsimile)

LEYDIG, VOIT & MAYER, LTD.

AMENDMENT OR ROA TRANSMITTAL (Revised 09/15/2009)

NSN677-1002,






Art Unit: 2617

Examiner: NGUYEN, David Q.

Docket No.: HW708564 (Client Ref. 81356140US)


AMENDMENT AFTER ALLOWANCE (37 CFR 1.312)

Sir:

In accordance with 37 CFR 1.312, please enter the following amendments after

allowance and consider the following remarks.

Amendments to the Claims are reflected in the listing of claims which begins on page 2 of

this paper.

Remarks begin on page 5.

Page 1 of 5

NSN677-1002,

Application No. 13/169,619 Amendment After Allowance

AMENDMENTS TO THE CLAIMS

1. (Original) A method for detaching a user equipment (UE) when a handover

from a 3rd generation partnership project (3GPP) network to a non-3GPP network occurs,

comprising:

receiving, by a mobility management entity (MME) of the 3GPP network, a delete



network to the non-3GPP network;


detaching, by the MME, the UE from the 3GPP network when all the bearer resources

of the UE are deleted.

2. (Original) The method according to claim 1, wherein the cause IE is set to

"UE's accessing RAT changed from a 3GPP network to a non-3GPP network".

3. (Original) The method according to claim 2, further comprising:

setting, by a packet data network gateway (PDN GW), the cause IE to "UE's

accessing RAT changed from a 3GPP network to a non-3GPP network";

sending, by the PDN GW, the delete bearer request message carrying the cause IE to

the serving GW; and

sending, by the serving GW, the delete bearer request message carrying the cause IE

to the MME.

4. (Original) The method according to claim 1, wherein detaching, by the MME,

the UE from the 3GPP network further comprises:

detaching, by the MME, the UE from the 3GPP network without sending a detach


5. (Original) The method according to claim 1, comprising:

detaching, by the MME, the UE from the 3GPP network if a terminal capability of the



Page 2 of 5

NSN677-1002,


detaching, by the MME, the UE from the 3GPP network if access policy information

of an operator is single radio access.



UE is dual radio capability and access policy information of an operator is single radio access;

or if the terminal capability of the UE is single radio capability and the access policy

information of the operator is dual radio access; or if the terminal capability of the UE is the


access.

8. (Currently Amended) A mobile mobility management entity (MME),

configured to:

receive a delete bearer request sent by a serving gateway (GW) of a 3GPP network

when a handover from the 3GPP network to a non-3GPP network occurs, wherein the delete

bearer request carries a cause information element (1E) which indicates a user equipment (UE)

handovers from the 3GPP network to the non-3GPP network;

delete bearer resources of the user equipment UE; and


deleted.

9. (Currently Amended) The mobile mobility management entity according to

claim 8, wherein the cause 1E is set to "UE's accessing RAT changed from a 3GPP network

to a non-3GPP network".


claim 9, wherein the delete bearer request is sent from a packet data network gateway to the

network device MME via the serving gateway, wherein the cause IE is set to "UE's accessing

RAT changed from a 3GPP network to a non-3GPP network" by the packet data network

gateway.

Page 3 of 5

NSN677-1002,



claim 8, wherein the network device MME is configured to detach the UE from the 3GPP

network without sending a detach request message to the UE.



network if a terminal capability of the UE is single radio capability.



network if access policy information of an operator is single radio access.



network if a terminal capability of the UE is dual radio capability and access policy


single radio capability and the access policy information of the operator is dual radio access;

or if the terminal capability of the UE is the single radio capability and the access policy


This listing of claims replaces all prior versions, and listings, of claims in the

application.

Page 4 of 5

NSN677-1002,


REMARKS

The Notice of Allowance for this application was mailed on August 8, 2011. With the

payment of the issue fee, please enter the foregoing amendments to claims 8-14.

Each of the requested changes in claims 8-14 is fully supported by the specification

and drawings as originally filed. The amendment merely corrects minor errors in the claims.

It is believed that no additional search is required and no new issues are raised.

Applicant respectfully requests the amendment be entered.




Page 5 of 5

NSN677-1002,

Please enter. 08/31/2011. /DN/






Art Unit: 2617

Examiner: NGUYEN, David Q.

Docket No.: HW708564 (Client Ref. 81356140US)


AMENDMENT AFTER ALLOWANCE (37 CFR 1.312)

Sir:

In accordance with 37 CFR 1.312, please enter the following amendments after

allowance and consider the following remarks.

Amendments to the Claims are reflected in the listing of claims which begins on page 2 of

this paper.

Remarks begin on page 5.

Page 1 of 5

NSN677-1002,


AMENDMENTS TO THE CLAIMS

1. (Original) A method for detaching a user equipment (UE) when a handover

from a 3rd generation partnership project (3GPP) network to a non-3GPP network occurs,

comprising:

receiving, by a mobility management entity (MME) of the 3GPP network, a delete



network to the non-3GPP network;


detaching, by the MME, the UE from the 3GPP network when all the bearer resources

of the UE are deleted.

2. (Original) The method according to claim 1, wherein the cause IE is set to

"UE's accessing RAT changed from a 3GPP network to a non-3GPP network".

3. (Original) The method according to claim 2, further comprising:

setting, by a packet data network gateway (PDN GW), the cause IE to "UE's

accessing RAT changed from a 3GPP network to a non-3GPP network";

sending, by the PDN GW, the delete bearer request message carrying the cause IE to

the serving GW; and

sending, by the serving GW, the delete bearer request message carrying the cause IE

to the MME.

4. (Original) The method according to claim 1, wherein detaching, by the MME,

the UE from the 3GPP network further comprises:

detaching, by the MME, the UE from the 3GPP network without sending a detach






Page 2 of 5

NSN677-1002,


detaching, by the MME, the UE from the 3GPP network if access policy information

of an operator is single radio access.



UE is dual radio capability and access policy information of an operator is single radio access;

or if the terminal capability of the UE is single radio capability and the access policy

information of the operator is dual radio access; or if the terminal capability of the UE is the


access.

8. (Currently Amended) A mobile mobility management entity (MME),

configured to:

receive a delete bearer request sent by a serving gateway (GW) of a 3GPP network

when a handover from the 3GPP network to a non-3GPP network occurs, wherein the delete

bearer request carries a cause information element (1E) which indicates a user equipment (UE)

handovers from the 3GPP network to the non-3GPP network;

delete bearer resources of the user equipment UE; and


deleted.


claim 8, wherein the cause 1E is set to "UE's accessing RAT changed from a 3GPP network

to a non-3GPP network".


claim 9, wherein the delete bearer request is sent from a packet data network gateway to the

network device MME via the serving gateway, wherein the cause IE is set to "UE's accessing

RAT changed from a 3GPP network to a non-3GPP network" by the packet data network

gateway.

Page 3 of 5

NSN677-1002,




network without sending a detach request message to the UE.



network if a terminal capability of the UE is single radio capability.



network if access policy information of an operator is single radio access.



network if a terminal capability of the UE is dual radio capability and access policy


single radio capability and the access policy information of the operator is dual radio access;

or if the terminal capability of the UE is the single radio capability and the access policy


This listing of claims replaces all prior versions, and listings, of claims in the

application.

Page 4 of 5

NSN677-1002,


REMARKS

The Notice of Allowance for this application was mailed on August 8, 2011. With the

payment of the issue fee, please enter the foregoing amendments to claims 8-14.

Each of the requested changes in claims 8-14 is fully supported by the specification

and drawings as originally filed. The amendment merely corrects minor errors in the claims.

It is believed that no additional search is required and no new issues are raised.

Applicant respectfully requests the amendment be entered.




Page 5 of 5

NSN677-1002,

77399 7590 09/07/2011


EXAMINER

ART UNIT

PAPER NUMBER

2617

NOTIFICATION DATE

DELIVERY MODE

09/07/2011

ELECTRONIC

NGUYEN, DAVID Q

UNITED STA1ES PA PENT AND TRADEMARK OFFICE






13/169,619

06/27/2011

Wenfu WU

HW708564

2286

Please find below and/or attached an Office communication concerning this application or proceeding.

The time period for reply, if any, is set in the attached communication.

Notice of the Office communication was sent electronically on above-indicated "Notification Date" to the following e-mail address(es): [email protected] [email protected]

PTOL-90A (Rev. 04/07)

NSN677-1002,

Application No.

13/169,619

Examiner

DAVID Q. NGUYEN

Applicant(s)

WU ET AL.

Art Unit

2617

Response to Rule 312 Communication

-- The MAILING DATE of this communication appears on the cover sheet with the correspondence address —

1. [E] The amendment filed on 29 August 2011 under 37 CFR 1.312 has been considered, and has been:

a) E] entered.

b) ❑ entered as directed to matters of form not affecting the scope of the invention.

c) ❑ disapproved because the amendment was filed after the payment of the issue fee.

Any amendment filed after the date the issue fee is paid must be accompanied by a petition under 37 CFR 1.313(c)(1)

and the required fee to withdraw the application from issue.

d) ❑ disapproved. See explanation below.

e) ❑ entered in part. See explanation below.



PTOL-271 (Rev. 04-01)

Reponse to Rule 312 Communication Part of Paper No. 20110831

NSN677-1002,

UNITED STA 1ES PA1ENT AND TRADEMARK OFFICE



APPLICATION NO. ISSUE DATE

PATENT NO. ATTORNEY DOCKET NO. CONFIRMATION NO.

13/169,619

10/04/2011

8031677

HW708564

2286

77399 7590 09/14/2011


ISSUE NOTIFICATION

The projected patent number and issue date are specified above.

Determination of Patent Term Adjustment under 35 U.S.C. 154 (b) (application filed on or after May 29, 2000)

The Patent Term Adjustment is 0 day(s). Any patent to issue from the above-identified application will include an indication of the adjustment on the front page.

If a Continued Prosecution Application (CPA) was filed in the above-identified application, the filing date that determines Patent Term Adjustment is the filing date of the most recent CPA.

Applicant will be able to obtain more detailed information by accessing the Patent Application Information Retrieval (PAIR) WEB site (http://pair.uspto.gov).

Any questions regarding the Patent Term Extension or Adjustment determination should be directed to the Office of Patent Legal Administration at (571)-272-7702. Questions relating to issue and publication fee payments should be directed to the Application Assistance Unit (AAU) of the Office of Data Management (ODM) at (571)-272-4200.

APPLICANT(s) (Please see PAIR WEB site http://pair.uspto.gov for additional applicants):

Wenfu WU, Shanghai, CHINA; Weihua HU, Shanghai, CHINA; Shanhan WANG, Shanghai, CHINA;

IR103 (Rev. 10/09)

NSN677-1002,

06/27/2011

Wenfu WU

HW708564

CONFIRMATION NO. 2286 PUBLICATION NOTICE




APPLICATION NUMBER




13/169,619


Title:METHOD, SYSTEM, AND DEVICE FOR USER DETACHMENT WHEN A HANDOVER OR CHANGE OCCURS IN HETEROGENEOUS NETWORK

Publication No.US-2011-0244865-Al Publication Date:10/06/2011

NOTICE OF PUBLICATION OF APPLICATION

The above-identified application will be electronically published as a patent application publication pursuant to 37 CFR 1.211, et seq. The patent application publication number and publication date are set forth above.

The publication may be accessed through the USPTO's publically available Searchable Databases via the Internet at www.uspto.gov. The direct link to access the publication is currently http://www.uspto.gov/patft/.

The publication process established by the Office does not provide for mailing a copy of the publication to applicant. A copy of the publication may be obtained from the Office upon payment of the appropriate fee set forth in 37 CFR 1.19(a)(1). Orders for copies of patent application publications are handled by the USPTO's Office of Public Records. The Office of Public Records can be reached by telephone at (703) 308-9726 or (800) 972-6382, by facsimile at (703) 305-8759, by mail addressed to the United States Patent and Trademark Office, Office of Public Records, Alexandria, VA 22313-1450 or via the Internet.

In addition, information on the status of the application, including the mailing date of Office actions and the dates of receipt of correspondence filed in the Office, may also be accessed via the Internet through the Patent Electronic Business Center at www.uspto.gov using the public side of the Patent Application Information and Retrieval (PAIR) system. The direct link to access this status information is currently http://pair.uspto.gov/. Prior to publication, such status information is confidential and may only be obtained by applicant using the private side of PAIR.

Further assistance in electronically accessing the publication, or about PAIR, is available by calling the Patent Electronic Business Center at 1-866-217-9197.

Office of Data Managment, Application Assistance Unit (571) 272-4000, or (571) 272-4200, or 1-888-786-0101

page 1 of 1

NSN677-1002,