WO2024104065A1 - 重定向方法、装置和移动管理实体 - Google Patents

重定向方法、装置和移动管理实体 Download PDF

Info

Publication number
WO2024104065A1
WO2024104065A1 PCT/CN2023/126457 CN2023126457W WO2024104065A1 WO 2024104065 A1 WO2024104065 A1 WO 2024104065A1 CN 2023126457 W CN2023126457 W CN 2023126457W WO 2024104065 A1 WO2024104065 A1 WO 2024104065A1
Authority
WO
WIPO (PCT)
Prior art keywords
identifier
management entity
mobility management
target
request message
Prior art date
Application number
PCT/CN2023/126457
Other languages
English (en)
French (fr)
Inventor
周盟
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2024104065A1 publication Critical patent/WO2024104065A1/zh

Links

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

Definitions

  • the present application belongs to the field of communication technology, and specifically relates to a redirection method, device and mobile management entity.
  • the Evolved Packet System (EPS) wireless network architecture of Long Term Evolution (LTE) has been widely used.
  • the private network mobility management entity (MME) and the public network MME share the same base station and are isolated from each other, which makes it impossible for the base station to determine whether the user equipment (UE) should access the private network or the public network, resulting in access errors. Therefore, after the base station receives the registration attachment request from the UE, it is often necessary to use the MME to assist the base station in redirection.
  • redirection is usually implemented based on the UE usage type.
  • the base station After receiving the registration attachment request from the UE, the base station sends the relevant information of the UE to the first MME.
  • the first MME further obtains the UE usage type from a third-party device (such as a contract server, etc.), and determines whether the UE should access a private network or a public network based on the UE usage type, thereby deciding whether to initiate the redirection process.
  • a third-party device such as a contract server, etc.
  • this redirection method must obtain the UE usage type. If the UE usage type cannot be obtained, the redirection process cannot be initiated, resulting in the UE's registration and attachment request being unable to be redirected to the matching MME, which is seriously lacking in flexibility.
  • the embodiments of the present application provide a redirection method, device and mobile management entity, which can solve the problem that the redirection must be implemented based on the UE usage type in the related art and lacks flexibility.
  • an embodiment of the present application provides a redirection method, the method comprising: a first mobile management entity receives an attachment request message from a target base station; the first mobile management entity obtains a first identifier based on the attachment request message, the first identifier being an identifier of a target user device or an identifier of a target user corresponding to the target user device; when the first identifier does not match a target identifier pre-configured in the first mobile management entity, the first mobile management entity obtains a second identifier of a second mobile management entity; the first mobile management entity returns a redirection indication message to the target base station, the redirection indication message carrying the second identifier, and the second identifier is used to indicate that the target base station is redirected to the second mobile management entity.
  • an embodiment of the present application provides a redirection device, which includes: a receiving module, used to receive an attachment request message from a target base station; an acquisition module, used to acquire a first identifier according to the attachment request message, the first identifier being an identifier of a target user device or an identifier of a target user corresponding to the target user device; when the first identifier does not match the target identifier pre-configured in the first mobile management entity, acquiring a second identifier of a second mobile management entity; a sending module, used to return redirection indication information to the target base station, the redirection indication information carrying the second identifier, and the second identifier being used to indicate that the target base station is redirected to the second mobile management entity.
  • an embodiment of the present application provides a mobile management entity, which includes a processor and a memory, wherein the memory stores programs or instructions, and when the programs or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.
  • an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.
  • an embodiment of the present application provides a chip, the chip comprising a processor and a communication
  • the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method described in the first aspect.
  • an embodiment of the present application provides a computer program product, which is stored in a storage medium and is executed by at least one processor to implement the method described in the first aspect.
  • FIG1 is a diagram of the EPS wireless network architecture of LTE
  • FIG2 is a schematic diagram of an interaction of a NAS redirection process of LTE
  • FIG3 is a flow chart of a redirection method provided in an embodiment of the present application.
  • FIG4 is a flow chart of another redirection method provided in an embodiment of the present application.
  • FIG5 is a flow chart of another redirection method provided in an embodiment of the present application.
  • FIG6 is a flow chart of another redirection method provided in an embodiment of the present application.
  • FIG7-1 is an interactive schematic diagram of a redirection process provided in an embodiment of the present application.
  • FIG7-2 is an interactive diagram of another redirection process provided in an embodiment of the present application.
  • FIG8 is a structural block diagram of a redirection device provided in an embodiment of the present application.
  • FIG. 9 is a structural block diagram of a mobility management entity provided in an embodiment of the present application.
  • first, second, etc. in the specification and claims of the present application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged where appropriate, so that the embodiments of the present application can be used in other ways than those shown or described herein.
  • the order of implementation is not limited to those described above, and the objects distinguished by “first”, “second”, etc. are usually of the same type, and the number of objects is not limited.
  • the first object can be one or more.
  • “and/or” in the specification and claims means at least one of the connected objects, and the character “/" generally means that the related objects are in an "or” relationship.
  • the standardization working group of the 3rd Generation Partnership Project (3GPP) is currently working on the evolution of the Packet Switch Core (PS Core) and the Universal Mobile Telecommunication System Radio Access Network (UTRAN).
  • the research project is called System Architecture Evolution (SAE), and its purpose is to enable the Evolved Packet Core (EPC) to provide higher transmission rates, shorter transmission delays, optimize packets, and support mobility management between Evolved UTRAN (Evolved UTRAN, E-UTRAN), UTRAN, Wireless Local Area Network (WLAN) and other non-3GPP access networks.
  • SAE System Architecture Evolution
  • EPC Evolved Packet Core
  • FIG. 1 is a diagram of the EPS wireless network architecture of LTE. As shown in Figure 1, the LTE network architecture is divided into four parts: UE, E-UTRAN (access network), EPC (core network) and Packet Data Network (PDN).
  • UE Evolved Packet System
  • EPC core network
  • PDN Packet Data Network
  • E-UTRAN is an access network composed of multiple evolved NodeBs (eNodeBs) and is used to provide wireless resources for user access.
  • eNodeBs are wireless base stations in the LTE network.
  • PDN is a network that provides services to UE.
  • EPC provides lower transmission delay and allows more non-access system access. Its network elements include: Mobility Management Entity (MME), Serving Gateway (SGW), Packet Data Gateway (PGW), Serving General Packet Radio Service Support Node (SGSN), Policy and Charging Rules Function (PCRF), Home Home Subscriber Server (HSS).
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • PGW Packet Data Gateway
  • SGSN Serving General Packet Radio Service Support Node
  • PCRF Policy and Charging Rules Function
  • HSS Home Home Subscriber Server
  • MME Mobility Management Entity
  • SGW Packet Data Gateway
  • PGW Packet Data Gateway
  • SGSN Serving General Packet Radio Service Support Node
  • PCRF Policy and Charging Rules Function
  • HSS Home Home Subscriber Server
  • MME Mobility Management Entity
  • SGW Packet Data Gateway
  • SGSN Serving General Packet Radio Service Support Node
  • PCRF Policy and Charging Rules Function
  • HSS Home Home Subscriber Server
  • the MME decides whether to initiate the NAS redirection process based on the UE usage type (UE Usage Type), and further determines the MME that matches the UE based on the UE usage type when the NAS redirection process needs to be initiated.
  • UE Usage Type the UE usage type
  • FIG. 2 is an interactive schematic diagram of a NAS redirection process of LTE. As shown in FIG. 2 , the redirection process of LTE may include the following steps.
  • Step 201 The UE sends an initial attach request message to the eNodeB.
  • Step 202 The eNodeB sends an initial attach request message to the 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.
  • 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 When the first MME fails to obtain 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, wherein the authentication information response message carries the UE usage type.
  • Step 209 The first MME determines whether a redirection process needs to be initiated based on the UE usage type, and when the redirection process needs to be initiated, determines a second MME based on the UE usage type.
  • Step 210 The first MME sends a redirection indication message to the eNodeB, wherein the redirection indication message carries the second MME identifier.
  • Step 211 The eNodeB sends an initial attach request message to the second MME.
  • the NAS message when the NAS message is redirected from the first MME to the second MME, it is necessary to obtain the UE usage type (UE Usage Type) from the third MME/SGSN or HSS, and decide whether to initiate the NAS redirection process based on the UE usage type.
  • UE Usage Type UE Usage Type
  • the first MME cannot initiate the NAS redirection process, resulting in the UE being unable to access the matching second MME.
  • the present application creatively proposes a redirection method, which can achieve redirection without using the UE usage type.
  • Fig. 3 is a flow chart of a redirection method provided in an embodiment of the present application. As shown in Fig. 3, the redirection method provided in an embodiment of the present application may include the following steps.
  • Step 310 The first mobility management entity receives an attach request message from a target base station.
  • the first MME may be an MME determined by the target base station for the target UE according to the 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, wherein the attach request message may carry relevant information of the target UE and the target base station.
  • the first MME may receive the attach request message sent by the target base station.
  • the UE needs to complete the process of registering and attaching to the network each time it is turned on or returns from a network coverage blind area to a network coverage area, so that the UE can normally use the activated services through the network.
  • the target UE can send an attachment request to the target base station and access the core network based on the attachment request.
  • the first MME can receive the attachment request message forwarded by the target base station.
  • Step 320 The first mobility management entity obtains a first identifier according to the attach request message, where the first identifier is an identifier of a target user equipment or a target user equipment corresponding to the target user equipment. The user's ID.
  • the attach request message may include the first identifier or may not include the first identifier.
  • obtaining the first identifier may include: when the attach request message includes the first identifier, directly obtaining the first identifier from the attach request message, or, when the attach request message does not include the first identifier, sending a first identifier acquisition request to the target UE/HSS, and receiving the first identifier returned by the target UE/HSS.
  • the identification of the target UE may include: at least one of: International Mobile Equipment Identity (IMEI), International Mobile Equipment Software Version Identifier (IMEISV), and 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 (IMSI) and Subscription Permanent Identifier (SUPI).
  • IMSI International Mobile Subscriber Identity
  • SUPI Subscription Permanent Identifier
  • Step 330 When the first identifier does not match the 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.
  • the second MME may be an MME that the target UE determined by the first MME according to the attachment request message can access.
  • the target identifier may include the identifier of at least one UE or the identifier of the user corresponding to the UE.
  • the pre-configured target identifier may be stored in the first MME in the form of a whitelist.
  • the attributes of the target identifier and the first identifier may be the same. For example, if the first identifier is IMEI, the target identifier may be at least one IMEI. If the first identifier is IMSI, etc., the target identifier may be at least one IMSI.
  • the whitelist may be a first identifier range list of target UEs that the first MME allows to access.
  • the pre-configured target identifier may include a large number of IMEIs corresponding to UEs that the first MME allows to access.
  • an IMEI segment whitelist may be pre-configured in the first UE, wherein the whitelist may include a large number of target identifiers, and each target identifier corresponds to an IMEI.
  • the pre-configured target identifier may include a large number of IMSIs corresponding to UEs that the first MME allows to access.
  • the first UE pre-configures an IMSI segment whitelist, wherein the whitelist may include a large number of target identifiers, each of which corresponds to an IMSI. It is understandable that for other first identifiers (such as IMEISV, SUPI, etc.), the configuration method of the target identifier may refer to the above description, and only the IMEI or IMSI in the configuration process needs to be replaced as a whole with other first identifiers. To avoid repetition, they are not listed one by one.
  • the mismatch between the first identifier and the target identifier may indicate that the first identifier cannot be found in the target identifier.
  • the match between the first identifier and the target identifier may indicate that the first identifier can be found in the target identifier.
  • the first MME may initiate a redirection process to obtain the second identifier of the second MME.
  • the target UE may directly access the first MME without redirection.
  • Step 340 The first mobility 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 to instruct the target base station to redirect to the second mobility management entity.
  • the first MME After the first MME obtains the second identifier of the second MME, it can send a redirection indication message carrying the second MME to the target base station, instructing the target base station to send an attachment request message to the second MME.
  • the attachment request message of the target UE can be redirected to the second MME.
  • the second MME After receiving the attachment request message of the target UE, the second MME can also continue to determine whether the target UE can directly access, and if it cannot access, start the redirection process again.
  • the redirection method provided by the embodiment of the present application is as follows: a first mobile management entity receives an attachment request message from a target base station; the first mobile management entity obtains a first identifier based on the attachment request message, 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; when the first identifier does not match the target identifier pre-configured in the first mobile management entity, the first mobile management entity obtains a second identifier of a second mobile management entity; the first mobile management entity returns a redirection indication message to the target base station, where the redirection indication message carries the second identifier, and the second identifier is used to indicate that the target base station is redirected to the second mobile management entity.
  • the first identifier and the target identifier pre-configured in the first MME can be used to redirect the target base station to the second mobile management entity.
  • the target identifier is used to determine whether redirection is needed, and when the first identifier does not match the target identifier, the second identifier of the second MME is further obtained to assist the target base station in redirecting to the second MME.
  • the redirection method provided in the embodiment of the present application removes the step of obtaining the UE usage type, so that the first MME does not need to obtain the UE usage type from other devices (such as HSS) through multiple signaling interactions, which can simplify the process, shorten the delay, and improve the processing performance of the first MME.
  • the UE usage type since the UE usage type is not used in the redirection process, the UE usage type can be signed in the HSS, which can reduce the subscription data stored in the HSS and release storage space.
  • the attach request message in the embodiment of the present application may carry the first identifier or may not carry the first identifier.
  • the following discusses the case where the attach request message carries the first identifier and the case where the attach request message does not carry the first identifier.
  • the attachment request message carries a first identifier.
  • the first mobility management entity obtaining the first identifier according to the attachment request message may include: the first mobility management entity extracting the first identifier from the attachment request message.
  • step 320 in which the first mobile management entity obtains the first identifier according to the attachment request message may include: the first mobile management entity determines whether the attachment request message carries the first identifier; when the attachment request message does not carry the first identifier, the first mobile management entity sends an identity request message to the target user equipment; the first mobile management entity receives an identity response message from the target user equipment, and the identity response message carries the first identifier.
  • the first MME can actively send an identity request message to the target UE, obtain the first identifier information based on the identity request message, and further determine whether redirection is required based on the first identifier, so as to assist the UE in redirection without using the UE usage type.
  • the first MME may send an identity request message to the target UE to request the target UE to report the first identifier. Afterwards, the first MME may receive identity response information carrying the first identifier from the target UE and extract the first identifier from the identity response information.
  • Fig. 4 is a flow chart of another redirection method provided by an embodiment of the present application. As shown in Fig. 4, the redirection method provided by an embodiment of the present application may include the following steps.
  • Step 410 The first mobility management entity receives an attach request message from a target base station; wherein the attach request message carries target indication information.
  • the target indication information may include any one of the tracking area identity (TAI), the location of the target UE, and the IMSI segment to which the target UE belongs.
  • TAI tracking area identity
  • the target indication information may include any one of the tracking area identity (TAI), the location of the target UE, and the IMSI segment to which the target UE belongs.
  • the target base station can receive the attachment request of the target UE, add the TAI or the location of the target UE, and send the attachment request message carrying the TAI or the location of the target UE to the first MME.
  • the target indication information is the IMSI segment to which the target UE belongs
  • the target UE can first report its IMSI segment, that is, send an attachment request carrying its IMSI segment to the target base station.
  • the target base station then sends the attachment request message carrying the IMSI segment to which the target UE belongs to the first MME.
  • the first MME can receive the attachment request message carrying the target indication information from the target base station.
  • Step 420 The first mobility management entity obtains a first identifier according to the attach 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 When the first identifier does not match the target identifier pre-configured in the first mobile management entity, the first mobile management entity queries the mobile management entity identifier corresponding to the target indication information in a pre-configured target mapping table, wherein the target mapping table contains a correspondence between the indication information and the mobile management entity identifier.
  • the target mapping table can be used to store the correspondence between the indication information and the MME identifier.
  • the MME identifier and the indication information in the target mapping table can be a one-to-many pair.
  • a one-to-many correspondence relationship may indicate that one MME identifier may correspond to multiple indication information, and one indication information has one and only one MME identifier corresponding to it.
  • a one-to-one correspondence relationship may indicate that one MME identifier corresponds to one indication information, and one indication information corresponds to one MME identifier.
  • the correspondence between the indication information and the MME identifier may be determined according to the type or management scope of the MME divided by the operator. If there is a correspondence between one indication information and one MME identifier, it means that the MME can be used to manage the target UE corresponding to the indication information.
  • the identifier of the MME used to manage the UE in the area can be determined according to any tracking area identifier. After determining the correspondence between the tracking area identifier and the MME identifier, the correspondence 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 location or IMSI segment), the configuration method of the target mapping table is similar. It is only necessary to replace the tracking area identifier in the configuration process described above with other target indication information. To avoid repetition, they are not introduced one by one.
  • the first MME searching the pre-configured target mapping table for the MME identity corresponding to the target indication information may include: the first MME uses the target indication information as an index to search the target mapping table for the MME identity that has a corresponding relationship with the target indication information.
  • Step 440 When the first mobility management entity obtains the mobility management entity identifier corresponding to the target indication information through query, the first mobility management entity uses the obtained mobility management entity identifier as the second identifier of the second mobility management entity.
  • the query obtains an MME identifier which can indicate that the target indication information exists in the target mapping table and that there is a corresponding relationship with the target indication information.
  • Step 450 The first mobility 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 to instruct the target base station to redirect to the second mobility management entity.
  • the target base station After receiving the redirection indication information, the target base station can send the target UE's attachment request message to the second MME.
  • the second MME can receive the attachment request message and further determine whether the target UE can directly access. It is determined that the selected second MME is closely related to the target UE. Therefore, in the embodiment of the present application, the target base station can generally directly access the second MME.
  • the redirection method provided in the embodiment of the present application can accurately determine the second MME used to manage the target UE by pre-configuring a target mapping table in the first MME for storing the correspondence between the indication information and the MME identifier, and using the target mapping table to query the second MME corresponding to the target indication information of the target UE, thereby facilitating the target UE to smoothly access the second MME and improving the redirection success rate to a certain extent.
  • the target mapping table may not contain all the correspondences between the indication information and the MME identifier. Furthermore, this application further introduces other methods for obtaining the second identifier of the second MME.
  • the first mobile management entity when the first identifier does not match the target identifier configured in the first mobile management entity, the first mobile management entity obtains the second identifier of the second mobile management entity.
  • the redirection method provided in the embodiment of the present application also includes: when the first mobile management entity fails to obtain the mobile management entity identifier corresponding to the target indication information, the first mobile management entity uses the pre-configured default mobile management entity identifier as the second identifier of the second mobile management entity. In this way, when the information in the target mapping table is incomplete, the default MME can be directly determined as the second MME, further improving the redirection flexibility.
  • Failure to obtain the result of the query may indicate that the target indication information does not exist in the target mapping table, and there is no MME identifier that corresponds to the target indication information.
  • the default MME identifier may also be an MME identifier determined according to operator division rules.
  • the first MME may directly determine the default MME identity as the second identity.
  • the first MME After the first MME determines the default MME as the second MME, it can return a redirection indication message carrying the default MME identifier to the target base station. After receiving the redirection indication message, the target base station can send an attach request message of the target UE to the default MME. Thus, the default MME can receive the attach request message and further determine whether the target UE can directly access. If it cannot access, the redirection process is restarted.
  • Fig. 5 is a flow chart of another redirection method provided by an embodiment of the present application. As shown in Fig. 5, the redirection method provided by an embodiment of the present application may include the following steps.
  • Step 510 The first mobility management entity receives an attach request message from a target base station; wherein the attach request message carries target indication information.
  • the target indication information includes any one of a tracking area identifier, a location of the target user equipment, and an international mobile subscriber identity code segment to which the target user equipment belongs.
  • Step 520 The first mobility management entity determines whether the attach request message carries the first identifier.
  • the first identifier in the case where the first identifier is the identifier of the target user equipment, the first identifier may include at least one of an international mobile equipment identity, an international mobile equipment software version identifier, and a universal unique identifier. In the case where the first identifier is the identifier of the target user corresponding to the target user equipment, the first identifier may include at least one of an international mobile user identity and a user permanent identifier.
  • Step 530 When the attach request message does not carry the first identifier, the first mobility management entity sends an identity request message to the target user equipment.
  • Step 540 The first mobility management entity receives an identity response message from the target user equipment, where the identity response message carries the first identifier.
  • step 530 and step 540 may not be performed, and subsequent steps may be performed directly.
  • Step 550 when the first identifier does not match the target identifier pre-configured in the first mobile management entity, the first mobile management entity queries the mobile management entity identifier corresponding to the target indication information in the pre-configured target mapping table, wherein the target mapping table contains a correspondence between the indication information and the mobile management entity identifier.
  • Step 560 When the first mobility management entity obtains the mobility management entity identifier corresponding to the target indication information through query, the first mobility management entity uses the obtained mobility management entity identifier as the second identifier of the second mobility management entity; when the mobility management entity identifier corresponding to the target indication information is not obtained through query, the first mobility management entity uses the pre-configured default mobility management entity identifier as the second identifier of the second mobility management entity.
  • the entity identifier is used as the second identifier of the second mobility management entity.
  • Step 570 The first mobility 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 to instruct the target base station to redirect to the second mobility management entity.
  • the redirection method provided in the embodiment of the present application can determine whether redirection is required based on the first identifier and the target identifier pre-configured in the first MME, and further obtain the second identifier of the second MME when the first identifier does not match the target identifier, and assist the target base station in redirecting to the second MME.
  • the redirection process there is no need to obtain the UE usage type. Compared with the method in the related art that can only rely on the UE usage type to achieve redirection, the flexibility can be improved to a certain extent.
  • FIG. 6 is a flow chart of another redirection method provided in the embodiment of the present application. As shown in Figure 6, taking the first identifier as IMSI and the target indication information as TAI as an example, the redirection method provided in the embodiment of the present application may include the following steps.
  • Step 610 configure the IMSI segment (corresponding to the target identifier) whitelist and the second MME identifier (corresponding to the target mapping table) redirected by NAS in the first MME.
  • the IMSI segment whitelist may be an IMSI range list of UEs allowed to access by the first MME. If the IMSI reported by the UE during initial attachment is in the IMSI range list of the first MME, the first MME allows the UE to access, otherwise the NAS redirection process is performed.
  • MMEGI MME Group Identity
  • Step 620 The first MME confirms that the IMSI reported by the UE does not match the IMSI segment whitelist.
  • Step 630 The first MME preferentially selects the second MME based on the TAI reported by the UE. If the selection fails, the default MME is selected as the second MME.
  • the first MME may return redirection indication information carrying the second identifier of the second MME to the target base station, instructing the target base station to send the UE's attach request message to the second MME. 2. MME.
  • the redirection method provided in the embodiment of the present application can quickly determine whether the redirection process needs to be started according to the IMSI reported by the UE, and select a suitable second MME when redirection is required, by pre-configuring the IMSI segment whitelist and the second MME identifier for NAS redirection in the first MME, without obtaining the UE usage type.
  • the second MME can be selected based on the TAI reported by the UE to accurately select the MME that matches the UE, which is conducive to the UE's smooth access to the second MME and improve the redirection success rate.
  • Figure 7-1 is an interactive schematic diagram of a redirection process provided by an embodiment of the present application. As shown in Figure 7-1, taking the first identifier as IMSI and the target indication information as TAI as an example, the redirection interaction process provided by an embodiment of the present application may include the following steps.
  • step 710 the user configures the IMSI segment (corresponding target identifier) whitelist and the MME group identifier (MME Group Identity, MMEGI) (corresponding target mapping table) of the second MME redirected by NAS on the first MME through the network management system.
  • MME Group Identity MMEGI
  • the MMEGI may be an identifier that corresponds to the TAI, or an identifier of a default MME.
  • Step 720 The UE sends an initial attach request message to the eNodeB, where the message carries UE identification information.
  • 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 target indication information).
  • Step 740 The first MME determines whether the UE identification information carried in the initial attach request message is IMSI. If the UE identification information carried in the initial attach request message is not IMSI (corresponding to the first identification), the first MME sends an identity request message to the UE, requesting the UE to report IMSI.
  • Step 750 The UE sends an identity response message to the first MME, which carries the UE IMSI.
  • Step 760 The first MME finds that the IMSI reported by the UE is not in the whitelist.
  • the first MME queries the mapping relationship between the TAI and the IMSI configured in the MME based on the tracking area identifier TAI reported by the UE.
  • the MMEGI of the system is used as the second MME identifier. If the query fails, the default MMEGI is selected as the second MME identifier.
  • Step 770 The first MME returns a redirection indication message to the eNodeB, where the message carries the MMEGI of the redirected second MME.
  • Step 780 The eNodeB sends an initial attach request message to the second MME according to the MMEGI in the redirection indication message.
  • the redirection method provided in the embodiment of the present application can quickly determine whether the redirection process needs to be started according to the IMSI reported by the UE by pre-configuring the IMSI segment whitelist and the second MME identifier for NAS redirection in the first MME, and can select a suitable second MME according to the tracking area identifier reported by the UE when redirection is required, without obtaining the UE usage type.
  • it can improve flexibility to a certain extent.
  • preferentially selecting the second MME based on the TAI reported by the UE can accurately select the MME that matches the UE, which is conducive to the UE's smooth access to the second MME and improves the redirection success rate.
  • Figure 7-1 is only an example provided by the present application and cannot be regarded as a limitation of the present application.
  • the UE identification information carried in the initial attachment request message is 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.
  • the specific interaction process of the redirection process provided in the embodiment of the present application can be shown in reference to Figure 7-2.
  • FIG8 is a structural block diagram of a redirection device provided in an embodiment of the present application.
  • the redirection device 800 provided in an embodiment of the present application includes a receiving module 810 , an acquiring module 820 and a sending module 830 .
  • the receiving module 810 is used to receive an attachment request message of a target base station; the acquiring module 820 is used to acquire a first identifier according to the attachment request message, wherein the first identifier is an identifier of a target user equipment or an identifier of a target user corresponding to the target user equipment; if the first identifier does not match a target identifier pre-configured in the first mobility management entity, the second identifier of the second mobility management entity is acquired; the sending module 830 is used to return the second identifier to the target base station.
  • the redirection indication information is returned, where the redirection indication information carries the second identifier, and the second identifier is used to indicate that the target base station is redirected to the second mobility management entity.
  • the redirection device provided in the embodiment of the present application can determine whether redirection is required based on the first identifier and the target identifier pre-configured in the first MME, and further obtain the second identifier of the second MME when the first identifier does not match the target identifier, and assist the target base station in redirecting to the second MME. There is no need to obtain the UE usage type during the redirection process. Compared with the method in the related art that can only rely on the UE usage type to achieve redirection, the flexibility can be improved to a certain extent.
  • the attachment request message also carries target indication information; in a case where the first identifier does not match the target identifier configured in the first mobile management entity, in the process of obtaining the second identifier of the second mobile management entity, the acquisition module 820 is specifically used to: in a case where the first identifier does not match the target identifier pre-configured in the first mobile management entity, query the mobile management entity identifier corresponding to the target indication information in a pre-configured target mapping table, wherein the target mapping table contains a correspondence between the indication information and the mobile management entity identifier; in a case where the mobile management entity identifier corresponding to the target indication information is obtained through query, the mobile management entity identifier obtained through query is used as the second identifier of the second mobile management entity.
  • the acquisition module 820 is also used to: when the mobile management entity identifier corresponding to the target indication information is not queried, use the pre-configured default mobile management entity identifier as the second identifier of the second mobile management entity.
  • the attachment request message carries a first identifier; in the process of acquiring the first identifier according to the attachment request message, the acquisition module 820 is specifically used to: extract the first identifier from the attachment request message.
  • the acquisition module 820 in the process of acquiring the first identifier according to the attachment request message, is specifically used to: determine the attachment request message whether the first identifier is carried in the attachment request message; if the first identifier is not carried in the attachment request message, sending an identity request message to the target user equipment; receiving an identity response message from the target user equipment, wherein the identity response message carries the first identifier.
  • the first identifier when the first identifier is the identifier of the target user device, the first identifier includes at least one of an international mobile equipment identity code, an international mobile equipment software version identification code, and a universal unique identification code; when the first identifier is the identifier of the target user corresponding to the target user device, the first identifier includes at least one of an international mobile user identity code and a user permanent identification.
  • the target indication information includes any one of a tracking area identifier, a location of the target user equipment, and an international mobile user identity code segment to which the target user equipment belongs.
  • redirection device provided in the embodiment of the present application corresponds to the redirection method mentioned above.
  • the relevant contents can refer to the description of the redirection method above, which will not be repeated here.
  • the embodiment of the present application further provides a mobility management entity 900, and the electronic device may be various types of computers, etc.
  • the mobility management entity 900 includes: a processor 910, a memory 920, and the memory 920 stores programs or instructions, and when the programs or instructions are executed by the processor 910, the steps of any of the methods described above are implemented.
  • the embodiment of the present application further provides a readable storage medium, on which a program or instruction is stored.
  • a program or instruction is stored on which a program or instruction is stored.
  • embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the present invention is a method, device (system), and computer program product according to an embodiment of the present invention.
  • the flowchart and/or block diagram of the product are described. It should be understood that each process and/or box in the flowchart and/or block diagram, as well as the combination of the processes and/or boxes in the flowchart and/or block diagram, can be implemented by computer program instructions.
  • These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate a device for implementing the functions specified in one process or multiple processes in the flowchart and/or one box or multiple boxes in the block diagram.
  • These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.
  • a computing device includes one or more processors (CPU), input/output interfaces, network interfaces, and memory.
  • processors CPU
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • Memory may include non-permanent storage in a computer-readable medium, in the form of random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash memory
  • Computer-readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information.
  • the information can be computer-readable instructions, data structures, program modules or other data.
  • Examples of computer storage media 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, read-only disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.
  • computer-readable media does not include transitory media such as modulated data signals and carrier waves.
  • the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.
  • a computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.

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

本申请公开了一种重定向方法、装置和移动管理实体，属于通信技术领域。所述方法包括：第一移动管理实体接收目标基站的附着请求消息；所述第一移动管理实体根据所述附着请求消息，获取第一标识，所述第一标识为目标用户设备的标识或者所述目标用户设备对应的目标用户的标识；在所述第一标识与所述第一移动管理实体中预先配置的目标标识不匹配的情况下，所述第一移动管理实体获取第二移动管理实体的第二标识；所述第一移动管理实体向所述目标基站返回重定向指示信息，所述重定向指示信息中携带所述第二标识，所述第二标识用于指示所述目标基站重定向至所述第二移动管理实体。

Description

重定向方法、装置和移动管理实体
相关申请的交叉引用
本申请要求在2022年11月14日提交中国专利局、申请号为202211422164.4、发明名称为“重定向方法、装置和移动管理实体”的中国专利申请的优先权，该中国专利申请的全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种重定向方法、装置和移动管理实体。
背景技术
随着通信技术的发展，目前长期演进(Long Term Evolution，LTE)的演进分组系统(Evolved Packet System，EPS)无线网络架构得到了广泛应用。由于，在LTE的EPS无线网络架构中专网移动管理实体(Mobility Management Entity，MME)与公网MME共用基站并且相互隔离，导致基站无法判断用户设备(User Equipment，UE)应该接入专网还是公网，会出现接入错误的情况。因而，在基站接收到UE的注册附着请求后，往往需要利用MME辅助基站进行重定向。
相关技术中通常会基于UE使用类型实现重定向。具体地，基站接收到UE的注册附着请求后，会向第一MME发送UE的相关信息。第一MME进一步从第三方设备(例如签约服务器等)获取UE使用类型，并根据UE使用类型确定UE应接入专网还是公网，从而决定是否发起重定向流程。
然而，相关技术中这种重定向方式必须获取UE使用类型，在无法获取UE使用类型的情况下不能发起重定向流程，导致UE的注册附着请求无法重定向到匹配的MME，严重缺乏灵活性。
发明内容
本申请实施例提供一种重定向方法、装置和移动管理实体，能够解决相关技术中必须基于UE使用类型实现重定向，缺乏灵活性的问题。
第一方面，本申请实施例提供了一种重定向方法，该方法包括：第一移动管理实体接收目标基站的附着请求消息；所述第一移动管理实体根据所述附着请求消息，获取第一标识，所述第一标识为目标用户设备的标识或者所述目标用户设备对应的目标用户的标识；在所述第一标识与所述第一移动管理实体中预先配置的目标标识不匹配的情况下，所述第一移动管理实体获取第二移动管理实体的第二标识；所述第一移动管理实体向所述目标基站返回重定向指示信息，所述重定向指示信息中携带所述第二标识，所述第二标识用于指示所述目标基站重定向至所述第二移动管理实体。
第二方面，本申请实施例提供了一种重定向装置，该装置包括：接收模块，用于接收目标基站的附着请求消息；获取模块，用于根据所述附着请求消息，获取第一标识，所述第一标识为目标用户设备的标识或者所述目标用户设备对应的目标用户的标识；在所述第一标识与第一移动管理实体中预先配置的目标标识不匹配的情况下，获取第二移动管理实体的第二标识；发送模块，用于向所述目标基站返回重定向指示信息，所述重定向指示信息中携带所述第二标识，所述第二标识用于指示所述目标基站重定向至所述第二移动管理实体。
第三方面，本申请实施例提供了一种移动管理实体，该移动管理实体包括处理器和存储器，所述存储器存储程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第四方面，本申请实施例提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤。
第五方面，本申请实施例提供了一种芯片，所述芯片包括处理器和通信 接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法。
第六方面，本申请实施例提供一种计算机程序产品，该程序产品被存储在存储介质中，该程序产品被至少一个处理器执行以实现如第一方面所述的方法。
附图说明
图1是LTE的EPS无线网络架构图；
图2是LTE的一种NAS重定向流程的交互示意图；
图3是本申请实施例提供的一种重定向方法的流程图；
图4是本申请实施例提供的另一种重定向方法的流程图；
图5是本申请实施例提供的另一种重定向方法的流程图；
图6是本申请实施例提供的另一种重定向方法的流程图；
图7-1是本申请实施例提供的一种重定向流程的交互示意图；
图7-2是本申请实施例提供的另一种重定向流程的交互示意图；
图8是本申请实施例提供的一种重定向装置的结构框图；
图9是本申请实施例提供的一种移动管理实体的结构框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描 述的那些以外的顺序实施，且“第一”、“第二”等所区分的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”，一般表示前后关联对象是一种“或”的关系。
第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)的标准化工作组，目前正致力于研究分组交换核心网(Packet Switch Core，PS Core)和全球移动通信系统无线接入网(Universal Mobile Telecommunication System Radio Access Network,UTRAN)的演进。该研究课题称为系统架构演进(System Architecture Evolution，SAE)，目的是使得演进的分组网(Evolved Packet Core，EPC)可提供更高的传输速率，更短的传输延时，优化分组及支持演进的UTRAN(Evolved UTRAN，E-UTRAN)、UTRAN、无线局域网(Wireless Local Area Network，WLAN)及其他非3GPP的接入网络之间的移动性管理。
随着通信技术的发展，基于EPC和E-UTRAN的LTE的演进分组系统(Evolved Packet System，EPS)也得到了广泛应用。图1是LTE的EPS无线网络架构图。如图1所示，LTE网络构架被分为四个部分：UE、E-UTRAN(接入网)、EPC(核心网)和分组数据网(Packet Data Network，PDN)。
其中，E-UTRAN为由多个演进型节点B(Evolved NodeB，eNodeB)组成的接入网，用于为用户的接入提供无线资源。其中，eNodeB为LTE网络中的无线基站。
PDN是为UE提供业务的网络。
EPC提供了更低的传输延迟，并允许更多的无接入系统接入，其网元包括：移动管理实体(Mobility Management Entity，MME)、服务网关(Serving Gateway，SGW)、分组数据网关(PDN Gateway，PGW)、服务通用无线分组业务支持节点(Serving General packet radio service Support Node，SGSN)、策略与计费规则功能实体(Policy and Charging Rules Function，PCRF)、归属 用户服务器(Home Subscriber Server，HSS)。其中，MME是EPC中的核心控制实体，能与eNodeB、SGW、HSS等进行互动，实现例如非接入层(Non Access Stratum，NAS)信令、用户验证及授权、移动性管理等功能。SGW负责UE用户平面数据的传送、转发和路由切换等。PGW是分组数据接口的终接点，与各分组数据网络进行连接。它提供与外部分组数据网络会话的定位功能。PCRF是支持业务数据流检测、策略实施和基于流量计费的功能实体的总称。HSS用于存储LTE网络中用户所有与业务相关的签约数据，提供用户签约信息管理和用户位置管理。
目前，在上述LTE网络架构中，当UE发起初始附着流程的时候，MME基于UE使用类型(UE Usage Type)决定是否发起NAS重定向流程，并在需要发起NAS重定向流程时基于UE使用类型进一步确定与UE匹配的MME。
图2是LTE的一种NAS重定向流程的交互示意图，如图2所示，LTE的重定向流程可以包括如下步骤。
步骤201，UE向eNodeB发起初始附着请求消息。
步骤202，eNodeB向第一MME发送初始附着请求消息。
步骤203，第一MME向第三MME/SGSN发送鉴定请求消息。
步骤204，第三MME/SGSN返回鉴定响应消息给第一MME，在一些情形下，鉴定响应消息中携带UE使用类型。
步骤205，第一MME向UE发送身份请求消息。
步骤206，UE返回身份响应消息给第一MME。
步骤207，在第一MME未从第三MME/SGSN获取到UE使用类型的情况下，第一MME向HSS发送认证信息请求消息。
步骤208，HSS返回认证信息响应消息给第一MME，其中，认证信息响应消息中携带UE使用类型。
步骤209，第一MME基于UE使用类型确定是否需要启动重定向流程，在需要启动重定向流程时，基于UE使用类型确定第二MME。
步骤210，第一MME向eNodeB发送重定向指示消息，其中，重定向指示消息中携带第二MME标识。
步骤211，eNodeB向第二MME发送初始附着请求消息。
根据图2所示流程可以发现NAS消息从第一MME重定向到第二MME时，需要从第三MME/SGSN或HSS获取UE使用类型(UE Usage Type)，根据UE使用类型决定是否发起NAS重定向流程。在无法获取UE使用类型时，第一MME不能发起NAS重定向流程，导致UE无法接入匹配的第二MME。
有鉴于此，本申请中创造性地提出了一种重定向方法，可以在不使用UE使用类型的情况下实现重定向。
下面结合附图，通过具体的实施例及其应用场景对本申请实施例提供的重定向方法进行详细地说明。
图3是本申请实施例提供的一种重定向方法的流程图。如图3所示，本申请实施例提供的重定向方法可以包括如下步骤。
步骤310，第一移动管理实体接收目标基站的附着请求消息。
第一MME可以为目标基站根据网络拓扑为目标UE确定的一个MME。
附着请求消息可以为目标基站向第一MME转发的目标UE的附着请求消息。其中，附着请求消息中可以携带目标UE以及目标基站的相关信息。
在目标UE向目标基站发送附着请求后，第一MME可以接收到目标基站发送的附着请求消息。
可以理解的是，对于已经与运营商签订入网协议的合法UE，UE在每次开机或者从网络覆盖盲区返回到网络覆盖区等情形下，需要完成注册附着到网络的流程，这样UE才可以通过网络正常使用已开通的业务。在此过程中，目标UE可以向目标基站发送附着请求，基于附着请求接入核心网。从而第一MME可以接收目标基站转发的附着请求消息。
步骤320，所述第一移动管理实体根据所述附着请求消息，获取第一标识，所述第一标识为目标用户设备的标识或者所述目标用户设备对应的目标 用户的标识。
附着请求消息中可以包括第一标识或不包括第一标识。根据附着请求消息，获取第一标识可以包括：在附着请求消息中包括第一标识的情况下，直接从附着请求消息中获取第一标识，或者，在附着请求消息中不包括第一标识的情况下，向目标UE/HSS发送第一标识获取请求，接收目标UE/HSS返回的第一标识。
目标UE的标识可以包括：国际移动设备识别码(International Mobile Equipment Identity，IMEI)、国际移动设备的软件版本识别码(IMEI software version，IMEISV)、通用唯一识别码(Universally Unique Identifier，UUID)中的至少一者。目标UE对应的目标用户的标识可以包括：国际移动用户识别码(International Mobile Subscriber Identity，IMSI)、用户永久标识(Subscription Permanent Identifier，SUPI)中的至少一者。
步骤330，在所述第一标识与所述第一移动管理实体中预先配置的目标标识不匹配的情况下，所述第一移动管理实体获取第二移动管理实体的第二标识。
在本申请实施例中，第二MME可以为第一MME根据附着请求消息确定的目标UE可以接入的MME。目标标识可以包括至少一个UE的标识或者UE对应的用户的标识。预先配置的目标标识可以以白名单的形式存储在第一MME中。其中，目标标识与第一标识的属性可以相同，举例而言，若第一标识为IMEI，则目标标识可以为至少一个IMEI，若第一标识为IMSI等，则目标标识可以为至少一个IMSI。白名单可以为第一MME允许接入的目标UE的第一标识范围列表。以第一标识为IMEI为例，预先配置的目标标识中可以包括大量第一MME允许接入的UE对应的IMEI。换言之，可以在第一UE中预先配置IMEI段白名单，其中，白名单中可以包含大量目标标识，每一个目标标识对应一个IMEI。以第一标识为IMSI为例，预先配置的目标标识中可以包括大量第一MME允许接入的UE对应的IMSI。换言之，可以在 第一UE中预先配置IMSI段白名单，其中，白名单中可以包含大量目标标识，每一个目标标识对应一个IMSI。可以理解的是，对于其他第一标识(例如IMEISV、SUPI等)，目标标识的配置方式可以参照上文描述，仅需将配置过程中的IMEI或IMSI整体替换为其他第一标识即可，为避免重复，不一一列举。
第一标识与目标标识不匹配可以表示在目标标识中无法查找到第一标识。第一标识与目标标识匹配可以表示在目标标识中可以查找到第一标识。
在不匹配的情况下，第一MME可以启动重定向流程，获取第二MME的第二标识。在匹配的情况下，则目标UE可以直接接入第一MME，无需重定向。
步骤340，所述第一移动管理实体向所述目标基站返回重定向指示信息，所述重定向指示信息中携带所述第二标识，所述第二标识用于指示所述目标基站重定向至所述第二移动管理实体。
第一MME获取第二MME的第二标识后，可以向目标基站发送携带第二MME的重定向指示信息，指示目标基站将附着请求消息发送给第二MME。从而目标UE的附着请求消息可以重定向至第二MME。第二MME接收目标UE的附着请求消息后，也可以继续判断目标UE能否直接接入，在不能接入的情况下，再次启动重定向流程。
本申请实施例提供的重定向方法，第一移动管理实体接收目标基站的附着请求消息；所述第一移动管理实体根据所述附着请求消息，获取第一标识，所述第一标识为目标用户设备的标识或者所述目标用户设备对应的目标用户的标识；在所述第一标识与所述第一移动管理实体中预先配置的目标标识不匹配的情况下，所述第一移动管理实体获取第二移动管理实体的第二标识；所述第一移动管理实体向所述目标基站返回重定向指示信息，所述重定向指示信息中携带所述第二标识，所述第二标识用于指示所述目标基站重定向至所述第二移动管理实体。如此，可以根据第一标识和第一MME中预先配置 的目标标识确定是否需要重定向，并在第一标识与目标标识不匹配的情况下进一步获取第二MME的第二标识，辅助目标基站重定向至第二MME，在重定向过程中无需获取UE使用类型，相较于相关技术中仅能依靠UE使用类型实现重定向的方法，可以在一定程度上提高灵活性。
另外，本申请实施例提供的重定向方法，去除了获取UE使用类型的步骤，使得第一MME无需通过多次信令交互从其他设备(例如HSS)获取UE使用类型，可以简化流程、缩短延时，提升第一MME的处理性能。同时，由于重定向过程中并未使用到UE使用类型，因而可以不在HSS签约UE使用类型，能够减少HSS存储的签约数据，释放存储空间。
如上文所论述，本申请实施例中的附着请求消息可携带第一标识或不携带第一标识。下面针对附着请求消息携带第一标识的情形和附着请求消息未携带第一标识的情形分别进行论述。
在本申请的一个实施例中，所述附着请求消息携带第一标识。在此情况下，步骤320所述第一移动管理实体根据所述附着请求消息，获取第一标识可以包括：所述第一移动管理实体从所述附着请求消息中提取所述第一标识。如此，可以快速获取第一标识，便于与目标标识进行比对，确定是否需要重定向，能够在一定程度上缩短重定向时间，提高效率。
在本申请的另一个实施例中，步骤320所述第一移动管理实体根据所述附着请求消息，获取第一标识可以包括：所述第一移动管理实体确定所述附着请求消息中是否携带所述第一标识；在所述附着请求消息中未携带所述第一标识的情况下，所述第一移动管理实体向所述目标用户设备发送身份请求消息；所述第一移动管理实体接收来自所述目标用户设备的身份响应消息，所述身份响应消息中携带所述第一标识。如此，在附着请求消息中未携带第一标识的情况下，第一MME可以主动向目标UE发送身份请求消息，基于身份请求消息获取第一标识信息，并进一步根据第一标识确定是否需要重定向，能够在不使用UE使用类型的情况下，辅助UE重定向。
在附着请求消息中未携带第一标识的情况下，第一MME可以向目标UE发送身份请求消息，请求目标UE上报第一标识。之后，第一MME可以接收来自目标UE的携带第一标识的身份响应信息，从身份响应信息中提取第一标识。
图4是本申请实施例提供的另一种重定向方法的流程图。如图4所示，本申请实施例提供的重定向方法可以包括如下步骤。
步骤410，第一移动管理实体接收目标基站的附着请求消息；其中，所述附着请求消息中携带目标指示信息。
所述目标指示信息可以包括跟踪区标识(Tracking Area identity，TAI)、目标UE的位置、目标UE所属的IMSI段中的任一者。
在目标指示信息为TAI或目标UE的位置的情况下，目标基站可以接收目标UE的附着请求，添加TAI或目标UE的位置，将携带有TAI或目标UE的位置的附着请求消息发送给第一MME。在目标指示信息为目标UE所属的IMSI段的情况下，目标UE可以先上报其IMSI段，即向目标基站发送携带其IMSI段的附着请求。再由目标基站将携带有目标UE所属的IMSI段的附着请求消息发送给第一MME。通过上述方式，第一MME可以接收目标基站的携带有目标指示信息的附着请求消息。
步骤420，所述第一移动管理实体根据所述附着请求消息，获取第一标识，所述第一标识为目标用户设备的标识或者所述目标用户设备对应的目标用户的标识。
步骤430，在所述第一标识与所述第一移动管理实体中预先配置的目标标识不匹配的情况下，所述第一移动管理实体在预先配置的目标映射表中查询与所述目标指示信息对应的移动管理实体标识，其中，所述目标映射表中存在指示信息与移动管理实体标识之间的对应关系。
在本申请实施例中，目标映射表可以用于存储指示信息与MME标识之间的对应关系。其中，目标映射表中MME标识与指示信息可以是一对多对 应关系或一对一对应关系。一对多对应关系可以表示一个MME标识可以对应多个指示信息，而一个指示信息有且仅有唯一与之对应的MME标识。一对一对应关系可以表示一个MME标识对应一个指示信息，且一个指示信息对应一个MME标识。其中，指示信息与MME标识之间的对应关系可以根据运营商划分的MME的类型或管理范围确定，一个指示信息与一个MME标识存在对应关系，则说明该MME可以用于管理此指示信息对应的目标UE。
以目标指示信息为跟踪区标识为例，根据任意一个跟踪区标识可以确定用于管理该区域的UE的MME的标识，在确定跟踪区标识与MME标识的对应关系之后，可以将跟踪区标识与MME标识的对应关系配置在目标映射表中。针对其他类型的目标指示信息(例如位置或IMSI段)，目标映射表的配置方式类似，仅需将上文所描述的配置过程中的跟踪区标识整体替换为其他目标指示信息即可，为避免重复，不一一介绍。
第一MME在预先配置的目标映射表中查询与目标指示信息对应的MME标识可以包括：第一MME以目标指示信息为索引，在目标映射表中查找与目标指示信息存在对应关系的MME标识。
步骤440，所述第一移动管理实体在查询得到与所述目标指示信息对应的移动管理实体标识的情况下，将查询得到的所述移动管理实体标识作为第二移动管理实体的第二标识。
查询得到可以表示目标映射表中存在目标指示信息以及与目标指示信息存在对应关系的MME标识。
步骤450，所述第一移动管理实体向所述目标基站返回重定向指示信息，所述重定向指示信息中携带所述第二标识，所述第二标识用于指示所述目标基站重定向至所述第二移动管理实体。
目标基站接收重定向指示信息后，可以将目标UE的附着请求消息发送给第二MME。从而，第二MME可以接收附着请求消息，并进一步判断目标UE能否直接接入。由于第二MME根据指示信息与MME之间的对应关系确 定，选取的第二MME与目标UE存在密切关联，因而，在本申请实施例中，目标基站一般可以直接接入第二MME。
本申请实施例提供的重定向方法，通过在第一MME中预先配置用于存储指示信息与MME标识之间的对应关系的目标映射表，并利用目标映射表查询与目标UE的目标指示信息对应的第二MME，能够准确确定用于管理目标UE的第二MME，进而有利于目标UE顺利接入第二MME，可以在一定程度上提高重定向成功率。
由于，目标映射表中未必包含所有指示信息与MME标识之间的对应关系。进而，本申请中进一步介绍了可以获取第二MME的第二标识的其他方法。在本申请的一个实施例中，在所述第一标识与所述第一移动管理实体中配置的目标标识不匹配的情况下，所述第一移动管理实体获取第二移动管理实体的第二标识，本申请实施例提供的重定向方法还包括：所述第一移动管理实体在未查询得到与所述目标指示信息对应的移动管理实体标识的情况下，所述第一移动管理实体将预先配置的默认移动管理实体标识作为所述第二移动管理实体的第二标识。如此，可以在目标映射表中信息不全面的情况下，直接将默认MME确定为第二MME，进一步提高重定向灵活性。
未查询得到可以表示目标映射表中不存在目标指示信息，更不存在与目标指示信息存在对应关系的MME标识。
默认MME标识也可以为按照运营商划分规则确定的MME标识。
第一MME在未查询得到与目标指示信息对应的MME标识的情况下，可以直接将默认MME标识确定为第二标识。
第一MME将默认MME确定为第二MME后，可以向目标基站返回携带有默认MME标识的重定向指示信息。目标基站接收重定向指示信息后，可以将目标UE的附着请求消息发送给默认MME。从而，默认MME可以接收附着请求消息，并进一步判断目标UE能否直接接入，在不能接入的情况下，重新启动重定向流程。
图5是本申请实施例提供的另一种重定向方法的流程图。如图5所示，本申请实施例提供的重定向方法可以包括如下步骤。
步骤510，第一移动管理实体接收目标基站的附着请求消息；其中，所述附着请求消息中携带目标指示信息。
其中，所述目标指示信息包括跟踪区标识、所述目标用户设备的位置、所述目标用户设备所属的国际移动用户识别码区段中的任一者。
步骤520，所述第一移动管理实体确定所述附着请求消息中是否携带所述第一标识。
其中，在第一标识为目标用户设备的标识的情况下，第一标识可以包括国际移动设备识别码、国际移动设备的软件版本识别码、通用唯一识别码中的至少一者。在第一标识为目标用户设备对应的目标用户的标识的情况下，第一标识可以包括国际移动用户识别码、用户永久标识中的至少一者。
步骤530，在所述附着请求消息中未携带所述第一标识的情况下，所述第一移动管理实体向所述目标用户设备发送身份请求消息。
步骤540，所述第一移动管理实体接收来自所述目标用户设备的身份响应消息，所述身份响应消息中携带所述第一标识。
当然，在附着请求消息中携带第一标识的情况下，可以不执行步骤530和步骤540，直接执行后续步骤。
步骤550，在所述第一标识与所述第一移动管理实体中预先配置的目标标识不匹配的情况下，所述第一移动管理实体在预先配置的目标映射表中查询与所述目标指示信息对应的移动管理实体标识，其中，所述目标映射表中存在指示信息与移动管理实体标识之间的对应关系。
步骤560，所述第一移动管理实体在查询得到与所述目标指示信息对应的移动管理实体标识的情况下，将查询得到的所述移动管理实体标识作为第二移动管理实体的第二标识；在未查询得到与所述目标指示信息对应的移动管理实体标识的情况下，所述第一移动管理实体将预先配置的默认移动管理 实体标识作为所述第二移动管理实体的第二标识。
步骤570，所述第一移动管理实体向所述目标基站返回重定向指示信息，所述重定向指示信息中携带所述第二标识，所述第二标识用于指示所述目标基站重定向至所述第二移动管理实体。
本申请实施例提供的重定向方法，可以根据第一标识和第一MME中预先配置的目标标识确定是否需要重定向，并在第一标识与目标标识不匹配的情况下进一步获取第二MME的第二标识，辅助目标基站重定向至第二MME，在重定向过程中无需获取UE使用类型，相较于相关技术中仅能依靠UE使用类型实现重定向的方法，可以在一定程度上提高灵活性。
为便于理解，后文进一步结合具体第一标识和目标指示信息对本申请实施例提出的重定向方法进行详细介绍。图6是本申请实施例提供的另一种重定向方法的流程图。如图6所示，以第一标识为IMSI、目标指示信息为TAI为例，本申请实施例提供的重定向方法可以包括如下步骤。
步骤610，在第一MME中配置IMSI段(对应于目标标识)白名单以及NAS重定向的第二MME标识(对应于目标映射表)。
在本申请实施例中，IMSI段白名单可以为第一MME允许接入的UE的IMSI范围列表。若UE初始附着时上报的IMSI在第一MME的IMSI范围列表中，则第一MME允许UE接入，否则进行NAS重定向流程。
NAS重定向的第二MME标识为MME群组标识(MME Group Identity，MMEGI)，且有两种配置方式，包括1、与跟踪区标识唯一映射的MMEGI，2、唯一默认的MMEGI。
步骤620，第一MME确认UE上报的IMSI与IMSI段白名单不匹配。
步骤630，第一MME优先基于UE上报的TAI选择第二MME，若选择失败，选择默认MME为第二MME。
在确定第二MME后，第一MME可以向目标基站返回携带第二MME的第二标识重定向指示信息，指示目标基站将UE的附着请求消息发送给第 二MME。
本申请实施例提供的重定向方法，通过在第一MME中预先配置IMSI段白名单以及NAS重定向的第二MME标识，可以快速实现根据UE上报的IMSI确定是否需要启动重定向流程，并在需要重定向时选取合适的第二MME，无需获取UE使用类型，相较于相关技术中仅能依靠UE使用类型实现重定向的方法，可以在一定程度上提高灵活性。同时，优先基于UE上报的TAI选择第二MME可以准确选取与UE匹配的MME，进而有利于UE顺利接入第二MME，提高重定向成功率。
图7-1是本申请实施例提供的一种重定向流程的交互示意图。如图7-1所示，以第一标识为IMSI、目标指示信息为TAI为例，本申请实施例提供的重定向交互流程可以包括如下步骤。
步骤710，用户通过网管系统，在第一MME上配置IMSI段(对应目标标识)白名单和NAS重定向的第二MME的MME群组标识(MME Group Identity，MMEGI)(对应目标映射表)。
其中，MMEGI可以为与TAI存在对应关系的标识，或默认的MME的标识。
步骤720，UE向eNodeB发起初始附着请求消息，消息中携带UE标识信息。
步骤730，eNodeB向第一MME发送初始附着请求消息，消息中携带UE标识信息和跟踪区标识(对应目标指示信息)。
步骤740，第一MME确定初始附着请求消息中携带的UE标识信息是否为IMSI。若初始附着请求消息中携带的UE标识信息不是IMSI(对应第一标识)，第一MME发送身份请求消息给UE，请求UE上报IMSI。
步骤750，UE向第一MME发送身份响应消息，消息中携带UE IMSI。
步骤760，第一MME发现UE上报的IMSI不在白名单中，第一MME基于UE上报的跟踪区标识TAI，查询本MME中配置的与TAI存在映射关 系的MMEGI作为第二MME标识，若查询失败，则选择默认MMEGI作为第二MME标识。
步骤770，第一MME向eNodeB返回重定向指示消息，消息中携带重定向的第二MME的MMEGI。
步骤780，eNodeB根据重定向指示消息中的MMEGI向第二MME发送初始附着请求消息。
本申请实施例提供的重定向方法，通过在第一MME中预先配置IMSI段白名单以及NAS重定向的第二MME标识，可以快速实现根据UE上报的IMSI确定是否需要启动重定向流程，并且可以在需要重定向时根据UE上报的跟踪区标识选取合适的第二MME，无需获取UE使用类型，相较于相关技术中仅能依靠UE使用类型实现重定向的方法，可以在一定程度上提高灵活性。同时，优先基于UE上报的TAI选择第二MME可以准确选取与UE匹配的MME，进而有利于UE顺利接入第二MME，提高重定向成功率。
另外，需要强调的是，图7-1仅是本申请提供的一种示例，不能视为对本申请的限制。实际上，若初始附着请求消息中携带的UE标识信息是IMSI，则第一MME无需向UE发送身份请求，UE也无须再次向第一MME上报IMSI。在初始附着请求消息中携带UE的IMSI的情况下，本申请实施例提供的重定向流程的具体交互过程可以参照图7-2所示。
图8是本申请实施例提供的一种重定向装置的结构框图。如图8所示，本申请实施例提供的重定向装置800包括接收模块810、获取模块820和发送模块830。
其中，所述接收模块810，用于接收目标基站的附着请求消息；所述获取模块820，用于根据所述附着请求消息，获取第一标识，所述第一标识为目标用户设备的标识或者所述目标用户设备对应的目标用户的标识；在所述第一标识与第一移动管理实体中预先配置的目标标识不匹配的情况下，获取第二移动管理实体的第二标识；所述发送模块830，用于向所述目标基站返 回重定向指示信息，所述重定向指示信息中携带所述第二标识，所述第二标识用于指示所述目标基站重定向至所述第二移动管理实体。
本申请实施例提供的重定向装置，可以根据第一标识和第一MME中预先配置的目标标识确定是否需要重定向，并在第一标识与目标标识不匹配的情况下进一步获取第二MME的第二标识，辅助目标基站重定向至第二MME，在重定向过程中无需获取UE使用类型，相较于相关技术中仅能依靠UE使用类型实现重定向的方法，可以在一定程度上提高灵活性。
可选地，在本申请的一个实施例中，所述附着请求消息中还携带目标指示信息；在所述第一标识与所述第一移动管理实体中配置的目标标识不匹配的情况下，在获取第二移动管理实体的第二标识的过程中，所述获取模块820具体用于：在所述第一标识与所述第一移动管理实体中预先配置的目标标识不匹配的情况下，在预先配置的目标映射表中查询与所述目标指示信息对应的移动管理实体标识，其中，所述目标映射表中存在指示信息与移动管理实体标识之间的对应关系；在查询得到与所述目标指示信息对应的移动管理实体标识的情况下，将查询得到的所述移动管理实体标识作为第二移动管理实体的第二标识。
可选地，在本申请的一个实施例中，在所述第一标识与所述第一移动管理实体中配置的目标标识不匹配的情况下，在获取第二移动管理实体的第二标识的过程中，所述获取模块820还用于：在未查询得到与所述目标指示信息对应的移动管理实体标识的情况下，将预先配置的默认移动管理实体标识作为所述第二移动管理实体的第二标识。
可选地，在本申请的一个实施例中，所述附着请求消息携带第一标识；在所述根据所述附着请求消息，获取第一标识的过程中，所述获取模块820具体用于：从所述附着请求消息中提取所述第一标识。
可选地，在本申请的一个实施例中，在所述根据所述附着请求消息，获取第一标识的过程中，所述获取模块820具体用于：确定所述附着请求消息 中是否携带所述第一标识；在所述附着请求消息中未携带所述第一标识的情况下，向所述目标用户设备发送身份请求消息；接收来自所述目标用户设备的身份响应消息，所述身份响应消息中携带所述第一标识。
可选地，在本申请的一个实施例中，在所述第一标识为目标用户设备的标识的情况下，所述第一标识包括国际移动设备识别码、国际移动设备的软件版本识别码、通用唯一识别码中的至少一者；在所述第一标识为目标用户设备对应的目标用户的标识的情况下，所述第一标识包括国际移动用户识别码、用户永久标识中的至少一者。
可选地，在本申请的一个实施例中，所述目标指示信息包括跟踪区标识、所述目标用户设备的位置、所述目标用户设备所属的国际移动用户识别码区段中的任一者。
需要说明的是，本申请实施例提供的重定向装置与上文提到的重定向方法相对应。相关内容可参照上文对重定向方法的描述，在此不做赘述。
此外，如图9所示，本申请实施例还提供一种移动管理实体900，所述电子设备可以为各种类型的计算机等。所述移动管理实体900包括：处理器910，存储器920，所述存储器920上存储程序或指令，所述程序或指令被所述处理器910执行时实现上文所描述的任一种方法的步骤。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被所述处理器910执行时实施上文所描述的任一种方法的步骤。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产 品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器 (CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本领域技术人员应明白，本申请的实施例可提供为方法、系统或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
以上所述仅为本申请的实施例而已，并不用于限制本申请。对于本领域技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本申请的权利要求范围之内。

Claims (10)

  1. 一种重定向方法，包括：
    第一移动管理实体接收目标基站的附着请求消息；
    所述第一移动管理实体根据所述附着请求消息，获取第一标识，所述第一标识为目标用户设备的标识或者所述目标用户设备对应的目标用户的标识；
    在所述第一标识与所述第一移动管理实体中预先配置的目标标识不匹配的情况下，所述第一移动管理实体获取第二移动管理实体的第二标识；
    所述第一移动管理实体向所述目标基站返回重定向指示信息，所述重定向指示信息中携带所述第二标识，所述第二标识用于指示所述目标基站重定向至所述第二移动管理实体。
  2. 根据权利要求1所述的方法，其中，所述附着请求消息中还携带目标指示信息；
    在所述第一标识与所述第一移动管理实体中配置的目标标识不匹配的情况下，所述第一移动管理实体获取第二移动管理实体的第二标识，包括：
    在所述第一标识与所述第一移动管理实体中预先配置的目标标识不匹配的情况下，所述第一移动管理实体在预先配置的目标映射表中查询与所述目标指示信息对应的移动管理实体标识，其中，所述目标映射表中存在指示信息与移动管理实体标识之间的对应关系；
    所述第一移动管理实体在查询得到与所述目标指示信息对应的移动管理实体标识的情况下，将查询得到的所述移动管理实体标识作为第二移动管理实体的第二标识。
  3. 根据权利要求2所述的方法，其中，在所述第一标识与所述第一移动管理实体中配置的目标标识不匹配的情况下，所述第一移动管理实体获取第二移动管理实体的第二标识，还包括：
    所述第一移动管理实体在未查询得到与所述目标指示信息对应的移动管理实体标识的情况下，所述第一移动管理实体将预先配置的默认移动管理实 体标识作为所述第二移动管理实体的第二标识。
  4. 根据权利要求1-3任一项所述的方法，其中，所述附着请求消息携带第一标识；
    所述第一移动管理实体根据所述附着请求消息，获取第一标识包括：所述第一移动管理实体从所述附着请求消息中提取所述第一标识。
  5. 根据权利要求1-3任一项所述的方法，其中，所述第一移动管理实体根据所述附着请求消息，获取第一标识包括：
    所述第一移动管理实体确定所述附着请求消息中是否携带所述第一标识；
    在所述附着请求消息中未携带所述第一标识的情况下，所述第一移动管理实体向所述目标用户设备发送身份请求消息；
    所述第一移动管理实体接收来自所述目标用户设备的身份响应消息，所述身份响应消息中携带所述第一标识。
  6. 根据权利要求4或5所述的方法，其中，在所述第一标识为目标用户设备的标识的情况下，所述第一标识包括国际移动设备识别码、国际移动设备的软件版本识别码、通用唯一识别码中的至少一者；
    在所述第一标识为目标用户设备对应的目标用户的标识的情况下，所述第一标识包括国际移动用户识别码、用户永久标识中的至少一者。
  7. 根据权利要求2或3所述的方法，其中，所述目标指示信息包括跟踪区标识、所述目标用户设备的位置、所述目标用户设备所属的国际移动用户识别码区段中的任一者。
  8. 一种重定向装置，其中，包括：
    接收模块，用于接收目标基站的附着请求消息；
    获取模块，用于根据所述附着请求消息，获取第一标识，所述第一标识为目标用户设备的标识或者所述目标用户设备对应的目标用户的标识；在所述第一标识与第一移动管理实体中预先配置的目标标识不匹配的情况下，获取第二移动管理实体的第二标识；
    发送模块，用于向所述目标基站返回重定向指示信息，所述重定向指示信息中携带所述第二标识，所述第二标识用于指示所述目标基站重定向至所述第二移动管理实体。
  9. 一种移动管理实体，其中，包括处理器和存储器，所述存储器存储程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1-7任一项所述的方法的步骤。
  10. 一种可读存储介质，其中，所述可读存储介质上存储程序或指令，所述程序或指令被执行时实现如权利要求1-7任一项所述的方法的步骤。
PCT/CN2023/126457 2022-11-14 2023-10-25 重定向方法、装置和移动管理实体 WO2024104065A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211422164.4 2022-11-14
CN202211422164.4A CN118042561A (zh) 2022-11-14 2022-11-14 重定向方法、装置和移动管理实体

Publications (1)

Publication Number Publication Date
WO2024104065A1 true WO2024104065A1 (zh) 2024-05-23

Family

ID=90991863

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/126457 WO2024104065A1 (zh) 2022-11-14 2023-10-25 重定向方法、装置和移动管理实体

Country Status (2)

Country Link
CN (1) CN118042561A (zh)
WO (1) WO2024104065A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160066219A1 (en) * 2013-04-16 2016-03-03 Nokia Solutions And Networks Oy Mobility management entity (mme) triggered detach and re-attach to a specific target mme
CN107645722A (zh) * 2016-07-20 2018-01-30 中国电信股份有限公司 专用网络选择接入方法和系统、公网mme、hss 和基站
CN111132256A (zh) * 2018-10-31 2020-05-08 华为技术有限公司 用户终端接入方法、初始移动管理实体及基站
CN112637841A (zh) * 2019-09-23 2021-04-09 普天信息技术有限公司 一种电力无线专网的国际移动设备标识检验方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160066219A1 (en) * 2013-04-16 2016-03-03 Nokia Solutions And Networks Oy Mobility management entity (mme) triggered detach and re-attach to a specific target mme
CN107645722A (zh) * 2016-07-20 2018-01-30 中国电信股份有限公司 专用网络选择接入方法和系统、公网mme、hss 和基站
CN111132256A (zh) * 2018-10-31 2020-05-08 华为技术有限公司 用户终端接入方法、初始移动管理实体及基站
CN112637841A (zh) * 2019-09-23 2021-04-09 普天信息技术有限公司 一种电力无线专网的国际移动设备标识检验方法和系统

Also Published As

Publication number Publication date
CN118042561A (zh) 2024-05-14

Similar Documents

Publication Publication Date Title
KR102442911B1 (ko) 네트워크 슬라이스 식별자의 선택
US12063550B2 (en) Multiple access policy control
CN109167847B (zh) 一种IPv6地址的生成方法及SMF、通信系统
US9967751B2 (en) Mobile network-based tenant network service implementation method, system, and network element
US20230308999A1 (en) Interception aware access node selection
EP3713300B1 (en) Network function database, mobile communication network component, method for selecting a network function and method for registering a network function
CN105357180B (zh) 网络系统、攻击报文的拦截方法、装置和设备
EP4106372A1 (en) Subscription data update method and apparatus, node, and storage medium
CN105828413A (zh) 一种d2d模式b发现的安全方法、终端和系统
WO2016180113A1 (zh) WiFi语音业务发起的方法、LTE通信设备、终端及通信系统
US20220210702A1 (en) Communication Method and Apparatus
US11076321B2 (en) Selecting 5G non-standalone architecture capable MME during registration and handover
CN110324807B (zh) 一种信息处理方法、功能和计算机可读存储介质
CN104125622B (zh) 一种接入制式的配置方法、设备及系统
WO2024104065A1 (zh) 重定向方法、装置和移动管理实体
WO2023040995A1 (zh) 通信方法和通信设备
CN106341851B (zh) 一种用于为指定终端建立专有承载的方法
WO2022077246A1 (en) System and methods for identifying edge application server
WO2017097060A1 (zh) Lte网络中的消息路由方法、系统和网关
KR20130060967A (ko) ＬＴＥ 가입자 Ｍｕｌｔｉｐｌｅ ＰＤＮ 기반 ＯＤＢ 적용을 통한 데이터서비스 방법
WO2012089030A1 (zh) 一种多种接入方式接入网络的方法、接入设备和认证设备
JP2022528409A (ja) セッション管理ネットワーク要素を選択するための方法および装置
EP3226482B1 (en) Method and apparatus for determining gateway information
US9843553B2 (en) Method and device for sending message
CN106686756B (zh) 一种基于位置的pcc会话建立方法及系统

Legal Events

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

Ref document number: 23890501

Country of ref document: EP

Kind code of ref document: A1