WO2013082984A1 - 一种附着到e-utran的方法及移动性管理实体 - Google Patents

一种附着到e-utran的方法及移动性管理实体 Download PDF

Info

Publication number
WO2013082984A1
WO2013082984A1 PCT/CN2012/084122 CN2012084122W WO2013082984A1 WO 2013082984 A1 WO2013082984 A1 WO 2013082984A1 CN 2012084122 W CN2012084122 W CN 2012084122W WO 2013082984 A1 WO2013082984 A1 WO 2013082984A1
Authority
WO
WIPO (PCT)
Prior art keywords
user terminal
authentication
message
mme
information
Prior art date
Application number
PCT/CN2012/084122
Other languages
English (en)
French (fr)
Inventor
吴鹏程
Original Assignee
大唐移动通信设备有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 大唐移动通信设备有限公司 filed Critical 大唐移动通信设备有限公司
Priority to US14/362,916 priority Critical patent/US20140335830A1/en
Priority to JP2014545069A priority patent/JP5813249B2/ja
Priority to EP12854709.8A priority patent/EP2790454B1/en
Priority to KR1020147018739A priority patent/KR101671270B1/ko
Publication of WO2013082984A1 publication Critical patent/WO2013082984A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W60/00Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06Authentication
    • H04W12/062Pre-authentication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06Authentication
    • H04W12/069Authentication using certificates or pre-shared keys
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08Access security
    • H04W12/082Access security using revocation of authorisation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/12Setup of transport tunnels
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and a mobility management entity attached to an E-UTRAN (Evolved Universal Terrestrial Radio Access Network). Background technique
  • the user As the user's requirements for network performance increase, the user expects the terminal to access the network for a shorter period of time, that is, the delay of the attachment process attached to the network is as small as possible to improve Long Term Evolution (LTE).
  • LTE Long Term Evolution
  • SAE System Architecture Evolution
  • the initial sub-process in the E-UTRAN includes the following sub-process: sub-process 1, interaction between the network side and the user equipment (User Equipment, UE) for authentication, authentication, security confirmation, and the like;
  • the sub-process 2 establishes a tunnel with the user terminal on the network side;
  • sub-process 3. After establishing a tunnel between the network side and the user terminal, the network side establishes a default bearer.
  • the total delay of the entire attachment process is the sum of the delays of the sub-processes.
  • the attach procedure shown in FIG. 1 can be used for the following situations:
  • the context information of the user terminal is not stored in the network side, and the attach request sent by the user terminal does not carry the session management information transmission mark. Or carry the session management information transmission tag but not set.
  • a flow chart of attaching a user terminal to a network side in the prior art includes:
  • Step 101 The UE sends an attach request message (ie, Attach Request) and a network selection indication to the evolved base station (evolved NodeB, e B ), where the attach request message carries the temporary mobile subscription user identifier of the UE ( Temporary Mobile Subscriber Identity, TMSI), UE capabilities, and Packet Data Network (PDN) addresses.
  • Attach Request an attach request message
  • e B the evolved base station
  • the attach request message carries the temporary mobile subscription user identifier of the UE ( Temporary Mobile Subscriber Identity, TMSI), UE capabilities, and Packet Data Network (PDN) addresses.
  • TMSI Temporary Mobile Subscriber Identity
  • PDN Packet Data Network
  • Step 102 The eNB determines a Mobility Management Entity (MME) according to a Service Temporary Mobile Subscriber Identity (S-TMSI) and a network selection indication of the service in the received attach request message. And forward the attach request message to the determined MME.
  • MME Mobility Management Entity
  • S-TMSI Service Temporary Mobile Subscriber Identity
  • step 102 if the eNB and the network selection indication in the eNB are incapable of determining the corresponding MME, an MME is selected by the MME selection function, and the attach request message is forwarded to the selected MME.
  • Step 103 The MME determines that the type of attachment initiated by the UE is an invalid global unique temporary user identifier (Globally The MME sends an authentication request message (ie, Identity Request) to the UE when the context information of the UE is not stored in the network side.
  • an authentication request message ie, Identity Request
  • Step 104 the UE receives the MME issued authentication request message, transmits an authentication request response message (i.e. Identity Response) to the MME, and the message carries the UE's international mobile subscriber identification code in response to the other 1 J in the authentication request (International Mobile Subscriber Identity, IMSI) information.
  • an authentication request response message i.e. Identity Response
  • IMSI International Mobile Subscriber Identity
  • Step 105 The MME sends an authentication information request message (ie, an Authentication Information Request message) to the Home Subscriber Server (HSS).
  • HSS Home Subscriber Server
  • Step 106 When receiving the authentication information request message sent by the MME, the HSS sends an authentication information response message (ie, an Authentication Information Answer message) to the MME, and carries multiple groups of authentications in the right information response message. vector.
  • an authentication information response message ie, an Authentication Information Answer message
  • Step 107 The MME selects a set of authentication vectors from the received multiple sets of authentication vectors, and sends an authentication request (ie, an Authentication Request) to the UE, where the authentication request carries the selected set of authentications. vector.
  • an authentication request ie, an Authentication Request
  • Step 108 When receiving the authentication request sent by the MME, the UE authenticates a group of authentication vectors carried in the authentication request, and sends an authentication response message to the MME when the authentication succeeds. (ie, Authentication Response), and carries the expected response value (XRES) parameter in the authentication response message.
  • Authentication Response ie, Authentication Response
  • XRES expected response value
  • Step 109 After receiving the authentication response message sent by the UE, the MME compares the XRES parameter in the authentication response message with the locally stored XRES parameter, and if yes, determines that the authentication succeeds; after the authentication succeeds Generating an integrity protection key and an encryption key by using the key Kasme, and sending a security mode command (ie, a Security Mode Command) to the UE, where the security mode command carries the integrity protection key and the encryption key. That is, the security control process is initiated.
  • a security mode command ie, a Security Mode Command
  • Step 110 When receiving the security mode command sent by the MME, the UE checks the integrity protection key and the encryption key carried in the security mode command, and when the verification succeeds, the UE sends the MME to the MME.
  • the security mode completion message ie, Security Mode Complete
  • the security mode completion message is sent, that is, the security control process is completed.
  • Step 111 The MME sends an authentication request message (ie, Identity Request), which is used to indicate the IMEI information of the UE, to the UE, and carries the identifier type in the authentication request message.
  • an authentication request message ie, Identity Request
  • Step 112 When receiving the authentication request message sent by the MME, the UE determines a corresponding IMEI according to the identifier type, and sends an authentication response message (Identity Response) to the MME, and the authentication response is The message carries the determined IMEI.
  • Step 113 The MME and the Device Identity Register (EIR) process determine whether the UE is allowed to access by using a device identity check (ME Identity Check) process, and continue the subsequent steps when the access is allowed. End the process when accessing.
  • EIR Device Identity Register
  • Step 114 The MME sends a location update message (ie, Updata Location Request) to the HSS.
  • Step 115 the HSS returns a location update response (ACK) message to the MME (ie, Updata Location Answer); if the MME determines that the HSS rejects the update according to the location update ACK message, rejects the attach request of the UE, and ends the process;
  • the MME determines, according to the location update ACK message, that the HSS accepts the update, accepts the attach request of the UE, and continues the subsequent steps.
  • Step 116 The MME selects a Serving Gateway (SGW), and sends a Create Session Request message (ie, a Create Session Request) to the selected SGW, where the Create Session Request message carries the IMSI, the ID of the context information of the UI, Radio Acess Technology (RAT) type, default bearer service quality (QoS), PDN address allocation, and Aggregate Maximum Bit Rate (AMBR).
  • SGW Serving Gateway
  • RAT Radio Acess Technology
  • QoS bearer service quality
  • AMBR Aggregate Maximum Bit Rate
  • Step 117 The SGW creates an entry in its Evolved Packet Cor (EPC) bearer list, and forwards the received Create Session Request message to the PDN Gateway (PDW).
  • EPC Evolved Packet Cor
  • Step 118 If the network side uses a Policy Control and Charging Rule Function (PCRF) entity, the PGW interacts with the PCRF entity to obtain a Policy and Charging Control (PCC) rule.
  • PCC Policy and Charging Control
  • the PCC rule is a rule predefined in the PGW when a default Evolved Packet System (EPS) bearer needs to be established.
  • EPS Evolved Packet System
  • Step 119 The PGW returns a Create Session Response message (ie, Create Session Response) to the SGW, where the Create Session Response message carries a User Plane PGW Address and a Tunnel Endpoint Identifier (TEID), and a Control Plane PDN Gateway Tunnel Endpoint Identifier ( PDN Gateway Tunnel Endpoint Identifier, PGW TEID), PDN Type, PDN Address, Protocol Configuration Option, Billing ID, Access Point Name (APN) Limit, Cause Value, and Maximum Bit Rate of the Access Point (Access Point Name) Aggregate Maximum Bit Rate, APN- AMBR) and other parameters.
  • TEID User Plane PGW Address and a Tunnel Endpoint Identifier
  • PDN Gateway Tunnel Endpoint Identifier PDN Gateway Tunnel Endpoint Identifier
  • PDN Type PDN Address
  • Protocol Configuration Option Billing ID
  • APN Access Point Name
  • APN Access Point Name
  • APN- AMBR Maximum Bit Rate
  • Step 120 When receiving the create session response message sent by the PGW, the SGW returns a create session response message (ie, Create Session Response) to the MME, where the create session response message carries the PDN type, the PDN address, and the user plane.
  • a create session response message ie, Create Session Response
  • the create session response message carries the PDN type, the PDN address, and the user plane.
  • SGW address and TEID, control plane SGW TEID, EPS carrier identifier, and PGW address ie, Create Session Response
  • Step 119 The MME sends an initial context setup request (ie, an Initial Context Setup Request) message to the eNB, where an attach accept message (ie, Attach Accept) is nested in the initial context setup message; wherein, if the MME allocates a new one to the UE The GUTI, the attach accept message further carries the new GUTI parameter; the initial context setup request includes a security context of the UE, a handover restriction list, a bearer QoS parameter, and an AMBR-related PDN address information, and needs to be established. Beared QoS information.
  • an initial context setup request ie, an Initial Context Setup Request
  • Attach Accept ie, Attach Accept
  • Step 122 When receiving the attach accept message sent by the MME, the eNB sends a Radio Resource Control (RRC) connection reconfiguration message to the UE (ie, Radio Resource Control Connection).
  • RRC Radio Resource Control
  • the attach accept message carries S-TMSI, PDN Address, Trace Area (TA) list, and PDN address information.
  • Step 123 The UE sends an RRC Connection Reconfiguration Complete message (ie, RRC Connection Reconfiguration Complete) to the e B.
  • RRC Connection Reconfiguration Complete ie, RRC Connection Reconfiguration Complete
  • Step 124 The eNB sends an initial context message (ie, an Initial Context Setup Response) to the MME, where the initial context message carries information such as the TEID of the eNB and the downlink transmission address of the eNB on the S1-U interface.
  • an initial context message ie, an Initial Context Setup Response
  • Step 125 The UE sends a direct transfer message (ie, Direct Transfer) to the eNB, where the direct transfer message includes an attach complete message (ie, Attach Complete).
  • a direct transfer message ie, Direct Transfer
  • an attach complete message ie, Attach Complete
  • Step 126 The eNB forwards the attach complete message in the direct transfer message to the MME.
  • the UE sends an uplink data packet to the SGW through the eNB according to the PDN address carried in the attach accept message, and then sends the uplink data packet to the PGW through the tunnel address through the SGW.
  • Step 127 The MME sends a bearer update request message (ie, Modify Bearer Request) to the SGW.
  • a bearer update request message ie, Modify Bearer Request
  • Step 128 If the bearer update request message sent by the MME to the SGW carries a handover indication (ie, Handover Indication), the SGW needs to send a bearer update request message (Modify Bearer Request) to the PGW; otherwise, directly perform the following step 130.
  • a handover indication ie, Handover Indication
  • Step 129 The PGW replies to the SGW with a bearer update response message (ie, Modify Bearer Response).
  • a bearer update response message ie, Modify Bearer Response
  • Step 130 The SGW returns a bearer update response message (ie, Modify Bearer Response) to the MME. At this time, the SGW may send the buffered downlink packet data.
  • a bearer update response message ie, Modify Bearer Response
  • Step 131 After receiving the bearer update response message, if the MME receives an bearer update response message, if the MME establishes an EPS bearer, the MME sends a notification request message (ie, Notify Request) for the mobility management of the user, where the notification request message is carried.
  • a notification request message ie, Notify Request
  • Step 132 The HSS stores the APN and PGW identifiers carried in the notification message, and sends a notification response message (ie, Notify Response) to the MME, thereby completing the entire attach process.
  • a notification response message ie, Notify Response
  • the attach procedure shown in FIG. 1 is used.
  • all the steps in the above attachment process are performed in a serial manner, so the consumption delay is relatively large, for example, the total delay of the above attachment process is the sum of the delays consumed by each sub-flow.
  • the present invention provides a method for attaching to an E-UTRAN and a mobility management entity to reduce the attachment of a user terminal to a network. Delay, improve adhesion efficiency.
  • a method for attaching to an evolved universal terrestrial radio access network E-UTRAN includes: Step A: The network side acquires context information of the user terminal when receiving an attach request sent by the user terminal;
  • Step B The network side performs an authentication process and a security process with the user terminal.
  • Step C The network side establishes a tunnel for information transmission with the user terminal
  • Step D The network side establishes a default bearer with the user terminal.
  • step A After step A is successfully executed, the step B and the step C are performed in parallel; and the step D is performed after confirming that the step B and the step C are successfully performed.
  • a mobility management entity MME includes a context information acquisition unit, an authentication security unit, a tunnel establishment unit, a default bearer unit, and a control unit, where:
  • a context information obtaining unit configured to acquire context information of the user terminal when receiving an attach request sent by the user terminal by the base station to which the user terminal belongs;
  • An authentication security unit configured to perform an authentication process and a security process between the MME and the user terminal, and a tunnel establishment unit, configured to establish a tunnel with the user terminal for transmitting information;
  • a default bearer unit configured to establish a default bearer with the user terminal
  • control unit configured to start the authentication security unit and the tunnel establishing unit to run in parallel after the context information acquiring unit is successfully run; and after the authentication security unit and the tunnel establishing unit are successfully run, Start the default is running in the unit.
  • the context information of the user terminal is acquired when receiving the attach request sent by the user terminal; and the following steps are performed in parallel: performing an authentication process and a security process with the user terminal, and establishing the user terminal with the user terminal The tunnel used for information transmission; after the success, the default bearer with the user terminal is established.
  • the authentication process and the security process are performed in parallel after the context information of the user terminal is acquired, and the tunnel for information transmission with the user terminal is established, the prior art is compared with the prior art. Performing the above steps serially reduces the delay of the user terminal to the network and improves the adhesion efficiency to some extent.
  • 1 is a flow chart of attach signaling of a user terminal attached to a network in the prior art
  • FIG. 2 is a flowchart of a method for attaching a user terminal to a network according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a method for acquiring context information of a user terminal according to an embodiment of the present invention
  • FIG. 4 is a flow chart of a method for performing an authentication process and a security process between a network side and a user terminal according to an embodiment of the present invention
  • FIG. 5 is a second flowchart of a method for performing an authentication process and a security process between a network side and a user terminal according to an embodiment of the present invention
  • FIG. 6 is a flowchart of a method for establishing a tunnel between a network side and a user terminal according to an embodiment of the present invention
  • FIG. 7 is a second flowchart of a method for establishing a tunnel between a network side and a user terminal according to an embodiment of the present invention
  • FIG. 8 is a flowchart of a method for establishing a default bearer between a network side and a user terminal according to an embodiment of the present invention
  • FIG. 9 is a flowchart of a method for establishing a default bearer between a network side and a user terminal according to an embodiment of the present invention.
  • FIG. 10 is a signaling flowchart of a user terminal attached to a network according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of a mobility management entity according to an embodiment of the present invention. detailed description
  • the network attachment process in the prior art has a problem of large delay and low efficiency: the user terminal uses the IMSI or the invalid GUTI to attach; the network side does not store the context information of the UE; the attachment initiated by the user terminal
  • the PDN Connectivity Request message contained in the request message does not contain the ESM Information Transfer flag (EIT) option or the EIT is set to 0 (a value of 0 indicates that the transmission does not require encryption).
  • EIT ESM Information Transfer flag
  • the embodiment of the present invention provides an attaching method in an evolved E-UTRAN and a mobility management entity, so as to reduce the delay of the user terminal attaching to the network and improve the attaching efficiency.
  • the attaching method may include: Step A: The network side acquires context information of the user terminal when receiving an attach request sent by the user terminal; Step B, the network side performs execution with the user terminal An authentication process and a security process; Step C: The network side establishes a tunnel for information transmission with the user terminal; Step D: The network side establishes a default bearer with the user terminal; After successfully performing step A Step B and step C are performed in parallel; and step D is performed after confirming that step B and step C are successfully performed.
  • steps B and C are performed in parallel, the delay of attaching the user terminal to the network is shortened compared to the serial execution of steps A to D in the prior art, and the user terminal is improved. Efficiency in the network.
  • FIG. 2 is a flowchart of a method for a user terminal to be attached to a network according to an embodiment of the present invention.
  • the method includes steps 21 to 24, where step 22 and step 23 are performed in parallel after successful execution of step 21, After step 22 and step 23, step 24 is performed:
  • Step 21 When receiving the attach request sent by the user terminal, the network side acquires context information of the user terminal.
  • Step 22 The network side performs an authentication process and a security process with the user terminal.
  • Step 23 The network side establishes a tunnel for information transmission with the user terminal.
  • Step 24 The network side establishes a default bearer with the user terminal.
  • step 21 specifically includes the following sub-steps, as shown in FIG. 3:
  • Step 211 The base station on the network side receives an attach request (that is, an Attach Request) and a network selection indication sent by the user terminal.
  • the foregoing attach request message carries parameters such as a TMSI, a UE capability, and a PDN address of the UE.
  • Step 212 The base station selects an MME according to the attach request and the network selection indication, and forwards the attach request to the selected MMEo.
  • Step 213 The MME determines that the attach request is an invalid GUTI attachment, and determines that the context information of the user terminal is not stored locally, and sends an authentication request message for indicating that the IMSI information of the user terminal is obtained to the user terminal ( Identity Request).
  • Step 214 The MME receives an authentication request response message (ie, Identity Response) that is returned by the user terminal and carries the IMSI information of the user terminal.
  • an authentication request response message ie, Identity Response
  • the foregoing step 22 may specifically include the following sub-steps, as shown in FIG. 4:
  • Step 221 The MME sends an authentication information request message indicating that the authentication vector is obtained to the HSS.
  • Step 222 The MME receives an authentication information response message (ie, an Authentication Information Answer message) returned by the HSS, where the authentication information response message carries multiple sets of authentication vectors.
  • an authentication information response message ie, an Authentication Information Answer message
  • Step 223 The MME selects a group of authentication vectors from the plurality of sets of authentication vectors carried in the authentication information response message, and sends an authentication request (ie, an Authentication Request) to the user terminal, where the authentication is performed.
  • the request carries the selected authentication vector.
  • Step 224 The MME receives an authentication response message (ie, an Authentication Response) returned by the user terminal, where the authentication response message is used by the user terminal to authenticate an authentication vector carried in the received authentication request.
  • the message sent after the success, and the authentication response message carries the XRES parameter.
  • Step 225 The MME sends the received XRES parameter in the authentication response message to the locally stored
  • the XRES parameters are compared, the authentication is determined to be successful, and the integrity protection key and the encryption key are generated by using the key, and a security mode command message (ie, Security Mode Command) is sent to the user terminal, where the security mode is The integrity message and the encryption key are carried in the command message.
  • a security mode command message ie, Security Mode Command
  • Step 226 The MME receives a security mode complete message (ie, Security Mode Complete) returned by the user terminal, where the security mode complete message is used by the user terminal to receive the security mode command message.
  • a security mode complete message ie, Security Mode Complete
  • the message sent after the integrity key is successfully authenticated by the protection key and the encryption key.
  • Step 227 The device identification check (ie, ME Identity Check) process between the MME and the RIE determines whether the user terminal is allowed to attach to the network side; if not, the process ends, and if so, the subsequent steps are continued.
  • ME Identity Check ME Identity Check
  • the MME needs to obtain the IMEI information of the user terminal, the following sub-steps are further included between the foregoing step 226 and step 227, as shown in FIG. 5:
  • Step 23 in the above process may further include the following sub-steps, as shown in FIG. 6:
  • Step 231 The MME sends a location update message to the HSS.
  • Step 232 The MME receives a location update response message returned by the HSS.
  • the MME rejects the current attachment of the user terminal, and ends. Process; otherwise continue with the steps below.
  • Step 233 The MME selects an SGW, and sends a create session request message to the selected SGW.
  • Step 235 The SGW receives a create session response message returned by the PGW.
  • Step 236 The SGW returns a create session response message to the MME.
  • the following sub-steps are further included between the step 234 and the step 235, as shown in FIG. 7:
  • Step 234a The PGW obtains a PCC rule from the PCRF entity, where the PCC rule is established.
  • Step 24 of the above process may specifically include the following sub-steps, as shown in FIG. 8:
  • Step 241 The MME sends an attach accept message to the base station.
  • Step 242 The base station sends an RRC connection reconfiguration message to the user terminal, and forwards the received attach accept message to the user terminal.
  • Step 243 The base station receives a connection reconfiguration complete message returned by the user terminal.
  • Step 244 The base station sends initial context information of the base station to the MME.
  • Step 245 The base station receives a direct transmission message that is sent by the user equipment and carries the attachment completion information, and forwards the attachment completion information to the MME.
  • Step 246 The MME sends a bearer update request message to the SGW.
  • Step 247 The MME receives the bearer update response message returned by the SGW, and establishes an EPS bearer, and sends a notification request message to the HSS, where the notification request message carries APN information and a PGW for user mobility management. Identification information.
  • Step 248 The HSS stores the APN information and the PGW identification information, and establish a correspondence between the APN and the PGW identification information, and returns a notification response message to the MME to indicate that the attach procedure is completed.
  • the bearer update request message sent by the MME to the SGW carries a handover indication
  • the following sub-steps are further included between the foregoing step 246 and step 247, as shown in FIG.
  • Step 246a The SGW sends a bearer update request message to the PGW.
  • Step 246b The SGW receives a bearer update response message returned by the SGW.
  • the subsequent sub-steps of step 22 are stopped and the step 23 is stopped.
  • Subsequent sub-steps Preferably, in order to ensure the accuracy of the establishment of the session, in the embodiment of the present invention, when a certain sub-step in step 22 fails, if the sub-step 234 in step 23 has been performed, the MME Sending a delete session request to the SGW and the PGW, respectively, to instruct the SGW and the PGW to delete an established session, and send an attach reject message to the user terminal; if the sub-step in step 23 has not been performed yet 234. The MME sends an attach reject message directly to the user terminal.
  • the MME sends an attach reject message to the user terminal, where the attach reject message carries a cause value.
  • the embodiment of the present invention further provides a signaling flowchart for the user terminal to be attached to the network.
  • the signaling flowchart may be as shown in FIG. 10, including steps a1 to a4, step bl to step b9, and step cl.
  • Step c7 and step dl to step dl2 wherein: step a1 to step a4 are sub-steps of step 21 in FIG. 2, corresponding to the foregoing steps 211 to 214; step bl to step b9 are step 22 in FIG.
  • the sub-steps correspond to the foregoing steps 221 to 227; the steps cl to c7 are the sub-steps of the step 23 in FIG.
  • Step 2 corresponding to the foregoing steps 231 to 236; the steps dl to dl2 are the sub-steps of FIG. Steps 241 to 248; Step b1 to Step b9 and Steps c1 to Step c7 are executed in parallel, and after step bl to step b9 and step c1 to step c7 are successfully performed, step dl to step dl2 are performed;
  • the signaling procedure is an example in which the MME needs to obtain the IMEI information of the user terminal, and the network side uses the PCRF.
  • Attach Request ie, an attach request message
  • the attach request message carries parameters such as the TMSI, the UE capability, and the PDN address of the UE.
  • Step a2 The eNB determines a corresponding MME according to the TMSI and the network selection indication in the received attach request message, and forwards the attach request message to the determined MME.
  • Step a3 The MME determines that the attachment type initiated by the UE is an invalid GUTI attachment, and sends an Identity Request (ie, an authentication request message) to the UE when the context information of the UE is not stored in the network side.
  • an Identity Request ie, an authentication request message
  • Step a4 After receiving the Identity Request sent by the MME, the UE sends an Identity Response (ie, an authentication request response message) to the MME, and carries the IMSI information of the UE in the authentication request response message.
  • an Identity Response ie, an authentication request response message
  • Step bl The MME sends an Authentication Information Request (ie, an authentication information request message) to the HSS.
  • Step b2 When receiving the Authentication Information Request sent by the MME, the HSS sends the Authentication Information Request (ie, an authentication information request message)
  • the MME sends an Authentication Information Answer (in the right message response message) and is in the Authentication
  • the Information Answer carries multiple sets of weight vectors.
  • Step b3 The MME selects a set of authentication vectors from the received multiple sets of authentication vectors, and sends the set of authentication vectors to the UE.
  • An Authentication Request which carries the selected set of weight vectors.
  • Step b4 When receiving the Authentication Request sent by the MME, the UE authenticates a set of authentication vectors carried in the Authentication Request, and sends an Authentication Response to the MME when the authentication succeeds. Responding to the message), and carrying the XRES parameter in the Authentication Response.
  • Step b5 After receiving the Authentication Response sent by the UE, the MME compares the XRES parameter in the Authentication Response with the locally stored XRES parameter, and if yes, determines that the authentication succeeds; after the authentication succeeds, the key is used.
  • the Kasme generates an integrity protection key and an encryption key, and sends a Security Mode Command (that is, a security mode command) to the UE, where the Security Mode Command carries the integrity protection key and the encryption key, that is, initiates security control. process.
  • a Security Mode Command that is, a security mode command
  • Step b6 When receiving the Security Mode Command sent by the MME, the UE checks the integrity protection key and the encryption key carried in the Security Mode Command, and when the verification succeeds, the MME is sent to the MME. Send Security Mode Complete, which completes the security control process.
  • Step b7 The MME sends an Identity Request (ie, an authentication request message) for indicating the IMEI information of the UE to the UE, and carries an identifier type in the Identity Request.
  • an Identity Request ie, an authentication request message
  • Step b8 When receiving the authentication request message sent by the MME, the UE determines a corresponding IMEI according to the identifier type, and sends an Identity Response (ie, an authentication response message) to the MME, and in the Identity The Response carries the determined IMEI.
  • an Identity Response ie, an authentication response message
  • Step b9 The MME and the EIR determine whether to allow the UE to access through the ME Identity Check process, and continue the subsequent steps when the access is allowed, and end the process when the access is not allowed.
  • Step cl The MME sends an Updata Location Request (that is, a location update message) to the HSS.
  • Step 2 The HSS returns a location update ACK message to the MME (ie, Updata Location Answer); if the MME determines that the HSS rejects the update according to the location update ACK message, rejects the attach request of the UE, and ends the process; And determining, according to the location update ACK message, that the HSS accepts the update, accepting the attach request of the UE, and continuing the subsequent steps.
  • MME Updata Location Answer
  • Step c3 The MME selects an SGW, and sends a Creat Session Request to the selected SGW.
  • the Creat Session Request carries the IMSI and MME context information ID, RAT information, default bearer QoS, PDN address assignment, and AMBR parameters.
  • Step c4 The SGW creates an entry in its EPC bearer list, and receives the Create Session.
  • the Request is forwarded to the PGW.
  • Step c5 The PGW interacts with the PCRF to obtain a PCC rule; the PCC rule is a rule predefined in the PGW when a default EPS bearer needs to be established.
  • the PGW returns a Create Session Response (ie, creates a session response message) to the SGW.
  • the Create Session Response carries the user plane PGW address and TEID, control plane PGW TEID, PDN type, PDN address, protocol configuration option, charging ID, APN limit, cause value, and APN-AMBR.
  • Step c7 When receiving the Create Session Response sent by the PGW, the SGW returns a Create Session Response to the ⁇ , where the Create Session Response carries a PDN type, a PDN address, a user plane SGW address and a TEID, and a control plane SGW TEID. , EPS bearer identifier and PGW address, etc.
  • Step dl The MME sends an Attach Accept message to the eNB. If the MME allocates a new GUTI to the UE, the Attach Accept also carries the GUTI parameter.
  • Step d2 When receiving the Attach Accept sent by the MME, the eNB sends an RRC Connection to the UE.
  • the attach accept message carries S-TMSI, PDN address, TA list, and PDN address information.
  • Step d3 The UE sends an RRC Connection Reconfiguration Complete message (ie, RRC Connection Reconfiguration Complete) to the eNB.
  • RRC Connection Reconfiguration Complete ie, RRC Connection Reconfiguration Complete
  • Step d4 The eNB sends an initial context message (ie, an Initial Context Setup Response) to the MME, where the initial context message carries information such as the TEID of the eNB and the downlink transmission address of the eNB on the S1-U interface.
  • an initial context message ie, an Initial Context Setup Response
  • Step d5 The UE sends a direct transfer message (ie, Direct Transfer) to the eNB, where the offline pass message includes an attach complete message (ie, Attach Complete).
  • a direct transfer message ie, Direct Transfer
  • an attach complete message ie, Attach Complete
  • Step d6 The eNB forwards the attach complete message in the direct transfer message to the MME.
  • Step d7 The MME sends a bearer update request message (ie, Modify Bearer Request) to the SGW.
  • a bearer update request message ie, Modify Bearer Request
  • Step d8 If the bearer update request message sent by the MME to the SGW carries a handover indication (that is,
  • the SGW needs to send a Bearer Update Request message (Modify Bearer Request) to the PGW.
  • Bearer Update Request message Modify Bearer Request
  • Step d9 The PGW replies to the SGW with a bearer update response message (ie, Modify Bearer Response).
  • a bearer update response message ie, Modify Bearer Response
  • Step dl0 The SGW returns a bearer update response message (ie, Modify Bearer Response) to the MME. At this time, the SGW may send the buffered downlink packet data.
  • a bearer update response message ie, Modify Bearer Response
  • Step dl1 After receiving the bearer update response message, the MME sends a notification request message (ie, Notify Request) for the mobility management of the user to the HSS, in the notification request message, after the MME receives the bearer update response message.
  • a notification request message ie, Notify Request
  • the MME After receiving the bearer update response message, the MME sends a notification request message (ie, Notify Request) for the mobility management of the user to the HSS, in the notification request message, after the MME receives the bearer update response message.
  • a notification request message ie, Notify Request
  • Step dl2 The HSS stores the APN and PGW identifiers carried in the notification message, and sends a notification response message (ie, Notify Response) to the MME, thereby completing the entire attach process.
  • a notification response message ie, Notify Response
  • the embodiment of the present invention further provides a mobility management entity, and the mobility management entity may be configured as shown in FIG.
  • the context information obtaining unit 1101 is configured to acquire context information of the user terminal when receiving an attach request sent by the user terminal by the base station to which the user terminal belongs;
  • the authentication security unit 1102 is configured to perform an authentication process and a security process between the MME and the user terminal.
  • the tunnel establishing unit 1103 is configured to establish a tunnel for transmitting information with the user terminal.
  • a default bearer unit 1104 configured to establish a default bearer with the user terminal
  • the control unit 1105 is configured to start the authentication security unit 1102 and the tunnel establishing unit 1103 to run in parallel after the context information acquiring unit 1101 successfully runs; and, in the authentication security unit 1102 and the tunnel establishing unit After the 1103 is successfully run, the default bearer unit 1104 is started to run.
  • the context information obtaining unit 1101 is specifically configured to:
  • the authentication security unit 1102 establishes an authentication process between the MME and the user terminal, and specifically includes:
  • an authentication response message where the authentication response message is a message sent by the user terminal after authenticating the authentication vector carried in the received authentication request, and the method is The weight response message carries the XRES parameter; and the XRES parameter in the received authentication response message is compared with the locally stored XRES parameter, and the authentication succeeds when the agreement is successful, and the authentication fails when the inconsistency occurs;
  • the authentication security unit 1102 establishes a security process between the MME and the user terminal, and specifically includes: after determining that the authentication succeeds, generating an integrity protection key and an encryption key by using a key, and The user terminal sends a security mode command message, where the security mode command message carries the integrity protection key and the encryption key; and receives a security mode complete message returned by the user terminal, where the security mode complete message is a message sent after the integrity verification of the integrity protection key and the encryption key by the user terminal after receiving the security mode command message; and performing a ME Identity Check process with the RIE to determine whether to allow The user terminal is attached to the network side.
  • the tunnel establishing unit 1103 is specifically configured to:
  • the create session response message returned by the SGW receives a create session response message returned by the SGW, the create session response message returned by the SGW, after the SGW sends a create session request message to the PGW after creating an entry in the evolved packet core EPC bearer list, the received PGW The created session response message returned.
  • the default bearer unit 1104 is specifically used to:
  • initialization context information and attachment completion information sent by the base station where the initialization context information is information sent by the base station after receiving the connection reconfiguration complete message returned by the user terminal; Receiving, by the base station, the information that is forwarded after the direct transmission message that carries the attachment completion information sent by the user terminal;
  • control unit 1105 is further configured to instruct the tunnel establishing unit 1103 to stop running when the authentication security unit 1102 fails to run.
  • control unit 1105 is further configured to: before determining that the tunnel establishing unit 1103 stops running, determining whether the authentication security unit 1102 has sent a create session request message to the SGW; if yes, instructing the authentication security unit 1102 to Sending, by the SGW, a delete session request, and sending an attach reject message to the user terminal; otherwise, sending an attach reject message directly to the user terminal.
  • control unit 1105 is further configured to: when the operation of the tunnel establishing unit 1103 fails, instruct the authentication security unit 1102 to stop running.
  • control unit 1105 instructs the tunnel establishing unit 1103 to send an attach reject message to the user terminal, where the attach reject message carries a cause value.
  • the user terminal context information is serially executed.
  • the process of authentication, security process, tunnel creation, default bearer, etc. therefore, the delay of serial execution is large.
  • the inventor has found that the authentication process and the security process are based on the passing between the MME and the e B and the UE.
  • the S1 interface is performed, and the tunnel is created on the S ll and S5/8 interfaces between the MME, the SGW, and the PGW. Therefore, after the context information of the user terminal is acquired by using the technical solution of the present invention, the parallel execution is performed. a rights process and a security process, and establishing a tunnel for information transmission with the user terminal, thus, compared to prior art serials Performing the above steps reduces the delay of the user terminal to the network and improves the attachment efficiency to some extent.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种附着到E-UTRAN的方法及移动性管理实体,以降低用户终端附着到网络中的时延,提高附着效率。附着方法包括:步骤 A、网络侧在接收到用户终端发送的附着请求时,获取所述用户终端的上下文信息;步骤 B,网络侧执行与所述用户终端之间的鉴权过程和安全过程;步骤 C、网络侧建立与所述用户终端之间用于信息传输的隧道;步骤 D、网络侧建立与所述用户终端之间的默认承载;在成功执行步骤 A之后,并行执行所述步骤 B与所述步骤 C;并在确认成功执行所述步骤 B和步骤 C之后执行步骤 D。

Description

一种附着到 E-UTRAN的方法及移动性管理实体 本申请要求在 2011年 12月 06日提交中国专利局、 申请号为 201110402126.8、发明名 称为 "一种附着到 E-UTRAN的方法及移动性管理实体"的中国专利申请的优先权, 其全部 内容通过引用结合在本申请中。 技术领域
本发明涉及通信领域, 尤其涉及一种附着到 E-UTRAN ( Evolved Universal Terrestrial Radio Access Network, 演进的通用陆地无线接入网) 的方法及移动性管理实体。 背景技术
随着用户对网络性能的要求的提高, 用户希望终端接入网络的时间越来越短, 即附着 到网络的附着过程的时延尽可能小, 以提高长期演进(Long Term Evolvement, LTE ) 1 统框架演进( System Architecture Evolution, SAE ) 网络的性能。
目前, 在 E-UTRAN中的初始附着过程中, 包括以下子过程: 子过程 1、 网络侧与用 户终端 ( User Equipment , UE )之间进行交互, 以进行认证、 鉴权、 安全确认等过程; 子 过程 2、 在网络侧建立与所述用户终端之间的隧道; 子过程 3、 在建立网络侧与用户终端 之间的隧道之后 , 网络侧建立默认承载。 从上可以看出, 整个附着过程的总时延为各子过 程的时延的和值。
根据 23401-940协议中的描述, 针对以下情况可釆用如图 1所示的附着流程: 在网络 侧中没有存储用户终端的上下文信息, 且用户终端发送的附着请求不携带会话管理信息传 输标记或者携带会话管理信息传输标记但不置位的。
参见图 1 , 为现有技术中用户终端附着到网络侧的附着过程流程图, 包括:
步骤 101 , UE向演进基站( evolved NodeB , e B )发送附着请求消息(即 Attach Request ) 和网络选择指示, 其中所述附着请求消息中携带有所述 UE 的临时移动签约用户标识 ( Temporary Mobile Subscriber Identity, TMSI )、 UE 能力和分组数据网络 ( Packet Data Network, PDN )地址等参数。
步骤 102, eNB根据接收到的附着请求消息中的服务的临时移动签约用户标识( Service Temporary Mobile Subscriber Identity, S-TMSI )和网络选择指示确定出相应的移动性管理 实体( Mobility Management Entity, MME ), 并将附着请求消息转发给确定出的 MME。
上述步骤 102中,若 eNB才 居附着请求中的 TMSI和网络选择指示无法确定出相应的 MME时,通过 "MME选择功能"选择一个 MME,并将附着请求消息转发给选取的 MME。
步骤 103 , MME确定所述 UE发起的附着类型为无效全球唯一临时用户标识( Globally Unique Temporary UE Identity, GUTI ) 附着, 且在网络侧中没有存储所述 UE的上下文信 息时, 所述 MME向所述 UE发送认证请求消息 (即 Identity Request )。
步骤 104, UE接收到 MME下发的认证请求消息之后, 向所述 MME发送认证请求响 应消息 (即 Identity Response ), 并在该认证请求响应消息中携带该 UE的国际移动用户识 另1 J码(International Mobile Subscriber Identity, IMSI )信息。
步骤 105 , MME向归属地签约数据服务器( Home Subscriber Server, HSS )发送鉴权 信息请求消息 (即 Authentication Information Request消息 )。
步骤 106, HSS在接收到 MME发送的鉴权信息请求消息时, 向所述 MME发送鉴权 信息应答消息(即 Authentication Information Answer消息), 并在该筌权信息应答消息中携 带有多组鉴权向量。
步骤 107, MME从接收到的多组鉴权向量中选取一组鉴权向量, 并向所述 UE发送鉴 权请求(即 Authentication Request ), 该鉴权请求中携带选取的所述一组鉴权向量。
步骤 108,所述 UE在接收到 MME下发的鉴权请求时,对该鉴权请求中携带的一组鉴 权向量进行鉴权, 并在鉴权成功时向所述 MME 发送鉴权响应消息 (即 Authentication Response ), 并在所述鉴权响应消息中携带期望回复值 ( Expected Response , XRES )参数。
步骤 109, MME接收到所述 UE发送的鉴权响应消息后, 将所述鉴权响应消息中的 XRES参数与本地存储的 XRES参数进行比较,若一致则确定鉴权成功; 在鉴权成功之后, 利用密钥 Kasme生成完整性保护密钥和加密密钥,并向 UE发送安全模式命令(即 Security Mode Command ), 所述安全模式命令中携带有所述完整性保护密钥和加密密钥, 即发起安 全控制过程。
步骤 110, UE接收到所述 MME下发的安全模式命令时, 对所述安全模式命令中携带 的完整性保护密钥和加密密钥进行校验, 并在校验成功时, 向所述 MME发送安全模式完 成消息 (即 Security Mode Complete ), 即完成安全控制过程。
步骤 111 , MME向所述 UE发送用于表示索要所述 UE的 IMEI信息的认证请求消息 (即 Identity Request ), 并在该认证请求消息中携带有标识类型。
步骤 112,所述 UE在接收到所述 MME下发的认证请求消息时,根据所述标识类型确 定出相应的 IMEI, 并向所述 MME发送认证响应消息 (Identity Response ), 并在该认证响 应消息中携带确定出的所述 IMEI。
步骤 113 , MME和设备标识寄存器( Equipment Identity register, EIR )之间通过设备 标识检查(ME Identity Check )过程, 判断是否允许所述 UE接入, 并在允许接入时继续 后续步骤, 在不允许接入时结束流程。
步骤 114, MME向 HSS发送位置更新消息 (即 Updata Location Request )。 步骤 115 , HSS向 MME回复位置更新应答 ( ACK )消息(即 Updata Location Answer ); 若所述 MME根据所述位置更新 ACK消息确定 HSS拒绝更新, 则拒绝该 UE的附着请求, 并结束流程; 若所述 MME根据所述位置更新 ACK消息确定 HSS接受更新,则接受该 UE 的附着请求, 并继续后续的步骤。
步骤 116, MME选择一个服务网关 ( Serving Gateway, SGW ), 向选择的所述 SGW 发送创建会话请求消息 (即 Creat Session Request ) , 该创建会话请求消息中携带有 IMSI、 ΜΜΕ的上下文信息的 ID、 无线接入技术( Radio Acess Technology, RAT )类型、 默认承 载服务盾量(Quality of Service, QoS )、 PDN地址分配以及总计最大比特率 (Aggregate Maximum Bit Rate, AMBR )等参数。
步骤 117, SGW在其演进分组核心 (Evolved Packet Cor, EPC )承载列表中创建一个 入口, 并将接收到的所述创建会话请求消息转发给 PDN网关 (PDN Gateway, PGW )。
步骤 118, 若网络侧使用了策略控制计费规则功能(Policy Control and Charging Rule Function, PCRF )实体, 所述 PGW与 PCRF实体进行交互以获取策略和计费控制 (Policy and Charging Control, PCC )规则; 所述 PCC规则为需要建立默认演进分组系统( Evolved Packet System, EPS )承载时在 PGW中预定义的规则。
步骤 119, PGW向 SGW返回创建会话响应消息 (即 Create Session Response ), 该创 建会话响应消息中携带有用户面 PGW地址和隧道端点标识(Tunnel Endpoint Identifier, TEID )、 控制面 PDN网关隧道端点标识(PDN Gateway Tunnel Endpoint Identifier, PGW TEID )、 PDN类型、 PDN地址、协议配置选项、计费 ID、接入点名称( Access Point Name, APN )限制、 原因值以及接入点最大比特速率( Access Point Name Aggregate Maximum Bit Rate, APN- AMBR )等参数。
步骤 120 , SGW在接收到所述 PGW发送的创建会话响应消息时, 向所述 MME返回 创建会话响应消息(即 Create Session Response ),该创建会话响应消息中携带有 PDN类型、 PDN地址、 用户面 SGW地址与 TEID、 控制面 SGW TEID、 EPS 载标识符和 PGW地址 等。
步骤 121 , MME向 eNB发送初始上下文建立请求(即 Initial Context Setup Request ) 消息,该初始上下文建立消息中嵌套有附着接受消息(即 Attach Accept );其中,如果 MME 为所述 UE分配了一个新的 GUTI , 则所述附着接受消息中还携带有所述新的 GUTI参数; 所述初始上下文建立请求包含 UE的安全上下文、切换限制列表、承载 QoS参数以及 AMBR 相关的 PDN地址信息, 以及需要建立承载的 QoS信息。
步骤 122, eNB接收到 MME发送的附着接受消息时, 向所述 UE发送无线资源控制 协议( Radio Resource Control, RRC )连接重配置消息(即 Radio Resource Control Connection
Reconfiguration ),并向所述 UE发送附着接受消息,该附着接受消息中携带有 S-TMSI、 PDN 地址、 跟踪区域 ( Trace Area, TA ) 列表及 PDN地址信息等。
步骤 123 , UE 向 e B 发送 RRC 连接重配置完成消息 (即 RRC Connection Reconfiguration Complete )。
步骤 124 , eNB向 MME发送初始上下文消息 (即 Initial Context Setup Response ), 该 初始上下文消息中携带有 eNB的 TEID和 eNB在 S 1-U接口的下行传输地址等信息。
步骤 125 , UE向 eNB发送直传消息 (即 Direct Transfer ), 该直传消息包含附着完成 消息 (即 Attach Complete )。
步骤 126 , eNB将所述直传消息中的附着完成消息转发给 MME。
UE根据附着接受消息中携带的 PDN地址, 通过 eNB向 SGW发送上行数据包, 再通 过 SGW将所述上行数据包通过隧道地址发送给 PGW。
步骤 127 , MME向 SGW发送承载更新请求消息 (即 Modify Bearer Request )。
步骤 128 , 如果 MME发送给 SGW 的所述承载更新请求消息中携带有切换指示(即 Handover Indication) ,则 SGW需要向 PGW发送承载更新请求消息( Modify Bearer Request ); 否则, 直接执行以下步骤 130。
步骤 129 , PGW向 SGW回复承载更新响应消息 (即 Modify Bearer Response )。
步骤 130 , SGW向 MME返回承载更新响应消息(即 Modify Bearer Response ), 此时, SGW可以发送緩存的下行分组数据。
步骤 131 , 在步骤 130中 MME接收到承载更新响应消息后, 如果建立了一个 EPS承 载, 则向 HSS发送用于用户的移动性管理的通知请求消息(即 Notify Request ), 该通知请 求消息中携带有 APN和 PGW标识。
步骤 132 , HSS存储所述通知消息中携带的 APN和 PGW标识, 并向所述 MME发送 通知响应消息 (即 Notify Response ), 从而完成整个附着过程。
现有的附着流程中需要交互至少 22个消息, 该 22个消息分别在 S l、 S l l、 S5/8、 S6a 等接口上进行交互; 在整个流程中, 至少要经历 11个子过程, 才能完成整个附着过程。
目前, 针对在网络侧不存在用户的上下文信息, 以及终端发送的附着请求中不携带会 话管理信息传输标记或者携带会话管理信息传输标记但不置位的情况, 釆用如图 1所示的 附着流程; 但是上述附着流程中所有步骤按照串行方式执行, 因此消耗时延比较大, 如上 述附着流程的总时延为各子流程所消耗的时延的和值。 发明内容
针对现有技术中在网络附着过程存在时延较大、 效率较低的问题, 本发明实施例提供 一种附着到 E-UTRAN的方法及移动性管理实体, 以降低用户终端附着到网络中的时延, 提高附着效率。 一种附着到演进的通用陆地无线接入网 E-UTRAN的附着方法, 包括: 步骤 A、 网络侧在接收到用户终端发送的附着请求时, 获取所述用户终端的上下文信 息;
步骤 B , 网络侧执行与所述用户终端之间的鉴权过程和安全过程;
步骤 C、 网络侧建立与所述用户终端之间用于信息传输的隧道;
步骤 D、 网络侧建立与所述用户终端之间的默认承载;
在成功执行步骤 A之后 , 并行执行所述步骤 B与所述步骤 C; 并在确认成功执行所述 步骤 B和步骤 C之后执行步骤 D。
一种移动性管理实体 MME, 包括上下文信息获取单元、 鉴权安全单元、 隧道建立单 元、 默认承载单元和控制单元, 其中:
上下文信息获取单元, 用于在接收到用户终端通过其所归属的基站发送的附着请求 时, 获取所述用户终端的上下文信息;
鉴权安全单元, 用于执行所述 MME与所述用户终端之间的鉴权过程和安全过程; 隧道建立单元, 用于建立与所述用户终端之间用于传输信息的隧道;
默认承载单元, 用于建立与所述用户终端之间的默认承载;
控制单元, 用于在上下文信息获取单元成功运行之后, 启动所述鉴权安全单元和所述 隧道建立单元并行运行; 以及,在所述鉴权安全单元和所述隧道建立单元均成功运行之后, 启动所述默认正在单元运行。
本发明实施例中, 在接收到用户终端发送的附着请求时获取用户终端的上下文信息; 再并行执行以下步骤: 进行与用户终端之间的鉴权过程和安全过程, 以及建立与所述用户 终端之间用于信息传输的隧道; 在成功后再建立与用户终端之间的默认承载。 釆用本发明 技术方案, 由于在获取用户终端的上下文信息之后, 并行执行鉴权过程和安全过程, 以及 建立与所述用户终端之间用于信息传输的隧道, 因此, 相对于现有技术中串行执行上述步 骤而言, 在一定程度上降低了用户终端附着到网络中的时延和提高了附着效率。 附图说明
图 1为现有技术中用户终端附着到网络中的附着信令流程图;
图 2为本发明实施例中用户终端附着到网络中的附着方法流程图;
图 3为本发明实施例中获取用户终端上下文信息的方法流程图;
图 4为本发明实施例中执行网络侧与用户终端之间的鉴权过程和安全过程的方法流程 图之一;
图 5为本发明实施例中执行网络侧与用户终端之间的鉴权过程和安全过程的方法流程 图之二; 图 6为本发明实施例中建立网络侧与用户终端之间的隧道的方法流程图之一; 图 7为本发明实施例中建立网络侧与用户终端之间的隧道的方法流程图之二; 图 8为本发明实施例中建立网络侧与用户终端之间的默认承载的方法流程图之一; 图 9为本发明实施例中建立网络侧与用户终端之间的默认承载的方法流程图之二; 图 10为本发明实施例中用户终端附着到网络中的信令流程图;
图 11为本发明实施例中移动性管理实体的结构示意图。 具体实施方式
针对以下附着场景现有技术中的网络附着过程存在时延较大、 效率较低的问题: 用户 终端使用 IMSI或者无效 GUTI进行附着; 网络侧中没有保存 UE的上下文信息; 在用户终 端发起的附着请求消息中所包含的 PDN连接请求( PDN Connectivity Request )消息中不包 含会话管理消息传输标记 (ESM Information Transfer flag, EIT )选项或者 EIT置为 0 (取值 为 0时表示传输不需要加密)。本发明实施例对此,提供了一种演进 E-UTRAN中的附着方 法及一种移动性管理实体, 以降低用户终端附着到网络中的时延, 提高附着效率。 本发明 实施例中, 附着方法可包括: 步骤 A、 网络侧在接收到用户终端发送的附着请求时, 获取 所述用户终端的上下文信息; 步骤 B , 网络侧执行与所述用户终端之间的鉴权过程和安全 过程; 步骤 C、 网络侧建立与所述用户终端之间用于信息传输的隧道; 步骤 D、 网络侧建 立与所述用户终端之间的默认承载; 在成功执行步骤 A之后 , 并行执行所述步骤 B与所述 步骤 C; 并在确认成功执行所述步骤 B和步骤 C之后执行步骤 D。 釆用本发明技术方案, 由于并行执行步骤 B和步骤 C , 相对于现有技术中串行执行步骤 A〜步骤 D而言, 缩短了 用户终端附着到网络中的时延, 提高了用户终端附着到网络中的效率。
下面结合说明书附图对本发明技术方案进行详细的描述。
参见图 2、 为本发明实施例中用户终端附着到网络中的方法流程图, 该方法包括步骤 21〜步骤 24 , 其中, 在成功执行步骤 21之后, 并行执行步骤 22和步骤 23 , 在成功执行完 步骤 22和步骤 23之后执行步骤 24:
步骤 21、 网络侧在接收到用户终端发送的附着请求时, 获取所述用户终端的上下文信 息。
步骤 22、 网络侧执行与所述用户终端之间的鉴权过程和安全过程。
步骤 23、 网络侧建立与所述用户终端之间用于信息传输的隧道。
步骤 24、 网络侧建立与所述用户终端之间的默认承载。
上述方法流程中, 步骤 21具体包括以下子步骤, 如图 3所示:
步骤 211、 网络侧的基站接收所述用户终端发送的附着请求(即 Attach Request )和网 络选择指示。 上述附着请求消息中携带有所述 UE的 TMSI、 UE能力和 PDN地址等参数。
步骤 212、基站根据所述附着请求和所述网络选择指示选取 MME, 并将所述附着请求 转发给选取的所述 MMEo
步骤 213、 MME确定所述附着请求为无效 GUTI附着, 且确定本地没有存储所述用户 终端的上下文信息时, 向所述用户终端发送用于表示获取所述用户终端的 IMSI信息的认 证请求消息 (即 Identity Request )。
步骤 214、 MME接收所述用户终端返回的携带有所述用户终端的 IMSI信息的认证请 求响应消息 (即 Identity Response )。
上述步骤 22, 具体可包括以下子步骤, 如图 4所示:
步骤 221、 所述 MME向 HSS发送用于表示获取鉴权向量的鉴权信息请求消息 (即
Authentication Information Request消' Ί )。
步骤 222、 所述 MME接收所述 HSS 返回的鉴权信息响应消息 (即 Authentication Information Answer消息), 所述鉴权信息响应消息中携带有多组鉴权向量。
步骤 223、 所述 MME从所述鉴权信息响应消息中携带的多组鉴权向量中选取一组鉴 权向量, 并向所述用户终端发送鉴权请求(即 Authentication Request ), 所述鉴权请求中携 带有选取的鉴权向量。
步骤 224、 所述 MME接收所述用户终端返回的鉴权响应消息 (即 Authentication Response ),所述鉴权响应消息为所述用户终端对接收到的鉴权请求中携带的鉴权向量进行 鉴权成功后所发送的消息, 且所述鉴权响应消息中携带有 XRES参数。
步骤 225、 所述 MME将接收到的所述鉴权响应消息中的 XRES 参数与本地存储的
XRES参数进行比较, 在一致时确定鉴权成功, 并利用密钥生成完整性保护密钥和加密密 钥, 并向所述用户终端发送安全模式命令消息(即 Security Mode Command ), 所述安全模 式命令消息中携带有所述完整性保护密钥和加密密钥。
步骤 226、 所述 MME接收所述用户终端返回的安全模式完成消息 (即 Security Mode Complete ),所述安全模式完成消息为所述用户终端在接收到所述安全模式命令消息时对所 述完整性保护密钥和加密密钥进行完整性认证成功之后发送的消息。
步骤 227、 所述 MME与 RIE之间通过设备标识检查(即 ME Identity Check )过程判 断是否允许所述用户终端附着到网络侧; 若不允许则结束流程, 若允许则继续执行后续步 骤。
较佳地, 当 MME需要获取用户终端的 IMEI信息时, 上述步骤 226和步骤 227之间 还包括以下子步骤, 如图 5所示:
步骤 226a、 所述 MME向所述用户终端发送用于表示获取所述用户终端的 IMEI信息 的认证请求消息, 所述认证请求消息中携带有标识类型信息。 步骤 226b、所述 MME接收所述用户终端返回的携带有与所述标识类型相对应的 IMEI 信息。
上述流程中的步骤 23还可具体包括以下子步骤, 如图 6所示:
步骤 231、 所述 MME向所述 HS S发送位置更新消息。
步骤 232、 所述 MME接收所述 HSS返回的位置更新响应消息; 在根据所述位置更新 响应消息确定所述 HSS拒绝进行位置更新时, 所述 MME拒绝所述用户终端的本次附着, 并结束流程; 否则继续下述步骤。
步骤 233、所述 MME选取一个 SGW, 并向选取的所述 SGW发送创建会话请求消息。 步骤 234、 所述 SGW在接收到所述创建会话请求消息时, 在该 SGW的 EPC承载列 表中创建一个入口, 并向 PGW发送创建会话请求消息。
步骤 235、 所述 SGW接收所述 PGW返回的创建会话响应消息。
步骤 236、 所述 SGW向所述 MME返回创建会话响应消息。
较佳地, 当所述网络侧使用了 PCRF实体时, 所述步骤 234和步骤 235之间还包括以 下子步骤, 如图 7所示:
步骤 234a、 所述 PGW从所述 PCRF实体中获取 PCC规则, 所述 PCC规则为在建立
EPS承载时在所述 PGW中预定义的规则。
上述流程的步骤 24具体可包括以下子步骤, 如图 8所示:
步骤 241、 所述 MME向所述基站发送附着接受消息。
步骤 242、 所述基站向所述用户终端发送 RRC连接重配置消息, 并将接收到的所述附 着接受消息转发给所述用户终端。
步骤 243、 所述基站接收所述用户终端返回的连接重配置完成消息。
步骤 244、 所述基站向所述 MME发送所述基站的初始上下文信息。
步骤 245、 所述基站接收所述用户终端发送的携带有附着完成信息的直传消息, 并将 所述附着完成信息转发给所述 MME。
步骤 246、 所述 MME向所述 SGW发送承载更新请求消息。
步骤 247、 所述 MME接收所述 SGW返回的承载更新响应消息, 并建立 EPS承载, 并向所述 HSS发送通知请求消息,所述通知请求消息中携带有用于用户移动性管理的 APN 信息和 PGW标识信息。
步骤 248、 所述 HSS存储所述 APN信息和 PGW标识信息, 并建立 APN与 PGW标 识信息的对应关系; 并向所述 MME返回通知响应消息, 以指示完成附着过程。
较佳地, 当所述 MME发送给所述 SGW的承载更新请求消息中携带有切换指示时, 在上述步骤 246与步骤 247之间还包括以下子步骤, 如图 9所示:
步骤 246a、 所述 SGW向所述 PGW发送承载更新请求消息; 步骤 246b、 所述 SGW接收所述 SGW返回的承载更新响应消息。
较佳地, 为确保用户终端成功附着到网络的成功率, 本发明实施例中, 当上述步骤 22 中的任意一个子步骤执行失败时, 停止执行步骤 22的后续子步骤以及停止执行步骤 23的 后续子步骤; 较佳地, 为确保建立会话的准确性, 本发明实施例中, 当步骤 22 中的某一 子步骤执行失败时, 若已经执行步骤 23中的子步骤 234, 则所述 MME向所述 SGW和所 述 PGW分别发送删除会话请求, 以指示所述 SGW和所述 PGW删除已经建立的会话, 并 向所述用户终端发送附着拒绝消息; 若还未执行步骤 23中的子步骤 234, 则所述 MME直 接向所述用户终端发送附着拒绝消息。
当上述步骤 23中的任意一个子步骤执行失败时, 停止执行步骤 22的后续子步骤以及 停止执行步骤 23的后续子步骤。 优选地, 所述 MME向所述用户终端发送附着拒绝消息, 所述附着拒绝消息中携带有原因值。
基于前述方法流程, 本发明实施例还提供用户终端附着到网络中的信令流程图, 该信 令流程图可如图 10所示, 包括步骤 al〜步骤 a4、 步骤 bl〜步骤 b9、 步骤 cl〜步骤 c7以及 步骤 dl〜步骤 dl2, 其中: 步骤 al〜步骤 a4为图 2中的步骤 21的子步骤, 对应于前述步骤 211〜步骤 214; 步骤 bl〜步骤 b9为图 2中的步骤 22的子步骤, 对应于前述步骤 221〜步骤 227; 步骤 cl〜步骤 c7为图 2中的步骤 23的子步骤, 对应于前述步骤 231〜步骤 236; 步骤 dl〜步骤 dl2为图 2中步骤 24的子步骤, 对应于前述步骤 241〜步骤 248; 步骤 bl〜步骤 b9 和步骤 cl〜步骤 c7并行执行, 并在成功执行步骤 bl〜步骤 b9和步骤 cl〜步骤 c7之后, 再 执行步骤 dl〜步骤 dl2; 该信令流程是以 MME需要获取用户终端的 IMEI信息、 网络侧使 用了 PCRF为例。
步骤 al、 UE向 e B发送 Attach Request (即附着请求消息 )和网络选择指示, 其中 所述附着请求消息中携带有所述 UE的 TMSI、 UE能力和 PDN地址等参数。
步骤 a2、 eNB根据接收到的附着请求消息中的 TMSI和网络选择指示确定出相应的 MME, 并将附着请求消息转发给确定出的 MME。
步骤 a3、 MME确定所述 UE发起的附着类型为无效 GUTI附着, 且在网络侧中没有 存储所述 UE的上下文信息时, 向所述 UE发送 Identity Request (即认证请求消息)。
步骤 a4、 UE接收到 MME下发的 Identity Request之后, 向所述 MME发送 Identity Response (即认证请求响应消息), 并在该认证请求响应消息中携带该 UE的 IMSI信息。
步骤 bl、MME向 HSS发送 Authentication Information Request(即鉴权信息请求消息)。 步骤 b2、 HSS在接收到 MME发送的 Authentication Information Request时, 向所述
MME发送 Authentication Information Answer(即筌权信息应答消息),并在该 Authentication
Information Answer中携带有多组筌权向量。
步骤 b3、 MME从接收到的多组鉴权向量中选取一组鉴权向量, 并向所述 UE发送 Authentication Request (即筌权请求), 该 Authentication Request中携带选取的所述一组筌 权向量。
步骤 b4、所述 UE在接收到 MME下发的 Authentication Request时,对该 Authentication Request中携带的一组鉴权向量进行鉴权 ,并在鉴权成功时向所述 MME发送 Authentication Response (即筌权响应消息), 并在所述 Authentication Response中携带 XRES参数。
步骤 b5、 MME接收到所述 UE发送的 Authentication Response后,将所述 Authentication Response中的 XRES参数与本地存储的 XRES参数进行比较, 若一致则确定鉴权成功; 在 鉴权成功之后, 利用密钥 Kasme生成完整性保护密钥和加密密钥, 并向 UE发送 Security Mode Command (即安全模式命令 ), 所述 Security Mode Command中携带有所述完整性保 护密钥和加密密钥, 即发起安全控制过程。
步骤 b6、UE接收到所述 MME下发的 Security Mode Command时,对所述 Security Mode Command中携带的完整性保护密钥和加密密钥进行校验, 并在校验成功时, 向所述 MME 发送 Security Mode Complete (即安全模式完成消息), 即完成安全控制过程。
步骤 b7、 MME向所述 UE发送用于表示索要所述 UE的 IMEI信息的 Identity Request (即认证请求消息), 并在该 Identity Request中携带有标识类型。
步骤 b8、 所述 UE在接收到所述 MME下发的认证请求消息时, 根据所述标识类型确 定出相应的 IMEI,并向所述 MME发送 Identity Response(即认证响应消息),并在该 Identity Response中携带确定出的所述 IMEI。
步骤 b9、 MME和 EIR之间通过 ME Identity Check过程,判断是否允许所述 UE接入, 并在允许接入时继续后续步骤, 在不允许接入时结束流程。
步骤 cl、 MME向 HSS发送 Updata Location Request (即位置更新消息)。
步骤 c2、 HSS向 MME回复位置更新 ACK消息 (即 Updata Location Answer ); 若所 述 MME根据所述位置更新 ACK消息确定 HSS拒绝更新, 则拒绝该 UE的附着请求, 并 结束流程; 若所述 MME根据所述位置更新 ACK消息确定 HSS接受更新, 则接受该 UE 的附着请求, 并继续后续的步骤。
步骤 c3、 MME选择一个 SGW, 向选择的所述 SGW发送 Creat Session Request (即创 建会话请求消息)。
上述 Creat Session Request中携带有 IMSI、 MME的上下文信息的 ID、 RAT信息、 默 认承载 QoS 、 PDN地址分配以及 AMBR等参数。
步骤 c4、 SGW在其 EPC承载列表中创建一个入口, 并将接收到的所述 Create Session
Request转发给 PGW。
步骤 c5、 所述 PGW与 PCRF进行交互以获取 PCC规则; 所述 PCC规则为需要建立 默认 EPS承载时在 PGW中预定义的规则。 步骤 c6、 PGW向 SGW返回 Create Session Response (即创建会话响应消息)。
上述 Create Session Response中携带有用户面 PGW地址和 TEID 、控制面 PGW TEID 、 PDN类型、 PDN地址、 协议配置选项、 计费 ID、 APN 限制、 原因值以及 APN-AMBR等 参数。
步骤 c7、 SGW在接收到所述 PGW发送的 Create Session Response时, 向所述 ΜΜΕ 返回 Create Session Response, 该 Create Session Response中携带有 PDN类型、 PDN地址、 用户面 SGW地址与 TEID、 控制面 SGW TEID, EPS承载标识符和 PGW地址等。
步骤 dl、 MME向 eNB发送 Attach Accept (即附着接受消息); 如果 MME为所述 UE 分配了一个新的 GUTI, 则所述 Attach Accept中还携带有 GUTI参数。
步骤 d2、 eNB接收到 MME发送的 Attach Accept时, 向所述 UE发送 RRC Connection
Reconfiguration (即 RRC连接重配置消息), 并向所述 UE发送附着接受消息; 该附着接受 消息中携带有 S-TMSI、 PDN地址、 TA列表及 PDN地址信息等。
步骤 d3、UE向 eNB发送 RRC连接重配置完成消息(即 RRC Connection Reconfiguration Complete )。
步骤 d4、 eNB向 MME发送初始上下文消息(即 Initial Context Setup Response ), 该初 始上下文消息中携带有 eNB的 TEID和 eNB在 S1-U接口的下行传输地址等信息。
步骤 d5、 UE向 eNB发送直传消息 (即 Direct Transfer ) , 该消直传消息包含附着完成 消息 (即 Attach Complete )。
步骤 d6、 eNB将所述直传消息中的附着完成消息转发给 MME。
步骤 d7、 MME向 SGW发送承载更新请求消息 (即 Modify Bearer Request )。
步骤 d8、 如果 MME发送给 SGW 的所述承载更新请求消息中携带有切换指示(即
Handover Indication),则 SGW需要向 PGW发送承载更新请求消息( Modify Bearer Request )。
步骤 d9、 PGW向 SGW回复承载更新响应消息 (即 Modify Bearer Response )。
步骤 dl0、 SGW向 MME返回承载更新响应消息(即 Modify Bearer Response ), 此时, SGW可以发送緩存的下行分组数据。
步骤 dl 1、 在步骤 dlO中 MME接收到承载更新响应消息后, 如果建立了一个 EPS承 载, 则向 HSS发送用于用户的移动性管理的通知请求消息(即 Notify Request ), 该通知请 求消息中携带有 APN和 PGW标识。
步骤 dl2、 HSS存储所述通知消息中携带的 APN和 PGW标识, 并向所述 MME发送 通知响应消息 (即 Notify Response ), 从而完成整个附着过程。
基于前述方法流程, 本发明实施例还提供一种移动性管理实体, 该移动性管理实体的 结构可如图 11所示, 包括:
上下文信息获取单元 1101、 鉴权安全单元 1102、 隧道建立单元 1103、 默认承载单元 1104和控制单元 1105 , 其中:
上下文信息获取单元 1101 ,用于在接收到用户终端通过其所归属的基站发送的附着请 求时, 获取所述用户终端的上下文信息;
鉴权安全单元 1102,用于执行所述 MME与所述用户终端之间的鉴权过程和安全过程; 隧道建立单元 1103 , 用于建立与所述用户终端之间用于传输信息的隧道;
默认承载单元 1104, 用于建立与所述用户终端之间的默认承载;
控制单元 1105 , 用于在上下文信息获取单元 1101成功运行之后, 启动所述鉴权安全 单元 1102和所述隧道建立单元 1103并行运行; 以及,在所述鉴权安全单元 1102和所述隧 道建立单元 1103均成功运行之后, 启动所述默认承载单元 1104运行。
所述上下文信息获取单元 1101 , 具体用于:
接收用户终端通过所述用户终端所归属的基站发送的附着请求;
确定所述附着请求为无效 GUTI附着, 且确定本地没有存储所述用户终端的上下文信 息时, 向所述用户终端发送用于表示获取所述用户终端的 IMSI信息的认证请求消息; 接收所述用户终端返回的携带有所述用户终端的 IMSI信息的认证请求响应消息。 较佳地,鉴权安全单元 1102建立所述 MME与所述用户终端之间的鉴权过程, 具体包 括:
向 HSS发送用于表示获取鉴权向量的鉴权信息请求消息;
接收所述 HSS返回的鉴权信息响应消息,所述鉴权信息响应消息中携带有多组鉴权向 量; 以及, 从所述多组鉴权向量中选取一组鉴权向量, 并向所述用户终端发送鉴权请求, 所述鉴权请求中携带有选取的鉴权向量;
接收所述用户终端返回的鉴权响应消息, 所述鉴权响应消息为所述用户终端对接收到 的鉴权请求中携带的鉴权向量进行鉴权成功后所发送的消息, 且所述鉴权响应消息中携带 有 XRES参数; 以及, 将接收到的所述鉴权响应消息中的 XRES参数与本地存储的 XRES 参数进行比较, 在一致时确定鉴权成功, 不一致时确定鉴权失败;
所述鉴权安全单元 1102建立所述 MME与所述用户终端之间的安全过程, 具体包括: 在确定鉴权成功后, 利用密钥生成完整性保护密钥和加密密钥, 并向所述用户终端发 送安全模式命令消息, 所述安全模式命令消息中携带有所述完整性保护密钥和加密密钥; 接收所述用户终端返回的安全模式完成消息, 所述安全模式完成消息为所述用户终端 在接收到所述安全模式命令消息时对所述完整性保护密钥和加密密钥进行完整性认证成 功之后发送的消息; 并通过与 RIE之间进行 ME Identity Check过程, 以判断是否允许所述 用户终端附着到网络侧。
较佳地, 隧道建立单元 1103 , 具体用于:
向所述 HSS发送位置更新消息; 接收所述 HSS 返回的位置更新响应消息, 并在根据所述位置更新响应消息确定所述 HSS拒绝进行位置更新时, 向所述用户终端发送拒绝附着请求消息, 否则进行以下操作: 选取一个服务网关 SGW, 并向选取的所述 SGW发送创建会话请求消息;
接收所述 SGW返回的创建会话响应消息,所述 SGW返回的创建会话响应消息为所述 SGW在演进分组核心 EPC承载列表中创建入口之后向 PGW发送创建会话请求消息之后, 接收到的所述 PGW返回的创建会话响应消息。
默认承载单元 1104 , 具体用于:
向所述基站发送附着接受消息, 以指示所述基站向所述用户终端发送 RRC 连接重配 置消息并将所述附着接受消息发送给所述用户终端;
接收所述基站发送的初始化上下文信息和附着完成信息, 所述初始化上下文信息为所 述基站接收到所述用户终端返回的连接重配置完成消息后所发送的信息; 所述附着完成信 息为所述基站接收到所述用户终端发送的携带有附着完成信息的直传消息之后转发的信 息;
向所述 SGW发送承载更新请求消息;
接收所述 SGW返回的承载更新响应消息, 建立 EPS承载, 并向所述 HSS发送通知请 求消息, 所述通知请求消息中携带有用于用户移动性管理的 APN信息和 PGW标识信息。
较佳地, 控制单元 1105进一步用于, 在所述鉴权安全单元 1102运行失败时, 指示隧 道建立单元 1103停止运行。
较佳地, 控制单元 1105进一步用于, 在指示所述隧道建立单元 1103停止运行前确定 鉴权安全单元 1102是否已经向所述 SGW发送创建会话请求消息; 若是, 则指示鉴权安全 单元 1102向所述 SGW发送删除会话请求, 并向所述用户终端发送附着拒绝消息; 否则直 接向所述用户终端发送附着拒绝消息。
较佳地, 控制单元 1105进一步用于, 在所述隧道建立单元 1103运行失败时, 指示所 述鉴权安全单元 1102停止运行。
较佳地, 控制单元 1105指示所述隧道建立单元 1103向所述用户终端发送附着拒绝消 息, 所述附着拒绝消息中携带有原因值。
现有技术中, 针对网络侧不存在用户上下文信息且用户终端发送的附着请求中不携带 会话管理信息传输标记或者携带会话管理信息传输标记但不置位的场景, 串行执行用户终 端上下文信息的获取、 鉴权过程、 安全过程、 创建隧道、 默认承载等过程, 因此, 串行执 行的时延较大。 本发明人发现, 鉴权过程和安全过程是基于 MME和 e B、 UE之间通过
S 1接口进行, 而创建隧道 ^&于 MME、 SGW、 PGW之间的 S l l、 S5/8接口上进行; 因 此, 釆用本发明技术方案, 在获取用户终端的上下文信息之后, 并行执行鉴权过程和安全 过程, 以及建立与所述用户终端之间用于信息传输的隧道, 因此, 相对于现有技术中串行 执行上述步骤而言, 在一定程度上降低了用户终端附着到网络中的时延和提高了附着效 率。
本发明是参照根据本发明实施例的方法、 设备(系统)、 和计算机程序产品的流程图 和 /或方框图来描述的。 应理解可由计算机程序指令实现流程图和 /或方框图中的每一流 程和 /或方框、 以及流程图和 /或方框图中的流程和 /或方框的结合。 可提供这些计算机 程序指令到通用计算机、 专用计算机、 嵌入式处理机或其他可编程数据处理设备的处理器 以产生一个机器, 使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用 于实现在流程图一个流程或多个流程和 /或方框图一个方框或多个方框中指定的功能的 装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方 式工作的计算机可读存储器中, 使得存储在该计算机可读存储器中的指令产生包括指令装 置的制造品, 该指令装置实现在流程图一个流程或多个流程和 /或方框图一个方框或多个 方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上, 使得在计算机 或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理, 从而在计算机或其他 可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和 /或方框图一个 方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例, 但本领域内的技术人员一旦得知了基本创造性概 念, 则可对这些实施例作出另外的变更和修改。 所以, 所附权利要求意欲解释为包括优选 实施例以及落入本发明范围的所有变更和修改。
显然, 本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和 范围。 这样, 倘若对本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之 内, 则本发明也意图包含这些改动和变型在内。

Claims

权 利 要 求
1、 一种附着到演进的通用陆地无线接入网 E-UTRAN的方法, 其特征在于, 包括: 步骤 A、 网络侧在接收到用户终端发送的附着请求时, 获取所述用户终端的上下文信 息;
步骤 B , 网络侧执行与所述用户终端之间的鉴权过程和安全过程;
步骤 C、 网络侧建立与所述用户终端之间用于信息传输的隧道;
步骤 D、 网络侧建立与所述用户终端之间的默认承载;
在成功执行步骤 A之后 , 并行执行所述步骤 B与所述步骤 C; 并在确认成功执行所述 步骤 B和步骤 C之后执行步骤 D。
2、 如权利要求 1所述的方法, 其特征在于, 所述步骤 A, 具体包括:
步骤 A1、 所述网络侧的基站接收所述用户终端发送的附着请求和网络选择指示; 步骤 A2、 所述基站根据所述附着请求和所述网络选择指示确定出移动性管理实体 MME , 并将所述附着请求转发给确定的所述 MME;
步骤 A3、 所述 MME确定所述附着请求为无效全球唯一临时用户标识 GUTI附着, 且 确定本地没有存储所述用户终端的上下文信息时, 向所述用户终端发送用于表示获取所述 用户终端的国际移动用户识别码 IMSI信息的认证请求消息;
步骤 A4、 所述 MME接收所述用户终端返回的携带有所述用户终端的 IMSI信息的认 证请求响应消息。
3、 如权利要求 2所述的方法, 其特征在于, 所述步骤 B具体包括:
步骤 B1、 所述 MME向归属地签约数据服务器 HSS发送用于表示获取鉴权向量的鉴 权信息请求消息;
步骤 B2、 所述 MME接收所述 HSS返回的鉴权信息响应消息, 所述鉴权信息响应消 息中携带有多组鉴权向量;
步骤 B3、所述 MME从所述鉴权信息响应消息中携带的多组鉴权向量中选取一组鉴权 向量, 并向所述用户终端发送鉴权请求, 所述鉴权请求中携带有选取的鉴权向量;
步骤 B4、 所述 MME接收所述用户终端返回的鉴权响应消息, 所述鉴权响应消息为所 述用户终端对接收到的鉴权请求中携带的鉴权向量进行鉴权成功后所发送的消息, 且所述 鉴权响应消息中携带有期望回复值 XRES参数;
步骤 B5、所述 MME将接收到的所述鉴权响应消息中的 XRES参数与本地存储的 XRES 参数进行比较, 在一致时确定鉴权成功, 并利用密钥生成完整性保护密钥和加密密钥, 并 向所述用户终端发送安全模式命令消息, 所述安全模式命令消息中携带有所述完整性保护 密钥和加密密钥;
步骤 B6、 所述 MME接收所述用户终端返回的安全模式完成消息, 所述安全模式完成 消息为所述用户终端在接收到所述安全模式命令消息时对所述完整性保护密钥和加密密 钥进行完整性认证成功之后发送的消息;
步骤 B7、所述 MME与设备标识寄存器 EIR之间通过设备标识检查过程判断是否允许 所述用户终端附着到网络侧。
4、 如权利要求 3所述的方法, 其特征在于, 在所述 B6与所述步骤 B7之间还包括: 步骤 B61、 所述 MME向所述用户终端发送用于表示获取所述用户终端的国际移动设 备标识 IMEI信息的认证请求消息, 所述认证请求消息中携带有标识类型信息;
步骤 B62、所述 MME接收所述用户终端返回的携带有与所述标识类型相对应的 IMEI 信息。
5、 如权利要求 3所述的方法, 其特征在于, 所述步骤 C具体包括:
步骤 Cl、 所述 MME向所述 HSS发送位置更新消息;
步骤 C2、 所述 MME接收所述 HSS返回的位置更新响应消息; 在根据所述位置更新 响应消息确定所述 HSS拒绝进行位置更新时, 所述 MME拒绝所述用户终端的本次附着, 并结束流程; 否则继续下述步骤;
步骤 C3、 所述 MME选取一个服务网关 SGW, 并向选取的所述 SGW发送创建会话 请求消息;
步骤 C4、 所述 SGW在接收到所述创建会话请求消息时, 在该 SGW的演进分组核心 EPC承载列表中创建一个入口, 并向 PDN网关 PGW发送创建会话请求消息;
步骤 C5、 所述 SGW接收所述 PGW返回的创建会话响应消息;
步骤 C6、 所述 SGW向所述 MME返回创建会话响应消息。
6、 如权利要求 5 所述的方法, 其特征在于, 当所述网络侧使用了策略控制计费规则 功能 PCRF实体时, 所述步骤 C4和步骤 C5之间还包括:
步骤 C41、 所述 PGW从所述 PCRF实体中获取策略和计费控制 PCC规则, 所述 PCC 规则为在建立 EPS承载时在所述 PGW中预定义的规则。
7、 如权利要求 5所述的方法, 其特征在于, 所述步骤 D具体包括:
步骤 D 1、 所述 MME向所述基站发送附着接受消息;
步骤 D2、 所述基站向所述用户终端发送无线资源控制协议 RRC连接重配置消息, 并 将接收到的所述附着接受消息转发给所述用户终端;
步骤 D3、 所述基站接收所述用户终端返回的连接重配置完成消息;
步骤 D4、 所述基站向所述 MME发送所述基站的初始上下文信息;
步骤 D5、所述基站接收所述用户终端发送的携带有附着完成信息的直传消息,并将所 述附着完成信息转发给所述 MME;
步骤 D6、 所述 MME向所述 SGW发送承载更新请求消息; 步骤 D7、 所述 MME接收所述 SGW返回的承载更新响应消息, 并建立 EPS承载, 并 向所述 HSS发送通知请求消息,所述通知请求消息中携带有用于用户移动性管理的接入点 名称 APN信息和 PGW标识信息;
步骤 D8、 所述 HSS存储所述 APN信息和 PGW标识信息, 并建立 APN与 PGW标识 信息的对应关系; 并向所述 MME返回通知响应消息, 以指示完成附着过程。
8、 如权利要求 7所述的方法, 其特征在于, 当所述 MME发送给所述 SGW的承载更 新请求消息中携带有切换指示时, 在所述步骤 D6与步骤 D7之间还包括:
步骤 D61、 所述 SGW向所述 PGW发送承载更新请求消息;
步骤 D62、 所述 SGW接收所述 SGW返回的承载更新响应消息。
9、 如权利要求 5所述的方法, 其特征在于, 当所述步骤 B中的任意一个子步骤执行 失败时, 停止继续执行所述步骤 C和所述步骤 B。
10、 如权利要求 9所述的方法, 其特征在于, 在停止执行所述步骤 C之前, 若已经执 行所述步骤 C4 , 所述 MME向所述 SGW和所述 PGW分别发送删除会话请求, 以指示所 述 SGW和所述 PGW删除已经建立的会话, 并向所述用户终端发送附着拒绝消息;
在停止执行所述步骤 C之前,若还未执行所述步骤 C4 ,所述 MME直接向所述用户终 端发送附着拒绝消息。
11、 如权利要求 5所述的方法, 其特征在于, 若所述步骤 C中的任意一个子步骤执行 失败, 则停止执行所述步骤 C和所述步骤 B。
12、 如权利要求 11所述的方法, 其特征在于, 所述 MME向所述用户终端发送附着拒 绝消息, 所述附着拒绝消息中携带有原因值。
13、 一种移动性管理实体 MME, 其特征在于, 包括上下文信息获取单元、 鉴权安全 单元、 隧道建立单元、 默认承载单元和控制单元, 其中:
上下文信息获取单元, 用于在接收到用户终端通过其所归属的基站发送的附着请求 时, 获取所述用户终端的上下文信息;
鉴权安全单元, 用于执行所述 MME与所述用户终端之间的鉴权过程和安全过程; 隧道建立单元, 用于建立与所述用户终端之间用于传输信息的隧道;
默认承载单元, 用于建立与所述用户终端之间的默认承载;
控制单元, 用于在上下文信息获取单元成功运行之后, 启动所述鉴权安全单元和所述 隧道建立单元并行运行; 以及,在所述鉴权安全单元和所述隧道建立单元均成功运行之后, 启动所述默认承载单元运行。
14、 如权利要求 13所述的移动性管理实体, 其特征在于, 所述上下文信息获取单元, 具体用于:
接收用户终端通过所述用户终端所归属的基站发送的附着请求; 确定所述附着请求为无效全球唯一临时用户标识 GUTI附着, 且确定本地没有存储所 述用户终端的上下文信息时, 向所述用户终端发送用于表示获取所述用户终端的国际移动 用户识别码 IMSI信息的认证请求消息;
接收所述用户终端返回的携带有所述用户终端的 IMSI信息的认证请求响应消息。
15、 如权利要求 14 所述的移动性管理实体, 其特征在于, 所述鉴权安全单元建立所 述 MME与所述用户终端之间的鉴权过程 , 具体包括:
向归属地签约数据服务器 HSS发送用于表示获取鉴权向量的鉴权信息请求消息; 接收所述 HSS返回的鉴权信息响应消息,所述鉴权信息响应消息中携带有多组鉴权向 量; 以及, 从所述多组鉴权向量中选取一组鉴权向量, 并向所述用户终端发送鉴权请求, 所述鉴权请求中携带有选取的鉴权向量;
接收所述用户终端返回的鉴权响应消息, 所述鉴权响应消息为所述用户终端对接收到 的鉴权请求中携带的鉴权向量进行鉴权成功后所发送的消息, 且所述鉴权响应消息中携带 有期望回复值 XRES参数; 以及, 将接收到的所述鉴权响应消息中的 XRES参数与本地存 储的 XRES参数进行比较, 在一致时确定鉴权成功, 不一致时确定鉴权失败;
所述鉴权安全单元建立所述 MME与所述用户终端之间的安全过程, 具体包括: 在确定鉴权成功后, 利用密钥生成完整性保护密钥和加密密钥, 并向所述用户终端发 送安全模式命令消息, 所述安全模式命令消息中携带有所述完整性保护密钥和加密密钥; 接收所述用户终端返回的安全模式完成消息, 所述安全模式完成消息为所述用户终端 在接收到所述安全模式命令消息时对所述完整性保护密钥和加密密钥进行完整性认证成 功之后发送的消息; 并通过与设备标识寄存器 EIR之间进行设备标识检查过程, 以判断是 否允许所述用户终端附着到网络侧。
16、 如权利要求 15 所述的移动性管理实体, 其特征在于, 所述隧道建立单元, 具体 用于:
向所述 HSS发送位置更新消息;
接收所述 HSS 返回的位置更新响应消息, 并在根据所述位置更新响应消息确定所述
HSS拒绝进行位置更新时, 向所述用户终端发送拒绝附着请求消息, 否则进行以下操作: 选取一个服务网关 SGW, 并向选取的所述 SGW发送创建会话请求消息;
接收所述 SGW返回的创建会话响应消息,所述 SGW返回的创建会话响应消息为所述 SGW在演进分组核心 EPC承载列表中创建入口之后向 PDN网关 PGW发送创建会话请求 消息之后, 接收到的所述 PGW返回的创建会话响应消息。
17、 如权利要求 16 所述的移动性管理实体, 其特征在于, 所述默认承载单元, 具体 用于:
向所述基站发送附着接受消息, 以指示所述基站向所述用户终端发送无线资源控制协 议 RRC连接重配置消息并将所述附着接受消息发送给所述用户终端;
接收所述基站发送的初始化上下文信息和附着完成信息, 所述初始化上下文信息为所 述基站接收到所述用户终端返回的连接重配置完成消息后所发送的信息; 所述附着完成信 息为所述基站接收到所述用户终端发送的携带有附着完成信息的直传消息之后转发的信 息;
向所述 SGW发送承载更新请求消息;
接收所述 SGW返回的承载更新响应消息, 建立 EPS承载, 并向所述 HSS发送通知请 求消息, 所述通知请求消息中携带有用于用户移动性管理的接入点名称 APN信息和 PGW 标识信息。
18、 如权利要求 13所述的移动性管理实体, 其特征在于, 所述控制单元进一步用于, 在所述鉴权安全单元运行失败时, 指示所述隧道建立单元停止运行。
19、 如权利要求 18所述的移动性管理实体, 其特征在于, 所述控制单元进一步用于, 在指示所述隧道建立单元停止运行前确定所述鉴权安全单元是否已经向所述 SGW发送创 建会话请求消息; 若是, 则指示所述鉴权安全单元向所述 SGW发送删除会话请求, 并向 所述用户终端发送附着拒绝消息; 否则直接向所述用户终端发送附着拒绝消息。
20、 如权利要求 13所述的移动性管理实体, 其特征在于, 所述控制单元进一步用于, 在所述隧道建立单元运行失败时, 指示所述鉴权安全单元停止运行。
21、 如权利要求 20 所述的移动性管理实体, 其特征在于, 所述控制单元指示所述隧 道建立单元向所述用户终端发送附着拒绝消息, 所述附着拒绝消息中携带有原因值。
PCT/CN2012/084122 2011-12-06 2012-11-06 一种附着到e-utran的方法及移动性管理实体 WO2013082984A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US14/362,916 US20140335830A1 (en) 2011-12-06 2012-11-06 Method for attaching e-utran and mobility management entity
JP2014545069A JP5813249B2 (ja) 2011-12-06 2012-11-06 E−utraへのアタッチ方法及び移動性管理エンティーティー
EP12854709.8A EP2790454B1 (en) 2011-12-06 2012-11-06 Method for attaching e-utran and mobility management entity
KR1020147018739A KR101671270B1 (ko) 2011-12-06 2012-11-06 E-utran에 부착하는 방법 및 이동성 관리 엔티티

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110402126.8 2011-12-06
CN2011104021268A CN102438330A (zh) 2011-12-06 2011-12-06 一种附着到e-tran的方法及移动性管理实体

Publications (1)

Publication Number Publication Date
WO2013082984A1 true WO2013082984A1 (zh) 2013-06-13

Family

ID=45986142

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/084122 WO2013082984A1 (zh) 2011-12-06 2012-11-06 一种附着到e-utran的方法及移动性管理实体

Country Status (6)

Country Link
US (1) US20140335830A1 (zh)
EP (1) EP2790454B1 (zh)
JP (1) JP5813249B2 (zh)
KR (1) KR101671270B1 (zh)
CN (1) CN102438330A (zh)
WO (1) WO2013082984A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101557849B1 (ko) * 2014-08-25 2015-10-06 에스케이텔레콤 주식회사 네트워크장치 및 네트워크장치의 동작 방법
WO2016021817A1 (ko) * 2014-08-04 2016-02-11 엘지전자 주식회사 무선 통신 시스템에서 단말을 인증 하는 방법 및 이를 위한 장치

Families Citing this family (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
BR112014002424A2 (pt) * 2011-08-01 2017-02-21 Intel Corp método e sistema para controle de acesso de rede
CN102438330A (zh) * 2011-12-06 2012-05-02 大唐移动通信设备有限公司 一种附着到e-tran的方法及移动性管理实体
CN102781006B (zh) * 2012-07-06 2016-02-03 大唐移动通信设备有限公司 一种全球移动设备标识的检验控制方法及装置
DE112012006984B4 (de) 2012-10-08 2023-09-14 Avago Technologies International Sales Pte. Ltd. Verfahren und Vorrichtung zur Verwaltung von Dualverbindungserrichtung
US20150223196A1 (en) * 2012-10-10 2015-08-06 Lg Electronics Inc. Method for processing paging and method for relaying downlink data
CN102905265B (zh) * 2012-10-11 2016-02-10 大唐移动通信设备有限公司 一种实现移动设备附着的方法及装置
CN102917332B (zh) * 2012-10-11 2015-06-03 大唐移动通信设备有限公司 一种实现移动设备附着的方法及装置
CN102905266B (zh) * 2012-10-11 2015-05-20 大唐移动通信设备有限公司 一种实现移动设备附着的方法及装置
WO2014113922A1 (zh) * 2013-01-22 2014-07-31 华为技术有限公司 移动通信系统的安全认证的方法和网络设备
CN103442385B (zh) * 2013-08-09 2016-08-17 大唐移动通信设备有限公司 一种终端网络附着方法及设备
US9596628B2 (en) 2013-10-31 2017-03-14 Intel Corporation Gateway arrangements for wireless communication networks
WO2015120902A1 (en) * 2014-02-14 2015-08-20 Telefonaktiebolaget L M Ericsson (Publ) Pcrf assisted apn selection
CN106576237B (zh) * 2014-07-21 2020-10-16 宇龙计算机通信科技(深圳)有限公司 移动管理实体、归属服务器、终端、身份认证系统和方法
CN105376851B (zh) * 2014-08-29 2019-06-11 中国电信股份有限公司 一种网络附着方法及系统
US9794266B2 (en) 2014-09-05 2017-10-17 Qualcomm Incorporated Using multiple credentials for access and traffic differentiation
JP6520044B2 (ja) * 2014-10-24 2019-05-29 日本電気株式会社 無線端末、ネットワーク装置、及びこれらの方法
KR102272838B1 (ko) 2014-11-11 2021-07-06 삼성전자주식회사 이동통신 네트워크를 통한 데이터 서비스 제공 방법 및 장치
EP3547739A1 (en) 2015-02-13 2019-10-02 NEC Corporation Apparatus, system and method for security management
CN104796887B (zh) * 2015-04-14 2018-08-21 大唐移动通信设备有限公司 一种安全信息交互的方法和装置
EP3166362B1 (en) * 2015-11-06 2019-10-23 Vodafone GmbH Method and network element for providing a registration to a communication network for a mobile terminal
JP2019009480A (ja) * 2015-11-10 2019-01-17 シャープ株式会社 端末装置、c−sgnおよび通信制御方法
JP2019004197A (ja) * 2015-11-10 2019-01-10 シャープ株式会社 端末装置、c−sgnおよび通信制御方法
US11381454B2 (en) * 2016-06-15 2022-07-05 Tejas Networks Ltd. System and method for network resource optimization
CN108306907A (zh) * 2016-09-30 2018-07-20 电信科学技术研究院 一种终端的管理方法、网络功能和终端
CN108307530B (zh) * 2016-09-30 2023-09-22 华为技术有限公司 一种会话连接建立方法、相关设备及系统
CN108076461B (zh) * 2016-11-18 2020-09-18 华为技术有限公司 一种鉴权方法、基站、用户设备和核心网网元
ES2908270T3 (es) * 2017-05-08 2022-04-28 Huawei Tech Co Ltd Método y dispositivo para movimiento entre sistemas de comunicación
CN109729042B (zh) * 2017-10-27 2021-03-12 大唐移动通信设备有限公司 一种信息传输、处理方法及装置
CN109756451B (zh) * 2017-11-03 2022-04-22 华为技术有限公司 一种信息交互方法及装置
CN108235300B (zh) * 2017-12-22 2020-05-22 中国科学院信息工程研究所 移动通信网络用户数据安全保护方法及系统
CN109982311B (zh) * 2017-12-28 2022-01-14 中国移动通信集团北京有限公司 一种终端接入核心网设备方法及终端、mme和saegw
CN110753362B (zh) * 2019-10-25 2023-04-07 恒安嘉新(北京)科技股份公司 基站的优化方法、终端注册方法、装置、基站及存储介质
CN111132162B (zh) * 2019-12-26 2022-11-22 新华三技术有限公司成都分公司 一种终端信息的获取方法及装置
CN116828460B (zh) * 2023-06-29 2024-04-19 广州爱浦路网络技术有限公司 基于附着流程的信息交互系统、方法、装置及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1947435A (zh) * 2004-02-27 2007-04-11 北方电讯网络有限公司 快速呼叫建立方法
CN1997208A (zh) * 2006-01-06 2007-07-11 上海原动力通信科技有限公司 移动通信系统中用户设备开机附着接入的方法
CN101227352A (zh) * 2007-01-15 2008-07-23 华为技术有限公司 用户终端紧急注册到ip连接接入网络的方法及系统
CN101466083A (zh) * 2007-12-18 2009-06-24 华为技术有限公司 一种紧急呼叫方法和装置
CN101730061A (zh) * 2008-10-31 2010-06-09 大唐移动通信设备有限公司 业务建立与小区更新的同步处理方法、装置及系统
CN102438330A (zh) * 2011-12-06 2012-05-02 大唐移动通信设备有限公司 一种附着到e-tran的方法及移动性管理实体

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB0315278D0 (en) * 2003-06-30 2003-08-06 Nokia Corp A method for optimising handover between communication networks
CN102714818B (zh) * 2009-10-30 2016-06-15 交互数字专利控股公司 用于无线通信的信令
KR101670253B1 (ko) * 2010-02-16 2016-10-31 삼성전자 주식회사 이동 무선통신 시스템에서 단말의 네트워크 억세스 제어 방법 및 장치.
US20130210386A1 (en) * 2010-06-23 2013-08-15 Polar Wireless Corporation Method And System For Routing Communications

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1947435A (zh) * 2004-02-27 2007-04-11 北方电讯网络有限公司 快速呼叫建立方法
CN1997208A (zh) * 2006-01-06 2007-07-11 上海原动力通信科技有限公司 移动通信系统中用户设备开机附着接入的方法
CN101227352A (zh) * 2007-01-15 2008-07-23 华为技术有限公司 用户终端紧急注册到ip连接接入网络的方法及系统
CN101466083A (zh) * 2007-12-18 2009-06-24 华为技术有限公司 一种紧急呼叫方法和装置
CN101730061A (zh) * 2008-10-31 2010-06-09 大唐移动通信设备有限公司 业务建立与小区更新的同步处理方法、装置及系统
CN102438330A (zh) * 2011-12-06 2012-05-02 大唐移动通信设备有限公司 一种附着到e-tran的方法及移动性管理实体

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 9)", 3GPP TS 23.401 V9.4.0, March 2010 (2010-03-01), XP055133494 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016021817A1 (ko) * 2014-08-04 2016-02-11 엘지전자 주식회사 무선 통신 시스템에서 단말을 인증 하는 방법 및 이를 위한 장치
US9949125B2 (en) 2014-08-04 2018-04-17 Lg Electronics Inc. Method for authenticating terminal in wireless communication system, and device for same
KR101557849B1 (ko) * 2014-08-25 2015-10-06 에스케이텔레콤 주식회사 네트워크장치 및 네트워크장치의 동작 방법

Also Published As

Publication number Publication date
EP2790454A4 (en) 2015-08-05
EP2790454B1 (en) 2018-08-22
CN102438330A (zh) 2012-05-02
JP5813249B2 (ja) 2015-11-17
KR20140109928A (ko) 2014-09-16
KR101671270B1 (ko) 2016-11-01
JP2015503291A (ja) 2015-01-29
EP2790454A1 (en) 2014-10-15
US20140335830A1 (en) 2014-11-13

Similar Documents

Publication Publication Date Title
WO2013082984A1 (zh) 一种附着到e-utran的方法及移动性管理实体
EP3673682B1 (en) Smf, amf and upf relocation during ue registration
US20220191813A1 (en) Connection processing method and apparatus in multi-access scenario
US10841302B2 (en) Method and apparatus for authenticating UE between heterogeneous networks in wireless communication system
US10911948B2 (en) Method and system for performing network access authentication based on non-3GPP network, and related device
KR101854095B1 (ko) 액세스 및 트래픽 차등화를 위한 다수의 크리렌셜의 이용
RU2727184C1 (ru) Способ обработки процедуры установления сеанса связи pdu и узел amf
TWI713614B (zh) 用於使用支援多個連線性和服務上下文的安全模型的無線通訊的方法和裝置
JP2019537901A (ja) 無線通信システムにおいて同一のplmnに属するネットワークアクセスを通じた登録方法及びそのための装置
JP2015503291A5 (zh)
TWI748952B (zh) 利用單個連線性上下文支援多個併發服務上下文
US20220240131A1 (en) Data transmission method, communications device, and communications system
WO2018132050A1 (en) Pdu session management
WO2019184651A1 (zh) 一种通信方法及装置
CN102917332B (zh) 一种实现移动设备附着的方法及装置
US9344890B2 (en) Trusted wireless local area network (WLAN) access scenarios
US20210127272A1 (en) User Plane Integrity Protection Method and Apparatus, and Device
WO2016155012A1 (zh) 一种无线通信网络中的接入方法、相关装置及系统
WO2011116713A2 (zh) Mtc终端通过网关与网络通信的方法、设备及系统
WO2012130133A1 (zh) 一种接入点及终端接入方法
WO2014075534A1 (zh) 通信路径的切换方法及装置、切换处理装置及系统
JP7285939B2 (ja) 接続確立のための方法および装置
JP2019515596A (ja) 異種ネットワーク環境での次世代ネットワークサービスを提供する方法及び装置
WO2017129101A1 (zh) 路由控制方法、装置及系统
WO2016173296A1 (zh) 一种移动网络分级架构的接入方法及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12854709

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2014545069

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 14362916

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2012854709

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20147018739

Country of ref document: KR

Kind code of ref document: A