WO2008055434A1

WO2008055434A1 - Method, system and device for user equipment attaching to a network

Info

Publication number: WO2008055434A1
Application number: PCT/CN2007/070942
Authority: WO
Inventors: Xiaolong Guo
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-11-06
Filing date: 2007-10-23
Publication date: 2008-05-15
Also published as: CN101179561B; CN101179561A

Abstract

A method, system and device for an user equipment attaching to a network. During the course that an UE is attaching to a network, if the UE and/or the network side does not meet the basic conditions for an UE to access to an evolution network, namely the UE has no ability to access to an evolution network, or the UE has no demand to access to an evolution network, or the UE has no permission to access to an evolution network, or the network side has no ability to access to an evolution network, the activation process of a PDP context is forbidden to perform.

Description

Method, system and device for user equipment attached to network

This application claims priority to Chinese Patent Application No. 200610146116.1, entitled "User Equipment Attachment Network Method and System", filed on November 6, 2006, the entire contents of which is incorporated herein by reference. In the application.

Technical field

The present invention relates to the field of wireless communications, and in particular, to a technology in which a user equipment attaches to a network.

Background technique

3G is the abbreviation of English 3rd Generation, referring to the third generation of mobile communication technology. Compared with the first generation analog mobile communication technology (1G) and the second generation global mobile communication system (Global System for mobile Communication ("GSM"), code division multiple access (Code Division Multiple Access (CDMA)) Mobile communication technology (2G), 3G generally refers to a new generation mobile communication system that combines wireless communication with multimedia communication such as the Internet. It can handle a variety of media formats such as images, music, video streaming, etc., providing a variety of information services including web browsing, teleconferencing, and e-commerce. However, with the gradual development of communication, people's requirements for mobile communication are getting higher and higher. The existing 3rd Generation Partnership Project ("3GPP") network architecture and protocol can no longer satisfy users. The high requirements of mobile communications, and 3GPP has proposed a concept of an evolved network that serves future communication needs.

In order to ensure the competitiveness of 3GPP systems in the next 10 years and beyond, especially in order to strengthen the 3GPP system's ability to handle fast-growing IP data services, 3GPP has started long term evolution since the second half of 2004 (Long Term Evolution, Referred to as "LTE" project, and System Architecture Evolution ("SAE") project. The purpose of LTE is to provide an evolved network that reduces latency, increases user data rates, enhances system capacity and coverage, and reduces overall carrier costs. At the same time, the evolution of the network structure is also an important indicator of the backward compatibility of existing networks. The principles that the evolving network architecture needs to meet include:

(1) In the initialization phase of the user equipment (User Equipment, referred to as "UE") access network, the basic IP connection needs to be established in the evolved network;

(2) The evolved network architecture must minimize the delay of user data;

(3) The definition of each functional module in the evolved network architecture should avoid overlapping or duplication of functions to avoid Eliminate unnecessary signaling interactions and delays.

A more popular network architecture derived from the above is shown in Figure 1. It mainly includes: Mobility Management Entity ("ΜΜΕ") and User Plane Entity (UPE). Now it is changed to Serving Gate Way, referred to as "S-GW". The following is still described by UPE. User Plane Anchor (now PDN GateWay), referred to as "P" -GW", described below in the user plane anchor point) and the evolved network radio access network (LTE Radio Access Network, LTE RAN) four logical function modules, and the home subscriber server (Home Subscriber Server , referred to as "HSS"). The MME is a mobility management module, which is responsible for mobility management of the control plane, including user context and mobility state management, assigning user temporary identity, mobility state, Tracking Area ("TA") information, etc. The user performs identity authentication, which corresponds to the control plane part of the current General Mobile Telecommunications System (UMTS) system internal Serving GPRS Support Node (SGSN); UPE The user plane entity is responsible for initiating paging for the downlink data of the UE in the idle state, managing the context of the UE, the IP bearer parameters, and the intra-network routing information, which corresponds to the data plane part of the current UMTS internal SGSN; The point may include a 3GPP Anchor (3GPP Anchor) and a SAE Anchor (SAE Anchor), which is a user plane anchor between different access systems in the 3GPP system, and the SAE Anchor is between the 3GPP access system and the non-3GPP system in the SAE. User plane anchor. The user plane anchor point is constant during the user's session time. The LTE RAN is a radio access network of an evolved network, and the nodes are not specifically limited, and generally have an eNodeB (Evolved Base Station), and may also include a Control Plane Server (CPS), which can be logically As a long-term evolution radio access network entity (LTE-RAN Entity).

In practical applications, the above evolved network can coexist with the existing 2G/3G network, so there may be a network structure using different radio access technologies (Radio Access Technology, referred to as "RAT") in the network structure. The UE needs to move between different RATs (such as 2G/3G network and evolved network). During the process of mobile, ping-pong may cause the network registration process due to UE changes camping on different networks. As shown in Figure 2, RA1 and RA2 are the existing 2G/3G Routing Areas (RAs). In the existing 2G/3G networks, the UEs must replace each RA. Initiate the Routing Area Update (RAU) process. Of course, the UE also has a periodic location update process without changing the RA. The function is to enable the network to know that the UE is still in the network, and prevent the UE from leaving the network but continuously paging the UE due to the network being unknown. The network registration process due to the location movement of the UE will be described below.

In Figure 2, TA1, TA2, TA3, and TA4 are the tracking areas of the evolved network, similar to the RA of the 2G/3G network. When a multimode UE moves between different RAs and TAs, in order to ensure that the UE can be paged in the network with different RATs, the UE needs to register in the RA and TA to be moved, for example, the UE is entering RA1. The SGSN of the 2G/3G needs to be registered with the SGSN of the 2G/3G. When the UE enters the TA1, it needs to register with the MME/UPE/Anchor of the evolved network. When the UE moves out of the TA1 and re-enters the RA1, it needs to re-enter the SGSN of the 2G/3G. registered. However, this method leads to frequent network registration processes while guaranteeing paging, which brings a large amount of registration signaling overhead.

In order to solve this problem, in the prior art, several methods have been proposed to avoid the great waste caused by the frequent network registration process to the air interface. At present, a scheme is basically established, which is mainly used to reduce the impact of the registration/updating of the UE in the idle mode on the air interface under different RAT networks. The idea of the solution is that after the UE attaches to the network, it registers with an access network (2G/3G network or evolved network), and then the UE moves to another access network and then registers with the other access network. In this way, the UE registers with both access systems at the same time, and then the UE does not need to initiate any registration process when moving within the corresponding registration areas (RA or TA) of the two networks. A normal RAU procedure is initiated when the UE changes the RA or TA. The access entities of the two access systems to which the UE is registered (the SGSN of 2G/3G or the MME of the evolved network) have the context of the UE.

The following describes the registration procedure in which the UE first attaches to the evolved network SAE and then moves to the 2G/3G network.

As shown in FIG. 3, in step 301, the UE attaches to the SAE and sends an attach request message to the MME.

Then, in step 302 and step 302', the MME registers with the HSS to obtain the context information of the UE. If the MME already has the context information of the UE, it does not need to obtain the information from the HSS. This step can also be done afterwards.

Next, in step 303, after obtaining the context from the HSS, the MME initiates an authentication process to the UE. Next, in step 304, the UE returns an authentication response to the MME. If the authentication succeeds, the UE registers with the MME successfully, and the MME allocates SAE Temperate Mobile Subscription Identity (S-TMSI)/S-RA and default bearer IP (default IP) information to the UE. S-RA is the RA of SAE, or TA.

Next, in step 305, the MME/UPE/Anchor confirms that the UE attach is successful, allows the access of the UE, and sends the information of the S-TMSI/S-RA allocated to the UE and the default bearer IP to the UE.

Next, in step 306, the UE moves to the 2G/3G network (replaces the RAT), initiates a RAU procedure, and carries the S-TMSI/S-RA allocated by the MME to the SGSN.

Next, in step 307 and step 307', the SGSN initiates an SGSN Context Request message to the MME corresponding to the S-TMSI/S-RA to request the context of the UE; after receiving the request message, the MME associates the relevant context. Sent to the SGSN, the process is called the Context Retrieval process.

Next, in step 308, an authentication process may be performed; the SGSN may register with the HSS, as in steps 309 and 309'. (It is also possible that the SGSN does not register with the HSS, but the SGSN uses the MME as the HSS).

Next, in step 310, the SGSN acknowledges the context acceptance and may trigger the MME/UPE/Anchor to transfer the data.

Next, in step 311 and step 311', the SGSN updates the Packet Data Protocol (PDP) context to the MME/UPE/Anchor, because on the user side, the MME/UPE/Anchor is similar to the original SGSN. Some general packet radio service support nodes (GPRS Gateway Support Node, referred to as "GGSN")

Next, in step 312, the SGSN allocates both U-TMSI/U-RA and S-TMSI/S-RA to the UE, and the UE does not have to initiate an update registration message when moving between the U-RA and the S-RA. U-TMSI indicates the temporary mobile subscriber identity of the 2G/3G network, and U-RA indicates the RA of the 2G/3G network.

Next, in step 313, the UE returns a RAU procedure complete message.

The registration process in which the UE first attaches to the 2G/3G network and then moves to the SAE is similar to the registration process in which the UE first attaches to the SAE and then moves to the 2G/3G network, as shown in FIG. 4, and no specific description is given here.

Simply put, the UE first attaches to the SGSN, the SGSN registers with the HSS, and then the UE re-enters The SAE, initiates the RAU, acquires the context from the SGSN, registers the MME with the HSS, and assigns the S-RA/S-TMSI to the UE. After the UE moves within the registered RA and S-RA, the location update/registration message is not initiated. When the UE moves to an area other than the registered S-RA/RA, an update message is to be initiated. It should be noted that, in the process of UE mobility, if the SGSN is not replaced, the SGSN registration process is not necessary in the process.

In the actual application, the following problems exist in the prior art: The UE may have redundant operations in the process of attaching the UMTS network, which increases the complexity of the UE attaching to the network.

The main reason for this situation is that in the traditional 2G/3G network, the UE does not need to have an activated PDP context after attaching, that is, it is not necessary to assign an IP address. However, in the SAE network, the UE must have an IP address attached to it, with a default bearer. Therefore, when the UE attaches the UMTS re-attachment to the evolved network, the UE needs to establish a default bearer for the evolved network in the process of attaching the UMTS network to the UE, that is, the activation process of the PDP context needs to be initiated; but not all UEs need to perform such processing. , the activation process of the PDP context is not required in the following cases:

UEs that do not support evolved network mode, such as UMTS single mode UE;

A UE that does not have an evolved network access requirement, such as a dual-mode UE, can be set by the user. When the user wants to save money, the UE can be set to use as a single mode when accessing the UMTS.

A SAE-restricted UE, such as user subscription information, does not allow the user to use the evolved network. Although the user uses the dual-mode UE, the network checks that the UE is an evolved network-restricted user and cannot use the evolved network; or the area in which the UE is located is SAE-restricted. Area, etc.

The network has no evolving network access capability or is limited. For example, some operators' UMTS networks do not deploy an evolved network or some SGSNs do not have an interface with the evolved network or cannot establish a connection with an evolved network entity.

In the above case, in the process of the UE attaching to the network, the PDP context activation process is meaningless to the UE, and the unnecessary signaling processing of the UE and the network side is added, which increases the complexity of the UE attached to the network, and reduces The speed at which the UE attaches to the network.

Summary of the invention

The main technical problem to be solved by various embodiments of the present invention is to provide a method, system and device for attaching a user equipment to a network.

To solve the above technical problem, the present invention provides a method for a user equipment to attach to a network, including The following steps:

In the process of attaching the user equipment to the network, if the user equipment and/or the network side do not satisfy the basic conditions for the user equipment to access the evolved network, the packet data protocol PDP context activation process is prohibited.

The present invention also provides a system for a user equipment to attach to a network, including a network side and a user equipment, and further includes:

a determining unit for determining whether the user equipment and/or the network side meet the basic conditions for the user equipment to access the evolved network in the process of attaching the network to the user equipment;

It is used to prohibit the prohibition unit of the PDP context activation process when the basic conditions for the user equipment to access the evolved network are not met.

The present invention further provides a network side device for a user equipment attachment network, comprising: determining, in a process of attaching a network by a user equipment, whether the user equipment and/or the network side meets a basic condition that the user equipment accesses the evolved network Conditional unit of judgment;

The invention also provides a user equipment, comprising:

In the process of attaching the network to the user equipment, determining whether the user equipment and/or the network side meet the basic condition that the user equipment accesses the evolved network.

The invention also provides a method for a user equipment to attach to a network, comprising the following steps:

In the process of the user equipment attaching to the network, if the user equipment and the network side satisfy the basic conditions for the user equipment to access the evolved network, the user equipment performs a packet data protocol PDP context activation process.

An activation unit for performing a PDP context activation process when the basic conditions for the user equipment to access the evolved network are met.

The invention also provides a user equipment, comprising:

Used to determine whether the user equipment and/or the network side is full during the process of attaching the user equipment to the network. a determining unit for the basic condition that the user equipment accesses the evolved network;

By comparison, it can be found that the main difference between the technical solution of the present invention and the prior art is that, in the process of the UE attaching to the network, if the UE and/or the network side do not meet the basic conditions for the UE to access the evolved network, that is, the UE does not connect. The PDP context activation process is prohibited when the capability of the evolved network, or the UE does not have access to the evolved network, or the UE does not have access to the evolved network, or the network side does not have access to the evolved network. When the UE that does not need or cannot use the evolved network is attached to the network, the processing flow can be simplified, and unnecessary operations on the network side and the UE side can be reduced.

DRAWINGS

1 is a schematic diagram of an evolved network architecture according to the prior art;

2 is a schematic diagram of a network structure in which different RATs are simultaneously used according to the prior art; FIG. 3 is a schematic diagram of a registration process in which a UE first attaches to an evolved network and then moves to a 2G/3G network according to the prior art;

4 is a schematic diagram of a registration process in which a UE first attaches to a 2G/3G network and then moves to an evolved network according to the prior art;

5 is a flowchart of a method for a UE to attach a network according to a first embodiment of the present invention; FIG. 6 is a flowchart of a method for a UE to attach a network according to a third embodiment of the present invention; FIG. 7 is a UE according to a fourth embodiment of the present invention; Flow chart of the method of attaching the network.

detailed description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be further described in detail with reference to the accompanying drawings.

In the present invention, in the process of the UE attaching to the network, if the UE and/or the network side do not meet the basic conditions for the UE to access the evolved network, that is, the UE does not have the capability of accessing the evolved network, or the UE does not have access to the evolved network. The PDP context activation process is prohibited, or the UE does not have access to the evolved network, or the network side does not have access to the evolved network. When the UE that does not need or cannot use the evolved network is attached to the network, the processing flow can be simplified, and unnecessary operations on the network side and the UE side can be reduced.

The first embodiment of the present invention will be described below, and the first embodiment of the present invention relates to UE attachment. The method of the network. In this embodiment, the UE is in an attach request (attag request message) sent to the SGSN according to its own evolved network access capability and/or evolved network access requirement, when it has the capability and requirement to access the evolved network. Carry the follow-on request identifier (follow-on request identifier), indicating that there is other signaling. The network side determines, according to the identifier, whether the UE needs to perform subsequent operations.

Specifically, as shown in FIG. 5, in step 501, the UE sends an attach request to the SGSN on the network side, where the attach request carries the evolved network access capability information of the UE, and if the UE has the capability and requirement for accessing the evolved network, The subsequent request identifier is also carried in the attach request, indicating that the network side does not release the current connection after returning the attach response (Attach Accept).

Optionally, in step 502, the SGSN may perform a security authentication process.

Optionally, in step 503, the SGSN registers with the HSS of the UE (may also register with the MME). If the SGSN has previously registered in the HSS, this step can be omitted.

The SGSN determines, according to the UE's attach request, whether the UE has the requirement to access the evolved network. If the attach request does not carry the subsequent request identifier, it indicates that the UE does not need to access the evolved network, and then proceeds to step 505, and the SGSN directly sends the UE to the UE. Returns an Attach Response, which does not carry other information in the attach response. After receiving the attach response, the UE no longer sends a PDP context activation request. The SGSN can directly release the connection with the UE. When the UE that does not need to use the evolved network is attached to the network, the process can be simplified, the network side and the UE side can be prevented from performing related capability judgments, or other unnecessary operations related to the evolved network can be performed, and the speed at which the UE attaches to the network is accelerated. .

If the subsequent request identifier is carried in the attach request, it indicates that the UE has the requirement to access the evolved network, and then proceeds to step 504, where the SGSN may further check the evolved network access capability of the network side and/or the evolved network access limit of the UE. And/or determining, according to the access capability information of the UE in the attach request, whether the UE has the capability of accessing the evolved network. If it is determined that the network side has the capability of accessing the evolved network, and the UE has the right to access the evolved network, the process proceeds to step 506. Otherwise, if the UE has the requirement to access the evolved network, the SGSN checks to determine that the UE is not connected. The SGSN also returns an attach response to the UE, and does not carry other information in the attach response, so as to enter the evolved network, or the capability of not accessing the evolved network, or the network side does not have the capability to access the evolved network. Avoid modification of the SGSN, or carry an identifier that prohibits the UE from initiating a PDP context activation process. After the UE is instructed to receive the attach response, it is not necessary to send a PDP context activation request. The SGSN can directly release the connection with the UE. When the UE or the network side does not have the basic conditions for accessing the evolved network, unnecessary operations related to the evolved network can be avoided, the processing flow is simplified, and the speed at which the UE attaches to the network is accelerated.

In step 506, the SGSN determines that the UE has the requirements, capabilities, and rights to access the evolved network, and the network side has the capability of accessing the evolved network. Therefore, the SGSN returns an attach response to the UE, where the attach response carries an indication that the UE is allowed to initiate. The identifier of the PDP context activation process, such as the subsequent request accepting the identifier, indicates that the network side allows the UE to perform subsequent operations of accessing the evolved network, and does not currently release the connection with the UE. Then proceed to step 507.

In step 507, after receiving the attach response, the UE determines, according to the identifier carried in the network, that the network side allows the PDP context to be activated. In this step, the UE sends a PDP context activation request to the SGSN.

The SGSN waits for the subsequent signaling of the UE, that is, the PDP context activation request of the UE. After receiving the activation request, the process proceeds to step 508, the SGSN creates a PDP context, and establishes a bearer to the evolved network, such as a bearer between the SGSN and the MME, to complete The PDP context activation process.

After the PDP context activation process is completed, the process proceeds to step 509. The SGSN sends a PDP context activation success response message to the UE, notifying the UE that the PDP context activation process has been completed, and successfully establishing a default bearer with the evolved network.

The second embodiment of the present invention is substantially the same as the first embodiment, except that in the first embodiment, the SGSN has evolved network access capabilities, and/or access rights to the UE, and/or before returning the attach response. Or the network-side evolved network access capability is checked. After determining that the UE has the capability and the right to access the evolved network, and the network side has the capability of accessing the evolved network, the returned attachment response carries an indication to allow the UE to initiate the PDP. The identifier of the context activation process. Otherwise, the attachment response does not carry redundant information or carries an identifier that prohibits the UE from initiating a PDP context activation process.

In the second embodiment, when the UE has the requirement to access the evolved network, that is, if the subsequent request identifier is carried in the attach request sent by the UE, the SGSN unconditionally receives the subsequent request, and returns an attach response to the UE. After receiving the attach response, the UE sends a PDP context activation request to the SGSN. After receiving the activation request, the network side checks the evolved network access capability, and/or access rights of the UE, and/or the evolved network access capability of the network side, if it is determined that the UE has an access evolution network. The ability and authority, and the network side has the ability to access the evolved network, then complete the PDP context The activation process establishes a bearer between the network and the evolved network. Otherwise, the PDP context activation process is prohibited from being completed, and a corresponding PDP context activation failure response message is returned to the UE.

Since the requirement of the UE to access the evolved network is indicated by the UE sending the subsequent request identifier in the second embodiment, when the SGSN receives the subsequent request identifier, the SGSN does not normally release the connection, and waits for the UE to continue to send signaling. Therefore, the evolved network access capability of the network side, or the access capability or authority of the UE may be determined during the PDP context activation process, and related processing is implemented according to the judgment result, in which the UE still needs to be in an uncertain situation. The PDP context activation request is sent, but the time for the SGSN to perform the correlation determination and the time for waiting for the reception of the PDP context activation request are combined, thereby reducing the time required for the UE to attach to the network and speeding up the attachment speed.

In addition, in practical applications, due to non-access stratum signaling (Non-Access Stratum, referred to as

"NAS" is a type length value (TLV) format. The information sent by the dual-mode UE is not upgraded (the upgrade of the evolved network access capability is not upgraded). Although it is not recognized, no error occurs. If the SGSN is not upgraded, the network side does not have the evolved network access capability, and the UE cannot receive additional information in the attach response, and the UE does not send the PDP context activation request.

The third embodiment of the present invention is described below. The third embodiment relates to a method for a UE to attach to a network, which is substantially the same as the first embodiment. The difference is that, in the first embodiment, the UE carries the subsequent request identifier in the attach request. Notifying the network side that the UE has the capability and/or requirement for accessing the evolved network, and the SGSN, when the received attach request includes the subsequent request identifier, the evolved network access capability or the right of the UE or the network side access evolution The capability of the network is judged; if the subsequent request identifier is not included, the connection request is directly returned without corresponding judgment, and no information is included in the attach request, and the UE does not initiate a PDP context activation request after receiving the attach request. .

In the third embodiment, when the UE initiates the attach request, the UE directly carries the evolved network access capability and/or access requirement information of the UE, and the SGSN determines according to the information, if it is determined that the UE has the access evolved network. The capability, the requirement, and the privilege, and the network side has the capability of accessing the evolved network, and the attach response carries an indication that the UE initiates the PDP context activation process; otherwise, the indication is prohibited from being carried. After receiving the attach response, the UE sends a PDP context activation request to the SGSN if the indication is carried therein, otherwise the PDP context activation request is prohibited from being sent.

Specifically, as shown in FIG. 6, in step 601, the UE initiates an attach request to the SGSN, where the attach The request carries the evolved network access capability and/or access requirement information of the UE.

Optionally, in step 602, the SGSN may perform a security authentication process.

Optionally, in step 603, the SGSN registers with the HSS of the UE (may also register with the MME). If the SGSN has previously registered in the HSS, this step can be omitted.

Next, proceeding to step 604, the SGSN checks the evolved network access capability, and/or access requirements, and/or access rights of the UE, and/or the evolved network access capability of the network side.

Next, proceeding to step 605, the SGSN returns an attach response to the UE. If, in step 604, the SGSN determines that the UE has the capability, the requirement, and the privilege to access the evolved network, and the network side has the capability to access the evolved network, in this step, the attach response carries the UE to initiate the PDP context. The indication of the activation process; otherwise, in this step, the indication that the UE is required to initiate the PDP context activation process is prohibited, and the connection with the UE is directly released. When the UE or the network side does not have the basic conditions for accessing the evolved network, unnecessary operations related to the evolved network can be avoided, the processing flow is simplified, and the speed at which the UE attaches to the network is accelerated. In FIG. 6, an indication that the UE initiates a PDP context activation process is carried in the attach response is taken as an example. Then proceed to step 606.

Then, in step 606, after receiving the attach response, the UE determines whether the network side requires the activation process of the PDP context according to the identifier carried in the network. If the identifier is not carried, the UE does not initiate the PDP context activation process. The identifier, the UE sends a PDP context activation request to the SGSN.

After the SGSN waits for the UE's subsequent signaling, that is, the UE's PDP context activation request, after receiving the activation request, the process proceeds to step 607, the SGSN creates a PDP context, and establishes a bearer to the evolved network, such as a bearer between the SGSN and the MME. Complete the PDP context activation process.

After the PDP context activation process is completed, the process proceeds to step 608. The SGSN sends a PDP context activation success response message to the UE, notifying the UE that the PDP context activation process has been completed, and successfully establishing a default bearer with the evolved network.

It is to be noted that, in this embodiment, the network side may, but not necessarily, carry an indication that the user equipment initiates a PDP context activation process in the attach response message returned to the UE; The message requesting the user equipment to initiate a PDP context activation process.

The fourth embodiment of the present invention relates to a method for a UE to attach a network. In this embodiment, the network side sends the evolved network access capability information of the network side to the UE in advance through a broadcast message, and the UE After the network side has the capability to access the evolved network, the subsequent request identifier is carried in the attach request according to its own requirements. Regarding the system broadcast message, the RAN is generally notified by the operation and maintenance (Operation and Maintenance, simply referred to as 'Ό&Μ'), as shown in Fig. 7.

In step 701, the UE first determines an evolved network access capability of the network side according to the broadcast message. The UE monitors the broadcast message, and when the broadcast message does not include the evolved network access capability information of the network side or the information indicating that the network side does not have the capability of accessing the evolved network, determining that the network side does not have the capability of accessing the evolved network, the UE When the monitored broadcast message includes the evolved network access capability information of the network side or contains information indicating that the network side has the capability of accessing the evolved network, it is determined that the network side has the capability of accessing the evolved network.

Then, the method proceeds to step 702, the UE sends an attach request to the SGSN of the network side, where the attach request carries the evolved network access capability information of the UE, if the UE has the capability and requirement for accessing the evolved network, and the UE determines that the network side has access The ability to enter the evolved network also carries the information that the UE has the capability and requirement for accessing the evolved network, such as the subsequent request identifier, indicating that the network side does not release the current connection after returning the attach response. The network side capability information is broadcasted, so that the UE can learn whether the UE can access the evolved network as soon as possible, and avoid sending unnecessary information when the basic conditions of the access evolved network are not met.

Optionally, in step 703, the SGSN may perform a security authentication process.

Optionally, in step 704, the SGSN registers with the HSS of the UE (may also register with the MME). If the SGSN has previously registered in the HSS, this step can be omitted.

If the subsequent request identifier is carried in the attach request, proceed to step 705, the SGSN checks the evolved network access capability of the UE, and/or the access right, and then proceeds to step 706; otherwise, directly proceeds to step 706, and no corresponding judgment is needed. .

In step 706, the SGSN returns an attach response to the UE. If, in step 705, the SGSN determines that the UE has the capability and the right to access the evolved network, in this step, the attach response carries an identifier indicating that the UE is allowed to initiate the PDP context activation process; otherwise, if the attach request is The SGSN determines that the UE does not have the capability or the right to access the evolved network. In this step, the indication is not carried in the attach response, and the connection with the UE is directly released. . When the UE or the network side does not have the basic conditions for accessing the evolved network, unnecessary operations related to the evolved network can be avoided, the processing flow is simplified, and the process is accelerated. The speed at which the UE attaches to the network. In FIG. 7, the UE has the capability and authority to access the evolved network as an example. Then proceed to step 707.

In step 707, after receiving the attach response, the UE determines, according to the identifier carried therein, that the network side allows the PDP context to be activated. In this step, the UE sends a PDP context activation request to the SGSN.

The SGSN waits for the subsequent signaling of the UE, that is, the PDP context activation request of the UE. After receiving the activation request, the process proceeds to step 708, where the SGSN creates a PDP context, and establishes a bearer to the evolved network, such as a bearer between the SGSN and the MME, to complete PDP context activation process.

After the PDP context activation process is completed, the process proceeds to step 709. The SGSN sends a PDP context activation success response message to the UE, notifying the UE that the PDP context activation process has been completed, and successfully establishing a default bearer with the evolved network.

In this embodiment, when the UE has the requirement of accessing the evolved network and the UE determines that the network side has the capability of accessing the evolved network, that is, when the subsequent request identifier is carried in the attach request sent by the UE, the SGSN can also receive the unconditionally. The subsequent request returns an attach response to the UE and does not release the connection. After receiving the attach response, the UE sends a PDP context activation request to the SGSN. After receiving the activation request, the network side checks the evolved network access capability and/or access rights of the UE. If it is determined that the UE has the capability and authority to access the evolved network, the PDP context activation process is completed. And establishing a bearer between the network and the evolved network. Otherwise, the PDP context activation process is prohibited from being completed, and a corresponding PDP context activation failure response message is returned to the UE.

The fifth embodiment of the present invention is substantially the same as the fourth embodiment, except that in the fifth embodiment, the UE determines the evolved network access capability of the network side according to the broadcast message, and the UE has access to the evolved network. The capability and the requirement, the access capability and the access requirement information of the UE are directly carried in the attach request. If the SGSN does not obtain the information from the attach request, the SGSN directly returns an attach response, does not carry any information in the response, and directly releases the related connection; otherwise, judges according to the information, if it is determined that the UE has access to the evolved network. The capability, the requirement, and the privilege carry an indication that the UE initiates a PDP context activation procedure in the attach response; otherwise, the indication is prohibited from being carried. After receiving the attach response, the UE sends a PDP context activation request to the SGSN if the indication is carried therein, otherwise the PDP context activation request is prohibited from being sent.

A sixth embodiment of the present invention relates to a UE attaching network, including a network side and a UE, And a determining unit, configured to determine, in the process of attaching the network, whether the UE and/or the network side meet the basic condition that the UE accesses the evolved network, and when the basic condition that the UE accesses the evolved network is not met, Prohibited units that prohibit the PDP context activation process. When the UE or the network side does not have the basic conditions for accessing the evolved network, unnecessary operations related to the evolved network can be avoided, the processing flow is simplified, and the speed at which the UE attaches to the network is accelerated.

The basic condition for the UE to access the evolved network is one of the following or any combination thereof:

The UE has the capability of accessing the evolved network, the UE has the requirement of accessing the evolved network, the UE has the right to access the evolved network, and the network side has the capability of accessing the evolved network.

Correspondingly, the determining unit may further comprise:

a first determining module, configured to determine whether the UE has the capability of accessing the evolved network, and a second determining module, configured to determine whether the UE has a requirement for accessing the evolved network, and a third determining module, configured to determine whether the UE has an access evolution The right of the network; the fourth determining module is configured to determine whether the network side has the capability of accessing the evolved network. The first judging module and/or the second judging module and/or the fourth judging module may be located at the network side or the UE; the third judging module is located at the network side.

In addition, the forbidden unit may have the capability of the UE not accessing the evolved network, and/or the capability of not accessing the evolved network, and/or the right to access the evolved network, and/or the capability of the network side not to access the evolved network. When the UE is prohibited from initiating a PDP context activation process.

Or, after receiving the PDP context activation request of the UE, when the UE does not have the capability to access the evolved network, and/or does not have access to the evolved network, and/or the network side does not have the capability to access the evolved network, the completion is prohibited. PDP context activation process.

Finally, it should be noted that the present invention does not limit the relationship between the MME, UPE, and Anchor entities. They may be completely separated, form three independent entities, or may be merged into one entity by two or more of them. The present invention is described by taking the full combination as an example, but does not limit other combinations. If the entities are separated, the interaction may be performed through signaling. If the entities are in the same physical entity, the interaction may be performed through internal primitives. There may be other signaling or data procedures between these entities and the SGSN/RNC when the entities are separated, and the invention is not described in detail herein.

In summary, it can be found that the main difference between the technical solution of the present invention and the prior art is that, in the process of the UE attaching to the network, if the UE and/or the network side do not satisfy the basic conditions for the UE to access the evolved network, , that is, the UE does not have access to the evolved network, or the UE does not access the evolved network. The PDP context activation process is prohibited if the requirement, or the UE does not have access to the evolved network, or the network side does not have access to the evolved network. When the UE that does not need or cannot use the evolved network is attached to the network, the processing flow can be simplified, and unnecessary operations on the network side and the UE side can be reduced.

The UE carries its evolved network access capability and/or access requirement information in an attach request and sends it to the network side, so that the network side can judge it, and the UE is prohibited when the UE has no or no access to the evolved network. The activation process of the PDP context is initiated to reduce unnecessary signaling interaction on the network side of the UE side.

When there is no access requirement, the UE does not include the subsequent request identifier in the attach request, so that the network side does not need to perform the UE access capability, or the access right, or the network side access capability judgment, and the PDP context activation can be directly prohibited. The process further reduces the operation on the network side.

The network side can send its own evolved network access capability to the broadcast message, so that the UE can determine the capability status of the network side before attaching the network, so that the excess information is not carried in the attach request, and the invalid signaling is minimized. In turn, the time required for the UE and the network side to process the signaling is reduced, and the process of attaching the UE to the network is simplified.

In implementation, the MME and the UPE and the Anchor may be fully separated entities, or two of the entities may be integrated, or all in one. The specific implementation does not affect the present invention. The present invention is described by taking all-in-one as an example, but does not exclude the possibility and application of separation.

While the invention has been illustrated and described with reference to the preferred embodiments embodiments The spirit and scope of the invention.

Claims

Rights request

A method for a user equipment to attach to a network, comprising the following steps: in a process of attaching a network to a user equipment, if the user equipment and/or the network side do not meet the basic conditions for the user equipment to access the evolved network, The packet data protocol PDP context activation process is prohibited.

The method for attaching a network to a user equipment according to claim 1, wherein the basic condition comprises one of the following conditions or any combination thereof:

The user equipment has the capability of accessing the evolved network, the user equipment has the right to access the evolved network, the user equipment has the right to access the evolved network, and the network side has the capability of accessing the evolved network.

The method for attaching a network to a user equipment according to claim 2, wherein the user equipment carries its evolved network access capability and/or access requirement information in an attach request to the network side;

The network side determines, according to the evolved network access capability and/or access requirement information of the user equipment, whether the user equipment has the capability and/or requirement for accessing the evolved network.

The method for attaching a network to a user equipment according to claim 2, wherein the user equipment carries a subsequent request identifier in the attach request when having a request for accessing an evolved network;

The network side determines, according to the subsequent request identifier, whether the user equipment has a requirement for accessing an evolved network, and if the subsequent request identifier is not carried in the attach request, the network side prohibits the user equipment from initiating PDP context activation. process.

The method for attaching a network to a user equipment according to claim 2, wherein the network side notifies the user equipment of the evolved network access capability information of the network side by using a broadcast message;

When the user equipment does not include the evolved network access capability information of the network side or the information indicating that the network side does not have the capability of accessing the evolved network, the user equipment determines that the network side does not access the evolved network. Ability;

When the broadcast message includes the evolved network access capability information of the network side or includes information indicating that the network side has the capability of accessing the evolved network, determining that the network side has the capability of accessing the evolved network.

The method for attaching a network by a user equipment according to claim 5, wherein The user equipment determines, according to the broadcast message, the evolved network access capability of the network side, after the user equipment determines that the network has the capability of accessing the evolved network, if the user equipment has the requirement of accessing the evolved network, And/or capability, carrying the evolved network access capability and/or access requirement information of the user equipment in the attach request;

The method for the user equipment to attach to the network according to claim 5, wherein the user equipment determines the evolved network access capability of the network side according to the broadcast message, if the user equipment determines the network The capability of accessing the evolved network does not include the evolved network access capability and/or access requirement information of the user equipment in the attach request.

The method for attaching a network to a user equipment according to any one of claims 1 to 6, wherein the network side determines the user after determining that the user equipment has a requirement to access an evolved network. The device does not have access to the evolved network capability and/or the right, and/or the network side does not have the evolved network access capability, and the user equipment is prohibited from initiating the PDP context activation process, otherwise waiting to receive the PDP context activation request sent by the user equipment. .

The method for attaching a network by a user equipment according to claim 8, wherein the network side notifies whether the user equipment is prohibited from initiating a PDP context activation process by using an attach response message.

The method for attaching a network to a user equipment according to any one of claims 1 to 6, wherein the network side waits to receive the user after determining that the user equipment has a requirement to access an evolved network. Device initiated PDP context activation request;

After the network side receives the PDP context activation request, if it is determined that the user equipment does not have the capability and/or rights to access the evolved network, and/or the network side does not have the evolved network access capability, the network side is prohibited from completing. The PDP context activation process, otherwise completing the PDP context activation process.

The method for attaching a network to a user equipment according to claim 3 or 5, wherein the network side determines the capability, requirement, and authority of the user equipment to access the evolved network, and the network side has access When the network capability is evolved, the user equipment is required to initiate a PDP context activation process; the network side requests the user equipment to initiate a PDP context activation process by using one of the following manners: the network side carries the attachment response message returned to the user equipment Require the user device Initiating an indication of the PDP context activation process; or

The network side requests the user equipment to initiate a PDP context activation process by sending an independent message to the user equipment.

A system for attaching a user equipment to a network, comprising a network side and a user equipment, and further comprising:

13. The system for attaching a network to a user equipment according to claim 12, wherein the basic condition comprises one or any combination of the following:

The user equipment has the capability of accessing the evolved network, and the user equipment has the requirement of accessing the evolved network, the user equipment has the right to access the evolved network, and the network side has the capability of accessing the evolved network.

The system for attaching a network to a user equipment according to claim 13, wherein the determining unit further comprises:

a first determining module, configured to determine whether the user equipment has the capability of accessing an evolved network, and a second determining module, configured to determine whether the user equipment has a requirement for accessing an evolved network, and a third determining module, configured to determine Whether the user equipment has the right to access the evolved network; the fourth determining module is configured to determine whether the network side has the capability of accessing the evolved network; the first determining module and/or the second determining module and/or The fourth determining module is located at the network side or the user equipment;

The third determining module is located on the network side.

The system for attaching a network to a user equipment according to claim 13, wherein the prohibiting unit further comprises one or any combination of the following:

The need for the user equipment not to access the evolved network, and/or the lack of access to the evolved network, and/or the lack of access to the evolved network, and/or the network side not accessing the evolved network The module that prohibits the user equipment from initiating a PDP context activation process when the capability is enabled;

After receiving the PDP context activation request of the user equipment, the user equipment does not have access to the evolved network, and/or does not have access to the evolved network, and/or the network side does not When there is the ability to access the evolved network, the module that completes the PDP context activation process is prohibited.

A network side device for a user equipment attachment network, comprising: determining, in a process of attaching a network by a user equipment, whether the user equipment and/or the network side meet the user equipment accessing the evolved network Judging unit of basic conditions;

17. The network side device for a user equipment attachment network according to claim 16, wherein the basic condition comprises one or any combination of the following:

The network side device for the user equipment attachment network according to claim 17, wherein the determining unit further comprises:

a first determining module, configured to determine whether the user equipment has the capability of accessing an evolved network, and a second determining module, configured to determine whether the user equipment has a requirement for accessing an evolved network, and a third determining module, configured to determine Whether the user equipment has the right to access the evolved network; and the fourth determining module is configured to determine whether the network side has the capability of accessing the evolved network.

19. The network side device for a user equipment attachment network according to claim 17, wherein the prohibition unit further comprises one or any combination of the following:

After receiving the PDP context activation request of the user equipment, the user equipment does not have access to the evolved network, and/or does not have access to the evolved network, and/or the network side does not have access. When the capability of the network is evolved, the module that completes the PDP context activation process is prohibited.

20. A user equipment, comprising:

21. The user equipment according to claim 20, wherein the basic condition comprises one or any combination of the following: The user equipment has the capability of accessing the evolved network, the user equipment has the requirement of accessing the evolved network, the user equipment has the right to access the evolved network, and the network side has the capability of accessing the evolved network.

The user equipment according to claim 21, wherein the determining unit further comprises:

a first determining module, configured to determine whether the user equipment has the capability of accessing an evolved network, and a second determining module, configured to determine whether the user equipment has a requirement for accessing an evolved network, and a fourth determining module, configured to determine Whether the network side has the capability of accessing an evolved network.

A method for a user equipment to attach to a network, comprising the following steps: in the process of attaching a network to a user equipment, if the user equipment and the network side meet the basic conditions for the user equipment to access the evolved network, the user equipment performs Packet Data Protocol PDP Context Activation Procedure.

24. A method of attaching a network to a user equipment according to claim 23, wherein the basic condition comprises one of the following conditions or any combination thereof:

26. A user equipment, comprising: