CN118042561A - Redirection method, device and mobile management entity - Google Patents
Redirection method, device and mobile management entity Download PDFInfo
- Publication number
- CN118042561A CN118042561A CN202211422164.4A CN202211422164A CN118042561A CN 118042561 A CN118042561 A CN 118042561A CN 202211422164 A CN202211422164 A CN 202211422164A CN 118042561 A CN118042561 A CN 118042561A
- Authority
- CN
- China
- Prior art keywords
- identifier
- management entity
- target
- identity
- mme
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 97
- 238000013507 mapping Methods 0.000 claims description 24
- 230000004044 response Effects 0.000 claims description 16
- 239000000284 extract Substances 0.000 claims description 3
- 238000004891 communication Methods 0.000 abstract description 6
- 230000008569 process Effects 0.000 description 17
- 238000010586 diagram Methods 0.000 description 16
- 238000004590 computer program Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 7
- 238000012545 processing Methods 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 4
- 230000003993 interaction Effects 0.000 description 4
- 230000002452 interceptive effect Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/16—Discovering, processing access restriction or access information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/12—Reselecting a serving backbone network switching or routing node
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/20—Transfer of user or subscriber data
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
The application discloses a redirection method, a redirection device and a mobile management entity, and belongs to the technical field of communication. The method comprises the following steps: the first mobility management entity receives an attachment request message of a target base station; the first mobility management entity obtains a first identifier according to the attachment request message, wherein the first identifier is an identifier of target user equipment or an identifier of a target user corresponding to the target user equipment; under the condition that the first identifier is not matched with a target identifier pre-configured in the first mobile management entity, the first mobile management entity acquires a second identifier of a second mobile management entity; and the first mobile management entity returns redirection indication information to the target base station, wherein the redirection indication information carries the second identifier, and the second identifier is used for indicating the target base station to redirect to the second mobile management entity.
Description
Technical Field
The present application belongs to the field of communication technology, and in particular, relates to a redirection method, a redirection device, and a mobility management entity.
Background
With the development of communication technology, the evolved packet system (EvolvedPacket System, EPS) wireless network architecture of long term evolution (Long Term Evolution, LTE) is widely used. Because the private network Mobility management entity (Mobility MANAGEMENT ENTITY, MME) and the public network MME share the base station and are isolated from each other in the EPS wireless network architecture of the LTE, the base station cannot judge whether the user equipment (UserEquipment, UE) should access the private network or the public network, and an access error condition can occur. Thus, after the base station receives the registration attach request of the UE, the base station is often required to be assisted with the MME for redirection.
Redirection is typically implemented in the related art based on the type of UE usage. Specifically, after receiving the registration attachment request of the UE, the base station sends relevant information of the UE to the first MME. The first MME further obtains a UE usage type from a third party device (e.g., a subscription server, etc.), and determines whether the UE should access a private network or a public network according to the UE usage type, thereby deciding whether to initiate a redirection procedure.
However, in the related art, the redirection method must acquire the UE usage type, and the redirection procedure cannot be initiated under the condition that the UE usage type cannot be acquired, so that the registration attachment request of the UE cannot be redirected to the matched MME, and the flexibility is seriously lacking.
Disclosure of Invention
The embodiment of the application provides a redirection method, a redirection device and a mobile management entity, which can solve the problem that redirection is realized based on the use type of UE and flexibility is lacked in the related technology.
In a first aspect, an embodiment of the present application provides a redirection method, including:
the first mobility management entity receives an attachment request message of a target base station;
the first mobility management entity obtains a first identifier according to the attachment request message, wherein the first identifier is an identifier of target user equipment or an identifier of a target user corresponding to the target user equipment;
Under the condition that the first identifier is not matched with a target identifier pre-configured in the first mobile management entity, the first mobile management entity acquires a second identifier of a second mobile management entity;
And the first mobile management entity returns redirection indication information to the target base station, wherein the redirection indication information carries the second identifier, and the second identifier is used for indicating the target base station to redirect to the second mobile management entity.
In a second aspect, an embodiment of the present application provides a redirecting device, including:
a receiving module, configured to receive an attach request message of a target base station;
The acquisition module is used for acquiring a first identifier according to the attachment request message, wherein the first identifier is an identifier of target user equipment or an identifier of a target user corresponding to the target user equipment; acquiring a second identifier of a second mobile management entity under the condition that the first identifier is not matched with a target identifier pre-configured in the first mobile management entity;
And the sending module is used for returning redirection indication information to the target base station, wherein the redirection indication information carries the second identifier, and the second identifier is used for indicating the target base station to redirect to the second mobile management entity.
In a third aspect, an embodiment of the present application provides a mobility management entity comprising a processor and a memory storing a program or instructions which, when executed by the processor, implement the steps of the method as described in the first aspect.
In a fourth aspect, embodiments of the present application provide a readable storage medium having stored thereon a program or instructions which when executed by a processor perform the steps of the method according to the first aspect.
In a fifth aspect, an embodiment of the present application provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and where the processor is configured to execute a program or instructions to implement a method according to the first aspect.
In a sixth aspect, embodiments of the present application provide a computer program product stored in a storage medium, the program product being executable by at least one processor to implement the method according to the first aspect.
In the embodiment of the application, a first mobility management entity receives an attachment request message of a target base station; the first mobility management entity obtains a first identifier according to the attachment request message, wherein the first identifier is an identifier of target user equipment or an identifier of a target user corresponding to the target user equipment; under the condition that the first identifier is not matched with a target identifier pre-configured in the first mobile management entity, the first mobile management entity acquires a second identifier of a second mobile management entity; and the first mobile management entity returns redirection indication information to the target base station, wherein the redirection indication information carries the second identifier, and the second identifier is used for indicating the target base station to redirect to the second mobile management entity. Therefore, whether redirection is needed or not can be determined according to the first identifier and the target identifier which is preconfigured in the first MME, and the second identifier of the second MME is further acquired under the condition that the first identifier is not matched with the target identifier, so that the target base station is assisted to redirect to the second MME, the UE use type is not required to be acquired in the redirection process, and compared with the method which can only rely on the UE use type to realize redirection in the related art, the flexibility can be improved to a certain extent.
Drawings
Fig. 1 is an EPS wireless network architecture diagram for LTE;
FIG. 2 is an interactive schematic diagram of a NAS redirection procedure for LTE;
FIG. 3 is a flow chart of a redirection method provided by an embodiment of the present application;
FIG. 4 is a flow chart of another redirection method provided by an embodiment of the present application;
FIG. 5 is a flow chart of another redirection method provided by an embodiment of the present application;
FIG. 6 is a flow chart of another redirection method provided by an embodiment of the present application;
FIG. 7-1 is an interactive schematic diagram of a redirection procedure provided in an embodiment of the present application;
FIG. 7-2 is an interactive schematic diagram of another redirection procedure provided by an embodiment of the present application;
FIG. 8 is a block diagram illustrating a redirecting device according to an embodiment of the present application;
Fig. 9 is a block diagram of a mobility management entity according to an embodiment of the present application.
Detailed Description
The technical solutions of the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which are obtained by a person skilled in the art based on the embodiments of the present application, fall within the scope of protection of the present application.
The terms first, second and the like in the description and in the claims, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged, as appropriate, such that embodiments of the present application may be implemented in sequences other than those illustrated or described herein, and that the objects identified by "first," "second," etc. are generally of a type, and are not limited to the number of objects, such as the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/", generally means that the associated object is an "or" relationship.
The standardization work group of the third generation partnership project (3rd Generation Partnership Project,3GPP) is currently working on studying the evolution of the packet-switched Core network (PACKET SWITCH Core, PS Core) and the global system for mobile communications radio access network (Universal MobileTelecommunication System RadioAccess Network, UTRAN). The subject of this study is called system architecture evolution (System Architecture Evolution, SAE) to enable an evolved packet network (Evolved Packet Core, EPC) to provide higher transmission rates, shorter transmission delays, optimize packets and support mobility management between evolved UTRAN (EvolvedUTRAN, E-UTRAN), UTRAN, wireless Local area network (Wireless Local AreaNetwork, WLAN) and other non-3 GPP access networks.
With the development of communication technology, the evolved packet system (EvolvedPacket System, EPS) of LTE based on EPC and E-UTRAN has also been widely used. Fig. 1 is an EPS wireless network architecture diagram of LTE. As shown in fig. 1, the LTE network architecture is divided into four parts: UE, E-UTRAN (access network), EPC (core network), and Packet data network (Packet DataNetwork, PDN).
Wherein the E-UTRAN is an access network composed of a plurality of evolved node Bs (EvolvedNodeB, eNodeB) for providing wireless resources for access of users. Wherein the eNodeB is a radio base station in the LTE network.
PDN is a network providing service for UE.
The EPC provides lower transmission delay and allows more access to the non-access system, its network elements include: a Mobility management entity (Mobility MANAGEMENT ENTITY, MME), a serving gateway (SERVING GATEWAY, SGW), a packet data gateway (PDN GATEWAY, PGW), a serving general packet radio service support node (SERVING GENERALPACKET radio service SupportNode, SGSN), a Policy and Charging Rules Function (PCRF) entity (Policy AND CHARGING Rules Function), a home subscriber server (Home Subscriber Server, HSS). The MME is a core control entity in the EPC, and can interact with eNodeB, SGW, HSS and the like to implement functions such as non-access stratum (Non Access Stratum, NAS) signaling, user authentication and authorization, and mobility management. The SGW is responsible for UE user plane data transfer, forwarding, and routing switching, among others. The PGW is a termination point of a packet data interface, and is connected to each packet data network. It provides a positioning function for sessions with external packet data networks. PCRF is a generic term for functional entities that support traffic data flow detection, policy enforcement, and traffic-based charging. The HSS is used for storing all the subscription data related to the service of the user in the LTE network and providing user subscription information management and user position management.
Currently, in the above LTE network architecture, when the UE initiates the initial attach procedure, the MME decides whether to initiate the NAS redirection procedure based on the UE Usage Type (UE Usage Type), and further determines the MME matching the UE based on the UE Usage Type when the NAS redirection procedure needs to be initiated.
Fig. 2 is an interactive schematic diagram of a NAS redirection procedure for LTE, as shown in fig. 2, where the redirection procedure for LTE may include the following steps:
Step 201, the ue initiates an initial attach request message to the eNodeB;
step 202, the enodeb sends an initial attach request message to a first MME;
Step 203, the first MME sends an authentication request message to the third MME/SGSN;
Step 204, the third MME/SGSN returns an authentication response message to the first MME, where in some cases, the authentication response message carries the UE usage type;
Step 205, the first MME sends an identity request message to the UE;
Step 206, the ue returns an identity response message to the first MME;
Step 207, in the case that the first MME does not acquire the UE usage type from the third MME/SGSN, the first MME sends an authentication information request message to the HSS;
step 208, the hss returns an authentication information response message to the first MME, where the authentication information response message carries a UE usage type;
step 209, the first MME determines whether a redirection procedure needs to be started based on the UE usage type, and when the redirection procedure needs to be started, determines the second MME based on the UE usage type;
step 210, the first MME sends a redirection indication message to the eNodeB, where the redirection indication message carries a second MME identifier;
in step 211, the enodeb sends an initial attach request message to the second MME.
When it can be found that the NAS message is redirected from the first MME to the second MME according to the procedure shown in fig. 2, a UE Usage Type (UE Usage Type) needs to be obtained from the third MME/SGSN or HSS, and whether to initiate the NAS redirection procedure is determined according to the UE Usage Type. When the usage type of the UE cannot be acquired, the first MME cannot initiate NAS redirection flow, so that the UE cannot access the matched second MME.
In view of this, the present application creatively proposes a redirection method that can achieve redirection without using the UE usage type.
The redirection method provided by the embodiment of the application is described in detail through specific embodiments and application scenes thereof with reference to the accompanying drawings.
Fig. 3 is a flowchart of a redirection method according to an embodiment of the present application. As shown in fig. 3, the redirection method provided by the embodiment of the present application may include the following steps:
Step 310, the first mobility management entity receives the attachment request message of the target base station;
the first MME may be an MME determined by the target base station for the target UE according to a network topology.
The attach request message may be an attach request message of the target UE forwarded by the target base station to the first MME. The attachment request message may carry related information of the target UE and the target base station.
After the target UE sends the attach request to the target base station, the first MME may receive an attach request message sent by the target base station.
It can be appreciated that, for a legal UE that has signed a network agreement with an operator, the UE needs to complete a procedure of registering and attaching to the network in a situation that the UE is turned on each time or returns from a network coverage blind area to a network coverage area, so that the UE can normally use an opened service through the network. In this process, the target UE may transmit an attach request to the target base station, accessing the core network based on the attach request. So that the first MME can receive the attach request message forwarded by the target base station.
Step 320, the first mobility management entity obtains a first identifier according to the attachment request message, where the first identifier is an identifier of a target user equipment or an identifier of a target user corresponding to the target user equipment;
The first identifier may or may not be included in the attach request message. According to the attach request message, obtaining the first identifier may include: and under the condition that the first identifier is included in the attach request message, the first identifier is directly acquired from the attach request message, or under the condition that the first identifier is not included in the attach request message, the first identifier acquisition request is sent to the target UE/HSS, and the first identifier returned by the target UE/HSS is received.
The identification of the target UE may include: at least one of an international mobile equipment identity (International Mobile Equipment Identity, IMEI), a software version identity (IMEI software version, IMEISV) of the international mobile equipment, a universally unique identity (Universally Unique Identifier, UUID). The identification of the target user corresponding to the target UE may include: at least one of international mobile subscriber identity (International Mobile SubscriberIdentity, IMSI), and subscriber permanent identity (Subscription PERMANENT IDENTIFIER, SUPI).
Step 330, when the first identifier does not match a target identifier pre-configured in the first mobility management entity, the first mobility management entity obtains a second identifier of a second mobility management entity;
In the embodiment of the present application, the second MME may be an MME to which the target UE determined by the first MME according to the attach request message may access. The target identity may include an identity of at least one UE or an identity of a user to which the UE corresponds. The preconfigured target identity may be stored in the first MME in the form of a white list. The attributes of the target identifier and the first identifier may be the same, for example, if the first identifier is an IMEI, the target identifier may be at least one IMEI, and if the first identifier is an IMSI or the like, the target identifier may be at least one IMSI. The white list may be a first list of identification ranges of target UEs that the first MME allows access to. Taking the first identifier as an IMEI as an example, the preconfigured target identifier may include IMEIs corresponding to UEs that are allowed to be accessed by a large number of first MMEs. In other words, an IMEI segment white list may be preconfigured in the first UE, where the white list may include a plurality of target identifiers, where each target identifier corresponds to one IMEI. Taking the first identifier as an IMSI as an example, the preconfigured target identifier may include IMSIs corresponding to a plurality of UEs that the first MME is allowed to access. In other words, an IMSI-segment white list may be preconfigured in the first UE, where the white list may include a plurality of target identifiers, where each target identifier corresponds to one IMSI. It can be appreciated that, for other first identifiers (such as IMEISV, SUPI, etc.), the configuration manner of the target identifier may refer to the above description, and only the IMEI or IMSI in the configuration process needs to be replaced by other first identifiers, which is not listed in order to avoid repetition.
A mismatch of the first identity with the target identity may indicate that the first identity cannot be found in the target identity. The first identifier matching the target identifier may indicate that the first identifier may be found in the target identifier.
Under the condition of no match, the first MME can start a redirection flow to acquire a second identification of the second MME. In case of matching, the target UE may access the first MME directly without redirection.
Step 340, the first mobility management entity returns redirection indication information to the target base station, where the redirection indication information carries the second identifier, and the second identifier is used to indicate the target base station to redirect to the second mobility management entity.
After the first MME obtains the second identifier of the second MME, the first MME can send redirection indication information carrying the second MME to the target base station, and the target base station is indicated to send the attachment request message to the second MME. So that the attach request message of the target UE may be redirected to the second MME. After receiving the attach request message of the target UE, the second MME may also continue to determine whether the target UE can be directly accessed, and restart the redirection procedure if the target UE cannot be accessed.
According to the redirection method provided by the embodiment of the application, whether redirection is needed or not can be determined according to the first identifier and the target identifier which is preconfigured in the first MME, and the second identifier of the second MME is further acquired under the condition that the first identifier is not matched with the target identifier, so that the target base station is assisted to redirect to the second MME, and the UE use type is not required to be acquired in the redirection process.
In addition, the redirection method provided by the embodiment of the application removes the step of acquiring the UE use type, so that the first MME does not need to acquire the UE use type from other equipment (such as HSS) through multiple signaling interactions, the flow can be simplified, the time delay can be shortened, and the processing performance of the first MME can be improved. Meanwhile, the UE use type is not used in the redirection process, so that the UE use type is not signed in the HSS, the signing data stored in the HSS can be reduced, and the storage space is released.
As discussed above, the attach request message in embodiments of the present application may or may not carry the first identifier. The following discussion is directed to the case where the attach request message carries the first identity and the case where the attach request message does not carry the first identity, respectively.
In one embodiment of the application, the attach request message carries a first identification. In this case, step 320, the first mobility management entity obtaining the first identifier according to the attach request message may include: the first mobility management entity extracts the first identity from the attach request message. Therefore, the first mark can be quickly obtained, comparison with the target mark is facilitated, whether redirection is needed or not is determined, the redirection time can be shortened to a certain extent, and the efficiency is improved.
In another embodiment of the present application, the obtaining, by the first mobility management entity, the first identifier according to the attach request message in step 320 may include: the first mobility management entity determines whether the attachment request message carries the first identifier; in the case that the attachment request message does not carry the first identifier, the first mobility management entity sends an identity request message to the target user equipment; and the first mobile management entity receives an identity response message from the target user equipment, wherein the identity response message carries the first identifier. In this way, under the condition that the attachment request message does not carry the first identifier, the first MME can actively send the identity request message to the target UE, acquire the first identifier information based on the identity request message, further determine whether redirection is required according to the first identifier, and assist UE redirection under the condition that the use type of the UE is not used.
Under the condition that the first identifier is not carried in the attachment request message, the first MME can send an identity request message to the target UE to request the target UE to report the first identifier. Then, the first MME may receive identity response information carrying the first identity from the target UE, and extract the first identity from the identity response information.
Fig. 4 is a flowchart of another redirection method provided in an embodiment of the present application. As shown in fig. 4, the redirection method provided by the embodiment of the present application may include the following steps:
Step 410, the first mobility management entity receives an attach request message of a target base station; wherein, the attachment request message carries target indication information;
The target indication information may include any one of a tracking area identification (TRACKINGAREA IDENTITY, TAI), a location of the target UE, and an IMSI field to which the target UE belongs.
And when the target indication information is the TAI or the position of the target UE, the target base station can receive the attachment request of the target UE, add the TAI or the position of the target UE, and send an attachment request message carrying the TAI or the position of the target UE to the first MME. Under the condition that the target indication information is the IMSI section to which the target UE belongs, the target UE can report the IMSI section first, namely, an attachment request carrying the IMSI section is sent to the target base station. And then the target base station sends the attachment request message carrying the IMSI section to which the target UE belongs to the first MME. By the above manner, the first MME can receive the attachment request message carrying the target indication information of the target base station.
Step 420, the first mobility management entity obtains a first identifier according to the attachment request message, where the first identifier is an identifier of a target user equipment or an identifier of a target user corresponding to the target user equipment;
Step 430, in the case that the first identifier is not matched with a target identifier pre-configured in the first mobility management entity, the first mobility management entity queries a mobility management entity identifier corresponding to the target indication information in a pre-configured target mapping table, where a correspondence between the indication information and the mobility management entity identifier exists in the target mapping table;
In the embodiment of the application, the target mapping table can be used for storing the corresponding relation between the indication information and the MME identifier. The MME identification and the indication information in the target mapping table may be a one-to-many correspondence or a one-to-one correspondence. The one-to-many correspondence may indicate that one MME identifier may correspond to a plurality of indication information, and that one indication information has and only has a MME identifier uniquely corresponding thereto. The one-to-one correspondence may represent that one MME identity corresponds to one indication information and one indication information corresponds to one MME identity. The correspondence between the indication information and the MME identifier may be determined according to the type or the management range of the MME divided by the operator, and if a correspondence exists between one indication information and one MME identifier, it is indicated that the MME may be used to manage the target UE corresponding to the indication information.
Taking the target indication information as a tracking area identifier as an example, the identifier of the MME for managing the UE of the area can be determined according to any one tracking area identifier, and after the corresponding relationship between the tracking area identifier and the MME identifier is determined, the corresponding relationship between the tracking area identifier and the MME identifier can be configured in the target mapping table. For other types of target indication information (such as a location or an IMSI field), the configuration manner of the target mapping table is similar, and only the tracking area identifier in the configuration process described above is required to be replaced by other target indication information, so that repetition is avoided, and description is not made one by one.
The first MME querying, in a pre-configured target mapping table, an MME identifier corresponding to the target indication information may include: the first MME takes the target indication information as an index, and searches MME identifications with corresponding relations with the target indication information in a target mapping table.
Step 440, when the first mobility management entity queries to obtain a mobility management entity identifier corresponding to the target indication information, the mobility management entity identifier obtained by the query is used as a second identifier of a second mobility management entity;
And inquiring to obtain MME identification which can indicate that the target indication information exists in the target mapping table and the corresponding relation exists between the target indication information and the MME identification.
Step 450, the first mobility management entity returns redirection indication information to the target base station, where the redirection indication information carries the second identifier, and the second identifier is used to indicate the target base station to redirect to the second mobility management entity.
After receiving the redirection indication information, the target base station may send an attach request message of the target UE to the second MME. Thus, the second MME may receive the attach request message and further determine whether the target UE can directly access. Because the second MME is determined according to the corresponding relation between the indication information and the MME, the selected second MME has close relation with the target UE, and therefore, in the embodiment of the application, the target base station can be directly accessed into the second MME.
According to the redirection method provided by the embodiment of the application, the target mapping table for storing the corresponding relation between the indication information and the MME identification is preconfigured in the first MME, and the second MME corresponding to the target indication information of the target UE is queried by utilizing the target mapping table, so that the second MME for managing the target UE can be accurately determined, further the target UE can be favorably accessed into the second MME, and the redirection success rate can be improved to a certain extent.
Since the target mapping table does not necessarily contain the correspondence between all indication information and MME identities. Further, other methods by which the second identity of the second MME may be obtained are further described in the present application. In one embodiment of the present application, in a case that the first identifier does not match with a target identifier configured in the first mobility management entity, the first mobility management entity obtains a second identifier of a second mobility management entity, and the redirection method provided in the embodiment of the present application further includes: and under the condition that the first mobile management entity does not inquire the mobile management entity identifier corresponding to the target indication information, the first mobile management entity takes the preset default mobile management entity identifier as a second identifier of the second mobile management entity. Therefore, under the condition that the information in the target mapping table is not comprehensive, the default MME can be directly determined as the second MME, and the redirection flexibility is further improved.
And if the target mapping table is not queried, the MME identification which can indicate that the target indication information does not exist in the target mapping table and has a corresponding relation with the target indication information does not exist.
The default MME identification may also be an MME identification determined according to an operator partitioning rule.
Under the condition that the first MME does not inquire the MME identification corresponding to the target indication information, the default MME identification can be directly determined as the second identification.
After the first MME determines the default MME as the second MME, the redirection indication information carrying the default MME identifier may be returned to the target base station. After receiving the redirection indication information, the target base station may send an attach request message of the target UE to a default MME. Therefore, the default MME can receive the attach request message, further determine whether the target UE can directly access, and restart the redirection procedure if the target UE cannot access.
Fig. 5 is a flowchart of another redirection method provided in an embodiment of the present application. As shown in fig. 5, the redirection method provided by the embodiment of the present application may include the following steps:
Step 510, the first mobility management entity receives the attachment request message of the target base station; wherein, the attachment request message carries target indication information;
wherein the target indication information comprises any one of tracking area identification, the position of the target user equipment and an international mobile subscriber identity section to which the target user equipment belongs.
Step 520, the first mobility management entity determines whether the first identifier is carried in the attach request message;
Wherein, in case the first identity is an identity of the target user equipment, the first identity may comprise at least one of an international mobile equipment identity, a software version identity of the international mobile equipment, a universally unique identity. In the case that the first identifier is an identifier of a target user corresponding to the target user equipment, the first identifier may include at least one of an international mobile subscriber identity and a user permanent identifier.
Step 530, the first mobility management entity sends an identity request message to the target ue when the first identifier is not carried in the attach request message;
Step 540, the first mobility management entity receives an identity response message from the target ue, where the identity response message carries the first identifier;
of course, in the case that the first identifier is carried in the attach request message, the subsequent steps may be directly performed without performing step 530 and step 540.
Step 550, in the case that the first identifier is not matched with a target identifier pre-configured in the first mobility management entity, the first mobility management entity queries a mobility management entity identifier corresponding to the target indication information in a pre-configured target mapping table, where a correspondence between the indication information and the mobility management entity identifier exists in the target mapping table;
Step 560, when the first mobility management entity queries to obtain a mobility management entity identifier corresponding to the target indication information, the mobility management entity identifier obtained by the query is used as a second identifier of a second mobility management entity; under the condition that the mobile management entity identifier corresponding to the target indication information is not inquired, the first mobile management entity takes a preset default mobile management entity identifier as a second identifier of the second mobile management entity;
In step 570, the first mobility management entity returns redirection indication information to the target base station, where the redirection indication information carries the second identifier, and the second identifier is used to indicate the target base station to redirect to the second mobility management entity.
According to the redirection method provided by the embodiment of the application, whether redirection is needed or not can be determined according to the first identifier and the target identifier which is preconfigured in the first MME, and the second identifier of the second MME is further acquired under the condition that the first identifier is not matched with the target identifier, so that the target base station is assisted to redirect to the second MME, and the UE use type is not required to be acquired in the redirection process.
For easy understanding, the redirection method provided in the embodiment of the present application is further described in detail below with reference to specific first identification and target indication information. Fig. 6 is a flowchart of another redirection method provided in an embodiment of the present application. As shown in fig. 6, taking the first identifier as the IMSI and the target indication information as the TAI as an example, the redirection method provided in the embodiment of the present application may include the following steps:
Step 610, configuring an IMSI field (corresponding to the target identifier) white list and a NAS redirected second MME identifier (corresponding to the target mapping table) in the first MME;
In the embodiment of the present application, the IMSI range white list may be an IMSI range list of the UE that the first MME allows access to. If the IMSI reported during the initial attachment of the UE is in the IMSI range list of the first MME, the first MME allows the UE to access, otherwise, NAS redirection flow is carried out.
The second MME identity for NAS redirection is MME group identity (MME Group Identity, MMEGI) and there are two configurations including 1, unique mapped MMEGI with tracking area identity, 2, unique default MMEGI.
In step 620, the first MME confirms that the IMSI reported by the UE does not match with the IMSI field white list.
In step 630, the first MME preferentially selects the second MME based on the TAI reported by the UE, and if the selection fails, selects the default MME as the second MME.
After determining the second MME, the first MME may return second identifier redirection indication information carrying the second MME to the target base station, indicating the target base station to send an attach request message of the UE to the second MME.
According to the redirection method provided by the embodiment of the application, through pre-configuring the IMSI section white list and the NAS redirection second MME identifier in the first MME, whether the redirection process needs to be started or not can be quickly realized according to the IMSI reported by the UE, and the proper second MME is selected when the redirection is needed, so that the UE use type is not required to be acquired, and compared with the method that the redirection can be realized only by the UE use type in the related art, the flexibility can be improved to a certain extent. Meanwhile, the second MME is preferentially selected based on the TAI reported by the UE, so that the MME matched with the UE can be accurately selected, thereby being beneficial to the UE to smoothly access the second MME and improving the redirection success rate.
Fig. 7-1 is an interaction schematic diagram of a redirection procedure according to an embodiment of the present application. As shown in fig. 7-1, taking the first identifier as the IMSI and the target indication information as the TAI as an example, the redirection interaction procedure provided by the embodiment of the present application may include the following steps:
In step 710, the user configures, via the network management system, an IMSI (corresponding to the target identifier) whitelist and MME group identifiers (MME Group Identity, MMEGI) (corresponding to the target mapping table) of the NAS redirected second MME on the first MME.
The MMEGI may be an identifier having a correspondence with the TAI, or a default identifier of the MME.
In step 720, the UE initiates an initial attach request message to the eNodeB, where the message carries UE identification information.
In step 730, the enodeb sends an initial attach request message to the first MME, where the message carries UE identification information and tracking area identification (corresponding to the target indication information).
In step 740, the first MME determines whether the UE identification information carried in the initial attach request message is an IMSI. If the UE identification information carried in the initial attach request message is not the IMSI (corresponding to the first identifier), the first MME sends an identity request message to the UE, requesting the UE to report the IMSI.
In step 750, the UE sends an identity response message to the first MME, where the message carries the UE IMSI.
In step 760, the first MME discovers that the IMSI reported by the UE is not in the white list, and based on the tracking area identifier TAI reported by the UE, the first MME queries the MMEGI configured in the MME and having a mapping relationship with the TAI as the second MME identifier, and if the querying fails, selects the default MMEGI as the second MME identifier.
In step 770, the first MME returns a redirection indication message to the eNodeB, carrying the MMEGI of the redirected second MME.
In step 780, the enodeb sends an initial attach request message to the second MME according to the MMEGI in the redirection indication message.
According to the redirection method provided by the embodiment of the application, through pre-configuring the IMSI section white list and the NAS redirection second MME identifier in the first MME, whether the redirection flow needs to be started or not can be quickly determined according to the IMSI reported by the UE, and a proper second MME can be selected according to the tracking area identifier reported by the UE when the redirection is needed, so that the UE use type does not need to be acquired, and compared with the method that the redirection can be realized only by the UE use type in the related art, the flexibility can be improved to a certain extent. Meanwhile, the second MME is preferentially selected based on the TAI reported by the UE, so that the MME matched with the UE can be accurately selected, thereby being beneficial to the UE to smoothly access the second MME and improving the redirection success rate.
In addition, it should be emphasized that FIG. 7-1 is merely an example provided by the present application and should not be construed as limiting the application. In practice, if the UE identification information carried in the initial attach request message is an IMSI, the first MME does not need to send an identity request to the UE, and the UE does not need to report the IMSI to the first MME again. In the case that the initial attach request message carries the IMSI of the UE, a specific interaction procedure of the redirection procedure provided in the embodiment of the present application may be shown in fig. 7-2.
Fig. 8 is a block diagram of a redirecting device according to an embodiment of the present application. As shown in fig. 8, the redirecting device 800 provided by the embodiment of the present application includes a receiving module 810, an obtaining module 820, and a sending module 830.
Wherein, the receiving module 810 is configured to receive an attach request message of a target base station;
The obtaining module 820 is configured to obtain, according to the attach request message, a first identifier, where the first identifier is an identifier of a target user device or an identifier of a target user corresponding to the target user device; acquiring a second identifier of a second mobile management entity under the condition that the first identifier is not matched with a target identifier pre-configured in the first mobile management entity;
The sending module 830 is configured to return, to the target base station, redirection indication information, where the redirection indication information carries the second identifier, and the second identifier is used to indicate that the target base station redirects to the second mobility management entity.
The redirection device provided by the embodiment of the application can determine whether redirection is needed according to the first identifier and the target identifier pre-configured in the first MME, further acquire the second identifier of the second MME under the condition that the first identifier is not matched with the target identifier, assist the target base station to redirect to the second MME, and does not need to acquire the UE use type in the redirection process, so that the flexibility can be improved to a certain extent compared with the method which can only realize redirection by depending on the UE use type in the related technology.
Optionally, in an embodiment of the present application, the attach request message further carries target indication information; in the case that the first identifier does not match the target identifier configured in the first mobility management entity, in a process of acquiring the second identifier of the second mobility management entity, the acquiring module 820 is specifically configured to: under the condition that the first identifier is not matched with a target identifier which is pre-configured in the first mobile management entity, inquiring the mobile management entity identifier corresponding to the target indication information in a pre-configured target mapping table, wherein the corresponding relation between the indication information and the mobile management entity identifier exists in the target mapping table; and under the condition that the mobile management entity identifier corresponding to the target indication information is obtained by inquiry, the mobile management entity identifier obtained by inquiry is used as a second identifier of a second mobile management entity.
Optionally, in an embodiment of the present application, in a process of acquiring the second identifier of the second mobility management entity, in a case that the first identifier does not match the target identifier configured in the first mobility management entity, the acquiring module 820 is further configured to: and under the condition that the mobile management entity identifier corresponding to the target indication information is not inquired, taking the preset default mobile management entity identifier as a second identifier of the second mobile management entity.
Optionally, in one embodiment of the present application, the attach request message carries a first identifier; in the process of acquiring the first identifier according to the attach request message, the acquiring module 820 is specifically configured to: the first identity is extracted from the attach request message.
Optionally, in an embodiment of the present application, in the process of acquiring the first identifier according to the attach request message, the acquiring module 820 is specifically configured to: determining whether the first identifier is carried in the attachment request message; sending an identity request message to the target user equipment under the condition that the first identifier is not carried in the attachment request message; and receiving an identity response message from the target user equipment, wherein the identity response message carries the first identifier.
Optionally, in one embodiment of the present application, in a case that the first identifier is an identifier of the target user equipment, the first identifier includes at least one of an international mobile equipment identifier, a software version identifier of the international mobile equipment, and a universally unique identifier; and under the condition that the first identifier is the identifier of the target user corresponding to the target user equipment, the first identifier comprises at least one of an international mobile subscriber identity and a user permanent identifier.
Optionally, in one embodiment of the present application, the target indication information includes any one of a tracking area identification, a location of the target user equipment, and an international mobile subscriber identity field to which the target user equipment belongs.
It should be noted that, the redirection device provided in the embodiment of the present application corresponds to the above mentioned redirection method. The relevant content can be referred to the above description of the redirection method, and will not be described here.
In addition, as shown in fig. 9, the embodiment of the present application further provides a mobility management entity 900, where the electronic device may be various types of computers, and so on. The mobility management entity 900 includes: a processor 910, a memory 920, said memory 920 having stored thereon a program or instructions which, when executed by said processor 910, implement the steps of any of the methods described above.
Embodiments of the present application also provide a readable storage medium having stored thereon a program or instructions which when executed by the processor 910 performs the steps of any of the methods described above.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transitorymedia), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and variations of the present application will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. which come within the spirit and principles of the application are to be included in the scope of the claims of the present application.
Claims (10)
1. A redirection method, comprising:
the first mobility management entity receives an attachment request message of a target base station;
the first mobility management entity obtains a first identifier according to the attachment request message, wherein the first identifier is an identifier of target user equipment or an identifier of a target user corresponding to the target user equipment;
Under the condition that the first identifier is not matched with a target identifier pre-configured in the first mobile management entity, the first mobile management entity acquires a second identifier of a second mobile management entity;
And the first mobile management entity returns redirection indication information to the target base station, wherein the redirection indication information carries the second identifier, and the second identifier is used for indicating the target base station to redirect to the second mobile management entity.
2. The method of claim 1, wherein the attach request message further carries target indication information;
in the case that the first identifier does not match with the target identifier configured in the first mobility management entity, the first mobility management entity obtains a second identifier of a second mobility management entity, including:
Under the condition that the first identifier is not matched with a target identifier which is pre-configured in the first mobility management entity, the first mobility management entity queries a mobility management entity identifier corresponding to the target indication information in a pre-configured target mapping table, wherein the target mapping table has a corresponding relation between the indication information and the mobility management entity identifier;
and under the condition that the first mobile management entity inquires and obtains the mobile management entity identifier corresponding to the target indication information, the inquired and obtained mobile management entity identifier is used as a second identifier of a second mobile management entity.
3. The method of claim 2, wherein the first mobility management entity obtains a second identity of a second mobility management entity if the first identity does not match a target identity configured in the first mobility management entity, further comprising:
And under the condition that the first mobile management entity does not inquire the mobile management entity identifier corresponding to the target indication information, the first mobile management entity takes the preset default mobile management entity identifier as a second identifier of the second mobile management entity.
4. A method according to any of claims 1-3, characterized in that the attach request message carries a first identity;
the first mobility management entity obtaining the first identifier according to the attach request message includes: the first mobility management entity extracts the first identity from the attach request message.
5. A method according to any of claims 1-3, wherein the first mobility management entity obtaining the first identity from the attach request message comprises:
The first mobility management entity determines whether the attachment request message carries the first identifier;
in the case that the attachment request message does not carry the first identifier, the first mobility management entity sends an identity request message to the target user equipment;
and the first mobile management entity receives an identity response message from the target user equipment, wherein the identity response message carries the first identifier.
6. The method according to claim 4 or 5, wherein in case the first identity is an identity of a target user equipment, the first identity comprises at least one of an international mobile equipment identity, a software version identity of an international mobile equipment, a universally unique identity;
And under the condition that the first identifier is the identifier of the target user corresponding to the target user equipment, the first identifier comprises at least one of an international mobile subscriber identity and a user permanent identifier.
7. A method according to claim 2 or 3, wherein the target indication information comprises any of a tracking area identification, a location of the target user equipment, an international mobile subscriber identity field to which the target user equipment belongs.
8. A redirecting device, comprising:
a receiving module, configured to receive an attach request message of a target base station;
The acquisition module is used for acquiring a first identifier according to the attachment request message, wherein the first identifier is an identifier of target user equipment or an identifier of a target user corresponding to the target user equipment; acquiring a second identifier of a second mobile management entity under the condition that the first identifier is not matched with a target identifier pre-configured in the first mobile management entity;
And the sending module is used for returning redirection indication information to the target base station, wherein the redirection indication information carries the second identifier, and the second identifier is used for indicating the target base station to redirect to the second mobile management entity.
9. A mobility management entity, characterized by comprising a processor and a memory storing a program or instructions which, when executed by said processor, implement the steps of the method according to any of claims 1-7.
10. A readable storage medium, characterized in that it stores thereon a program or instructions, which when executed, implement the steps of the method according to any of claims 1-7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211422164.4A CN118042561A (en) | 2022-11-14 | 2022-11-14 | Redirection method, device and mobile management entity |
| PCT/CN2023/126457 WO2024104065A1 (en) | 2022-11-14 | 2023-10-25 | Redirection method and apparatus, and mobility management entity |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211422164.4A CN118042561A (en) | 2022-11-14 | 2022-11-14 | Redirection method, device and mobile management entity |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN118042561A true CN118042561A (en) | 2024-05-14 |
Family
ID=90991863
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211422164.4A Pending CN118042561A (en) | 2022-11-14 | 2022-11-14 | Redirection method, device and mobile management entity |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN118042561A (en) |
| WO (1) | WO2024104065A1 (en) |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014169950A1 (en) * | 2013-04-16 | 2014-10-23 | Nokia Solutions And Networks Oy | Mobility management entity (mme) triggered detach and re-attach to a specific target mme |
| CN107645722B (en) * | 2016-07-20 | 2021-01-26 | 中国电信股份有限公司 | Private network selective access method and system, public network MME, HSS and base station |
| CN111132256B (en) * | 2018-10-31 | 2021-06-04 | 华为技术有限公司 | User terminal access method, initial mobile management entity and base station |
| CN112637841A (en) * | 2019-09-23 | 2021-04-09 | 普天信息技术有限公司 | International mobile equipment identification checking method and system for electric power wireless private network |
-
2022
- 2022-11-14 CN CN202211422164.4A patent/CN118042561A/en active Pending
-
2023
- 2023-10-25 WO PCT/CN2023/126457 patent/WO2024104065A1/en unknown
Also Published As
| Publication number | Publication date |
|---|---|
| WO2024104065A1 (en) | 2024-05-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102442911B1 (en) | Selection of Network Slice Identifiers | |
| EP3487196B1 (en) | Privacy managing entity selection in communication system | |
| KR101111153B1 (en) | Accessing gateway selecting method, system and gateway selecting implementing node of mobile group domain | |
| US10595187B2 (en) | System and method of selective packet data network gateway discovery | |
| US11659621B2 (en) | Selection of IP version | |
| US12003592B2 (en) | Method and apparatus for service discovery | |
| US10757645B2 (en) | Access control in communications network comprising slices | |
| EP3481138B1 (en) | Information transmission method, convergence gateway and system | |
| JP7399188B2 (en) | Method and apparatus for service discovery | |
| US10021726B2 (en) | Method and device for implementing proximity communication service | |
| EP3815401A1 (en) | Security management for service access in a communication system | |
| CN113785552B (en) | Session management function selection | |
| CN103228004A (en) | Lawful intercept without mobile station international subscriber directory number | |
| CN102547658B (en) | Method and device for transmitting data | |
| CN110324807B (en) | Information processing method, function and computer readable storage medium | |
| WO2015135269A1 (en) | Service discovery and authentication method, device, terminal, system, and computer storage medium | |
| CN106341851B (en) | Method for establishing special bearing for specified terminal | |
| CN107615238A (en) | Access the method and relevant device of local network | |
| CN106851763B (en) | Message routing method, system and gateway in LTE network | |
| CN118042561A (en) | Redirection method, device and mobile management entity | |
| KR20130060967A (en) | Data service method of multiple pdn based odb scheme for lte mobile users | |
| US9843553B2 (en) | Method and device for sending message | |
| US9282439B1 (en) | Systems and methods of wireless device push-to-talk registration | |
| EP4055792B1 (en) | Proxy-call session control function (p-cscf) to p-cscf communication | |
| CN106686756B (en) | PCC conversation establishing method and system based on position |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication |