WO2023143111A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2023143111A1
WO2023143111A1 PCT/CN2023/072021 CN2023072021W WO2023143111A1 WO 2023143111 A1 WO2023143111 A1 WO 2023143111A1 CN 2023072021 W CN2023072021 W CN 2023072021W WO 2023143111 A1 WO2023143111 A1 WO 2023143111A1
Authority
WO
WIPO (PCT)
Prior art keywords
management entity
access
user
connection
mobility management
Prior art date
Application number
PCT/CN2023/072021
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 WO2023143111A1 publication Critical patent/WO2023143111A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer

Definitions

  • the embodiments of the present application relate to the field of communication technologies, and in particular, to a communication method and device.
  • access management functions and mobility management functions are usually provided by an access and mobility management entity.
  • the access and mobility management entity can provide the network with access management functions such as access authentication and access authorization, and can also provide users with mobility management functions such as session management signaling channels.
  • the processing object of access management is the network access capability, focusing on the connection between the location of the terminal device and the access network (AN).
  • AN access network
  • the embodiments of the present application provide a communication method and device, which are conducive to satisfying requirements for independent establishment, independent control, and independent evolution of access management and mobility management.
  • the embodiment of the present application provides a communication method, the method includes: an access network device sends a first connection request message to an access management entity, the first connection request message includes user access information, and is used to request to establish an connection The connection between the network access device and the mobility management entity; the access management entity receives the first connection request message, and based on the first connection request message, sends the second connection request message to the mobility management entity, and the second connection request message is used to request Establish a connection between the access management entity and the mobility management entity, wherein the mobility management entity is determined by the access management entity according to user access information; the mobility management entity receives the second connection request message, and sends the second connection request message to the access management entity A connection response message, where the second connection response message is used to indicate the connection information between the access management entity and the mobility management entity; the access management entity receives the second connection response message, and sends the first connection response message to the access network device, The first connection response message is used to indicate connection information between the access network device and the access management entity; the access network
  • the functions of access management and mobility management can be implemented by the access management entity and the mobility management entity respectively, and the access management and mobility management can be decoupled.
  • One access management entity can correspond to multiple user networks. Different user networks can no longer share the mobility management entity, which is conducive to meeting the requirements of independent establishment, independent control and independent evolution of access management and mobility management, and meeting the differentiated capacity planning of access management and mobility management. , deployment location, and availability requirements.
  • the first connection request message further includes the access network connection identifier of the access network device, and the second connection request message includes the access management connection identifier of the access management entity; the access management entity and the mobility management
  • the connection information between entities includes the association relationship between the access management connection identifier and the mobility management connection identifier of the mobility management entity; the connection information between the access network device and the access management entity includes the access management connection identifier and the access network connection Identified relationship.
  • the Connections are established between management entities to enable terminal devices to connect to mobility management entities through access network equipment, meeting the communication requirements between terminal devices and user networks.
  • the user access information includes user identification and user network information
  • the access management entity sends the second connection request message to the mobility management entity based on the first connection request message, including: the access management entity sends the second connection request message to the mobility management entity according to The user ID and the user network information determine that the mobility management entity associated with the user ID and supporting the user network is the mobility management entity that receives the second connection request message.
  • the access management entity may query the mobility management entity associated with the user identifier and supporting the user network through the user context addressing entity according to the information of the user identifier and the user network, as the mobility management entity receiving the second connection request message entity.
  • the mobile management entity that the terminal device has been connected to and supports the user network can be queried through the user context according to the user ID and user network information, which is conducive to the accurate and fast access of the terminal device to the required user network.
  • the user access information includes user network information
  • the access management entity sends the second connection request message to the mobility management entity based on the first connection request message, including: the access management entity information to determine a list of mobility management entities supporting the user network; the access management entity determines a mobility management entity in the mobility management entity list as the mobility management entity that receives the second connection request message.
  • the access management entity may send a user network addressing request message to the user network addressing entity, and the user network addressing request message includes user network information; receive a user network addressing response from the user network addressing entity
  • the message, the user network addressing reply message includes a list of MMEs supporting the user network; and determining a MME in the list of MMEs as the MME receiving the second connection request message.
  • the information of the user network it is possible to query whether there is a user network that can provide services for the user in the created user network, which is beneficial for the terminal device to quickly access the required user network and reduce the resource overhead of the user network.
  • the first connection response message is also used to indicate the connection relationship between the access network device and the mobility management entity.
  • the second connection request message also includes the connection The network access connection identifier
  • the first connection response message also includes an association relationship between the access network connection identifier and the mobility management connection identifier.
  • the access network device and the mobility management entity can establish a connection between the access network device and the mobility management entity through the association between the access network connection identifier and the mobility management connection identifier , enabling the terminal device to connect to the mobility management entity through the access network device, so as to meet the communication requirements between the terminal device and the user network.
  • the method further includes: the mobility management entity sends a first paging request message to the access management entity, where the first paging request message includes the user identifier of the terminal device and information about the user network; the access management entity The entity receives the first paging request message, and forwards the first paging request message to the access network device; the access network device is also used to receive the first paging request message, and send the paging message to the terminal device, the paging message Contains information about the user's identity and the user's network.
  • the method further includes: the mobility management entity sends a second paging request message to the access network device, and the second paging request message
  • the request message includes the user identifier of the terminal device and information of the user network;
  • the access network device receives the second paging message and sends the paging message to the terminal device, and the paging message includes the user identifier and information of the user network.
  • the information of the user network such as the identifier of the user network, is carried in the paging request message and the paging message, which is beneficial for the terminal device to accurately access the user network.
  • the method further includes: the access network device sends a first user request message to the access management entity, where the first user request message includes an access management connection identifier; the access management entity receives the first user request message message, and send a second user request message to the mobility management entity, where the second user request message includes a mobility management connection identifier, wherein the mobility management connection identifier is determined according to the association relationship between the access management connection identifier and the mobility management connection identifier; the mobility management The entity receives the second user request message, and sends the second user response message to the access management entity, the second user response message includes the access management connection identifier, wherein the access management connection identifier is based on the access management connection identifier and the mobility management connection The association relationship of the identification is determined; the access management entity receives the second user response message, and sends the first user response message to the access network device, wherein the first user response message includes the access network connection identification, wherein the access network connection identification It is determined according to the association relationship between the access management connection
  • the access network device after the terminal device accesses the user network, the access network device, the access management entity and the mobility management entity can Connect the associated relationship of the identification to communicate.
  • the terminal device When the terminal device has service data, it can send a user request message carrying the service data to the mobility management entity through the access network device to meet the communication needs of the terminal device and the user network.
  • the method further includes: the mobility management entity sends a first network request message to the access management entity, where the first network request message includes an access management connection identifier, and the access management connection identifier is based on the access management The association between the connection identifier and the mobility management connection identifier is determined; the access management entity receives the first network request message, and sends a second network request message to the access network device, and the second network request message includes the access network connection identifier, wherein The access network connection identifier is determined according to the association relationship between the access management connection identifier and the access network connection identifier; the access network device is also used to receive the second network request message.
  • the access network device after the terminal device accesses the user network, the access network device, the access management entity and the mobility management entity can The association relationship of the connection identifier is used for communication.
  • the user network When the user network has service data, it can send a network request message carrying service data to the access network device accessed by the terminal device through the mobility management entity, so as to meet the communication needs of the user network and the terminal device.
  • the embodiment of the present application provides a communication method, the method includes: the access network device sends a third connection request message to the mobility management entity, and the third connection request message is used to request to establish the connection between the access network device and the mobility management entity Connection between: the mobility management entity receives the third connection request message, and sends the third connection response message to the access network device, and the third connection response message is used to indicate the connection information between the access network device and the mobility management entity.
  • the method further includes: the access network device sends a mobility management entity addressing request message to the access management entity, where the mobility management entity addressing request message includes user access information; the access management entity receives the mobility management entity addressing request message request message, and send the mobile management entity addressing response message to the access network equipment, the mobile management entity addressing response message includes the information of the mobile management entity, and the mobile management entity is determined by the access management entity according to the user access information; the access The network equipment receives the MME addressing response message.
  • the access management and mobility management functions can be implemented by the access management entity and the mobility management entity respectively, which can decouple the access management and mobility management, and one access management entity can correspond to multiple user networks.
  • Multiple mobility management entities, different user networks can no longer share mobility management entities, which is conducive to meeting the independent establishment, independent control and independent evolution requirements of access management and mobility management, and meeting the differentiated capacity of access management and mobility management Planning, deployment location, availability requirements.
  • the third connection request message includes the access network connection identifier of the access network device; the connection information between the access network device and the mobility management entity includes the mobility management connection identifier and the access The association relationship of network connection identification.
  • the connection between the access network device and the access management entity can be established through the association relationship between the access network connection identifier and the mobility management connection identifier, so that the terminal device can pass
  • the access network equipment is connected to the mobility management entity to meet the communication requirements between the terminal equipment and the user network.
  • the user access information includes user identification and user network information
  • the access management entity determines the mobility management entity according to the user access information, including: the access management entity determines the mobility management entity based on the user identification and user network information, Determine a mobility management entity associated with the user identifier and supporting the user network, and address the mobility management entity indicated by the information of the mobility management entity carried in the response message for the mobility management entity.
  • the access management entity may query the mobility management entity associated with the user identity and supporting the user network through the user context addressing entity according to the information of the user identity and the user network, as the information carried in the mobility management entity addressing response message The mobility management entity indicated by the information of the mobility management entity.
  • the mobile management entity that the terminal device has been connected to and supports the user network can be queried through the user context according to the user ID and user network information, which is conducive to the accurate and fast access of the terminal device to the required user network.
  • the user access information includes the information of the user network, and the access management entity determines the mobility management entity according to the user access information, including: the access management entity determines the mobility management entity that supports the user network according to the user network information. a list of management entities; and determining a mobility management entity in the mobility management entity list as the mobility management entity indicated by the information of the mobility management entity carried in the mobility management entity address response message.
  • the access management entity may send a user network addressing request message to the user network addressing entity, and the user network addressing request message includes user network information; receive a user network addressing response message from the user network addressing entity
  • the user network addressing response message includes a list of mobile management entities supporting the user network; and a mobile management entity in the list of mobile management entities is determined as the information of the mobile management entity carried in the mobile management entity addressing response message Indicates the Mobility Management Entity.
  • the information of the user network it is possible to query whether there is a user network that can provide services for the user in the created user network, which is beneficial for the terminal device to quickly access the required user network and reduce the resource overhead of the user network.
  • the method further includes: the mobility management entity sends a second paging request message to the access network device, where the second paging request message includes the user identifier of the terminal device and information about the user network; the access network The device receives the second paging message, and sends the paging message to the terminal device, where the paging message includes user identification and user network information.
  • the information of the user network such as the identifier of the user network, is carried in the paging request message and the paging message, which is beneficial for the terminal device to accurately access the user network.
  • an embodiment of the present application provides a communication method, the method includes: an access management entity receives a first connection request message from an access network device, and the first connection request message includes user access information for requesting establishment The connection between the access network equipment and the mobility management entity; the access management entity sends a second connection request message to the mobility management entity based on the first connection request message, and the second connection request message is used to request the establishment of the access management entity and the mobile management entity The connection between the mobile management entity, wherein the mobility management entity is determined by the access management entity according to the user access information; the access management entity receives the second connection response message from the mobility management entity, and the second connection response message is used to indicate that the access management entity Connection information with the mobility management entity; the access management entity sends a first connection response message to the access network device, and the first connection response message is used to indicate connection information between the access network device and the access management entity.
  • the first connection request message further includes the access network connection identifier of the access network device, and the second connection request message includes the access management connection identifier of the access management entity; the access management entity and the mobility management
  • the connection information between entities includes the association relationship between the access management connection identifier and the mobility management connection identifier of the mobility management entity; the connection information between the access network device and the access management entity includes the access management connection identifier and the access network connection Identified relationship.
  • the user access information includes user identification and user network information
  • the access management entity sends the second connection request message to the mobility management entity based on the first connection request message, including: the access management entity sends the second connection request message to the mobility management entity according to The user ID and the user network information determine that the mobility management entity associated with the user ID and supporting the user network is the mobility management entity that receives the second connection request message.
  • the access management entity may query the mobility management entity associated with the user identifier and supporting the user network through the user context addressing entity according to the information of the user identifier and the user network, as the mobility management entity receiving the second connection request message entity.
  • the user access information includes user network information
  • the access management entity sends the second connection request message to the mobility management entity based on the first connection request message, including: the access management entity information to determine a list of mobility management entities supporting the user network; the access management entity determines a mobility management entity in the mobility management entity list as the mobility management entity that receives the second connection request message.
  • the access management entity may send a user network addressing request message to the user network addressing entity, and the user network addressing request message includes user network information; receive a user network addressing response from the user network addressing entity
  • the message, the user network addressing reply message includes a list of MMEs supporting the user network; and determining a MME in the list of MMEs as the MME receiving the second connection request message.
  • the first connection response message is also used to indicate the connection relationship between the access network device and the mobility management entity.
  • the second connection request message also includes the connection The network access connection identifier
  • the first connection response message also includes an association relationship between the access network connection identifier and the mobility management connection identifier.
  • the method further includes: the access management entity receives a first paging request message from the mobility management entity, where the first paging request message includes the user identifier of the terminal device and information about the user network; The management entity forwards the first paging request message to the access network device.
  • the method further includes: the access management entity receives a first user request message from the access network device, where the first user request message includes an access management connection identifier; the access management entity sends the mobility management entity Send a second user request message, the second user request message includes a mobility management connection identifier, wherein the mobility management connection identifier is determined according to the association relationship between the access management connection identifier and the mobility management connection identifier; the access management entity receives the The second user response message includes the access management connection identifier; the access management entity sends the first user response message to the access network device, and the first user response message includes the access network connection identifier, wherein the access The network connection identifier is determined according to the association relationship between the access management connection identifier and the access network connection identifier.
  • the method further includes: the access management entity receives a first network request message from the mobility management entity, where the first network request message includes an access management connection identifier; the access management entity sends the access network device Sending a second network request message, where the second network request message includes the access network connection identifier, where the access network connection identifier is determined according to the association relationship between the access management connection identifier and the access network connection identifier.
  • the embodiment of the present application provides a communication method, the method comprising: an access management entity receives a mobile management entity addressing request message from an access network device, and the mobile management entity addressing request message includes user access information; The access management entity sends a mobility management entity addressing response message to the access network device.
  • the mobility management entity addressing response message includes the information of the mobility management entity, and the mobility management entity is determined by the access management entity based on user access information.
  • the user access information includes user identification and user network information
  • the access management entity determines the mobility management entity according to the user access information, including: the access management entity determines the mobility management entity based on the user identification and user network information, Determine the mobility management entity associated with the user identity and supporting the user network.
  • the access management entity may query the mobility management entity associated with the user identity and supporting the user network through the user context addressing entity according to the information of the user identity and the user network, as the information carried in the mobility management entity addressing response message The mobility management entity indicated by the information of the mobility management entity.
  • the user access information includes the information of the user network, and the access management entity determines the mobility management entity according to the user access information, including: the access management entity determines the mobility management entity that supports the user network according to the user network information. a list of management entities; and determining a mobility management entity in the mobility management entity list as the mobility management entity indicated by the information of the mobility management entity carried in the mobility management entity address response message.
  • the access management entity may send a user network addressing request message to the user network addressing entity, and the user network addressing request message includes user network information; receive a user network addressing response message from the user network addressing entity
  • the user network addressing response message includes a list of mobile management entities supporting the user network; and a mobile management entity in the list of mobile management entities is determined as the information of the mobile management entity carried in the mobile management entity addressing response message Indicates the Mobility Management Entity.
  • the embodiment of the present application provides a communication method, the method includes: the mobility management entity receives a second connection request message from the access management entity, and the second connection request message is used to request the establishment of the access management entity and the mobility management entity Connection between entities: the mobility management entity sends a second connection response message to the access management entity, and the second connection response message is used to indicate connection information between the access management entity and the mobility management entity.
  • the second connection request message includes the access management connection identifier of the access management entity; the connection information between the access management entity and the mobility management entity includes the access management connection identifier and the mobility of the mobility management entity.
  • the method further includes: the mobility management entity sends a first paging request message to the access management entity, where the first paging request message includes the user identifier of the terminal device and information about the user network; or, the mobile The management entity sends a second paging request message to the access network device, where the second paging request message includes the user identifier of the terminal device and the information of the user network.
  • the method further includes: the mobility management entity receives a second user request message from the access management entity, where the second user request message includes a mobility management connection identifier; the mobility management entity sends the second user request message to the access management entity Two user response messages, the second user response message includes the access management connection identifier, wherein the access management connection identifier is determined according to the association relationship between the access management connection identifier and the mobility management connection identifier.
  • the method further includes: the mobility management entity sends a first network request message to the access management entity, where the first network request message includes an access management connection identifier, and the access management connection identifier is based on the access management The association relationship between the connection ID and the mobility management connection ID is determined.
  • the embodiment of the present application provides a communication method, the method includes: a mobility management entity receives a third connection request message from an access network device, and the third connection request message is used to request to establish a connection between the access network device and the mobility management A connection between entities; the mobility management entity sends a third connection response message to the access network device, and the third connection response message uses It is used to indicate the connection information between the access network equipment and the mobility management entity.
  • the third connection request message includes the access network connection identifier of the access network device; the connection information between the access network device and the mobility management entity includes the mobility management connection identifier and the access The association relationship of network connection identification.
  • the method further includes: the mobility management entity sends a second paging request message to the access network device, where the second paging request message includes the user identifier of the terminal device and information of the user network.
  • the embodiment of the present application provides a communication method, the method includes: an access network device sends a first connection request message to an access management entity, the first connection request message includes user access information, and is used to request to establish a connection The connection between the network access device and the mobility management entity; the access network device receives a first connection response message from the access management entity, and the first connection response message is used to indicate the connection between the access network device and the access management entity information.
  • the first connection request message further includes the access network connection identifier of the access network device; the connection information between the access network device and the access management entity includes the access management connection identifier of the access management entity The association relationship between the identifier and the access network connection identifier.
  • the user access information includes user identification and user network information.
  • the first connection response message further includes the association relationship between the mobility management connection identifier of the mobility management entity and the access network connection identifier
  • the method further includes: the access network device records the mobility management connection identifier and the access network connection identifier.
  • the access network device receives the first paging request from the access management entity, and the first paging request includes the user identifier of the terminal device and the information of the user network; the access network device sends the A paging message, where the paging message includes user identification and user network information; or, the access network device receives a second paging request from the mobility management entity, and the second paging request includes the user identification of the terminal device and user network information ; The access network device sends a paging message to the terminal device, and the paging message includes user identification and user network information.
  • the embodiment of the present application provides a communication method, the method includes: the access network device sends a third connection request message to the mobility management entity, and the third connection request message is used to request to establish the connection between the access network device and the mobility management entity The connection between them; the access network device receives the third connection response message from the mobility management entity, and the third connection response message is used to indicate the connection information between the access network device and the mobility management entity.
  • the third connection request message includes the access network connection identifier of the access network device; the connection information between the access network device and the mobility management entity includes the mobility management connection identifier and the access The association relationship of network connection identification.
  • the method further includes: the access network device sends a mobility management entity addressing request message to the access management entity, where the mobility management entity addressing request message includes user access information; the access network device receives the The MME addressing response message of the access management entity, the MME addressing response message includes the information of the MME.
  • the user access information includes user identification and user network information.
  • the access network device receives the second paging request from the mobility management entity, and the second paging request includes the user identifier of the terminal device and the information of the user network; the access network device sends the paging request to the terminal device paging message, the paging message includes user ID and user network information.
  • the embodiment of the present application provides a communication device, which can be used in the communication device of the third aspect, and the communication device can be an access management entity, or a device in an access management entity (for example, chip, or chip system, or circuit), or a device that can be matched with the access management entity.
  • the communication device can be an access management entity, or a device in an access management entity (for example, chip, or chip system, or circuit), or a device that can be matched with the access management entity.
  • the communication device may include a one-to-one corresponding module or unit for executing the method/operation/step/action described in the third aspect.
  • the module or unit may be a hardware circuit, software, or It can be implemented by combining hardware circuits with software.
  • the communication apparatus may include: an interface unit and a processing unit; the interface unit is configured to receive a first connection request message from an access network device, where the first connection request message includes user access information for Request to establish a connection between the access network device and the mobility management entity; the processing unit is configured to send a second connection request message to the mobility management entity through the interface unit based on the first connection request message, and the second connection request message is used to request establishment The connection between the access management entity and the mobility management entity, wherein the mobility management entity is determined by the access management entity according to user access information; the interface unit is also used to receive a second connection response message from the mobility management entity, and the second The connection response message is used to indicate the connection information between the access management entity and the mobility management entity; and the first connection response message is sent to the access network device, and the first connection response message is used to indicate that the access network device and the access management entity connection information between.
  • the first connection request message further includes the access network connection identifier of the access network device, and the second connection request message includes the access management connection identifier of the access management entity; the access management entity and the mobility management
  • the connection information between entities includes the association relationship between the access management connection identifier and the mobility management connection identifier of the mobility management entity; the connection information between the access network device and the access management entity includes the access management connection identifier and the access network connection Identified relationship.
  • the user access information includes user identification and user network information
  • the processing unit sends the second connection request message to the mobility management entity through the interface unit based on the first connection request message, it is specifically configured to The ID and the information of the user network determine that the mobility management entity associated with the user ID and supporting the user network is the mobility management entity that receives the second connection request message.
  • the processing unit may query, through the user context addressing entity, a mobility management entity associated with the user ID and supporting the user network as the mobility management entity that receives the second connection request message.
  • the user access information includes user network information, and when the processing unit sends the second connection request message to the mobility management entity through the interface unit based on the first connection request message, it is specifically used to Determine a list of mobility management entities supporting the user network; determine a mobility management entity in the list of mobility management entities as the mobility management entity that receives the second connection request message.
  • the processing unit can send a user network addressing request message to the user network addressing entity through the interface unit, and the user network addressing request message includes the information of the user network; receive user network addressing from the user network addressing entity The response message, the user network addressing response message includes a list of mobility management entities supporting the user network; and determining a mobility management entity in the list of mobility management entities as the mobility management entity receiving the second connection request message.
  • the interface unit is further configured to receive a first paging request message from the mobility management entity, where the first paging request message includes the user identifier of the terminal device and information of the user network; The device forwards the first paging request message.
  • the interface unit is further configured to receive a first user request message from the access network device, where the first user request message includes an access management connection identifier; send a second user request message to the mobility management entity, The second user request message includes a mobility management connection identifier, wherein the mobility management connection identifier is determined by the processing unit according to the association relationship between the access management connection identifier and the mobility management connection identifier; the interface unit is also configured to receive the second A user response message, where the second user response message includes an access management connection identifier; and sending a first user response message to the access network device, where the first user response message includes an access network connection identifier, wherein the access network connection identifier is a processing unit It is determined according to the association relationship between the access management connection identifier and the access network connection identifier.
  • the interface unit is further configured to receive a first network request message from the mobility management entity, where the first network request message includes an access management connection identifier; and send a second network request message to the access network device , the second network request message includes an access network connection identifier, where the access network connection identifier is determined by the processing unit according to the association relationship between the access management connection identifier and the access network connection identifier.
  • the embodiment of the present application provides a communication device, which can be used in the communication device of the fourth aspect, and the communication device can be an access management entity, or a device in an access management entity (for example, chip, or chip system, or circuit), or a device that can be matched with the access management entity.
  • the communication device can be an access management entity, or a device in an access management entity (for example, chip, or chip system, or circuit), or a device that can be matched with the access management entity.
  • the communication device may include a one-to-one corresponding module or unit for executing the method/operation/step/action described in the fourth aspect.
  • the module or unit may be a hardware circuit, software, or It can be implemented by combining hardware circuits with software.
  • the communication device may include: an interface unit and a processing unit; the interface unit is configured to receive a mobility management entity addressing request message from an access network device, where the mobility management entity addressing request message includes a user access information; the interface unit is also used to send a mobile management entity addressing response message to the access network device, the mobile management entity addressing response message includes the information of the mobile management entity, and the mobile management entity is determined by the processing unit according to the user access information.
  • the user access information includes user identification and user network information
  • the processing unit determines the mobility management entity according to the user access information, it is specifically used to determine the information related to the user identification based on the user identification and user network information.
  • a mobility management entity that is associated with and supports the user network.
  • the processing unit may query the mobility management entity associated with the user ID and supporting the user network through the user context addressing entity, as the mobility management entity carried in the mobility management entity addressing response message.
  • the user access information includes user network information
  • the processing unit determines the mobility management entity according to the user access information, it is specifically used to determine the list of mobility management entities supporting the user network according to the user network information and determining a mobility management entity in the mobility management entity list as the mobility management entity indicated by the mobility management entity information carried in the mobility management entity address response message.
  • the processing unit can send a user network addressing request message to the user network addressing entity through the interface unit, and the user network addressing request message includes the information of the user network; receive a user network addressing response from the user network addressing entity message, the user network addressing response message includes a list of mobility management entities supporting the user network; and a mobility management entity in the list of mobility management entities is determined as the information of the mobility management entity carried in the mobility management entity addressing response message The indicated Mobility Management Entity.
  • the embodiment of the present application provides a communication device, which can be used in the communication device of the fifth aspect, and the communication device can be a mobility management entity, or a device in a mobility management entity (for example, a chip , or a chip system, or a circuit), or a device that can be used in conjunction with a mobility management entity.
  • the communication device may include a one-to-one corresponding module or unit for executing the method/operation/step/action described in the fifth aspect.
  • the module or unit may be a hardware circuit, software, or It can be implemented by combining hardware circuits with software.
  • the communication device may include: an interface unit and a processing unit; the interface unit is configured to receive a second connection request message from the access management entity, and the second connection request message is used to request the establishment of the access management entity The connection with the mobility management entity; the processing unit is used to determine the second connection response message, and the second connection response message is used to indicate the connection information between the access management entity and the mobility management entity; the interface unit is also used to send second connection Respond to the message.
  • the second connection request message includes the access management connection identifier of the access management entity; the connection information between the access management entity and the mobility management entity includes the access management connection identifier and the mobility of the mobility management entity.
  • the interface unit is further configured to send a first paging request message to the access management entity, where the first paging request message includes the user identifier of the terminal device and information about the user network;
  • the network device sends a second paging request message, where the second paging request message includes the user identifier of the terminal device and information about the user network.
  • the interface unit is further configured to receive a second user request message from the access management entity, where the second user request message includes a mobility management connection identifier; and send a second user response message to the access management entity , the second user response message includes the access management connection identifier, where the access management connection identifier is determined by the processing unit according to the association relationship between the access management connection identifier and the mobility management connection identifier.
  • the interface unit is further configured to send a first network request message to the access management entity, where the first network request message includes an access management connection identifier, and the access management connection identifier is the processing unit according to the access management The association relationship between the connection ID and the mobility management connection ID is determined.
  • the embodiment of the present application provides a communication device, which can be used in the communication device of the sixth aspect, and the communication device can be a mobility management entity, or a device in a mobility management entity (for example, a chip , or a chip system, or a circuit), or a device that can be used in conjunction with a mobility management entity.
  • the communication device may include a one-to-one corresponding module or unit for executing the method/operation/step/action described in the sixth aspect.
  • the module or unit may be a hardware circuit, software, or It can be implemented by combining hardware circuits with software.
  • the communication apparatus may include: an interface unit and a processing unit; the interface unit is configured to receive a third connection request message from the access network device, and the third connection request message is used to request to establish an access network device The connection with the mobility management entity; the processing unit is used to determine the third connection response message, and the third connection response message is used to indicate the connection information between the access network device and the mobility management entity; the interface unit is also used to send the The access network device sends a third connection response message.
  • the third connection request message includes the access network connection identifier of the access network device; the connection information between the access network device and the mobility management entity includes the mobility management connection identifier and the access The association relationship of network connection identification.
  • the interface unit is further configured to send a second paging request message to the access network device, where the second paging request message includes the user identifier of the terminal device and information of the user network.
  • the embodiment of this application provides a communication device, which can be used in the communication device of the seventh aspect, and the communication device can be an access network device, or a device in an access network device (such as , chip, or chip system, or circuit), or a device that can be matched with access network equipment.
  • the communication device can be an access network device, or a device in an access network device (such as , chip, or chip system, or circuit), or a device that can be matched with access network equipment.
  • the communication device may include a one-to-one corresponding module or unit for executing the method/operation/step/action described in the seventh aspect.
  • the module or unit may be a hardware circuit, software, or It can be implemented by combining hardware circuits with software.
  • the communication device may include: an interface unit and a processing unit; the processing unit is configured to determine a first connection request message, where the first connection request message includes user access information and is used to request to establish an access network device To a connection between a mobility management entity; an interface unit, configured to send a first connection request message to an access management entity; and to receive a first connection response message from an access management entity, where the first connection response message is used to indicate access Network equipment and connection Enter connection information between managed entities.
  • the first connection request message further includes the access network connection identifier of the access network device; the connection information between the access network device and the access management entity includes the access management connection identifier of the access management entity The association relationship between the identifier and the access network connection identifier.
  • the user access information includes user identification and user network information.
  • the first connection response message further includes the mobility management connection identifier of the mobility management entity
  • the processing unit is further configured to record an association relationship between the mobility management connection identifier and the access network connection identifier of the access network device.
  • the interface unit is further configured to receive a first paging request from the access management entity, where the first paging request includes the user identifier of the terminal device and information about the user network; the processing unit is also configured to Send a paging message to the terminal device through the interface unit, the paging message includes user identification and user network information; or, the interface unit is also used to receive a second paging request from the mobility management entity, the second paging request includes the terminal The user identification of the device and the information of the user network; the processing unit is also configured to send a paging message to the terminal device through the interface unit, and the paging message includes the information of the user identification and the user network.
  • the embodiment of the present application provides a communication device, which can be used in the communication device of the eighth aspect, and the communication device can be an access network device, or a device in an access network device (such as , chip, or chip system, or circuit), or a device that can be matched with access network equipment.
  • the communication device can be an access network device, or a device in an access network device (such as , chip, or chip system, or circuit), or a device that can be matched with access network equipment.
  • the communication device may include a module or unit corresponding to one-to-one execution of the methods/operations/steps/actions described in the eighth aspect.
  • the modules or units may be hardware circuits, software, or It can be implemented by combining hardware circuits with software.
  • the communication device may include: an interface unit and a processing unit; the processing unit is configured to determine a third connection request message, and the third connection request message is used to request to establish a connection between the access network device and the mobility management entity connection; an interface unit, configured to send a third connection request message to the mobility management entity; and receive a third connection response message from the mobility management entity, where the third connection response message is used to indicate the connection between the access network device and the mobility management entity connection information.
  • the third connection request message includes the access network connection identifier of the access network device; the connection information between the access network device and the mobility management entity includes the mobility management connection identifier and the access The association relationship of network connection identification.
  • the interface unit is further configured to send a mobility management entity addressing request message to the access management entity, where the mobility management entity addressing request message includes user access information; and receive a mobile The management entity addresses the response message, and the mobility management entity address response message includes the information of the mobility management entity.
  • the user access information includes user identification and user network information.
  • the interface unit is further configured to receive a second paging request from the mobility management entity, where the second paging request includes the user identifier of the terminal device and information about the user network; the processing unit is also configured to pass The interface unit sends a paging message to the terminal device, and the paging message includes user identification and user network information.
  • the embodiment of the present application provides a communication device, where the communication device includes an interface circuit and a processor, and the processor and the interface circuit are coupled to each other.
  • the processor implements the above-mentioned third aspect or the method in any possible design of the third aspect through a logic circuit or executes instructions, or is used to realize the above-mentioned fourth aspect or any of the possible designs of the fourth aspect Methods.
  • the interface circuit is used for receiving signals from other communication devices other than the communication device and transmitting to the processor or sending signals from the processor to other communication devices other than the communication device. It can be understood that the interface circuit may be a transceiver or a transceiver or a transceiver or an input-output interface.
  • the communication device may further include a memory for storing instructions executed by the processor, or storing input data required by the processor to execute the instructions, or storing data generated after the processor executes the instructions.
  • the memory may be a physically independent unit, or may be coupled with the processor, or the processor may include the memory.
  • the embodiment of the present application provides a communication device, where the communication device includes an interface circuit and a processor, and the processor and the interface circuit are coupled to each other.
  • the processor is used to implement the above-mentioned fifth aspect or the method in any possible design of the fifth aspect through a logic circuit or executing instructions, or to realize the above-mentioned sixth aspect or any possible design of the sixth aspect Methods.
  • the interface circuit is used for receiving signals from other communication devices other than the communication device and transmitting to the processor or sending signals from the processor to other communication devices other than the communication device. It can be understood that the interface circuit may be a transceiver or a transceiver or a transceiver or an input-output interface.
  • the communication device may further include a memory for storing instructions executed by the processor, or storing input data required by the processor to execute the instructions, or storing data generated after the processor executes the instructions.
  • the memory may be a physically independent unit, or may be coupled with the processor, or the processor may include the memory.
  • the embodiment of the present application provides a communication device, where the communication device includes an interface circuit and a processor, and the processor and the interface circuit are coupled to each other.
  • the processor implements the above-mentioned seventh aspect or the method in any possible design of the seventh aspect through a logic circuit or executes instructions, or is used to realize the above-mentioned eighth aspect or any of the possible designs of the eighth aspect Methods.
  • the interface circuit is used for receiving signals from other communication devices other than the communication device and transmitting to the processor or sending signals from the processor to other communication devices other than the communication device. It can be understood that the interface circuit may be a transceiver or a transceiver or a transceiver or an input-output interface.
  • the communication device may further include a memory for storing instructions executed by the processor, or storing input data required by the processor to execute the instructions, or storing data generated after the processor executes the instructions.
  • the memory may be a physically independent unit, or may be coupled with the processor, or the processor may include the memory.
  • the embodiments of the present application provide a computer-readable storage medium, in which computer programs or instructions are stored, and when the computer programs or instructions are executed, any of the above-mentioned third aspect or the third aspect can be realized.
  • the embodiment of the present application also provides a computer program product, including computer programs or instructions.
  • a computer program product including computer programs or instructions.
  • the above third aspect or any possible design of the third aspect can be realized.
  • method, or realize the above-mentioned fourth aspect or a method in any possible design of the fourth aspect, or realize the above-mentioned fifth aspect or a method in any possible design of the fifth aspect, or realize the above-mentioned sixth aspect A method in any possible design of the aspect or the sixth aspect, or a method in any possible design that realizes the seventh aspect or the seventh aspect, or realizes any of the eighth aspect or the eighth aspect a possible design approach.
  • the embodiment of the present application also provides a chip, the chip is coupled with the memory, and is used to read and execute the programs or instructions stored in the memory, so as to realize the above-mentioned third aspect or any possible possibility of the third aspect.
  • the method in the design, or the method in the design that realizes the above fourth aspect or any possible design of the fourth aspect, or the method in the design that realizes the above fifth aspect or any possible design of the fifth aspect, or realizes the above The sixth aspect or the method in any possible design of the sixth aspect, or the method for realizing the above-mentioned seventh aspect or any of the possible designs of the seventh aspect, or the method for realizing the above-mentioned eighth aspect or the eighth aspect Any one of the possible design methods.
  • the embodiment of the present application also provides a communication system, which may include: the above-mentioned ninth aspect The access management entity of the eleventh aspect, the mobility management entity of the eleventh aspect, and the access network device of the thirteenth aspect.
  • the communication system may further include the user context addressing entity and the user network addressing entity mentioned in the ninth aspect, the eleventh aspect, and the thirteenth aspect.
  • the embodiment of the present application further provides a communication system, which includes: the access management entity in the tenth aspect, the mobility management entity in the twelfth aspect, and the access network device in the fourteenth aspect.
  • the communication system may further include the user context addressing entity and the user network addressing entity mentioned in the tenth aspect, the twelfth aspect and the fourteenth aspect.
  • the embodiment of the present application further provides a core network system, including: the access management entity in the ninth aspect and the mobility management entity in the eleventh aspect.
  • the communication system may further include the user context addressing entity and the user network addressing entity mentioned in the ninth aspect and the eleventh aspect.
  • the embodiment of the present application further provides a core network system, including: the access management entity in the tenth aspect and the mobility management entity in the twelfth aspect.
  • the communication system may further include the user context addressing entity and the user network addressing entity mentioned in the tenth aspect and the twelfth aspect.
  • FIG. 1 is a schematic diagram of a network architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a decoupled network architecture for access management and mobility management provided by an embodiment of the present application
  • FIG. 3 is a schematic diagram of direct mode and indirect mode communication provided by the embodiment of the present application.
  • FIG. 4 is one of the interactive schematic diagrams of the communication method provided by the embodiment of the present application.
  • FIG. 5 is a schematic diagram of a process for determining a mobility management entity provided in an embodiment of the present application
  • FIG. 6 is a schematic diagram of message processing of a mobility management entity provided by an embodiment of the present application.
  • FIG. 7 is the second interactive schematic diagram of the communication method provided by the embodiment of the present application.
  • FIG. 8 is a schematic diagram of a process of initiating a network request by the network side provided in an embodiment of the present application.
  • FIG. 9 is the third interactive schematic diagram of the communication method provided by the embodiment of the present application.
  • FIG. 10 is the fourth interactive schematic diagram of the communication method provided by the embodiment of the present application.
  • Fig. 11 is the fifth interactive schematic diagram of the communication method provided by the embodiment of the present application.
  • FIG. 12 is the sixth interactive schematic diagram of the communication method provided by the embodiment of the present application.
  • FIG. 13 is the seventh interactive schematic diagram of the communication method provided by the embodiment of the present application.
  • FIG. 14 is one of the structural schematic diagrams of the communication device provided by the embodiment of the present application.
  • FIG. 15 is a second structural schematic diagram of a communication device provided by an embodiment of the present application.
  • 5G fifth generation
  • 5G new radio
  • NR new radio
  • 6 generation networks etc. and can also be applied to communication systems that evolve after 5G, such as sixth generation networks etc., and can also be applied to long term evolution (long term evolution, LTE) network, LTE frequency division duplex (frequency division duplex, FDD) network, LTE time division duplex (time division duplex, TDD) network, etc.
  • LTE long term evolution
  • LTE frequency division duplex frequency division duplex
  • FDD frequency division duplex
  • TDD time division duplex
  • FIG. 1 it is a schematic diagram of a network architecture.
  • user equipment user equipment
  • UE user equipment
  • AMF access and mobility management function
  • AN access network
  • the (R)AN can communicate with the AMF through an N2 interface.
  • the (R)AN can also communicate with the user plane function (UPF) through the N3 interface
  • the UPF can communicate with other UPFs through the N9 interface
  • the UPF can also communicate with the data network (DN) through the N6 interface.
  • DN data network
  • SMF session management function
  • the AMF can communicate with other AMFs through the N14 interface, and the AMF can also communicate with the SMF through the N11 interface, communicate with the authentication server function (authentication server function, AUSF) through the N12 interface, and communicate with the unified data management (unified data management) through the N8 interface.
  • UDM communication with policy control function (policy control function, PCF) through N15 interface, and communication with network slice selection function (network slice selection function, NSSF) through N22 interface
  • SMF can communicate with UDM through N10 interface, and through The N7 interface communicates with the PCF, and the PCF can communicate with an application function (application function, AF) through the N5 interface.
  • (R)AN can be implemented by access network equipment
  • UPF can be implemented by user plane entities
  • AMF can be implemented by access and mobility management entities
  • SMF can be implemented by session management entities
  • PCF can be implemented by
  • the policy control entity is implemented, the AF can be implemented through the application entity, the NSSF can be implemented through the network slicing selection entity, the AUSF can be implemented through the authentication service entity, and the UDM function can be implemented through the unified data management entity.
  • the above entity or function may be a network element in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (eg, a cloud platform).
  • a platform eg, a cloud platform
  • the above entity or function may be implemented by one device, or jointly implemented by multiple devices, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.
  • the access management function and the mobility management function are usually provided by the access and mobility management entity.
  • the access and mobility management entity may provide one or more of the following access management functions:
  • Provide external parameters provisioning of external parameters, such as providing expected UE behavior parameters (expected UE behavior parameters) or network configuration parameters (network configuration parameters).
  • the access and mobility management entity may provide one or more of the following mobility management functions:
  • N1 non-access stratum
  • N1 Termination of non-access stratum (NAS) (N1), NAS encryption and integrity protection;
  • SM session management
  • SMS short message service
  • SMSF short message service function
  • SEAF security anchor function
  • LMF location management function
  • EPS bearer ID allocation for interworking with the evolved packet system (EPS);
  • the processing object of access management is the network access capability, focusing on the connection between terminal equipment and the access network
  • the processing object of mobility management is the user's mobility management capability, focusing on service functions.
  • Access management and mobility management are coupled together, and access and mobility management entities implement corresponding access management functions and mobility management functions, which is not conducive to the independent construction of access management and mobility management.
  • the network access management process is controlled by the operator, and the user's mobility management process can be controlled by the service user or tenant in principle.
  • this application proposes a communication solution in order to decouple access management and mobility management, meet the requirements of independent establishment, independent control and independent evolution of access management and mobility management, and support the differentiated capacity of access management and mobility management Planning, deployment location, availability requirements.
  • FIG. 2 it is a schematic diagram of a network architecture applicable to the embodiment of the present application, including terminal equipment, access network equipment, access management entities, mobility management entities, user network addressing entities, user context addressing entities and others network entities.
  • the access management entity has access management functions such as access authentication and access authorization.
  • the access management entity may have part or all of the access management functions of the above-mentioned access and mobility management entity.
  • the access network device can first access (or connect) to the access management entity, and the access management entity can process user-related signaling, select a mobility management entity for the user, and transmit user-related information (or signaling) forwarded to the mobility management entity.
  • the access management entity After the user accesses the user network, in the indirect mode, the uplink message and downlink message between the user and the mobility management entity are forwarded and processed by the access management entity.
  • the mobility management entity has mobility management functions such as location service management and providing session management signaling channels for users.
  • the mobility management entity may have part or all of the mobility management functions of the above-mentioned access and mobility management entity. It can provide users with the network function of mobile management services, and can maintain the user's mobile management context, including user network side registration status, access network device connection status, location and other information.
  • the user context addressing entity can provide user context addressing functions for other network entities.
  • the identity of the corresponding mobility management entity can be queried through the user context addressing entity ( identifier, ID) or address.
  • the user context addressing entity can be integrated with a network storage entity that can implement the network function (network function, NF) storage function (NF repository function, NRF), or implement the user context addressing entity through the network storage entity Some or all of the functions of the user context addressing entity, or some or all of the functions of the user context addressing entity through the binding support entity capable of implementing the binding support function (BSF).
  • BSF binding support function
  • the user network addressing entity When the user network addressing entity initially accesses the user network (such as initially registering to the user network or attaching to the user network), it can provide the access management entity with a pass service, which can be used to query a group of mobile devices that can serve the user. Active management entity ID or address set.
  • the user network addressing entity may also be integrated with the network storage entity, or part or all of the functions of the user network addressing entity may be implemented through the network storage entity.
  • the user network addressing entity and the user context addressing entity can also be integrated with other network entities, or embedded in other network entities, for example, the user context addressing entity can be embedded in the mobility management entity, and the mobility management Entities can also implement the functionality of user context addressing entities.
  • Other network entities may include session management entities, policy control entities, user plane entities, authentication service entities, unified data management entities, etc., and can provide session management, policy services, user plane services, etc.
  • the access network device can be connected to the mobility management entity through the user signaling interface A, and the user signaling interface A can be used for the access network device to send an uplink message (or signaling) to the mobility management entity, and the mobility management entity to send an uplink message (or signaling) to the access network entity
  • the network device sends a downlink message (or signaling).
  • the access management entity can be connected to the access network device and the mobility management entity respectively through the user signaling interface B and the user signaling interface C, and the user signaling interface B and the user signaling interface C can be used for the access network device to connect the uplink
  • the message (or signaling) is sent to the access management entity, the access management entity forwards the uplink message (or signaling) to the mobility management entity, and the mobility management entity sends the downlink message (or signaling) to the access management entity , the access management entity forwards the downlink message (or signaling) to the access network device.
  • the user network addressing entity can be connected to the access management entity through the user network query interface, and the access management entity can query the ID or address of at least one mobility management entity that can serve the user through the user network query interface according to the identifier on the user network gather.
  • the user context addressing entity can be connected with the access management entity, the mobility management entity and other network entities respectively through the user context query interface A, the user context query interface B and the user context query interface C, and the access management entity, the mobility management entity and other network entities
  • the network entity can query the ID or address of the mobility management entity of the user network to which the user belongs.
  • Fig. 3 is a schematic diagram of a direct mode and an indirect mode communication provided by the embodiment of the present application.
  • the terminal device that is, the user
  • the access network device can directly communicate with the mobility management entity for user-related messages (or signaling).
  • the access network device can directly send the user request message to the mobility management entity, and the mobility management entity can also directly send the user response message to the access network device, and the mobility management entity and the access network device communicate directly.
  • the access network device and the mobility management entity perform user-related messages (or information Order) communication needs to be forwarded by the access management entity, that is, the access network device and the mobility management entity communicate indirectly through the access management entity.
  • a user network may be a network that provides dedicated services to one or more terminal devices (ie, users), and the user network may be a collection of one or more network entities.
  • the user network in the network shown in Figure 1 may refer to the execution of one or more functions such as mobility management, session management, policy management, data forwarding, traffic statistics, and quality of service (quality of service, QoS) processing.
  • a collection of network entities In a network where access management and mobility management are not decoupled, the mobility management entity can also be replaced by an access and mobility management entity.
  • the user network can be a communication device entity, a virtualized logical network function entity, or a collection of one or a group of physical machines, virtual machines, containers, processes or other runnable resources.
  • the access network device may also be referred to as a network device or a radio access network (radio access network, RAN) device. It can be a base station (base station), an evolved base station (evolved NodeB, eNodeB), a transceiver point (transmitter and receiver point, TRP), integrated access and backhaul (integrated access and backhauling, IAB) node, next generation base station (next generation NodeB, gNB) in the fifth generation (5th generation, 5G) mobile communication system, 6G, etc.
  • base station base station
  • evolved NodeB, eNodeB evolved base station
  • TRP transceiver point
  • IAB integrated access and backhaul
  • next generation base station next generation NodeB, gNB
  • Base stations in communication systems evolved after 5G home base stations (for example, home evolved nodeB, or home node B, HNB), access points (access point, AP) in wireless fidelity (wireless fidelity, WiFi) systems, wireless Relay nodes, wireless backhaul nodes, transmitting points (TP), mobile switching centers, and device-to-device (D2D), vehicle-to-everything (V2X), machine-to-everything In machine-to-machine (M2M) communication, a device that assumes the function of a base station and the like. It may also be a module or unit that completes some functions of the base station, for example, it may be a centralized unit (central unit, CU) or a distributed unit (distributed unit, DU).
  • home base stations for example, home evolved nodeB, or home node B, HNB
  • access points access point, AP
  • wireless fidelity wireless fidelity
  • WiFi wireless Relay nodes
  • wireless backhaul nodes transmitting points (TP), mobile switching
  • the CU here completes the functions of the radio resource control protocol and the packet data convergence protocol (PDCP) of the base station, and can also complete the function of the service data adaptation protocol (SDAP); the DU completes the functions of the base station
  • the functions of the radio link control layer and the medium access control (medium access control, MAC) layer can also complete the functions of part or all of the physical layer.
  • 3rd generation partnership project, 3GPP third generation partnership project
  • the network equipment can also be a non-terrestrial base station, such as a low earth orbit (LEO)/very low earth orbit (VLEO) satellite, a high-attitude platform station (HAPS) )wait.
  • the terminal device may be a device with a wireless transceiver function, and the terminal device may also refer to a terminal, UE, mobile terminal, access terminal, subscriber unit, subscriber station, mobile station, Remote station, remote terminal, wireless communication equipment, user agent or user device, etc.
  • Terminal devices can be widely used in various scenarios.
  • terminal devices can be D2D, V2X communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial Terminals in control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation or smart city.
  • Terminal devices can be mobile phones, tablet computers, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, vehicle terminals, IoT terminals, wearable devices wait.
  • the embodiment of the present application does not limit the specific technology and specific device form adopted by the terminal device.
  • Connection management (connection management, CM) status can be used to describe the signaling connection status between the terminal device and the mobility management entity.
  • CM idle state indicates that the terminal equipment has not established a connection with the mobility management entity, and the uplink and downlink messages (or signaling) between the terminal equipment and the mobility management entity cannot be indexed to the opposite end through the connection identifier.
  • CM connected state indicates that the terminal equipment establishes a connection with the mobility management entity, and the uplink and downlink messages (or signaling) between the terminal equipment and the mobility management entity can be indexed to the opposite end through the connection identifier.
  • the registration management (registration management, RM) status can be used to describe whether the terminal device has been registered to the user network.
  • RM deregistration means that the terminal device (that is, the user) is not registered to the access management entity, and the access management entity and other network entities do not have the context of the terminal device;
  • RM registration means that the terminal device (that is, the user ) is registered with the access management entity, and the access management entity and other network entities have the context of the terminal device.
  • first and second are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, etc. of multiple objects. priority or importance etc.
  • first threshold and the second threshold can be the same threshold or different thresholds, and this name does not mean the values, corresponding parameters, priority or importance of these two thresholds, etc. s difference.
  • the number of nouns means “singular noun or plural noun", That is, “one or more”. "At least one” means one or more, and “plurality” means two or more. "And/or” describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural. The character “/" generally indicates that the contextual objects are an "or” relationship. For example, A/B means: A or B. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items.
  • At least one item (piece) of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c Can be single or multiple.
  • Figure 4 is one of the schematic diagrams of the communication method provided by the embodiment of the present application, the method includes:
  • the terminal device sends a user connection request message to the access network device, where the user connection request message includes user access information, and correspondingly, the access network device receives the user connection request message.
  • a terminal device When a terminal device needs to send service data to the user network, if the terminal device is not connected to the user network, that is, it is not connected to the mobility management entity in the user network, the terminal device needs to initiate a connection to the user network and access the user network. Network, connected to the mobility management entity in the user network. Therefore, when the terminal device needs to send service data to the user network, if the terminal device is not connected to the user network, the terminal device can send a user connection request message including user access information to the access network device, requesting access to the user network. Network, connected to the mobility management entity in the user network.
  • the user access information may include user identification and user network information.
  • the user identifier may be a user permanent identifier (subscription permanent identifier, SUPI) of the terminal device, or a globally unique temporary identity (globally unique temporary identity, GUTI) assigned to the terminal device by the user network before.
  • the information of the user network may include the user network type and/or the user network identifier (such as the user network ID).
  • the terminal device may carry the corresponding user network type when initiating different services according to user subscription information or local policies, for example, when initiating an IoT service, carry the IoT network type.
  • the user network identifier corresponding to each service can be pre-configured in the terminal device through subscription information, etc., and the corresponding user network identifier is carried when the terminal device sends different services.
  • the user connection request message may also include a wireless connection identifier (such as a wireless connection ID) allocated by the terminal device for this service, which is used to establish a connection between the access network device and the terminal device.
  • the wireless connection identifier may also reuse the wireless network temporary identifier configured for the terminal device by the access network device, the user identifier of the terminal device, and the like.
  • the access network device After the access network device receives the user connection request message from the terminal device, it can create an access network connection identifier (such as an access network connection ID) associated with the wireless connection identifier, and can create an access network user context for the terminal device , and record the association relationship between the wireless connection identifier and the access network connection identifier in the access network user context.
  • the access network user context created for the terminal device may be associated with the user identifier of the terminal device for querying.
  • the wireless connection identifier may be a connection identifier assigned by the terminal device to a service (or connection) of the terminal device, and the terminal device and the corresponding service (or connection) may be determined through the wireless connection identifier.
  • the terminal device and the corresponding service such as browsing service A
  • the access network connection identifier may be a connection identifier assigned by the access network device to the service (or connection) of the terminal device, and the access network device and the corresponding service (or connection) may be determined through the access network connection identifier.
  • the subsequent access management connection identifiers, mobility management connection identifiers, etc. are connection identifiers assigned by access management entities, mobility management entities, etc.
  • the access network connection identifier is similar and will not be repeated here.
  • the access network device sends a first connection request message to the access management entity, and correspondingly, the access management entity receives Receive a first connection request message, where the first connection request message includes user access information and is used to request establishment of a connection between the access network device and the mobility management entity.
  • the access network device may select randomly, or select according to a certain policy.
  • the access network device may select an access management entity with the least load from one or more access management entities connected to the access network device as the access management entity that receives the first connection request message.
  • the access management entity that receives the first connection request message may also be selected according to the mapping policy between the user identifier (or some fields in the user identifier) and the access management entity.
  • the mapping policy between the user ID (or some fields in the user ID) and the access management entity may be derived from the local configuration of the access network device or domain name system (domain name system, DNS) configuration, etc.
  • the first connection request message may further include an access network connection identifier, which is used to establish a connection between the access network device and the access management entity.
  • the access management entity receives the first connection request message from the access network device, can create an access management connection identifier (such as an access management connection ID) associated with the access network connection identifier, and can create an access management connection ID for the terminal device. Enter the management user context, and record the association relationship between the access network connection identifier and the access management connection identifier in the access management user context.
  • the access management user context created for the terminal device may be associated with the user identifier of the terminal device for query.
  • the access management entity can also interact with terminal equipment and other network equipment, such as authentication service entities, unified data management entities, etc., to complete the terminal equipment access user network authentication. For example: according to the information of the user network, it is authenticated whether the current access management entity can serve the user network that the terminal device requests to access.
  • the access management entity sends a second connection request message to the mobility management entity based on the first connection request message.
  • the mobility management entity receives the second connection request message, and the second connection request message is used to request establishment of the access management entity Connections with Mobility Management Entities.
  • the access management entity may determine the mobility management entity that receives the second connection request message based on the user access information.
  • the user access information may include user identification and user network information
  • the access management entity may query and associate with the user identification through the user context addressing entity according to the user access information (that is, the terminal device has been connected to ), and support the mobility management entity of the user network, as the mobility management entity receiving the second connection request message, so that the terminal device can accurately and quickly access the desired user network.
  • the user access information may include user network information
  • the access management entity may query one or more mobility management entities supporting the user network through the user network addressing entity according to the user network information, And select a mobility management entity from one or more mobility management entities found in the query, as the mobility management entity receiving the second connection request message, so as to search for a user network that can provide services for the user in the existing user network for connection.
  • the access management entity may send a user addressing request message including the user identifier to the user context addressing entity.
  • the user context addressing entity receives the user addressing request message, it can query whether the terminal device corresponding to the user ID has ever registered to the network in the registration information saved by itself according to the user ID, and has obtained a temporary user ID (such as GUTI) assigned by the network. wait). If the terminal device has been registered to the network, the user context addressing entity may query the mobility management entity that the user temporary identifier is associated with (or pointed to) the terminal device has registered with according to the user temporary identifier assigned to the terminal device.
  • GUTI temporary user ID
  • the user context addressing entity may send information carrying the mobility management entity (such as the ID or the ID of the mobility management entity) to the access management entity Internet Protocol (Internet Protocol, IP) address, etc.) user addressing response message; if the user context addressing entity does not query the mobile management entity that the terminal device was registered to, the user context addressing entity can send the access management entity
  • the user addressing response message that does not carry the information of the mobility management entity, that is, the information of the mobility management entity returned to the access management entity is empty.
  • the user addressing response message may also include user registration status information, for example, the terminal device corresponding to the user ID has registered to the network, and the user registration status information is "registered", if the user ID If the corresponding terminal device has not been registered to the network, the user registration status information is "unregistered”.
  • the access management entity may also determine whether the mobility management entity supports the user network that the terminal device requests to access according to the information of the user network. If the mobility management entity supports the user network that the terminal device requests to access, the access management entity determines the mobility management entity as the mobility management entity that receives the second connection request message.
  • the user network information includes the user network identifier, and when the queried mobility management entity supports the user network identifier, the access management entity can determine that the mobility management entity supports the user network that the terminal device requests to access.
  • the access management entity may also send the user network
  • the addressing entity sends a user network addressing request message including user network information, requesting the user network addressing entity to query a mobility management entity capable of supporting the user network according to the user network information.
  • the user network information may include the user network identifier
  • the user network addressing entity receives the user network addressing request message including the user network information
  • the user network addressing entity may In the mobile management entity table of identification and supporting user network identification, inquire whether there is the user network identification carried in the user network addressing request message, if it exists, the user network addressing entity may support the mobile management entity of the user network identification
  • the list is sent to the access management entity through the user network address response message, where the list of the mobility management entity may include information of at least one mobility management entity that supports the user network identity.
  • the user network information may include the user network type, and the user network addressing entity receives the user network addressing request message including the user network information, and the user network addressing entity may be in the user network maintained by itself.
  • the network type and the mobile management entity table supporting the user network type query whether there is the user network type carried in the user network addressing request message, and if the user network type carried in the user network addressing request message is found, then the user network addressing request message
  • the addressing entity may send the list of mobility management entities supporting the user network type to the access management entity through the user network addressing response message, wherein the list of the mobility management entities may include at least one mobile entity supporting the user network type Manage entity information.
  • the information of the queried MME can be carried in the user network addressing response message in the form of a list, or can be carried in the user network addressing response message in other forms, which is not limited in this application .
  • the user network information may include the user network identifier and the user network type, and the user network addressing entity may first query the list of mobility management entities that support the user network identifier through the user network identifier. The list of mobility management entities that support the user network identifier is sent to the access management entity through the user network address response message. If the list of mobility management entities that support the user network identifier is not found, the user network addressing entity may query the list of mobility management entities that support the user network type through the user network type, and may use the queried information that supports the user network The list of mobility management entities of the type is sent to the access management entity through the user network addressing reply message.
  • the user network addressing entity may not carry any information about the mobility management entity, that is, the list of mobility management entities included in the user network addressing response message may be empty.
  • the access management entity can send access failure information to the access network device, enabling the access network device to reselect the access management entity, or notify the terminal device of the access failure, Or the access management entity can also interact with the network control function, and the network control function instantiates a new mobility management entity, and returns the information of the mobility management entity to the access management entity for subsequent processing, such as as A mobility management entity that receives the second connection request message.
  • the user network address response message may also carry information about user network identification status and/or user network type status.
  • the user network addressing request message carries the user network identifier, and the user network addressing entity finds the user identifier in the user network identifier maintained by itself and the mobility management entity table that supports the user network identifier, the user The network identification status is present, otherwise it is not present; if the user network addressing request message carries the user network type, and the user network addressing entity queries the user network type and the mobility management entity table that supports the user network type maintained by itself The user network type, the user network type status is supported, otherwise it is not supported.
  • the access management entity may select one mobility management entity from at least one mobility management entity queried by the user network addressing entity as the mobility management entity receiving the second connection request message.
  • the access management entity may randomly select a mobility management entity from at least one mobility management entity as the mobility management entity to receive the second connection request message, or may select a mobility management entity from at least one mobility management entity according to a certain strategy.
  • the management entity serves as the mobility management entity receiving the second connection request message, which is not limited in this application.
  • the access management entity may query the mobility management entity only through the user context addressing entity, or may query the mobility management entity only through the user network addressing entity. It is also possible to query the mobility management entity through the user context addressing entity first, and then query the mobility management entity through the user network addressing entity after the mobility management entity is not found through the user context addressing entity. Or first query the mobility management entity through the user network addressing entity, and then query the mobility management entity through the user context addressing entity after the user network addressing entity fails to find the mobility management entity.
  • the comparison of the embodiments of this application is not limited.
  • part or all of the functions of the user context addressing entity and the user network addressing entity can also be integrated or configured in the access management entity, and the above-mentioned mobility management implemented by the user context addressing entity and the user network addressing entity Operations such as entity query or determination can also be implemented inside the access management entity, for example, the access management entity directly determines the mobility management entity that is associated with the user ID and supports the user network based on the information of the user ID and the user network; According to the information of the user network, information of at least one mobility management entity supporting the user network is determined, which is not limited in this application.
  • the second connection request message may further include the access management connection identifier of the access management entity, which is used to establish a connection between the access management entity and the mobility management entity.
  • the mobile management entity After the mobile management entity receives the second connection request message from the access management entity, it can create a mobility management connection identifier (such as a mobility management connection ID) associated with the access management connection identifier, and can create a mobility management user for the terminal device. context, and record the association relationship between the access management connection identifier and the mobility management connection identifier in the mobility management user context.
  • the mobile management user context created for the terminal device may be associated with the user identifier of the terminal device for querying.
  • the mobility management entity may also perform message (or signaling) interaction with other network entities (such as a session management entity) to assign a temporary user identifier to a terminal device.
  • the mobility management entity may create a session management session through a protocol data unit (protocol data unit, PDU) session carrying the second connection request message
  • PDU protocol data unit
  • the following request message forwards the second connection request message to the session management entity, and receives the PDU session creation session management context response message from the session management entity, wherein the PDU session creation session management context response message carries the user temporary identifier allocated for the terminal device .
  • the mobility management entity may also send a user registration status update request message to the user context addressing entity, where the user registration status update request may carry the information of the mobility management entity, registration status (such as registered), And the user identification information of the terminal device, wherein the user identification information of the terminal device may be one or more of the SUPI of the terminal device, the temporary user identification (such as the allocated GUTI) assigned to the terminal device, and the like.
  • the user context addressing entity After the user context addressing entity receives the user registration status update request message, it can update the user registration status of the terminal device, for example, update the user identification information, registration status and information of the corresponding mobility management entity of the terminal device to the user registration status saved by itself. information sheet.
  • the user context addressing entity may also send a user registration status update response message to the access management entity, informing the access management entity of completing the update of the user registration status.
  • the mobility management entity sends a second connection response message to the access management entity, and the access management entity receives the second connection response message, where the second connection response message is used to indicate connection information between the access management entity and the mobility management entity.
  • the second connection response message may include the access management connection identifier carried in the second connection request message, and the mobility management connection identifier associated with the access management connection identifier created (or allocated) by the mobility management entity, thereby indicating that the access management Enter the connection information between the management entity and the mobility management entity.
  • the access management entity may save the association relationship between the access management connection identifier and the mobility management connection identifier in the access management user context.
  • the second connection response message may also include the registration status (for example, registered) of the terminal device, the user's temporary ID, the user's network ID, and the like. It is convenient for the access management entity to quickly determine the mobility management entity that the terminal device has registered with based on the registration information of the terminal device when the terminal device accesses the user network next time, and the terminal device can send information to the user network according to the temporary user ID and the user network ID. Sending messages, signaling, or data, etc., and subsequently re-connecting to the user network, etc.
  • the registration status for example, registered
  • the access management entity it is convenient for the access management entity to quickly determine the mobility management entity that the terminal device has registered with based on the registration information of the terminal device when the terminal device accesses the user network next time, and the terminal device can send information to the user network according to the temporary user ID and the user network ID. Sending messages, signaling, or data, etc., and subsequently re-connecting to the user network, etc.
  • the access management entity sends a first connection response message to the access network device.
  • the access network device receives the first connection response message.
  • the first connection response message is used to indicate the connection between the access network device and the access management entity. connection information.
  • the first connection response message may include the access network connection identifier carried in the first connection request message, and the access management connection identifier created (or allocated) by the access management entity and associated with the access network connection identifier. Thereby indicating the connection information between the access management entity and the access network equipment.
  • the first connection response message may also include the registration status (such as registered), user temporary identifier and user network identifier of the terminal device in the second connection response message.
  • the access network device may save the association relationship between the access network connection identifier and the access management connection identifier in the access network user context.
  • the access network device sends a user connection response message to the terminal device, and correspondingly, the terminal device receives the user connection response message.
  • the access network device may query the wireless connection identifier associated with the access network connection identifier according to the access network connection identifier in the first connection response message, and may send the user connection identifier carrying the wireless connection identifier to the terminal device according to the wireless connection identifier. Respond to the message.
  • the user connection response message may also carry the registration status (such as registered) of the above-mentioned terminal device, the user temporary ID and the user network ID.
  • the terminal device can record information such as user network identification and user temporary identification, which are used to send messages to the user network, Signaling, or data, etc., and subsequent re-access to the user network, etc.
  • the indirect mode connection of the access network equipment to the mobility management entity through the access management entity can be established.
  • the terminal equipment can be connected to the mobility management entity through the access network equipment through the access management entity, and through the access network equipment and the mobility management entity.
  • the access management entity performs message (or signaling) interaction with the mobility management entity.
  • the access network connection identifier may be included in the second connection request message
  • the mobility management connection identifier may be included in the first connection response message
  • the mobility management entity may also use the mobility management user context saved by itself. Record the association relationship between the access network connection ID and the mobility management connection ID.
  • the access network device can also record the association relationship between the access network connection ID and the mobility management connection ID in the access network user context saved by itself, so as to establish the access network connection ID.
  • the terminal device can also perform message (or signaling) interaction with the mobility management entity through the access network device.
  • the terminal device can access the corresponding user network through the access management entity for different services, and establish a connection with the mobility management entity in the corresponding user network.
  • the terminal device may be an ordinary Internet browsing service, access the user network of the Internet browsing service (such as an enhanced mobile broadband (eMBB) network), and connect to the user network of the Internet browsing service through an access management entity
  • the mobile management entity A in the company's proprietary office service can also access the company's proprietary office user network, and connect to the mobile management entity B in the company's proprietary office user network through the access management entity.
  • the access management entities through which the terminal device connects to the mobility management entity A and the mobility management entity B may be the same or different.
  • different user networks can have different mobility management entities, which can meet the requirements of differentiated evolution that do not affect each other among users.
  • Fig. 7 is the second schematic diagram of the communication method provided by the embodiment of the present application.
  • the solution includes:
  • the terminal device sends a user connection request message to the access network device, where the user connection request message includes user access information, and correspondingly, the access network device receives the user connection request message.
  • the access network device sends a MME addressing request message to the AME, and correspondingly, the AME receives the MME addressing request message, and the MME addressing request message includes user access information.
  • the implementation of the access network device selecting the access management entity that receives the addressing request message of the mobility management entity may refer to the implementation in S402 above, and will not be repeated here.
  • the access management entity can also interact with the terminal device and other network devices, such as the authentication service entity, the unified data management entity, etc., to complete the authentication of the terminal device's access to the user network. right. For example: according to the information of the user network, it is authenticated whether the current access management entity can serve the user network that the terminal device requests to access.
  • the access management entity sends a MME addressing response message to the access network device.
  • the access network device receives the MME addressing response message.
  • the MME addressing response message includes the information of the MME.
  • the information of the mobility management entity may be the ID or IP address of the mobility management entity.
  • the user access information includes user identification and user network information.
  • the access management entity After the access management entity receives the addressing request message of the mobility management entity, it can search for the association with the user identification through the user context addressing entity according to the user access information, and The mobility management entity supporting the user network may also query the mobility management entity supporting the user network through the user network addressing entity, and send the information of the queried mobility management entity to the access network device through the mobility management entity addressing response message.
  • the implementation of how the access management entity determines the mobility management entity according to the user access information may refer to the implementation in S403 above, and details will not be repeated here.
  • the access network device sends a third connection request message to the mobility management entity.
  • the mobility management entity receives the third connection request message, and the third connection request message is used to request establishment of a connection between the access network device and the mobility management entity. connect.
  • the third connection request message may include an access network connection identifier, which is used for establishing a connection between the access network device and the mobility management entity.
  • the mobility management entity can create a mobility management connection identifier associated with the access network connection identifier, and can create a mobility management user context for the terminal device, and in the mobility management user
  • the association relationship between the access network connection identifier and the mobility management connection identifier is recorded in the context.
  • the mobile management user context created for the terminal device may be associated with the user identifier of the terminal device for querying.
  • the mobility management entity may also perform message (or signaling) interaction with other network entities (such as a session management entity) to assign a temporary user identifier to a terminal device.
  • the mobility management entity may transmit the third connection request message to the session management entity through the PDU session carrying the third connection request message to create a session management context request message, and receive the PDU session creation session management context response message from the session management entity , wherein the PDU session creation session management context response message carries the user temporary identifier allocated for the terminal device.
  • the mobility management entity may also send a user registration status update request message to the user context addressing entity, where the user registration status update request may carry the information of the mobility management entity, registration status (such as registered), and user identification information of the terminal device.
  • the user context addressing entity After the user context addressing entity receives the user registration status update request message, it can update the user registration status of the terminal device, for example, update the user identification information, registration status and information of the corresponding mobility management entity of the terminal device to the user registration status saved by itself. information sheet.
  • the user context addressing entity may also send a user registration status update response message to the access management entity, informing the access management entity of completing the update of the user registration status.
  • the mobility management entity sends a third connection response message to the access management entity, and correspondingly, the access management entity receives the third connection response message, where the third connection response message is used to indicate the connection between the access network device and the mobility management entity connection information.
  • the third connection response message may include the access network connection identifier and the mobility management connection identifier associated with the access network connection identifier created (or allocated) by the mobility management entity, thereby indicating the connection between the access network device and the mobility management entity connection information.
  • the third connection response message may also include the registration status (registered) of the terminal device, the user temporary identifier and the user network identifier.
  • the access network device may save the association relationship between the access network connection identifier and the mobility management connection identifier in the access network user context.
  • the access network device sends a user connection response message to the terminal device, and correspondingly, the terminal device receives the user connection response message.
  • the access network device may query the wireless connection identifier associated with the access network connection identifier according to the access network connection identifier in the third connection response message, and may send a user connection response carrying the wireless connection identifier to the terminal device according to the wireless connection identifier information.
  • the user connection response message may also carry the registration status (registered) of the above-mentioned terminal equipment, User Temporary ID and User Network ID.
  • the terminal device can record information such as the user network identifier and the user temporary identifier, and use it for sending messages, signaling, or data to the user network, and subsequently re-connecting to the user network.
  • a direct mode connection between the access network device and the mobility management entity can be established, and the terminal device can be connected to the mobility management entity through the access network device, and exchange messages (or signaling) with the mobility management entity through the access network device interact.
  • the terminal device can be connected to the mobility management entity through the access network device, and exchange messages (or signaling) with the mobility management entity through the access network device interact.
  • the terminal device actively triggers access to the user network when the terminal device has service data to be sent to the user network.
  • the user network When there is data to be sent to the terminal device, if the terminal device is not connected to the user network, the user network can also initiate paging to the terminal device, instructing the terminal device to access the user network.
  • the other network entity may send a message including the user identifier of the terminal device to the user context addressing entity.
  • User addressing request message wherein the user identifier can be the permanent user identifier of the terminal device, such as SUPI, or the temporary user identifier assigned to the terminal device by the user network before, such as GUTI, or the IP address of the terminal device.
  • the user context addressing entity can query the registration information corresponding to the terminal device according to the user identifier, such as the information of the mobile management entity corresponding to the terminal device (such as the fully qualified domain name (fully qualified domain name, FQDN) of the mobile management entity, or the IP address ), and the registration status of the end device.
  • the user context addressing entity may reply to other network entities with a user addressing response message carrying the information of the mobility management entity, and the user addressing response message may also carry user registration information.
  • Other network entities can send a network request message carrying the user identifier of the terminal device to the corresponding mobility management entity according to the information of the mobility management entity included in the user addressing response message. After the mobility management entity receives the user request message from other network entities, if there is no mobility management entity context corresponding to the terminal device, it needs to initiate paging for the terminal device.
  • the mobility management entity may, according to the historical access information of the terminal device, such as the information of the access management entity that the terminal device has accessed, and the paging policy of the mobility management entity, etc., A first paging request message is sent to the access management entity.
  • the mobility management entity may send a message including terminal
  • the first paging request message is the user identification of the device and the information of the user network.
  • the mobility management entity can All the access management entities within a certain range of the management entity send the first paging request message including the user identifier of the terminal equipment and the information of the user network. If the paging policy of the mobility management entity is to initiate paging to the network-wide access management entity, the mobility management entity sends a first paging request message including the user identifier of the terminal device and the information of the user network to the network-wide access management entity.
  • the paging policy of the mobility management entity can also be to initiate paging to the access management entity that the terminal equipment has accessed in history first. The terminal device is not connected to the user network, but is connected to the access management entity), and then initiates paging to the network-wide access management entity.
  • the access management entity may also access information according to the history of the terminal equipment, such as The information of the access network device that the terminal device has accessed and the paging policy of the access management entity forward the first paging request message to the access network device.
  • the access network device can send a paging message including user identification and user network information to terminal devices within the coverage of the access network device, and initiate paging to the terminal devices.
  • the mobility management entity may also access information based on the historical access information of the terminal device, such as information about the access network device that the terminal device has accessed, and the information of the mobility management entity
  • the paging strategy and the like directly send the second paging request message to the access network device.
  • the paging policy of the mobility management entity is to initiate paging to access network devices that the terminal device has accessed in history
  • the mobility management entity sends a paging message to all access network devices that the terminal device has accessed, including the The user identification and user network information of the second paging request message.
  • the access network device can send a paging message including user identification and user network information to terminal devices within the coverage of the access network device, and initiate paging to the terminal devices.
  • the terminal device After receiving the paging message, the terminal device can answer the paging, such as accessing the user network in the manner shown in FIG. 4 and FIG. 7 .
  • the terminal device and the user network can exchange messages (or signaling) to transmit service data.
  • the access network device and the mobility management entity are connected through the direct mode or through the indirect mode
  • the terminal device initiates the user request message and the mobility management entity initiates the network request message, how the terminal device and the network device perform message processing Explain interactively.
  • Case 1 When the access network device and the mobility management entity are connected through an indirect mode, the terminal device initiates a user request message, and the terminal device and the network device perform message interaction.
  • the method includes:
  • the terminal device sends a third user request message to the access network device, and correspondingly, the access network device receives the third user request message, where the third user request message includes a wireless connection identifier.
  • the terminal device When the terminal device is already connected to the user network and connected to the mobility management entity, it means that the terminal device has been registered with a certain mobility management entity and has obtained the temporary user identifier.
  • the terminal device When the terminal device has service data to send to the user network, it can send a third user request message including the user temporary identifier and service data to the access network device, and carry the information when the terminal device accesses the user network in the third user request message.
  • the access network device sends a first user request message to the access management entity.
  • the access management entity receives the first user request message, where the first user request message includes an access management connection identifier.
  • the access network device may, according to the wireless connection identifier carried in the third user request message, the association relationship between the wireless connection identifier and the access network connection identifier recorded by itself, and the connection The association relationship between the network access connection identifier and the access management connection identifier determines the access network connection identifier associated with the wireless connection identifier and the access management connection identifier associated with the wireless connection identifier. According to the access management connection identifier, the access network device can send the first user request message to the access management entity. Wherein the first user request message may be used to forward the third user request message.
  • the access management connection identifier may be included in the first user request message, and optionally, the access network connection identifier may also be included.
  • the third user request message or specific data in the third user request message may be carried in the first user request message.
  • the access network device may re-encapsulate the packet carrying the third user request message, and add a packet header for sending the message to the access management entity. It is also possible to re-encapsulate the message carrying the third user request message, and replace the message header of the message carrying the third user request message with the message header used to send the message to the access management entity, so as to send the message to the access management entity.
  • the management entity sends a first user request message.
  • the access management entity sends a second user request message to the mobility management entity, and correspondingly, the mobility management entity The entity receives the second user request message, where the second user request message includes the mobility management connection identifier.
  • the access management entity After the access management entity receives the first user request message, it may determine the connection with the access management entity according to the access management connection identifier carried in the first user request message and the association relationship between the access management connection identifier and the mobility management connection identifier recorded by itself.
  • the mobile management connection ID associated with the management connection ID.
  • the access management entity can send the second user request message to the mobility management entity.
  • the second user request message may be used to forward the first user request message.
  • the mobility management connection identifier is included in the second user request message, and optionally, the access management connection identifier may also be included.
  • the mobility management entity sends a second user response message to the access management entity.
  • the access management entity receives the second user response message, where the second user response message includes the access management connection identifier.
  • the mobility management entity After the mobility management entity receives the second user request message, it can process the service data of the terminal device carried in the second user request message with other network entities (such as a session management entity, a user plane entity, etc.) according to the user temporary identifier, And generate business response data.
  • other network entities such as a session management entity, a user plane entity, etc.
  • the mobility management entity may determine the access management connection identifier according to the association relationship between the mobility management connection identifier carried in the second user request message and the access management connection identifier and the mobility management connection identifier recorded by itself . According to the access management connection identifier, the mobility management entity can send the second user response message to the access management entity.
  • the second user response message includes the access management connection identifier and the above service response data, and may also include the mobility management connection identifier.
  • the access management entity sends a first user response message to the access network device, and correspondingly, the access network device receives the first user response message, where the first user response message includes the access network connection identifier.
  • the access management entity may determine the access management connection identifier according to the access management connection identifier carried in the second user response message and the association relationship between the access management connection identifier and the access network connection identifier recorded by itself. Network connection logo. According to the access network connection identifier, the access management entity may send the first user response message to the access network device. Wherein the first user response message may be used to forward the second user response message.
  • the first user response message includes the access network connection identifier, and optionally, may also include the access management connection identifier.
  • the access network device sends a third user response message to the terminal device, and correspondingly, the terminal device receives the third user response message, where the third user response message includes the wireless connection identifier.
  • the access network device may determine the connection with the access network according to the access network connection identifier carried in the first user response message and the association relationship between the wireless connection identifier and the access network connection identifier recorded by itself.
  • the wireless connection ID associated with the connection ID.
  • the access network device can send a third user response message to the terminal device, where the third user response message can be used to forward the first user response message.
  • Case 2 When the access network device and the mobility management entity are connected through the direct mode, the terminal device initiates a user request message, and the terminal device and the network device perform a message interaction process.
  • the method includes:
  • the terminal device sends a third user request message to the access network device, and correspondingly, the access network device receives the third user request message, where the third user request message includes a wireless connection identifier.
  • the terminal device When the terminal device is already connected to the user network and connected to the mobility management entity, it means that the terminal device has been registered with a certain mobility management entity and has obtained the temporary user identifier.
  • the terminal device When the terminal device has service data to send to the user network, it can send a third user request message including the user temporary identifier and service data to the access network device, and carry the information when the terminal device accesses the user network in the third user request message.
  • the access network device sends a fourth user request message to the mobility management entity.
  • the access management entity receives the fourth user request message, where the fourth user request message includes the mobility management connection identifier.
  • the access network device may, according to the wireless connection identifier carried in the third user request message, the association relationship between the wireless connection identifier and the access network connection identifier recorded by itself, and the connection The association relationship between the network access connection identifier and the mobility management connection identifier determines the access network connection identifier associated with the wireless connection identifier, and the mobility management connection identifier associated with the wireless connection identifier. According to the mobility management connection identifier, the access network device can send the fourth user request message to the mobility management entity. The fourth user request message may be used to forward the third user request message.
  • the fourth user request message may include the mobility management connection identifier of the mobility management entity, and optionally, may also include the access network connection identifier of the access network device.
  • the third user request message or specific data in the third user request message may be carried in the fourth user request message.
  • the mobility management entity sends a fourth user response message to the access network device, and correspondingly, the access network device receives the fourth user response message, where the fourth user response message includes the access network connection identifier.
  • the mobile management entity After the mobile management entity receives the fourth user request message, it can process the service data of the terminal device carried in the fourth user request message with other network entities (such as the session management entity, the user plane entity, etc.) according to the user temporary identifier, and Generate business response data.
  • other network entities such as the session management entity, the user plane entity, etc.
  • the mobility management entity may determine the access network connection identifier according to the association relationship between the mobility management connection identifier carried in the fourth user request message and the access network connection identifier and the mobility management connection identifier recorded by itself . According to the access network connection identifier, the mobility management entity can send the fourth user response message to the access network device.
  • the fourth user response message includes the access network connection identifier and service response data, and optionally, may also include the mobility management connection identifier.
  • the access network device sends a third user response message to the terminal device, and correspondingly, the terminal device receives the third user response message, where the third user response message includes the wireless connection identifier.
  • the access network device may determine the connection with the access network according to the access network connection identifier carried in the fourth user response message and the association relationship between the wireless connection identifier and the access network connection identifier recorded by itself.
  • the wireless connection ID associated with the connection ID.
  • the access network device can send a third user response message to the terminal device, where the third user response message can be used to forward the fourth user response message.
  • the access network device receives the third user request message from the terminal device, it is based on the recorded association relationship between the access network connection identifier and the access management connection identifier, or the connection relationship between the access network connection identifier and the mobility management
  • the second user request message or the fourth user request message is sent using the association relationship identified by the connection identifier. It does not perceive whether the purpose of the sent message is the access management entity (ie, indirect mode connection with the mobility management entity) or the mobility management entity (ie, direct mode connection with the mobility management entity).
  • Case 3 When the access network device and the mobility management entity are connected through an indirect mode, the mobility management entity initiates a network request message, and the terminal device and the network device perform message interaction.
  • the method includes:
  • the mobility management entity sends a first network request message to the access management entity.
  • the access management entity receives the first network request message, where the first network request message includes an access management connection identifier.
  • the user network entities may send the user context addressing entity including the The user addressing request message of the user ID, wherein the user ID may be a permanent user ID of the terminal device, such as SUPI, or a temporary user ID of the terminal device, such as GUTI, or an IP address of the terminal device.
  • the user ID may be a permanent user ID of the terminal device, such as SUPI, or a temporary user ID of the terminal device, such as GUTI, or an IP address of the terminal device.
  • the user context addressing entity can query the registration information corresponding to the terminal device according to the user identifier, such as the information of the mobile management entity corresponding to the terminal device (such as the FQDN of the mobile management entity, or the IP address), and the registration status of the terminal device.
  • the user context addressing entity may reply to other network entities with a user addressing response message carrying the information of the mobility management entity, and the user addressing response message may also carry user registration information.
  • Other network entities can send the network request message carrying the user identification and service data of the terminal device to the corresponding mobility management entity according to the information of the mobility management entity included in the user addressing response message.
  • the mobility management entity can, according to the context of the mobility management entity corresponding to the terminal device, such as the association between the access management connection identifier and the mobility management connection identifier associated with the user identifier of the terminal device relationship to determine the access management connection ID.
  • the mobility management entity can send a first network request message to the access management entity, wherein the first network request message can be used to forward user request messages sent by other network entities to the mobility management entity.
  • the access management connection identifier is included in the first network request message, and optionally, the mobility management connection identifier may also be included.
  • the access management entity sends a second network request message to the access network device, and correspondingly, the access network device receives the second network request message, where the second network request message includes the access network connection identifier.
  • the access management entity may determine the access management connection identifier according to the access management connection identifier carried in the first network request message and the association relationship between the access management connection identifier and the access network connection identifier recorded by itself. Network connection logo. According to the access network connection identifier, the access management entity may send the second network request message to the access network device. Wherein the second network request message may be used to forward the first network request message.
  • the access network connection identifier is included in the first network request message, and optionally, the access management connection identifier may also be included.
  • the access network device sends a third network request message to the terminal device, and correspondingly, the terminal device receives the third network request message, where the third network request message includes a wireless connection identifier.
  • the access network device may determine the connection with the access network according to the access network connection identifier carried in the second network request message and the association relationship between the wireless connection identifier and the access network connection identifier recorded by itself.
  • the wireless connection ID associated with the connection ID.
  • the access network device can send a third network request message to the terminal device, where the third network request message can be used to forward the second network request message.
  • the method includes:
  • the mobility management entity sends a fourth network request message to the access network device, and correspondingly, the access network device receives the fourth network request message, where the fourth network request message includes an access network connection identifier.
  • the other network entity may send a message including the user identifier of the terminal device to the user context addressing entity.
  • the user identifier may be a permanent user identifier of the terminal device, such as SUPI, or a temporary user identifier of the terminal device, such as GUTI, or an IP address of the terminal device.
  • the user context addressing entity can query the registration information corresponding to the terminal device according to the user ID, such as the information of the mobility management entity corresponding to the terminal device (such as the FQDN of the mobility management entity, or the IP address), and the terminal device the registration status of .
  • the user context addressing entity may reply to other network entities with a user addressing response message carrying the information of the mobility management entity, and the user addressing response message may also carry user registration information.
  • Other network entities can send the network request message carrying the user identification and service data of the terminal device to the corresponding mobility management entity according to the information of the mobility management entity included in the user addressing response message.
  • the mobility management entity can, according to the context of the mobility management entity corresponding to the terminal device, such as the association between the access network connection identifier and the mobility management connection identifier associated with the user identifier of the terminal device relationship to determine the access network connection identifier.
  • the mobility management entity can send a fourth network request message to the access network device, where the fourth network request message can be used to forward user request messages sent by other network entities to the mobility management entity.
  • the fourth user response message includes the access network connection identifier, and optionally, may also include the mobility management connection identifier.
  • the access network device sends a fifth network request message to the terminal device, and correspondingly, the terminal device receives the fifth network request message, where the fifth network request message includes a wireless connection identifier.
  • the access network device may determine the connection with the access network according to the access network connection identifier carried in the fourth network request message and the association relationship between the wireless connection identifier and the access network connection identifier recorded by itself.
  • the wireless connection ID associated with the connection ID.
  • the access network device can send a fifth network request message to the terminal device, where the fifth network request message can be used to forward the fourth network request message.
  • the access network device, the access management entity, and the mobility management entity include hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software with reference to the units and method steps of the examples described in the embodiments disclosed in the present application. Whether a certain function is executed by hardware or computer software drives the hardware depends on the specific application scenario and design constraints of the technical solution.
  • FIG. 14 and FIG. 15 are schematic structural diagrams of possible communication devices provided by the embodiments of the present application. These communication devices can be used to realize the functions of the access network device, the access management entity, and the mobility management entity in the above method embodiments, and thus can also realize the beneficial effects of the above method embodiments.
  • the communication device may be an access network device as shown in Figure 2, or an access management entity as shown in Figure 2, or a mobility management entity as shown in Figure 2 , may also be a module (such as a chip) applied to an access network device, an access management entity, or a mobility management entity.
  • a communication device 1400 includes a processing unit 1410 and an interface unit 1420 , where the interface unit 1420 may also be a transceiver unit or an input-output interface.
  • the communication apparatus 1400 may be used to realize the functions of the access network device, the access management entity or the mobility management entity in the method embodiments shown in FIGS. 4-13 above.
  • the interface unit 1420 is configured to receive a first connection request message from the access network device, the first connection request message includes user access information, and is used to request establishment of a connection between the access network device and the mobility management entity; the processing unit 1410 , for sending a second connection request message to the mobility management entity through the interface unit 1420 based on the first connection request message, where the second connection request message is used to request establishment of a connection between the access management entity and the mobility management entity, wherein the mobility management The entity is determined by the access management entity according to the user access information; the interface unit 1420 is also configured to receive a second connection response message from the mobility management entity, and the second connection response message is used to indicate the connection between the access management entity and the mobility management entity and sending a first connection response message to the access network device, where the first connection response message is used to indicate the connection information between the access network device and the access management entity.
  • the first connection request message further includes the access network connection identifier of the access network device, and the second The connection request message includes the access management connection identifier of the access management entity; the connection information between the access management entity and the mobility management entity includes the association relationship between the access management connection identifier and the mobility management connection identifier of the mobility management entity; The connection information between the device and the access management entity includes the association relationship between the access management connection identifier and the access network connection identifier.
  • the user access information includes user identification and user network information
  • the processing unit 1410 sends the second connection request message to the mobility management entity through the interface unit 1420 based on the first connection request message, it is specifically used to According to the information of the user identifier and the user network, determine that the mobility management entity associated with the user identifier and supporting the user network is the mobility management entity that receives the second connection request message.
  • the user access information includes user network information, and when the processing unit 1410 sends the second connection request message to the mobility management entity through the interface unit 1420 based on the first connection request message, it is specifically configured to determining a list of mobility management entities supporting the user network; determining a mobility management entity in the mobility management entity list as the mobility management entity receiving the second connection request message.
  • the second connection request message further includes an access network connection identifier
  • the first connection response message further includes an association relationship between the access network connection identifier and the mobility management connection identifier.
  • the interface unit 1420 is also configured to receive a first paging request message from the mobility management entity, where the first paging request message includes the user identifier of the terminal device and information about the user network; The network device forwards the first paging request message.
  • the interface unit 1420 is also configured to receive a first user request message from the access network device, where the first user request message includes an access management connection identifier; and send a second user request message to the mobility management entity , the second user request message includes a mobility management connection identifier, wherein the mobility management connection identifier is determined by the processing unit 1410 according to the association relationship between the access management connection identifier and the mobility management connection identifier; the interface unit 1420 is also configured to receive The second user response message, the second user response message includes the access management connection identifier; and sends the first user response message to the access network device, the first user response message includes the access network connection identifier, wherein the access network connection identifier It is determined by the processing unit 1410 according to the association relationship between the access management connection identifier and the access network connection identifier.
  • the interface unit 1420 is also configured to receive a first network request message from the mobility management entity, where the first network request message includes an access management connection identifier; and send a second network request message to the access network device , the second network request message includes the access network connection identifier, where the access network connection identifier is determined by the processing unit 1410 according to the association relationship between the access management connection identifier and the access network connection identifier.
  • the interface unit 1420 is configured to receive a mobility management entity addressing request message from the access network device, where the mobility management entity addressing request message includes user access information; the interface unit 1420 is also configured to send the mobile The management entity addressing response message, the mobility management entity addressing response message includes the information of the mobility management entity, and the mobility management entity is determined by the processing unit 1410 according to the user access information.
  • the user access information includes user identification and user network information.
  • the processing unit 1410 determines the mobility management entity according to the user access information, it is specifically configured to determine the Identifies the mobility management entity that is associated and supports the user network.
  • the user access information includes user network information, and when the processing unit 1410 determines the mobility management entity according to the user access information, it is specifically configured to determine the mobility management entity supporting the user network according to the user network information. list; and determining a mobility management entity in the mobility management entity list as the mobility management entity indicated by the mobility management entity information carried in the mobility management entity address response message.
  • the interface unit 1420 is configured to receive a second connection request message from the access management entity, and the second connection request message is used to request establishment of a connection between the access management entity and the mobility management entity; the processing unit 1410 is configured to determine the second The connection response message, the second connection response message is used to indicate the connection information between the access management entity and the mobility management entity; the interface unit 1420 is also used to send the second connection response message.
  • the second connection request message includes the access management connection identifier of the access management entity; the connection information between the access management entity and the mobility management entity includes the access management connection identifier and the mobility of the mobility management entity.
  • the interface unit 1420 is further configured to send a first paging request message to the access management entity, where the first paging request message includes the user identifier of the terminal device and information about the user network;
  • the network access device sends a second paging request message, where the second paging request message includes the user identifier of the terminal device and the information of the user network.
  • the interface unit 1420 is also configured to receive a second user request message from the access management entity, where the second user request message includes the mobility management connection identifier; and send the second user response to the access management entity message, the second user response message includes the access management connection identifier, where the access management connection identifier is determined by the processing unit 1410 according to the association relationship between the access management connection identifier and the mobility management connection identifier.
  • the interface unit 1420 is further configured to send a first network request message to the access management entity, where the first network request message includes an access management connection identifier, and the access management connection identifier is the It is determined by the association relationship between the incoming management connection ID and the mobile management connection ID.
  • the interface unit 1420 is configured to receive a third connection request message from the access network device, the third connection request message is used to request establishment of a connection between the access network device and the mobility management entity; the processing unit 1410 is configured to determine A third connection response message, where the third connection response message is used to indicate connection information between the access network device and the mobility management entity; the interface unit 1420 is also configured to send the third connection response message to the access network device.
  • the third connection request message includes the access network connection identifier of the access network device; the connection information between the access network device and the mobility management entity includes the mobility management connection identifier and the access The association relationship of network connection identification.
  • the interface unit 1420 is further configured to send a second paging request message to the access network device, where the second paging request message includes the user identifier of the terminal device and information of the user network.
  • the processing unit 1410 is configured to determine a first connection request message, the first connection request message includes user access information, and is used to request to establish a connection between the access network device and the mobility management entity; the interface unit 1420 is configured to send the access network device The management entity sends a first connection request message; and receives a first connection response message from the access management entity, where the first connection response message is used to indicate connection information between the access network device and the access management entity.
  • the first connection request message further includes the access network connection identifier of the access network device; the connection information between the access network device and the access management entity includes the access management connection identifier of the access management entity The association relationship between the identifier and the access network connection identifier.
  • the user access information includes user identification and user network information.
  • the first connection response message further includes the mobility management connection identifier of the mobility management entity
  • the processing unit 1410 is further configured to record the association relationship between the mobility management connection identifier and the access network connection identifier of the access network device .
  • the interface unit 1420 is further configured to receive a first paging request from the access management entity, where the first paging request includes the user identifier of the terminal device and information about the user network; the processing unit 1410 is also configured to It is used to send a paging message to the terminal device through the interface unit 1420, where the paging message includes user identification and user network information; or, The interface unit 1420 is also configured to receive a second paging request from the mobility management entity, where the second paging request includes the user identifier of the terminal device and the information of the user network; the processing unit 1410 is also configured to send the terminal device a Send a paging message, the paging message includes user identification and user network information.
  • the processing unit 1410 is configured to determine a third connection request message, where the third connection request message is used to request establishment of a connection between the access network device and the mobility management entity; the interface unit 1420 is configured to send the third connection request message to the mobility management entity a connection request message; and receiving a third connection response message from the mobility management entity, where the third connection response message is used to indicate connection information between the access network device and the mobility management entity.
  • the third connection request message includes the access network connection identifier of the access network device; the connection information between the access network device and the mobility management entity includes the mobility management connection identifier and the access The association relationship of network connection identification.
  • the interface unit 1420 is also configured to send a mobility management entity addressing request message to the access management entity, where the mobility management entity addressing request message includes user access information; and receive a message from the access management entity
  • the MME addressing response message, the MME addressing response message includes the information of the MME.
  • the user access information includes user identification and user network information.
  • the interface unit 1420 is also configured to receive a second paging request from the mobility management entity, where the second paging request includes the user identifier of the terminal device and information about the user network; the processing unit 1410 is also configured to To send a paging message to the terminal device through the interface unit 1420, the paging message includes user identification and user network information.
  • the present application also provides a communication device 1500 , including a processor 1510 and an interface circuit 1520 .
  • the processor 1510 and the interface circuit 1520 are coupled to each other.
  • the interface circuit 1520 may be a transceiver, an input and output interface, an input interface, an output interface, a communication interface, and the like.
  • the communication device 1500 may further include a memory 1530 for storing instructions executed by the processor 1510 or storing input data required by the processor 1510 to execute the instructions or storing data generated by the processor 1510 after executing the instructions.
  • the memory 1530 may also be integrated with the processor 1510.
  • the processor 1510 may be used to implement the functions of the processing unit 1410 described above, and the interface circuit 1520 may be used to implement the functions of the interface unit 1420 described above.
  • processor in the embodiments of the present application may be a central processing unit (central processing unit, CPU), and may also be other general processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), logic circuit, field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • a general-purpose processor can be a microprocessor, or any conventional processor.
  • the method steps in the embodiments of the present application may be implemented by means of hardware, or may be implemented by means of a processor executing software instructions.
  • Software instructions can be composed of corresponding software modules, and software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only Memory, registers, hard disk, removable hard disk, CD-ROM or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium.
  • the storage medium may also be a component of the processor.
  • the processor and storage medium can be located in the ASIC.
  • the ASIC can be located in a network device or a terminal device. Certainly, the processor and the storage medium may also exist in the network device or the terminal device as discrete components.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program produces Products consist of one or more computer programs or instructions.
  • the processes or functions described in the embodiments of the present application are executed in whole or in part.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, network equipment, user equipment, or other programmable devices.
  • the computer program or instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program or instructions may be transmitted from a network device, terminal, A computer, server or data center transmits to another network device, terminal, computer, server or data center through wired or wireless means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrating one or more available media.
  • the available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a digital video disk; or it may be a semiconductor medium, such as a solid-state hard disk.
  • the computer readable storage medium may be a volatile or a nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

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年01月29日提交中国国家知识产权局、申请号为202210112910.3、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
在无线通信系统中，通常由接入和移动性管理实体提供接入管理功能和移动管理功能。例如：接入和移动性管理实体可以为网络提供接入鉴权、接入授权等接入管理功能，还能为用户提供会话管理信令通道等移动管理功能。
然而，接入管理的处理对象是网络接入能力，关注终端设备位置与接入网(access network，AN)的连接，移动管理的处理对象是用户的移动管理能力，关注用户的业务功能，接入管理和移动管理两者的容量规划，部署位置，可用性要求存在着差异。并且随着网络的不断演进，还面临着用户定制移动管理，需要不断部署满足各种移动管理需求的接入和移动性管理实体的问题。
发明内容
本申请实施例提供一种通信方法及装置，有利于满足接入管理和移动管理的独立建立、独立控制和独立演进的需求。
第一方面，本申请实施例提供一种通信方法，该方法包括：接入网设备向接入管理实体发送第一连接请求消息，第一连接请求消息包括用户接入信息，用于请求建立接入网设备至移动管理实体之间的连接；接入管理实体接收第一连接请求消息，以及基于第一连接请求消息，向移动管理实体发送第二连接请求消息，第二连接请求消息用于请求建立接入管理实体与移动管理实体之间的连接，其中移动管理实体是接入管理实体根据用户接入信息确定的；移动管理实体接收第二连接请求消息，以及向接入管理实体发送第二连接响应消息，第二连接响应消息用于指示接入管理实体与移动管理实体之间的连接信息；接入管理实体接收第二连接响应消息，以及向接入网设备发送第一连接响应消息，第一连接响应消息用于指示接入网设备与接入管理实体之间的连接信息；接入网设备接收第二连接响应消息。
采用上述通信方法，接入管理和移动管理的功能可以分别由接入管理实体和移动管理实体实现，能够解耦接入管理和移动管理，一个接入管理实体，可以对应多个用户网络的多个移动管理实体，不同的用户网络可以不再共享移动管理实体，有利于满足接入管理和移动管理的独立建立、独立控制和独立演进的需求，满足接入管理和移动管理差异化的容量规划、部署位置、可用性要求。
在一种可能的设计中，第一连接请求消息还包括接入网设备的接入网连接标识，第二连接请求消息包括接入管理实体的接入管理连接标识；接入管理实体与移动管理实体之间的连接信息包括接入管理连接标识和移动管理实体的移动管理连接标识的关联关系；接入网设备与接入管理实体之间的连接信息包括接入管理连接标识和接入网连接标识的关联关系。
上述设计中，在终端设备接入用户网络时，通过接入网连接标识和接入管理连接标识、以及接入管理连接标识和移动管理连接标识的关联关系，能够在接入网设备和接入管理实体之间建立连接，使能终端设备可以通过接入网设备连接到移动管理实体，满足终端设备与用户网络的通信需求。
在一种可能的设计中，用户接入信息包括用户标识和用户网络的信息，接入管理实体基于第一连接请求消息，向移动管理实体发送第二连接请求消息，包括：接入管理实体根据用户标识和用户网络的信息，确定与用户标识关联、且支持用户网络的移动管理实体，为接收第二连接请求消息的移动管理实体。作为一种示例：接入管理实体可以根据用户标识和用户网络的信息，通过用户上下文寻址实体查询与用户标识关联、且支持用户网络的移动管理实体，作为接收第二连接请求消息的移动管理实体。
上述设计中，可以根据用户标识和用户网络的信息，通过用户的上下文查询终端设备已连接过，且支持用户网络的移动管理实体，有利于终端设备准确、快速的接入所需的用户网络。
在一种可能的设计中，用户接入信息包括用户网络的信息，接入管理实体基于第一连接请求消息，向移动管理实体发送第二连接请求消息，包括：接入管理实体根据用户网络的信息，确定支持用户网络的移动管理实体的列表；接入管理实体将移动管理实体的列表中的一个移动管理实体，确定为接收第二连接请求消息的移动管理实体。作为一种示例：接入管理实体，可以向用户网络寻址实体发送用户网络寻址请求消息，用户网络寻址请求消息包括用户网络的信息；接收来自用户网络寻址实体的用户网络寻址应答消息，用户网络寻址应答消息包括支持用户网络的移动管理实体的列表；以及将移动管理实体的列表中的一个移动管理实体，确定为接收第二连接请求消息的移动管理实体。
上述设计中，可以根据用户网络的信息，查询已创建的用户网络中是否存在能够为用户提供服务的用户网络，有利于终端设备快速接入所需的用户网络，减少用户网络的资源开销。
在一种可能的设计中，第一连接响应消息还用于指示接入网设备和移动管理实体之间的连接关系，具体的，在一种可能的实现中，第二连接请求消息还包括接入网连接标识，第一连接响应消息还包括接入网连接标识和移动管理连接标识的关联关系。
上述设计中，在终端设备接入用户网络时，接入网设备和移动管理实体通过接入网连接标识和移动管理连接标识的关联关系，能够在接入网设备和移动管理实体之间建立连接，使能终端设备通过接入网设备连接到移动管理实体，满足终端设备与用户网络的通信需求。
在一种可能的设计中，该方法还包括：移动管理实体向接入管理实体发送第一寻呼请求消息，第一寻呼请求消息包括终端设备的用户标识和用户网络的信息；接入管理实体接收第一寻呼请求消息，以及向接入网设备转发第一寻呼请求消息；接入网设备，还用于接收第一寻呼请求消息，向终端设备发送寻呼消息，寻呼消息包括用户标识和用户网络的信息。或者，该方法还包括：移动管理实体向接入网设备发送第二寻呼请求消息，第二寻呼 请求消息包括终端设备的用户标识和用户网络的信息；接入网设备接收第二寻呼消息，以及向终端设备发送寻呼消息，寻呼消息包括用户标识和用户网络的信息。
上述设计中，在寻呼请求消息和寻呼消息中携带用户网络的信息，如用户网络的标识，有利于终端设备准确接入用户网络。
在一种可能的设计中，该方法还包括：接入网设备向接入管理实体发送第一用户请求消息，第一用户请求消息包括接入管理连接标识；接入管理实体接收第一用户请求消息，以及向移动管理实体发送第二用户请求消息，第二用户请求消息包括移动管理连接标识，其中移动管理连接标识是根据接入管理连接标识和移动管理连接标识的关联关系确定的；移动管理实体接收第二用户请求消息，以及向接入管理实体发送第二用户应答消息，第二用户应答消息包括接入管理连接标识，其中接入管理连接标识是根据接入管理连接标识和移动管理连接标识的关联关系确定的；接入管理实体接收第二用户应答消息，以及向接入网设备发送第一用户应答消息，其中第一用户应答消息包括接入网连接标识，其中接入网连接标识是根据接入管理连接标识和接入网连接标识的关联关系确定的；接入网设备，还用于接收第一用户应答。
上述设计中，在终端设备接入用户网络后，接入网设备、接入管理实体和移动管理实体，能够根据接入网连接标识和接入管理连接标识、以及接入管理连接标识和移动管理连接标识的关联关系进行通信，终端设备在有业务数据时，能够通过接入网设备向移动管理实体发送携带业务数据的用户请求消息，满足终端设备与用户网络的通信需求。
在一种可能的设计中，该方法还包括：移动管理实体向接入管理实体发送第一网络请求消息，第一网络请求消息包括接入管理连接标识，接入管理连接标识是根据接入管理连接标识和移动管理连接标识的关联关系确定的；接入管理实体接收第一网络请求消息，以及向接入网设备发送第二网络请求消息，第二网络请求消息包括接入网连接标识，其中接入网连接标识是根据接入管理连接标识和接入网连接标识的关联关系确定的；接入网设备，还用于接收第二网络请求消息。
上述设计中，在终端设备接入用户网络后，接入网设备、接入管理实体和移动管理实体，能够根据接入网连接标识和接入管理连接标识、以及接入管理连接标识和移动管理连接标识的关联关系进行通信，用户网络在有业务数据时，能够通过移动管理实体向终端设备接入的接入网设备发送携带业务数据的网络请求消息，满足用户网络与终端设备的通信需求。
第二方面，本申请实施例提供一种通信方法，该方法包括：接入网设备向移动管理实体发送第三连接请求消息，第三连接请求消息用于请求建立接入网设备与移动管理实体之间的连接；移动管理实体接收第三连接请求消息，以及向接入网设备发送第三连接响应消息，第三连接响应消息用于指示接入网设备与移动管理实体之间的连接信息。可选地，该方法还包括：接入网设备向接入管理实体发送移动管理实体寻址请求消息，移动管理实体寻址请求消息包括用户接入信息；接入管理实体接收移动管理实体寻址请求消息，以及向接入网设备发送移动管理实体寻址响应消息，移动管理实体寻址响应消息包括移动管理实体的信息，移动管理实体是接入管理实体根据用户接入信息确定的；接入网设备接收移动管理实体寻址响应消息。
采用上述通信方法，接入管理和移动管理的功能可以分别由接入管理实体和移动管理实体实现，能够解耦接入管理和移动管理，一个接入管理实体，可以对应多个用户网络的 多个移动管理实体，不同的用户网络可以不再共享移动管理实体，有利于满足接入管理和移动管理的独立建立、独立控制和独立演进的需求，满足接入管理和移动管理差异化的容量规划、部署位置、可用性要求。
在一种可能的设计中，第三连接请求消息包括接入网设备的接入网连接标识；接入网设备与移动管理实体之间的连接信息包括移动管理实体的移动管理连接标识和接入网连接标识的关联关系。
上述设计中，在终端设备接入用户网络时，通过接入网连接标识和移动管理连接标识的关联关系，能够在接入网设备和接入管理实体之间建立连接，使能终端设备可以通过接入网设备连接到移动管理实体，满足终端设备与用户网络的通信需求。
在一种可能的设计中，用户接入信息包括用户标识和用户网络的信息，接入管理实体根据用户接入信息确定移动管理实体，包括：接入管理实体根据用户标识和用户网络的信息，确定与用户标识关联、且支持用户网络的移动管理实体，为移动管理实体寻址响应消息中携带的移动管理实体的信息所指示的移动管理实体。作为一种示例：接入管理实体可以根据用户标识和用户网络的信息，通过用户上下文寻址实体查询与用户标识关联、且支持用户网络的移动管理实体，作为移动管理实体寻址响应消息中携带的移动管理实体的信息所指示的移动管理实体。
上述设计中，可以根据用户标识和用户网络的信息，通过用户的上下文查询终端设备已连接过，且支持用户网络的移动管理实体，有利于终端设备准确、快速的接入所需的用户网络。
在一种可能的设计中，用户接入信息包括用户网络的信息，接入管理实体根据用户接入信息确定移动管理实体，包括：接入管理实体根据用户网络的信息，确定支持用户网络的移动管理实体的列表；以及将移动管理实体的列表中的一个移动管理实体，确定为移动管理实体寻址响应消息中携带的移动管理实体的信息所指示的移动管理实体。作为一种示例：接入管理实体可以向用户网络寻址实体发送用户网络寻址请求消息，用户网络寻址请求消息包括用户网络的信息；接收来自用户网络寻址实体的用户网络寻址应答消息，用户网络寻址应答消息包括支持用户网络的移动管理实体的列表；以及将移动管理实体的列表中的一个移动管理实体，确定为移动管理实体寻址响应消息中携带的移动管理实体的信息所指示的移动管理实体。
上述设计中，可以根据用户网络的信息，查询已创建的用户网络中是否存在能够为用户提供服务的用户网络，有利于终端设备快速接入所需的用户网络，减少用户网络的资源开销。
在一种可能的设计中，该方法还包括：移动管理实体向接入网设备发送第二寻呼请求消息，第二寻呼请求消息包括终端设备的用户标识和用户网络的信息；接入网设备接收第二寻呼消息，向终端设备发送寻呼消息，寻呼消息包括用户标识和用户网络的信息。
上述设计中，在寻呼请求消息和寻呼消息中携带用户网络的信息，如用户网络的标识，有利于终端设备准确接入用户网络。
第三方面，本申请实施例提供一种通信方法，该方法包括：接入管理实体接收来自接入网设备的第一连接请求消息，第一连接请求消息包括用户接入信息，用于请求建立接入网设备至移动管理实体之间的连接；接入管理实体基于第一连接请求消息，向移动管理实体发送第二连接请求消息，第二连接请求消息用于请求建立接入管理实体与移动管理实体 之间的连接，其中移动管理实体是接入管理实体根据用户接入信息确定的；接入管理实体接收来自移动管理实体的第二连接响应消息，第二连接响应消息用于指示接入管理实体与移动管理实体之间的连接信息；接入管理实体向接入网设备发送第一连接响应消息，第一连接响应消息用于指示接入网设备与接入管理实体之间的连接信息。
在一种可能的设计中，第一连接请求消息还包括接入网设备的接入网连接标识，第二连接请求消息包括接入管理实体的接入管理连接标识；接入管理实体与移动管理实体之间的连接信息包括接入管理连接标识和移动管理实体的移动管理连接标识的关联关系；接入网设备与接入管理实体之间的连接信息包括接入管理连接标识和接入网连接标识的关联关系。
在一种可能的设计中，用户接入信息包括用户标识和用户网络的信息，接入管理实体基于第一连接请求消息，向移动管理实体发送第二连接请求消息，包括：接入管理实体根据用户标识和用户网络的信息，确定与用户标识关联、且支持用户网络的移动管理实体，为接收第二连接请求消息的移动管理实体。作为一种示例：接入管理实体可以根据用户标识和用户网络的信息，通过用户上下文寻址实体查询与用户标识关联、且支持用户网络的移动管理实体，作为接收第二连接请求消息的移动管理实体。
在一种可能的设计中，用户接入信息包括用户网络的信息，接入管理实体基于第一连接请求消息，向移动管理实体发送第二连接请求消息，包括：接入管理实体根据用户网络的信息，确定支持用户网络的移动管理实体的列表；接入管理实体将移动管理实体的列表中的一个移动管理实体，确定为接收第二连接请求消息的移动管理实体。作为一种示例：接入管理实体，可以向用户网络寻址实体发送用户网络寻址请求消息，用户网络寻址请求消息包括用户网络的信息；接收来自用户网络寻址实体的用户网络寻址应答消息，用户网络寻址应答消息包括支持用户网络的移动管理实体的列表；以及将移动管理实体的列表中的一个移动管理实体，确定为接收第二连接请求消息的移动管理实体。
在一种可能的设计中，第一连接响应消息还用于指示接入网设备和移动管理实体之间的连接关系，具体的，在一种可能的实现中，第二连接请求消息还包括接入网连接标识，第一连接响应消息还包括接入网连接标识和移动管理连接标识的关联关系。
在一种可能的设计中，该方法还包括：接入管理实体接收来自移动管理实体的第一寻呼请求消息，第一寻呼请求消息包括终端设备的用户标识和用户网络的信息；接入管理实体向接入网设备转发第一寻呼请求消息。
在一种可能的设计中，该方法还包括：接入管理实体接收来自接入网设备的第一用户请求消息，第一用户请求消息包括接入管理连接标识；接入管理实体向移动管理实体发送第二用户请求消息，第二用户请求消息包括移动管理连接标识，其中移动管理连接标识是根据接入管理连接标识和移动管理连接标识的关联关系确定的；接入管理实体接收来自移动管理实体的第二用户应答消息，第二用户应答消息包括接入管理连接标识；接入管理实体向接入网设备发送第一用户应答消息，第一用户应答消息包括接入网连接标识，其中接入网连接标识是根据接入管理连接标识和接入网连接标识的关联关系确定的。
在一种可能的设计中，该方法还包括：接入管理实体接收来自移动管理实体的第一网络请求消息，第一网络请求消息包括接入管理连接标识；接入管理实体向接入网设备发送第二网络请求消息，第二网络请求消息包括接入网连接标识，其中接入网连接标识是根据接入管理连接标识和接入网连接标识的关联关系确定的。
第四方面，本申请实施例提供一种通信方法，该方法包括：接入管理实体接收来自接入网设备的移动管理实体寻址请求消息，移动管理实体寻址请求消息包括用户接入信息；接入管理实体向接入网设备发送移动管理实体寻址响应消息，移动管理实体寻址响应消息包括移动管理实体的信息，移动管理实体是接入管理实体根据用户接入信息确定的。
在一种可能的设计中，用户接入信息包括用户标识和用户网络的信息，接入管理实体根据用户接入信息确定移动管理实体，包括：接入管理实体根据用户标识和用户网络的信息，确定与用户标识关联、且支持用户网络的移动管理实体。作为一种示例：接入管理实体可以根据用户标识和用户网络的信息，通过用户上下文寻址实体查询与用户标识关联、且支持用户网络的移动管理实体，作为移动管理实体寻址响应消息中携带的移动管理实体的信息所指示的移动管理实体。
在一种可能的设计中，用户接入信息包括用户网络的信息，接入管理实体根据用户接入信息确定移动管理实体，包括：接入管理实体根据用户网络的信息，确定支持用户网络的移动管理实体的列表；以及将移动管理实体的列表中的一个移动管理实体，确定为移动管理实体寻址响应消息中携带的移动管理实体的信息所指示的移动管理实体。作为一种示例：接入管理实体可以向用户网络寻址实体发送用户网络寻址请求消息，用户网络寻址请求消息包括用户网络的信息；接收来自用户网络寻址实体的用户网络寻址应答消息，用户网络寻址应答消息包括支持用户网络的移动管理实体的列表；以及将移动管理实体的列表中的一个移动管理实体，确定为移动管理实体寻址响应消息中携带的移动管理实体的信息所指示的移动管理实体。
第五方面，本申请实施例提供一种通信方法，该方法包括：移动管理实体接收来自接入管理实体的第二连接请求消息，第二连接请求消息用于请求建立接入管理实体与移动管理实体之间的连接；移动管理实体向接入管理实体发送第二连接响应消息，第二连接响应消息用于指示接入管理实体与移动管理实体之间的连接信息。
在一种可能的设计中，第二连接请求消息包括接入管理实体的接入管理连接标识；接入管理实体与移动管理实体之间的连接信息包括接入管理连接标识和移动管理实体的移动管理连接标识的关联关系。
在一种可能的设计中，该方法还包括：移动管理实体向接入管理实体发送第一寻呼请求消息，第一寻呼请求消息包括终端设备的用户标识和用户网络的信息；或，移动管理实体向接入网设备发送第二寻呼请求消息，第二寻呼请求消息包括终端设备的用户标识和用户网络的信息。
在一种可能的设计中，该方法还包括：移动管理实体接收来自接入管理实体的第二用户请求消息，第二用户请求消息包括移动管理连接标识；移动管理实体向接入管理实体发送第二用户应答消息，第二用户应答消息包括接入管理连接标识，其中接入管理连接标识是根据接入管理连接标识和移动管理连接标识的关联关系确定的。
在一种可能的设计中，该方法还包括：移动管理实体向接入管理实体发送第一网络请求消息，第一网络请求消息包括接入管理连接标识，接入管理连接标识是根据接入管理连接标识和移动管理连接标识的关联关系确定的。
第六方面，本申请实施例提供一种通信方法，该方法包括：移动管理实体接收来自接入网设备的第三连接请求消息，第三连接请求消息用于请求建立接入网设备与移动管理实体之间的连接；移动管理实体向接入网设备发送第三连接响应消息，第三连接响应消息用 于指示接入网设备与移动管理实体之间的连接信息。
在一种可能的设计中，第三连接请求消息包括接入网设备的接入网连接标识；接入网设备与移动管理实体之间的连接信息包括移动管理实体的移动管理连接标识和接入网连接标识的关联关系。
在一种可能的设计中，该方法还包括：移动管理实体向接入网设备发送第二寻呼请求消息，第二寻呼请求消息包括终端设备的用户标识和用户网络的信息。
第七方面，本申请实施例提供一种通信方法，该方法包括：接入网设备向接入管理实体发送第一连接请求消息，第一连接请求消息包括用户接入信息，用于请求建立接入网设备至移动管理实体之间的连接；接入网设备接收来自接入管理实体的第一连接响应消息，第一连接响应消息用于指示接入网设备与接入管理实体之间的连接信息。
在一种可能的设计中，第一连接请求消息还包括接入网设备的接入网连接标识；接入网设备与接入管理实体之间的连接信息包括接入管理实体的接入管理连接标识和接入网连接标识的关联关系。
在一种可能的设计中，用户接入信息包括用户标识和用户网络的信息。
在一种可能的设计中，第一连接响应消息还包括移动管理实体的移动管理连接标识和接入网连接标识的关联关系，该方法还包括：接入网设备记录移动管理连接标识和接入网设备的接入网连接标识的关联关系。
在一种可能的设计中，接入网设备接收来自接入管理实体的第一寻呼请求，第一寻呼请求包括终端设备的用户标识和用户网络的信息；接入网设备向终端设备发送寻呼消息，寻呼消息包括用户标识和用户网络的信息；或，接入网设备接收来自移动管理实体的第二寻呼请求，第二寻呼请求包括终端设备的用户标识和用户网络的信息；接入网设备向终端设备发送寻呼消息，寻呼消息包括用户标识和用户网络的信息。
第八方面，本申请实施例提供一种通信方法，该方法包括：接入网设备向移动管理实体发送第三连接请求消息，第三连接请求消息用于请求建立接入网设备与移动管理实体之间的连接；接入网设备接收来自移动管理实体的第三连接响应消息，第三连接响应消息用于指示接入网设备与移动管理实体之间的连接信息。
在一种可能的设计中，第三连接请求消息包括接入网设备的接入网连接标识；接入网设备与移动管理实体之间的连接信息包括移动管理实体的移动管理连接标识和接入网连接标识的关联关系。
在一种可能的设计中，该方法还包括：接入网设备向接入管理实体发送移动管理实体寻址请求消息，移动管理实体寻址请求消息包括用户接入信息；接入网设备接收来自接入管理实体的移动管理实体寻址响应消息，移动管理实体寻址响应消息包括移动管理实体的信息。
在一种可能的设计中，用户接入信息包括用户标识和用户网络的信息。
在一种可能的设计中，接入网设备接收来自移动管理实体的第二寻呼请求，第二寻呼请求包括终端设备的用户标识和用户网络的信息；接入网设备向终端设备发送寻呼消息，寻呼消息包括用户标识和用户网络的信息。
第九方面，本申请实施例提供一种通信装置，该通信装置可以用于第三方面的通信装置，该通信装置可以是接入管理实体，也可以是接入管理实体中的装置(例如，芯片，或者芯片系统，或者电路)，或者是能够和接入管理实体匹配使用的装置。
一种可能的实现中，该通信装置可以包括执行第三方面中所描述的方法/操作/步骤/动作所一一对应的模块或单元，该模块或单元可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。
一种可能的实现中，该通信装置可以包括：接口单元和处理单元；接口单元，用于接收来自接入网设备的第一连接请求消息，第一连接请求消息包括用户接入信息，用于请求建立接入网设备至移动管理实体之间的连接；处理单元，用于基于第一连接请求消息，通过接口单元向移动管理实体发送第二连接请求消息，第二连接请求消息用于请求建立接入管理实体与移动管理实体之间的连接，其中移动管理实体是接入管理实体根据用户接入信息确定的；接口单元，还用于接收来自移动管理实体的第二连接响应消息，第二连接响应消息用于指示接入管理实体与移动管理实体之间的连接信息；以及向接入网设备发送第一连接响应消息，第一连接响应消息用于指示接入网设备与接入管理实体之间的连接信息。
在一种可能的设计中，第一连接请求消息还包括接入网设备的接入网连接标识，第二连接请求消息包括接入管理实体的接入管理连接标识；接入管理实体与移动管理实体之间的连接信息包括接入管理连接标识和移动管理实体的移动管理连接标识的关联关系；接入网设备与接入管理实体之间的连接信息包括接入管理连接标识和接入网连接标识的关联关系。
在一种可能的设计中，用户接入信息包括用户标识和用户网络的信息，处理单元基于第一连接请求消息，通过接口单元向移动管理实体发送第二连接请求消息时，具体用于根据用户标识和用户网络的信息，确定与用户标识关联、且支持用户网络的移动管理实体，为接收第二连接请求消息的移动管理实体。作为一种示例：处理单元可以根据用户标识和用户网络的信息，通过用户上下文寻址实体查询与用户标识关联、且支持用户网络的移动管理实体，作为接收第二连接请求消息的移动管理实体。
在一种可能的设计中，用户接入信息包括用户网络的信息，处理单元基于第一连接请求消息，通过接口单元向移动管理实体发送第二连接请求消息时，具体用于根据用户网络的信息，确定支持用户网络的移动管理实体的列表；将移动管理实体的列表中的一个移动管理实体，确定为接收第二连接请求消息的移动管理实体。作为一种示例：处理单元通过接口单元，可以向用户网络寻址实体发送用户网络寻址请求消息，用户网络寻址请求消息包括用户网络的信息；接收来自用户网络寻址实体的用户网络寻址应答消息，用户网络寻址应答消息包括支持用户网络的移动管理实体的列表；以及将移动管理实体的列表中的一个移动管理实体，确定为接收第二连接请求消息的移动管理实体。
在一种可能的设计中，接口单元，还用于接收来自移动管理实体的第一寻呼请求消息，第一寻呼请求消息包括终端设备的用户标识和用户网络的信息；以及向接入网设备转发第一寻呼请求消息。
在一种可能的设计中，接口单元，还用于接收来自接入网设备的第一用户请求消息，第一用户请求消息包括接入管理连接标识；向移动管理实体发送第二用户请求消息，第二用户请求消息包括移动管理连接标识，其中移动管理连接标识是处理单元根据接入管理连接标识和移动管理连接标识的关联关系确定的；接口单元，还用于接收来自移动管理实体的第二用户应答消息，第二用户应答消息包括接入管理连接标识；以及向接入网设备发送第一用户应答消息，第一用户应答消息包括接入网连接标识，其中接入网连接标识是处理单元根据接入管理连接标识和接入网连接标识的关联关系确定的。
在一种可能的设计中，接口单元，还用于接收来自移动管理实体的第一网络请求消息，第一网络请求消息包括接入管理连接标识；以及向接入网设备发送第二网络请求消息，第二网络请求消息包括接入网连接标识，其中接入网连接标识是处理单元根据接入管理连接标识和接入网连接标识的关联关系确定的。
第十方面，本申请实施例提供一种通信装置，该通信装置可以用于第四方面的通信装置，该通信装置可以是接入管理实体，也可以是接入管理实体中的装置(例如，芯片，或者芯片系统，或者电路)，或者是能够和接入管理实体匹配使用的装置。
一种可能的实现中，该通信装置可以包括执行第四方面中所描述的方法/操作/步骤/动作所一一对应的模块或单元，该模块或单元可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。
一种可能的实现中，该通信装置可以包括：接口单元和处理单元；接口单元，用于接收来自接入网设备的移动管理实体寻址请求消息，移动管理实体寻址请求消息包括用户接入信息；接口单元，还用于向接入网设备发送移动管理实体寻址响应消息，移动管理实体寻址响应消息包括移动管理实体的信息，移动管理实体是处理单元根据用户接入信息确定的。
在一种可能的设计中，用户接入信息包括用户标识和用户网络的信息，处理单元根据用户接入信息确定移动管理实体时，具体用于根据用户标识和用户网络的信息，确定与用户标识关联、且支持用户网络的移动管理实体。作为一种示例：处理单元可以根据用户标识和用户网络的信息，通过用户上下文寻址实体查询与用户标识关联、且支持用户网络的移动管理实体，作为移动管理实体寻址响应消息中携带的移动管理实体的信息所指示的移动管理实体。
在一种可能的设计中，用户接入信息包括用户网络的信息，处理单元根据用户接入信息确定移动管理实体时，具体用于根据用户网络的信息，确定支持用户网络的移动管理实体的列表；以及将移动管理实体的列表中的一个移动管理实体，确定为移动管理实体寻址响应消息中携带的移动管理实体的信息所指示的移动管理实体。作为一种示例：处理单元通过接口单元可以向用户网络寻址实体发送用户网络寻址请求消息，用户网络寻址请求消息包括用户网络的信息；接收来自用户网络寻址实体的用户网络寻址应答消息，用户网络寻址应答消息包括支持用户网络的移动管理实体的列表；以及将移动管理实体的列表中的一个移动管理实体，确定为移动管理实体寻址响应消息中携带的移动管理实体的信息所指示的移动管理实体。
第十一方面，本申请实施例提供一种通信装置，该通信装置可以用于第五方面的通信装置，该通信装置可以是移动管理实体，也可以是移动管理实体中的装置(例如，芯片，或者芯片系统，或者电路)，或者是能够和移动管理实体匹配使用的装置。
一种可能的实现中，该通信装置可以包括执行第五方面中所描述的方法/操作/步骤/动作所一一对应的模块或单元，该模块或单元可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。
一种可能的实现中，该通信装置可以包括：接口单元和处理单元；接口单元，用于接收来自接入管理实体的第二连接请求消息，第二连接请求消息用于请求建立接入管理实体与移动管理实体之间的连接；处理单元，用于确定第二连接响应消息，第二连接响应消息用于指示接入管理实体与移动管理实体之间的连接信息；接口单元，还用于发送第二连接 响应消息。
在一种可能的设计中，第二连接请求消息包括接入管理实体的接入管理连接标识；接入管理实体与移动管理实体之间的连接信息包括接入管理连接标识和移动管理实体的移动管理连接标识的关联关系。
在一种可能的设计中，接口单元，还用于向接入管理实体发送第一寻呼请求消息，第一寻呼请求消息包括终端设备的用户标识和用户网络的信息；或，向接入网设备发送第二寻呼请求消息，第二寻呼请求消息包括终端设备的用户标识和用户网络的信息。
在一种可能的设计中，接口单元，还用于接收来自接入管理实体的第二用户请求消息，第二用户请求消息包括移动管理连接标识；以及向接入管理实体发送第二用户应答消息，第二用户应答消息包括接入管理连接标识，其中接入管理连接标识是处理单元根据接入管理连接标识和移动管理连接标识的关联关系确定的。
在一种可能的设计中，接口单元，还用于向接入管理实体发送第一网络请求消息，第一网络请求消息包括接入管理连接标识，接入管理连接标识是处理单元根据接入管理连接标识和移动管理连接标识的关联关系确定的。
第十二方面，本申请实施例提供一种通信装置，该通信装置可以用于第六方面的通信装置，该通信装置可以是移动管理实体，也可以是移动管理实体中的装置(例如，芯片，或者芯片系统，或者电路)，或者是能够和移动管理实体匹配使用的装置。
一种可能的实现中，该通信装置可以包括执行第六方面中所描述的方法/操作/步骤/动作所一一对应的模块或单元，该模块或单元可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。
一种可能的实现中，该通信装置可以包括：接口单元和处理单元；接口单元，用于接收来自接入网设备的第三连接请求消息，第三连接请求消息用于请求建立接入网设备与移动管理实体之间的连接；处理单元，用于确定第三连接响应消息，第三连接响应消息用于指示接入网设备与移动管理实体之间的连接信息；接口单元，还用于向接入网设备发送第三连接响应消息。
在一种可能的设计中，第三连接请求消息包括接入网设备的接入网连接标识；接入网设备与移动管理实体之间的连接信息包括移动管理实体的移动管理连接标识和接入网连接标识的关联关系。
在一种可能的设计中，接口单元，还用于向接入网设备发送第二寻呼请求消息，第二寻呼请求消息包括终端设备的用户标识和用户网络的信息。
第十三方面，本申请实施例提供一种通信装置，该通信装置可以用于第七方面的通信装置，该通信装置可以是接入网设备，也可以是接入网设备中的装置(例如，芯片，或者芯片系统，或者电路)，或者是能够和接入网设备匹配使用的装置。
一种可能的实现中，该通信装置可以包括执行第七方面中所描述的方法/操作/步骤/动作所一一对应的模块或单元，该模块或单元可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。
一种可能的实现中，该通信装置可以包括：接口单元和处理单元；处理单元，用于确定第一连接请求消息，第一连接请求消息包括用户接入信息，用于请求建立接入网设备至移动管理实体之间的连接；接口单元，用于向接入管理实体发送第一连接请求消息；以及接收来自接入管理实体的第一连接响应消息，第一连接响应消息用于指示接入网设备与接 入管理实体之间的连接信息。
在一种可能的设计中，第一连接请求消息还包括接入网设备的接入网连接标识；接入网设备与接入管理实体之间的连接信息包括接入管理实体的接入管理连接标识和接入网连接标识的关联关系。
在一种可能的设计中，用户接入信息包括用户标识和用户网络的信息。
在一种可能的设计中，第一连接响应消息还包括移动管理实体的移动管理连接标识，处理单元，还用于记录移动管理连接标识和接入网设备的接入网连接标识的关联关系。
在一种可能的设计中，接口单元，还用于接收来自接入管理实体的第一寻呼请求，第一寻呼请求包括终端设备的用户标识和用户网络的信息；处理单元，还用于通过接口单元向终端设备发送寻呼消息，寻呼消息包括用户标识和用户网络的信息；或，接口单元，还用于接收来自移动管理实体的第二寻呼请求，第二寻呼请求包括终端设备的用户标识和用户网络的信息；处理单元，还用于通过接口单元向终端设备发送寻呼消息，寻呼消息包括用户标识和用户网络的信息。
第十四方面，本申请实施例提供一种通信装置，该通信装置可以用于第八方面的通信装置，该通信装置可以是接入网设备，也可以是接入网设备中的装置(例如，芯片，或者芯片系统，或者电路)，或者是能够和接入网设备匹配使用的装置。
一种可能的实现中，该通信装置可以包括执行第八方面中所描述的方法/操作/步骤/动作所一一对应的模块或单元，该模块或单元可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。
一种可能的实现中，该通信装置可以包括：接口单元和处理单元；处理单元，用于确定第三连接请求消息，第三连接请求消息用于请求建立接入网设备与移动管理实体之间的连接；接口单元，用于向移动管理实体发送第三连接请求消息；以及接收来自移动管理实体的第三连接响应消息，第三连接响应消息用于指示接入网设备与移动管理实体之间的连接信息。
在一种可能的设计中，第三连接请求消息包括接入网设备的接入网连接标识；接入网设备与移动管理实体之间的连接信息包括移动管理实体的移动管理连接标识和接入网连接标识的关联关系。
在一种可能的设计中，接口单元，还用于向接入管理实体发送移动管理实体寻址请求消息，移动管理实体寻址请求消息包括用户接入信息；以及接收来自接入管理实体的移动管理实体寻址响应消息，移动管理实体寻址响应消息包括移动管理实体的信息。
在一种可能的设计中，用户接入信息包括用户标识和用户网络的信息。
在一种可能的设计中，接口单元，还用于接收来自移动管理实体的第二寻呼请求，第二寻呼请求包括终端设备的用户标识和用户网络的信息；处理单元，还用于通过接口单元向终端设备发送寻呼消息，寻呼消息包括用户标识和用户网络的信息。
第十五方面，本申请实施例提供一种通信装置，该通信装置包括接口电路和处理器，处理器和接口电路之间相互耦合。处理器通过逻辑电路或执行指令用于实现上述第三方面或者第三方面的任一种可能的设计中的方法，或用于实现上述第四方面或者第四方面的任一种可能的设计中的方法。接口电路用于接收来自该通信装置之外的其它通信装置的信号并传输至处理器或将来自处理器的信号发送给该通信装置之外的其它通信装置。可以理解的是，接口电路可以为收发器或收发机或收发信机或输入输出接口。
可选的，通信装置还可以包括存储器，用于存储处理器执行的指令或存储处理器运行指令所需要的输入数据或存储处理器运行指令后产生的数据。存储器可以是物理上独立的单元，也可以与处理器耦合，或者处理器包括该存储器。
第十六方面，本申请实施例提供一种通信装置，该通信装置包括接口电路和处理器，处理器和接口电路之间相互耦合。处理器通过逻辑电路或执行指令用于实现上述第五方面或者第五方面的任一种可能的设计中的方法，或用于实现上述第六方面或者第六方面的任一种可能的设计中的方法。接口电路用于接收来自该通信装置之外的其它通信装置的信号并传输至处理器或将来自处理器的信号发送给该通信装置之外的其它通信装置。可以理解的是，接口电路可以为收发器或收发机或收发信机或输入输出接口。
可选的，通信装置还可以包括存储器，用于存储处理器执行的指令或存储处理器运行指令所需要的输入数据或存储处理器运行指令后产生的数据。存储器可以是物理上独立的单元，也可以与处理器耦合，或者处理器包括该存储器。
第十七方面，本申请实施例提供一种通信装置，该通信装置包括接口电路和处理器，处理器和接口电路之间相互耦合。处理器通过逻辑电路或执行指令用于实现上述第七方面或者第七方面的任一种可能的设计中的方法，或用于实现上述第八方面或者第八方面的任一种可能的设计中的方法。接口电路用于接收来自该通信装置之外的其它通信装置的信号并传输至处理器或将来自处理器的信号发送给该通信装置之外的其它通信装置。可以理解的是，接口电路可以为收发器或收发机或收发信机或输入输出接口。
可选的，通信装置还可以包括存储器，用于存储处理器执行的指令或存储处理器运行指令所需要的输入数据或存储处理器运行指令后产生的数据。存储器可以是物理上独立的单元，也可以与处理器耦合，或者处理器包括该存储器。
第十八方面，本申请实施例提供一种计算机可读存储介质，在存储介质中存储有计算机程序或指令，当计算机程序或指令被执行时，可以实现上述第三方面或者第三方面的任一种可能的设计中的方法，或实现上述第四方面或者第四方面的任一种可能的设计中的方法，或实现上述第五方面或者第五方面的任一种可能的设计中的方法，或实现上述第六方面或者第六方面的任一种可能的设计中的方法，或实现上述第七方面或者第七方面的任一种可能的设计中的方法，或实现上述第八方面或者第八方面的任一种可能的设计中的方法。
第十九方面，本申请实施例还提供一种计算机程序产品，包括计算机程序或指令，当计算机程序或指令被执行时，可以实现上述第三方面或者第三方面的任一种可能的设计中的方法，或实现上述第四方面或者第四方面的任一种可能的设计中的方法，或实现上述第五方面或者第五方面的任一种可能的设计中的方法，或实现上述第六方面或者第六方面的任一种可能的设计中的方法，或实现上述第七方面或者第七方面的任一种可能的设计中的方法，或实现上述第八方面或者第八方面的任一种可能的设计中的方法。
第二十方面，本申请实施例还提供一种芯片，该芯片与存储器耦合，用于读取并执行存储器中存储的程序或指令，实现上述第三方面或者第三方面的任一种可能的设计中的方法，或实现上述第四方面或者第四方面的任一种可能的设计中的方法，或实现上述第五方面或者第五方面的任一种可能的设计中的方法，或实现上述第六方面或者第六方面的任一种可能的设计中的方法，或实现上述第七方面或者第七方面的任一种可能的设计中的方法，或实现上述第八方面或者第八方面的任一种可能的设计中的方法。
第二十一方面，本申请实施例还提供一种通信系统，该系统可以包括：上述第九方面 的接入管理实体、第十一方面的移动管理实体和第十三方面的接入网设备。
一种可能的实现中，该通信系统还可以包括上述第九方面、第十一方面和第十三方面涉及的用户上下文寻址实体和用户网络寻址实体。
第二十二方面，本申请实施例还提供一种通信系统，该系统包括：上述第十方面的接入管理实体、第十二方面的移动管理实体和第十四方面的接入网设备。
一种可能的实现中，该通信系统还可以包括上述第十方面、第十二方面和第十四方面涉及的用户上下文寻址实体和用户网络寻址实体。
第二十三方面，本申请实施例还提供一种核心网系统，包括：上述第九方面的接入管理实体和第十一方面的移动管理实体。可选地，该通信系统还可以包括上述第九方面、第十一方面涉及的用户上下文寻址实体和用户网络寻址实体。
第二十四方面，本申请实施例还提供一种核心网系统，包括：上述第十方面的接入管理实体和第十二方面的移动管理实体。可选地，该通信系统还可以包括上述第十方面、第十二方面涉及的用户上下文寻址实体和用户网络寻址实体。
上述第三方面至第二十四方面所能达到的技术效果请参照上述第一方面或第二方面所能达到的技术效果，这里不再重复赘述。
附图说明
图1为本申请实施例提供的一种网络架构示意图；
图2为本申请实施例提供的接入管理和移动管理解耦的网络架构示意图；
图3为本申请实施例提供的直接模式和间接模式通信示意图；
图4为本申请实施例提供的通信方法的交互示意图之一；
图5为本申请实施例提供的移动管理实体确定过程示意图；
图6为本申请实施例提供的移动管理实体消息处理示意图；
图7为本申请实施例提供的通信方法的交互示意图之二；
图8为本申请实施例提供的网络侧发起网络请求过程示意图；
图9为本申请实施例提供的通信方法的交互示意图之三；
图10为本申请实施例提供的通信方法的交互示意图之四；
图11为本申请实施例提供的通信方法的交互示意图之五；
图12为本申请实施例提供的通信方法的交互示意图之六；
图13为本申请实施例提供的通信方法的交互示意图之七；
图14为本申请实施例提供的通信装置的结构示意图之一；
图15为本申请实施例提供的通信装置的结构示意图之二。
具体实施方式
本申请实施例提供的技术方案可以应用于第五代(5th generation，5G)网络，如新无线(new radio，NR)网络等，还可以应用于5G之后演进的通信系统，如第六代网络等，还可以应用于长期演进(long term evolution，LTE)网络、LTE频分双工(frequency division duplex，FDD)网络、LTE时分双工(time division duplex，TDD)网络等。
参照图1所示，为一种网络架构示意图。在图1中，用户设备(user equipment，UE) 可通过接入网(radio access network，AN)与接入和移动性管理功能(access and mobility management function，AMF)通信，其中(R)AN可通过N2接口与AMF通信。另外(R)AN还可通过N3接口与用户面功能(user plane function，UPF)通信，UPF可通过N9接口与其他的UPF通信，UPF还可通过N6接口与数据网络(data network，DN)通信，以及通过N4接口与会话管理功能(session management function，SMF)通信。AMF可通过N14接口与其他的AMF通信，AMF还可通过N11接口与SMF通信、通过N12接口与鉴权服务功能(authentication server function，AUSF)通信、通过N8接口与统一数据管理(unified data management，UDM)通信、通过N15接口与策略控制功能(policy control function，PCF)通信、以及通过N22接口与网络切片选择功能(network slice selection function，NSSF)通信，SMF可通过N10接口与UDM通信，以及通过N7接口与PCF通信，PCF可通过N5接口与应用功能(application function，AF)通信。
具体的，(R)AN的功能可以通过接入网设备实现，UPF可以通过用户面实体实现，类似的，AMF可以通过接入和移动性管理实体实现，SMF可以通过会话管理实体实现，PCF可以策略控制实体实现，AF可以通过应用实体实现，NSSF可以通过网络切片选择实体实现，AUSF可以通过鉴权服务实体实现，UDM功能可以通过统一数据管理实体实现。
可以理解的是，上述实体或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。可选的，上述实体或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
在目前的网络架构中，例如在图1所示的网络架构中，通常由接入和移动性管理实体提供接入管理功能和移动管理功能。具体的，接入和移动性管理实体可以提供如下等中的一项或多项接入管理功能：
终止RAN控制面(control plane，CP)接口(N2)；
连接管理(connection management)；
可达性管理(reachability management)；
接入鉴权(access authentication)；
接入授权(access authorization)；
提供外部参数(provisioning of external parameters)，如提供预期的UE行为参数(expected UE behaviour parameters)或网络配置参数(network configuration parameters)。
接入和移动性管理实体可以提供如下等中的一项或多项移动管理功能：
终止非接入层(non-access stratum，NAS)(N1)，NAS加密和完整性保护；
注册管理(registration management)；
移动管理(mobility management)；
为UE和SMF之间的会话管理(session management，SM)消息提供传输；
用于路由SM消息的透明代理(transparent proxy for routing SM messages)；
提供UE和短信服务功能(short message service function，SMSF)间短消息服务(short message service，SMS)消息的传输；
安全锚点功能(security anchor function，SEAF)；
定位服务管理(location services management)；
为UE和位置管理功能(location management function，LMF)之间以及RAN和LMF 之间的位置服务消息提供传输；
用于与演进的分组系统(evolved packet system，EPS)互通的EPS承载ID分配；
UE移动事件通知(mobility event notification)；
支持控制面蜂窝物联网(cellular internet of things，CIoT)优化；
支持用户面CIoT优化。
由上可知，接入管理的处理对象是网络接入能力，关注终端设备与接入网的连接，移动管理的处理对象是用户的移动管理能力，关注业务功能。接入管理和移动管理两者的容量规划，部署位置，可用性要求存在着差异。接入管理和移动管理耦合在一起，由接入与移动性管理实体实现相应的接入管理功能和移动管理功能，不利于接入管理和移动管理的独立建设。另外，网络的接入管理处理由运营商控制，用户的移动管理处理，原则上可以由服务的用户或租户控制，当网络需要对一个用户开放移动管理权限时，不希望影响整个网络的接入管理，对其它用户产生影响，接入管理和移动管理耦合在一起，也不利于满足接入管理和移动管理的独立控制需求。此外，接入管理和移动管理两者的演进步伐和方式都不相同，耦合在一起也不利于接入管理和移动管理的独立演进。例如：IoT的网络可能需要定制移动管理，但是不希望影响接入管理。
因此，本申请提出一种通信方案，以期解耦接入管理和移动管理，满足接入管理和移动管理的独立建立、独立控制和独立演进的需求，支持接入管理和移动管理差异化的容量规划、部署位置、可用性要求。下面将结合附图，对本申请实施例进行详细描述。
如图2所示，为本申请实施例适用的一种网络架构示意图，包括终端设备、接入网设备、接入管理实体、移动管理实体、用户网络寻址实体、用户上下文寻址实体和其它网络实体。
其中，接入管理实体具有接入鉴权、接入授权等接入管理功能。作为一种示例：接入管理实体可以具备上述接入和移动性管理实体的部分或全部的接入管理功能。在用户初始接入网络时，可以通过接入网设备首先接入(或连接)到接入管理实体，接入管理实体可以处理用户相关信令，并为用户选择移动管理实体，将用户相关消息(或信令)转发至移动管理实体。在用户接入用户网络后，在间接模式下，用户和移动管理实体之间的上行消息和下行消息，经过接入管理实体进行转发处理。
移动管理实体具有定位服务管理、为用户提供会话管理信令通道等移动管理功能。作为一种示例：移动管理实体可以具备上述接入和移动性管理实体的部分或全部的移动管理功能。可以为用户提供移动管理服务的网络功能，可以维护用户移动管理上下文，包括用户网络侧注册状态，接入网设备连接状态、位置等信息。
用户上下文寻址实体能够为其它网络实体提供用户上下文寻址功能，当某条用户相关消息需要转给对应移动管理实体处理时，通过用户上下文寻址实体可以查询到对应的移动管理实体的标识(identifier，ID)或者地址。在一些实施中，用户上下文寻址实体可以和能够实现网络功能(network function，NF)存储功能(NF repository function，NRF)的网络仓储实体集成在一起，或者通过网络仓储实体实现用户上下文寻址实体的部分或全部功能，或者通过能够实现绑定支持功能(binding support function，BSF)的绑定支持实体，来实现用户上下文寻址实体的部分或全部功能等。
用户网络寻址实体在用户初始接入用户网络(如初始注册到用户网络或附着到用户网络)时，可以为接入管理实体提供通过服务，可用来查询可以为该用户进行服务的一组移 动管理实体ID或者地址集合。在一些实施中，用户网络寻址实体也可以和网络仓储实体集成在一起，或者通过网络仓储实体实现用户网络寻址实体的部分或全部功能。
另外，需要理解的是，用户网络寻址实体和用户上下文寻址实体也可以与其它网络实体集成在一起，或嵌入其它网络实体内部，例如用户上下文寻址实体可以嵌入移动管理实体内部，移动管理实体也可以实现用户上下文寻址实体的功能。
其它网络实体，可以包括会话管理实体、策略控制实体、用户面实体、鉴权服务实体、统一数据管理实体等，能够提供会话管理，策略服务，用户面服务等。
接入网设备可以与移动管理实体通过用户信令接口A连接，用户信令接口A，可以用于接入网设备向移动管理实体发送上行消息(或信令)，以及移动管理实体向接入网设备发送下行消息(或信令)。
接入管理实体可以通过用户信令接口B和用户信令接口C分别与接入网设备和移动管理实体连接，用户信令接口B和用户信令接口C，可以用于接入网设备将上行消息(或信令)发送至接入管理实体，由接入管理实体将上行消息(或信令)转发至移动管理实体，以及移动管理实体将下行消息(或信令)发送至接入管理实体，由接入管理实体将下行消息(或信令)转发至接入网设备。
用户网络寻址实体可以通过用户网络查询接口与接入管理实体连接，接入管理实体可以根据用户网络上的标识，通过用户网络查询接口查询可以为用户服务的至少一个移动管理实体的ID或者地址集合。
用户上下文寻址实体可以通过用户上下文查询接口A、用户上下文查询接口B和用户上下文查询接口C分别与接入管理实体、移动管理实体和其它网络实体连接，接入管理实体、移动管理实体和其它网络实体通过用户上下文查询接口A、用户上下文查询接口B和用户上下文查询接口C，可以查询用户归属的用户网络的移动管理实体的ID或者地址。
图3为本申请实施例提供的一种直接模式和间接模式通信示意图，参照图3中A所示，在直接模式下，在终端设备(即用户)已接入用户网络，处于连接到用户网络中的移动管理实体的状态时，接入网设备可以直接和移动管理实体进行用户相关消息(或信令)的通信。例如：接入网设备可以直接将用户请求消息发送给移动管理实体，移动管理实体也可以直接将用户应答消息发送给接入网设备，移动管理实体和接入网设备进行直接通信。如图3中B所示，在间接模式下，在用户已接入用户网络，处于连接到用户网络中的移动管理实体的状态时，接入网设备和移动管理实体进行用户相关消息(或信令)的通信，需要经过接入管理实体转发，即接入网设备和移动管理实体通过接入管理实体进行间接通信。
为了便于本领域技术人员理解，下面对本申请实施例中的部分用语进行解释说明。
1)、用户网络可以是向一个或多个终端设备(即用户)提供专属服务的网络，该用户网络可以是一个或多个网络实体的集合。作为一种示例：图1所示的网络中用户网络可以是指执行移动管理，会话管理、策略管理、数据转发、流量统计、服务质量(quality of service，QoS)处理等一项或多项功能组成的网络实体集合。其中在接入管理和移动管理未解耦的网络中，移动管理实体还可以替换为接入和移动性管理实体。该用户网络可以是通信设备实体，也可以是虚拟化的逻辑网络功能实体，或者是由一个或一组物理机，虚机、容器、进程或其他可运行的资源集合。
2)、接入网设备，也可以称为网络设备或无线接入网(radio access network，RAN)设备。可以是基站(base station)、演进型基站(evolved NodeB，eNodeB)、收发点(transmitter  and receiver point，TRP)、集成接入和回传(integrated access and backhauling，IAB)节点、第五代(5th generation，5G)移动通信系统中的下一代基站(next generation NodeB，gNB)、6G等5G之后演进的通信系统中的基站、家庭基站(例如，home evolved nodeB，或home node B，HNB)、无线保真(wireless fidelity，WiFi)系统中的接入点(access point，AP)、无线中继节点、无线回传节点、发射点(transmitting point，TP)、移动交换中心以及设备到设备(device-to-device，D2D)、车辆外联(vehicle-to-everything，V2X)、机器到机器(machine-to-machine，M2M)通信中承担基站功能的设备等等。也可以是完成基站部分功能的模块或单元，例如，可以是集中式单元(central unit，CU)，也可以是分布式单元(distributed unit，DU)。这里的CU完成基站的无线资源控制协议和分组数据汇聚层协议(packet data convergence protocol，PDCP)的功能，还可以完成业务数据适配协议(service data adaptation protocol，SDAP)的功能；DU完成基站的无线链路控制层和介质访问控制(medium access control，MAC)层的功能，还可以完成部分物理层或全部物理层的功能，有关上述各个协议层的具体描述，可以参考第三代合作伙伴计划(3rd generation partnership project，3GPP)的相关技术规范。网络设备还可以是非地面(non-terrestrial)基站，如低地球轨道(low earth orbit，LEO)/极低地球轨道(very low earth orbit，VLEO)卫星、高空平台站(high-attitude platform station，HAPS)等。
3)、终端设备，可以是一种具有无线收发功能的设备，终端设备也可以指终端、UE、移动终端、接入终端、用户单元(subscriber unit)、用户站、移动台(mobile station)、远方站、远程终端、无线通信设备、用户代理或用户装置等。终端设备可以广泛应用于各种场景，例如，终端设备可以是D2D、V2X通信、机器类通信(machine-type communication，MTC)、物联网(internet of things，IoT)、虚拟现实、增强现实、工业控制、自动驾驶、远程医疗、智能电网、智能家具、智能办公、智能穿戴、智能交通或智慧城市中的终端。终端设备可以是手机、平板电脑、带无线收发功能的电脑、可穿戴设备、车辆、无人机、直升机、飞机、轮船、机器人、机械臂、智能家居设备、车载终端、IoT终端、可穿戴设备等。本申请的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
4)、连接管理(connection management，CM)状态，可用于描述终端设备与移动管理实体之间的信令连接状态。其中，CM空闲态(CM-IDLE)表示终端设备与移动管理实体未建立连接，终端设备与移动管理实体之间的上下行消息(或信令)不能通过连接标识索引到对端。CM连接态(CM-CONNECTED)表示终端设备与移动管理实体建立连接，终端设备与移动管理实体之间的上下行消息(或信令)可以通过连接标识索引到对端。
5)、注册管理(registration management，RM)状态，可用于描述终端设备是否已经注册到用户网络。RM注销(RM-DEREGISTERED)，表示终端设备(即用户)没有注册到接入管理实体，接入管理实体以及其他网络实体没有终端设备的上下文；RM注册(RM-REGISTERED)表示终端设备(即用户)注册到接入管理实体，接入管理实体以及其他网络实体有终端设备的上下文。
另外，需要理解的是，本申请实施例提及“第一”、“第二”等序数词是用于对多个对象进行区分，不用于限定多个对象的大小、内容、顺序、时序、优先级或者重要程度等。例如，第一阈值和第二阈值，可以是同一个阈值，也可以是不同的阈值，且，这种名称也并不是表示这两个阈值的取值、对应的参数、优先级或者重要程度等的不同。
本申请实施例中，对于名词的数目，除非特别说明，表示“单数名词或复数名词”， 即"一个或多个”。“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。例如，A/B，表示：A或B。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，表示：a，b，c，a和b，a和c，b和c，或a和b和c，其中a，b，c可以是单个，也可以是多个。
图4为本申请实施例提供的通信方法示意图之一，该方法包括：
S401：终端设备向接入网设备发送用户连接请求消息，用户连接请求消息包括用户接入信息，相应的，接入网设备接收用户连接请求消息。
在终端设备有业务数据需要向用户网络发送时，如果终端设备未接入用户网络，即未连接到该用户网络中的移动管理实体，需要终端设备发起对该用户网络的连接，接入该用户网络，连接到该用户网络中的移动管理实体。因此，在终端设备有业务数据需要向用户网络发送时，如果终端设备未接入该用户网络，终端设备可以向接入网设备发送包括用户接入信息的用户连接请求消息，请求接入该用户网络，连接到该用户网络中的移动管理实体。
在用户接入信息中可以包括用户标识和用户网络的信息。其中，用户标识可以为终端设备的用户永久标识(subscription permanent identifier，SUPI)，或用户网络之前为终端设备分配的全局唯一临时标识(globally unique temporary identity，GUTI)等。用户网络的信息可以包括用户网络类型和/或用户网络标识(如用户网络ID)。具体的，对于用户网络类型，终端设备可以根据用户签约信息或者本地策略，在发起不同业务时携带对应的用户网络类型，例如发起IoT业务时，携带IoT网络类型。对于用户网络标识，在终端设备中可以通过签约信息等预先配置每种业务对应的用户网络标识，在终端设备发送不同业务时携带对应的用户网络标识。
另外，在用户连接请求消息中还可以包括终端设备为此次业务分配的无线连接标识(如无线连接ID)，用于接入网设备和终端设备之间建立连接。在一些实现中，无线连接标识也可以复用接入网设备为终端设备配置的无线网络临时标识、终端设备的用户标识等。接入网设备接收到来自终端设备的用户连接请求消息后，可以创建与无线连接标识关联的接入网连接标识(如接入网连接ID)，并可以为该终端设备创建接入网用户上下文，并在接入网用户上下文中记录无线连接标识和接入网连接标识的关联关系。可选地，为该终端设备创建的接入网用户上下文可以与该终端设备的用户标识关联，以便查询。
在一些实施中，无线连接标识可以为终端设备为该终端设备的业务(或连接)分配的连接标识，通过无线连接标识可以确定终端设备和对应的业务(或连接)。例如通过终端设备为浏览业务A分配的无线连接标识可以确定该终端设备和对应的业务(如浏览业务A)。类似的，接入网连接标识可以为接入网设备为终端设备的业务(或连接)分配的连接标识，通过接入网连接标识可以确定接入网设备和对应的业务(或连接)。在本申请实施例中，后续涉及的接入管理连接标识、移动管理连接标识等为接入管理实体、移动管理实体等为终端设备的业务(或连接)分配的连接标识，与无线连接标识、接入网连接标识类似，不再进行赘述。
S402：接入网设备向接入管理实体发送第一连接请求消息，相应的，接入管理实体接 收第一连接请求消息，第一连接请求消息包括用户接入信息，用于请求建立接入网设备至移动管理实体之间的连接。
对于接收第一连接请求消息的接入管理实体，接入网设备可以随机选择，也可以按照一定的策略选择。作为一种示例：接入网设备可以在接入网设备连接的一个或多个接入管理实体中选择负载最小的接入管理实体作为接收第一连接请求消息的接入管理实体。也可以根据用户标识(或用户标识中部分字段)与接入管理实体的映射策略来选择接收第一连接请求消息的接入管理实体。可选地，用户标识(或用户标识中部分字段)与接入管理实体的映射策略可以来源于接入网设备的本地配置或域名系统(domain name system，DNS)配置等。
一种可能的实现中，在第一连接请求消息中还可以包括接入网连接标识，用于接入网设备和接入管理实体之间建立连接。接入管理实体接收到来自接入网设备的第一连接请求消息，可以创建与接入网连接标识关联的接入管理连接标识(如接入管理连接ID)，并可以为该终端设备创建接入管理用户上下文，并在接入管理用户上下文中记录接入网连接标识和接入管理连接标识的关联关系。可选地，为该终端设备创建的接入管理用户上下文可以与该终端设备的用户标识关联，以便查询。
此外，在一些实施中，接入管理实体还可以与终端设备以及其他网络设备，如鉴权服务实体、统一数据管理实体等进行消息(或信令)的交互，完成对终端设备接入用户网络的鉴权。例如：根据用户网络的信息，鉴权当前接入管理实体是否能为终端设备请求接入的用户网络服务等。
S403：接入管理实体基于第一连接请求消息，向移动管理实体发送第二连接请求消息，相应的，移动管理实体接收第二连接请求消息，第二连接请求消息用于请求建立接入管理实体与移动管理实体之间的连接。
接入管理实体可以基于用户接入信息来确定接收第二连接请求消息的移动管理实体。
一种可能的实现中，用户接入信息可以包括用户标识和用户网络的信息，接入管理实体可以根据用户接入信息，通过用户上下文寻址实体查询与用户标识关联(即终端设备曾经连接过)、且支持用户网络的移动管理实体，作为接收第二连接请求消息的移动管理实体，以便终端设备准确、快速地接入所需的用户网络。
又一种可能的实现中，用户接入信息可以包括用户网络的信息，接入管理实体还可以根据用户网络的信息，通过用户网络寻址实体查询支持用户网络的一个或多个移动管理实体，并从查询到的一个或多个移动管理实体中选择一个移动管理实体，作为接收第二连接请求消息的移动管理实体，以便在已有用户网络中查询能够为用户提供服务的用户网络进行连接。
作为一种示例，参照图5所示的移动管理实体确定过程，接入管理实体可以向用户上下文寻址实体发送包括用户标识的用户寻址请求消息。用户上下文寻址实体接收到用户寻址请求消息，可以根据用户标识，在自身保存的注册信息中查询该用户标识对应的终端设备是否曾经注册到网络，获得过网络分配的用户临时标识(如GUTI等)。如果终端设备曾经注册到网络，则用户上下文寻址实体可以根据为该终端设备分配的用户临时标识，查询该用户临时标识关联的(或指向的)终端设备曾经注册到的移动管理实体。
如果用户上下文寻址实体查询到该终端设备曾经注册到的移动管理实体，用户上下文寻址实体可以向接入管理实体发送携带该移动管理实体的信息(如移动管理实体的ID或 互联网协议(Internet Protocol，IP)地址等)的用户寻址应答消息；如果用户上下文寻址实体未查询到该终端设备曾经注册到的移动管理实体，用户上下文寻址实体可以向接入管理实体发送不携带移动管理实体的信息的用户寻址应答消息，也即向接入管理实体返回的移动管理实体的信息为空。在一些实施中，在用户寻址应答消息中还可以包括用户注册状态的信息，例如该用户标识对应的终端设备曾经注册到网络，则用户注册状态的信息为“已注册”，如果该用户标识对应的终端设备未曾注册到网络，则用户注册状态的信息为“未注册”。
一种可能的实现中，对于通过用户上下文寻址实体查询到的移动管理实体，接入管理实体还可以根据用户网络的信息，确定该移动管理实体是否支持终端设备请求接入的用户网络。如果该移动管理实体支持终端设备请求接入的用户网络，则接入管理实体将该移动管理实体确定为接收第二连接请求消息的移动管理实体。作为一种示例，用户网络的信息包括用户网络标识，在查询到的移动管理实体支持该用户网络标识时，接入管理实体即可将确定该移动管理实体支持终端设备请求接入的用户网络。
在一些实施中，如果接入管理实体通过用户上下文寻址实体未查询到移动管理实体，或查询到的移动管理实体不支持终端设备请求接入的用户网络，接入管理实体还可以向用户网络寻址实体发送包括用户网络的信息的用户网络寻址请求消息，请求用户网络寻址实体根据用户网络的信息查询能够支持用户网络的移动管理实体。
在一种可能的实现中，用户网络的信息可以包括用户网络标识，用户网络寻址实体接收到包括用户网络的信息的用户网络寻址请求消息，用户网络寻址实体可以在自身维护的用户网络标识与支持用户网络标识的移动管理实体表中，查询是否存在用户网络寻址请求消息中携带的用户网络标识，如果存在，则用户网络寻址实体可以将支持该用户网络标识的移动管理实体的列表，通过用户网络寻址应答消息发送给接入管理实体，其中在该移动管理实体的列表中可以包括支持该用户网络标识的至少一个移动管理实体的信息。
在另一种可能的实现中，用户网络的信息可以包括用户网络类型，用户网络寻址实体接收到包括用户网络的信息的用户网络寻址请求消息，用户网络寻址实体可以在自身维护的用户网络类型与支持用户网络类型的移动管理实体表中，查询是否存在用户网络寻址请求消息中携带的用户网络类型，如果查询到用户网络寻址请求消息中携带的用户网络类型，则用户网络寻址实体可以将支持该用户网络类型的移动管理实体的列表，通过用户网络寻址应答消息发送给接入管理实体，其中在该移动管理实体的列表中可以包括支持该用户网络类型的至少一个移动管理实体的信息。需要理解的是，查询到的移动管理实体的信息可以以列表的形式在用户网络寻址应答消息中携带，也可以以其它形式在用户网络寻址应答消息中携带，本申请对此不做限定。
在又一种可能的实现中，用户网络的信息可以包括用户网络标识和用户网络类型，用户网络寻址实体可以首先通过用户网络标识查询支持该用户网络标识的移动管理实体的列表，如果查询到支持该用户网络标识的移动管理实体的列表，则通过用户网络寻址应答消息发送给接入管理实体。如果未查询到支持该用户网络标识的移动管理实体的列表，用户网络寻址实体可以再通过用户网络类型查询支持该用户网络类型的移动管理实体的列表，并可以将查询到的支持该用户网络类型的移动管理实体的列表，通过用户网络寻址应答消息发送给接入管理实体。
需要理解的是，如果用户网络寻址实体根据用户网络的信息，未查询到任何移动管理 实体，则向接入管理实体发送的用户网络寻址应答消息可以不携带任何移动管理实体的信息，也即用户网络寻址应答消息包括的移动管理实体列表可以为空。接入管理实体在未查询到任何移动管理实体的情况下，可以向接入网设备发送接入失败的信息，使能接入网设备重新选择接入管理实体，或通知终端设备接入失败，或者接入管理实体还可以与网络控制功能进行交互，由网络控制功能实例化一个新的移动管理实体，并将此移动管理实体的信息返回给接入管理实体，用于后续的处理，如作为接收第二连接请求消息的移动管理实体。
在一些实施中，在用户网络寻址应答消息中还可以携带用户网络标识状态和/或用户网络类型状态的信息。作为一种示例：如果用户网络寻址请求消息中携带用户网络标识，且用户网络寻址实体在自身维护的用户网络标识与支持用户网络标识的移动管理实体表中查询到该用户标识，则用户网络标识状态为存在，否则为不存在；如果用户网络寻址请求消息中携带用户网络类型，且用户网络寻址实体在自身维护的用户网络类型与支持用户网络类型的移动管理实体表中查询到该用户网络类型，则用户网络类型状态为支持，否则为不支持。
接入管理实体可以在通过用户网络寻址实体查询到的至少一个移动管理实体中，选择一个移动管理实体作为接收第二连接请求消息的移动管理实体。其中，接入管理实体可以随机在至少一个移动管理实体中，选择一个移动管理实体作为接收第二连接请求消息的移动管理实体，也可以按照一定的策略在至少一个移动管理实体中，选择一个移动管理实体作为接收第二连接请求消息的移动管理实体，本申请对此不作限定。
此外，需要理解的是，接入管理实体可以仅通过用户上下文寻址实体查询移动管理实体，也可以仅通过用户网络寻址实体查询移动管理实体。还可以先通过用户上下文寻址实体查询移动管理实体，在通过用户上下文寻址实体未查询到移动管理实体后，再通过用户网络寻址实体查询移动管理实体。或先通过用户网络寻址实体查询移动管理实体，在通过用户网络寻址实体未查询到移动管理实体后，再通过用户上下文寻址实体查询移动管理实体，本申请实施例对比不作限定。
在一些实施中，用户上下文寻址实体、用户网络寻址实体的部分或全部功能也可以集成或配置在接入管理实体中，上述通过用户上下文寻址实体、用户网络寻址实体实现的移动管理实体的查询或确定等操作，也可以在接入管理实体的内部实现，如由接入管理实体直接根据用户标识和用户网络的信息，确定与用户标识关联、且支持用户网络的移动管理实体；根据用户网络的信息，确定支持用户网络的至少一个移动管理实体的信息等，本申请对此不作限定。
一种可能的实现中，在第二连接请求消息中还可以包括接入管理实体的接入管理连接标识，用于接入管理实体和移动管理实体之间建立连接。移动管理实体接收的来自接入管理实体的第二连接请求消息后，可以创建与接入管理连接标识关联的移动管理连接标识(如移动管理连接ID)，并可以为该终端设备创建移动管理用户上下文，并在移动管理用户上下文中记录接入管理连接标识和移动管理连接标识的关联关系。可选地，为该终端设备创建的移动管理用户上下文可以与该终端设备的用户标识关联，以便查询。
在一些实施中，如图6所示，移动管理实体还可以与其他网络实体(如会话管理实体)进行消息(或信令)的交互，为终端设备分配用户临时标识。例如：移动管理实体可以通过携带第二连接请求消息的协议数据单元(protocol data unit，PDU)会话创建会话管理上 下文请求消息，将第二连接请求消息转发给会话管理实体，并接收来自会话管理实体的PDU会话创建会话管理上下文响应消息，其中PDU会话创建会话管理上下文响应消息携带为终端设备分配的用户临时标识。
在一种可能的实现中，移动管理实体还可以向用户上下文寻址实体发送用户注册状态更新请求消息，其中用户注册状态更新请求中可以携带移动管理实体的信息、注册状态(如已注册)、以及终端设备的用户标识信息，其中终端设备的用户标识信息可以为终端设备的SUPI、为终端设备分配的用户临时标识(如分配的GUTI)等中的一项或多项。用户上下文寻址实体接收到用户注册状态更新请求消息后，可以更新终端设备的用户注册状态，例如将终端设备的用户标识信息、注册状态和对应的移动管理实体的信息更新到自身保存的用户注册信息表中。另外，用户上下文寻址实体在更新完终端设备的用户注册状态后，还可以向接入管理实体发送用户注册状态更新应答消息，告知接入管理实体完成用户注册状态更新。
S404：移动管理实体向接入管理实体发送第二连接响应消息，接入管理实体接收第二连接响应消息，第二连接响应消息用于指示接入管理实体与移动管理实体之间的连接信息。
在第二连接响应消息中可以包括第二连接请求消息中携带的接入管理连接标识，以及移动管理实体创建的(或分配的)与接入管理连接标识关联的移动管理连接标识，从而指示接入管理实体与移动管理实体之间的连接信息。接入管理实体接收到第二连接响应消息后，可以将接入管理连接标识和移动管理连接标识的关联关系保存到接入管理用户上下文中。
可选地，第二连接响应消息还可以包括终端设备的注册状态(如已注册)、用户临时标识和用户网络标识等。便于在终端设备下次接入用户网络时，接入管理实体根据终端设备的注册信息，快速确定终端设备曾注册的移动管理实体，以及终端设备根据用户临时标识和用户网络标识，向该用户网络发送消息、信令、或者数据等，以及后续重新接入到该用户网络等。
S405：接入管理实体向接入网设备发送第一连接响应消息，相应的，接入网设备接收第一连接响应消息，第一连接响应消息用于指示接入网设备与接入管理实体之间的连接信息。
在第一连接响应消息中可以包括第一连接请求消息中携带的接入网连接标识，以及接入管理实体创建的(或分配的)与接入网连接标识关联的接入管理连接标识。从而指示接入管理实体与接入网设备之间的连接信息。可选地，在第一连接响应消息中还可以包括第二连接响应消息中的终端设备的注册状态(如已注册)、用户临时标识和用户网络标识。
接入网设备接收到第一连接响应消息后，可以将接入网连接标识和接入管理连接标识的关联关系保存到接入网用户上下文中。
S406：接入网设备向终端设备发送用户连接响应消息，相应的，终端设备接收用户连接响应消息。
接入网设备可以根据第一连接响应消息中的接入网连接标识，查询与接入网连接标识关联的无线连接标识，并可以根据无线连接标识，向终端设备发送携带无线连接标识的用户连接响应消息。其中用户连接响应消息中还可以携带上述终端设备的注册状态(如已注册)、用户临时标识和用户网络标识。
终端设备可以记录用户网络标识和用户临时标识等信息，用于向该用户网络发送消息、 信令、或者数据等，以及后续重新接入到该用户网络等。
通过上述步骤可建立接入网设备经过接入管理实体至移动管理实体的间接模式的连接，终端设备可以通过接入网设备，经接入管理实体连接至移动管理实体，通过接入网设备和接入管理实体与移动管理实体进行消息(或信令)的交互。
在一些实施中，在第二连接请求消息中还可以包括接入网连接标识，在第一连接响应消息中还可以包括移动管理连接标识，移动管理实体还可以在自身保存的移动管理用户上下文中记录接入网连接标识和移动管理连接标识的关联关系，接入网设备还可以在自身保存的接入网用户上下文中记录接入网连接标识和移动管理连接标识的关联关系，从而建立接入网设备和移动管理设备的直接模式的连接。终端设备还可以通过接入网设备与移动管理实体进行消息(或信令)的交互。
通过上述图4所示的通信方法，终端设备可以为不同的业务，通过接入管理实体接入相应的用户网络，与相应的用户网络中的移动管理实体建立连接。作为一种示例，终端设备可以为普通上网浏览业务，接入上网浏览业务的用户网络(如增强移动带宽(enhanced mobile broadband，eMBB)网络)，通过接入管理实体连接到上网浏览业务的用户网络中的移动管理实体A；还可以为公司专有办公业务，接入公司专有的办公用户网络，通过接入管理实体连接到公司专有的办公用户网络中的移动管理实体B。需要理解的是，终端设备连接到移动管理实体A和移动管理实体B通过的接入管理实体可以相同，也可以不同。在本申请的通信方法下，不同的用户网络可以拥有不同的移动管理实体，可以满足用户间互不影响的差异化演进的诉求。
上述图4所示的通信方法，从终端设备请求接入用户网络时，接入网设备和移动管理实体之间通过接入管理实体建立间接模式连接和直接模式连接的角度，对终端设备如何接入用户网络，连接到用户网络中的移动管理实体进行说明的。在一些实施中，终端设备请求接入用户网络时，接入网设备和移动管理实体之间，也可以采用如图7所示的方法建立直接模式的连接，下面结合图7进行具体说明。
图7为本申请实施例提供的通信方法示意图之二，该方案包括：
S701：终端设备向接入网设备发送用户连接请求消息，用户连接请求消息包括用户接入信息，相应的，接入网设备接收用户连接请求消息。
具体内容参见上述S401，此处不再赘述。
S702：接入网设备向接入管理实体发送移动管理实体寻址请求消息，相应的，接入管理实体接收移动管理实体寻址请求消息，移动管理实体寻址请求消息包括用户接入信息。
其中，接入网设备选择接收移动管理实体寻址请求消息的接入管理实体的实现，可以参照上述S402中的实现不再进行赘述。
在一些实施中，接入管理实体还可以与终端设备以及其他网络设备，如鉴权服务实体、统一数据管理实体等进行消息(或信令)的交互，完成对终端设备接入用户网络的鉴权。例如：根据用户网络的信息，鉴权当前接入管理实体是否能为终端设备请求接入的用户网络服务等。
S703：接入管理实体向接入网设备发送移动管理实体寻址响应消息，相应的，接入网设备接收移动管理实体寻址响应消息，移动管理实体寻址响应消息包括移动管理实体的信息。其中，移动管理实体的信息可以为移动管理实体的ID或IP地址等。
在用户接入信息中包括用户标识和用户网络的信息，接入管理实体接收到移动管理实体寻址请求消息后，可以根据用户接入信息，通过用户上下文寻址实体查询与用户标识关联、且支持用户网络的移动管理实体，也可以通过用户网络寻址实体查询支持用户网络的移动管理实体，并将查询到的移动管理实体的信息通过移动管理实体寻址响应消息发送给接入网设备。其中接入管理实体如何根据用户接入信息确定移动管理实体的实现，可以参照上述S403中的实现，不再进行赘述。
S704：接入网设备向移动管理实体发送第三连接请求消息，相应的，移动管理实体接收第三连接请求消息，第三连接请求消息用于请求建立接入网设备与移动管理实体之间的连接。
在第三连接请求消息中可以包括接入网连接标识，用于接入网设备与移动管理实体之间建立连接。移动管理实体接收的来自接入网设备的第三连接请求消息后，可以创建与接入网连接标识关联的移动管理连接标识，并可以为该终端设备创建移动管理用户上下文，并在移动管理用户上下文中记录接入网连接标识和移动管理连接标识的关联关系。可选地，为该终端设备创建的移动管理用户上下文可以与该终端设备的用户标识关联，以便查询。
在一些实施中，如图6所示，移动管理实体还可以与其他网络实体(如会话管理实体)进行消息(或信令)的交互，为终端设备分配用户临时标识。例如：移动管理实体可以通过携带第三连接请求消息的PDU会话创建会话管理上下文请求消息，将第三连接请求消息转发给会话管理实体，并接收来自会话管理实体的PDU会话创建会话管理上下文响应消息，其中PDU会话创建会话管理上下文响应消息携带为终端设备分配的用户临时标识。
在一种可能的实现中，移动管理实体还可以向用户上下文寻址实体发送用户注册状态更新请求消息，其中用户注册状态更新请求中可以携带移动管理实体的信息、注册状态(如已注册)、以及终端设备的用户标识信息。用户上下文寻址实体接收到用户注册状态更新请求消息后，可以更新终端设备的用户注册状态，例如将终端设备的用户标识信息、注册状态和对应的移动管理实体的信息更新到自身保存的用户注册信息表中。另外，用户上下文寻址实体在更新完终端设备的用户注册状态后，还可以向接入管理实体发送用户注册状态更新应答消息，告知接入管理实体完成用户注册状态更新。
S705：移动管理实体向接入管理实体发送第三连接响应消息，相应的，接入管理实体接收第三连接响应消息，第三连接响应消息用于指示接入网设备与移动管理实体之间的连接信息。
在第三连接响应消息中可以包括接入网连接标识，以及移动管理实体创建的(或分配的)与接入网连接标识关联的移动管理连接标识，从而指示接入网设备与移动管理实体之间的连接信息。可选的，第三连接响应消息还可以包括终端设备的注册状态(已注册)、用户临时标识和用户网络标识。
接入网设备接收到第三连接响应消息后，可以将接入网连接标识和移动管理连接标识的关联关系保存到接入网用户上下文中。
S706：接入网设备向终端设备发送用户连接响应消息，相应的，终端设备接收用户连接响应消息。
接入网设备可以根据第三连接响应消息中的接入网连接标识，查询接入网连接标识关联的无线连接标识，并可以根据无线连接标识，向终端设备发送携带无线连接标识的用户连接响应消息。其中用户连接响应消息中还可以携带上述终端设备的注册状态(已注册)、 用户临时标识和用户网络标识。
终端设备可以记录用户网络标识和用户临时标识等信息，用于向该用户网络发送消息、信令、或者数据等，以及后续重新接入到该用户网络等。
通过上述步骤可建立接入网设备至移动管理实体的直接模式的连接，终端设备可以通过接入网设备连接至移动管理实体，通过接入网设备与移动管理实体进行消息(或信令)的交互。需要理解的是，在本申请的通信方法下，不同的用户网络可以拥有不同的移动管理实体，可以满足用户间互不影响的差异化演进的诉求。
上述图4和图7所示的通信方法，主要是从终端设备有业务数据需要向用户网络发送时，终端设备主动触发接入用户网络的角度来进行说明的，在一些实施中，在用户网络有数据向终端设备发送时，如果终端设备与用户网络没有处于连接态，用户网络也可以对终端设备发起寻呼，指示终端设备接入用户网络。
作为一种示例，如图8所示，其他网络实体(如会话管理实体)确定用户网络有业务数据向终端设备发送时，其他网络实体可以向用户上下文寻址实体发送包括终端设备的用户标识的用户寻址请求消息，其中用户标识可以为终端设备的用户永久标识，如SUPI、还可以是用户网络之前为终端设备分配的用户临时标识，如GUTI，还可以是终端设备的IP地址等。
用户上下文寻址实体根据用户标识，可以查询到终端设备对应的注册信息，如终端设备对应的移动管理实体的信息(如移动管理实体的完全限定域名(fully qualified domain name，FQDN)，或者IP地址)，以及终端设备的注册状态。用户上下文寻址实体可以向其他网络实体回复携带移动管理实体的信息的用户寻址应答消息，在用户寻址应答消息中还可以携带用户的注册信息。
其他网络实体根据用户寻址应答消息中包括的移动管理实体的信息，即可向对应的移动管理实体发送携带终端设备的用户标识的网络请求消息。移动管理实体接收到来自其他网络实体的用户请求消息后，如果没有该终端设备对应的移动管理实体上下文，则需要对终端设备发起寻呼。
一种可能的实现中，如图9中A，移动管理实体可以根据终端设备的历史接入信息，如终端设备接入过的接入管理实体的信息，以及移动管理实体的寻呼策略等，向接入管理实体发送第一寻呼请求消息。作为一种示例，如果移动管理实体的寻呼策略为向终端设备历史接入过的接入管理实体发起寻呼，则移动管理实体可以向终端设备接入过的所有接入管理实体发送包括终端设备的用户标识和用户网络的信息第一寻呼请求消息。类似的，如果移动管理实的寻呼策略为向终端设备历史接入过的接入管理实体一定范围内的接入管理实体发起寻呼，则移动管理实体可以向终端设备接入过的接入管理实体一定范围内的所有接入管理实体发送包括终端设备的用户标识和用户网络的信息第一寻呼请求消息。如果移动管理实的寻呼策略为向全网接入管理实体发起寻呼，则移动管理实体向全网接入管理实体发送包括终端设备的用户标识和用户网络的信息第一寻呼请求消息。当然，移动管理实体的寻呼策略也可以为先向终端设备历史接入过的接入管理实体发起寻呼，如果未寻呼到终端设备(如发送第一寻呼消息后的设定时长内终端设备未接入用户网络，连接到接入管理实体)，再向全网接入管理实体发起寻呼等。
接入管理实体接收到第一寻呼请求消息后，也可以根据终端设备的历史接入信息，如 终端设备接入过的接入网设备的信息，以及接入管理实体的寻呼策略向接入网设备转发第一寻呼请求消息。接入网设备接收到第一寻呼请求消息，即可向接入网设备覆盖范围内的终端设备发送包括用户标识和用户网络的信息的寻呼消息，对终端设备发起寻呼。
又一种可能的实现中，如图9中的B所示，移动管理实体也可以根据终端设备的历史接入信息，如终端设备接入过的接入网设备的信息，以及移动管理实体的寻呼策略等直接向接入网设备发送第二寻呼请求消息。作为一种示例，如果移动管理实的寻呼策略为向终端设备历史接入过的接入网设备发起寻呼，则移动管理实体向终端设备接入过的所有接入网设备发送包括终端设备的用户标识和用户网络的信息第二寻呼请求消息。接入网设备接收到第二寻呼请求消息，即可向接入网设备覆盖范围内的终端设备发送包括用户标识和用户网络的信息的寻呼消息，对终端设备发起寻呼。
终端设备接收到寻呼消息后，可应答寻呼，如通过图4和图7的方式接入用户网络。
终端设备接入用户网络后，终端设备和用户网络即可进行消息(或信令)的交互，进行业务数据的传输。下面就接入网设备和移动管理实体通过直接模式连接和通过间接模式连接的情况下，由终端设备发起用户请求消息和由移动管理实体发起网络请求消息时，终端设备和网络设备如何进行消息的交互进行说明。
情况一：接入网设备和移动管理实体通过间接模式连接情况下，由终端设备发起用户请求消息，终端设备和网络设备进行消息的交互过程。
参照图10所示的通信方法示意图之四，该方法包括：
S1001：终端设备向接入网设备发送第三用户请求消息，相应的，接入网设备接收第三用户请求消息，第三用户请求消息包括无线连接标识。
在终端设备已处于接入用户网络，连接到移动管理实体的状态，意味着终端设备曾经注册到某个移动管理实体，并且获取到了用户临时标识。终端设备在有业务数据向用户网络发送时，可以向接入网设备发送包括用户临时标识和业务数据的第三用户请求消息，并在第三用户请求消息中携带终端设备接入该用户网络时采用的无线连接标识。
S1002：接入网设备向接入管理实体发送第一用户请求消息，相应的，接入管理实体接收第一用户请求消息，第一用户请求消息包括接入管理连接标识。
在间接模式下，接入网设备接收到第三用户请求消息后，可以根据第三用户请求消息携带的无线连接标识，以及自身记录的无线连接标识和接入网连接标识的关联关系，以及接入网连接标识和接入管理连接标识的关联关系，确定与无线连接标识关联的接入网连接标识，以及与无线连接标识关联的接入管理连接标识。根据接入管理连接标识，接入网设备即可向接入管理实体发送第一用户请求消息。其中第一用户请求消息可用于转发第三用户请求消息。
在第一用户请求消息中可以包括接入管理连接标识，可选地，还可以包括接入网连接标识。在第一用户请求消息中可以携带第三用户请求消息或者携带第三用户请求消息中的具体数据。作为一种示例，接入网设备可以对承载第三用户请求消息的报文进行再封装，增加用于向接入管理实体发送消息的报文头。也可以对承载第三用户请求消息的报文进行重封装，将承载第三用户请求消息的报文的报文头替换为用于向接入管理实体发送消息的报文头，从而向接入管理实体发送第一用户请求消息。
S1003：接入管理实体向移动管理实体发送第二用户请求消息，相应的，移动管理实 体接收第二用户请求消息，第二用户请求消息包括移动管理连接标识。
接入管理实体接收到第一用户请求消息后，可以根据第一用户请求消息携带的接入管理连接标识，以及自身记录的接入管理连接标识和移动管理连接标识的关联关系，确定与接入管理连接标识关联的移动管理连接标识。根据移动管理连接标识，接入管理实体即可向移动管理实体发送第二用户请求消息。其中第二用户请求消息可用于转发第一用户请求消息。
在第二用户请求消息中包括移动管理连接标识，可选地，还可以包括接入管理连接标识。
S1004：移动管理实体向接入管理实体发送第二用户应答消息，相应的，接入管理实体接收第二用户应答消息，第二用户应答消息包括接入管理连接标识。
移动管理实体接收到第二用户请求消息后，根据用户临时标识即可和其它网络实体(如会话管理实体、用户面实体等)对第二用户请求消息中携带的终端设备的业务数据进行处理，并生成业务响应数据。
对终端设备的业务数据进行处理后，移动管理实体可以根据第二用户请求消息携带的移动管理连接标识和自身记录的接入管理连接标识和移动管理连接标识的关联关系，确定接入管理连接标识。根据接入管理连接标识，移动管理实体即可向接入管理实体发送第二用户应答消息。在第二用户应答消息中包括接入管理连接标识和上述业务响应数据，还可以包括移动管理连接标识。
S1005：接入管理实体向接入网设备发送第一用户应答消息，相应的，接入网设备接收第一用户应答消息，第一用户应答消息包括接入网连接标识。
接入管理实体接收到第二用户应答消息后，可以根据第二用户应答消息携带的接入管理连接标识，以及自身记录的接入管理连接标识和接入网连接标识的关联关系，确定接入网连接标识。根据接入网连接标识，接入管理实体可以向接入网设备发送第一用户应答消息。其中第一用户应答消息可用于转发第二用户应答消息。
在第一用户应答消息中包括接入网连接标识，可选地，还可以包括接入管理连接标识。
S1006：接入网设备向终端设备发送第三用户应答消息，相应的，终端设备接收第三用户应答消息，第三用户应答消息包括无线连接标识。
接入网设备接收到第一用户应答消息后，可以根据第一用户应答消息携带的接入网连接标识，以及自身记录的无线连接标识和接入网连接标识的关联关系，确定与接入网连接标识关联的无线连接标识。根据无线连接标识，接入网设备即可向终端设备发送第三用户应答消息，其中第三用户应答消息可用于转发第一用户应答消息。
情况二：接入网设备和移动管理实体通过直接模式连接情况下，由终端设备发起用户请求消息，终端设备和网络设备进行消息的交互过程。
参照图11所示的通信方法示意图之五，该方法包括：
S1101：终端设备向接入网设备发送第三用户请求消息，相应的，接入网设备接收第三用户请求消息，第三用户请求消息包括无线连接标识。
在终端设备已处于接入用户网络，连接到移动管理实体的状态，意味着终端设备曾经注册到某个移动管理实体，并且获取到了用户临时标识。终端设备在有业务数据向用户网络发送时，可以向接入网设备发送包括用户临时标识和业务数据的第三用户请求消息，并在第三用户请求消息中携带终端设备接入该用户网络时采用的无线连接标识。
S1102：接入网设备向移动管理实体发送第四用户请求消息，相应的，接入管理实体接收第四用户请求消息，第四用户请求消息包括移动管理连接标识。
在直接模式下，接入网设备接收到第三用户请求消息后，可以根据第三用户请求消息携带的无线连接标识，以及自身记录的无线连接标识和接入网连接标识的关联关系，以及接入网连接标识和移动管理连接标识的关联关系，确定与无线连接标识关联的接入网连接标识，以及与无线连接标识关联的移动管理连接标识。根据移动管理连接标识，接入网设备即可向移动管理实体发送第四用户请求消息。其中第四用户请求消息可用于转发第三用户请求消息。
在第四用户请求消息中可以包括移动管理实体的移动管理连接标识，可选地，还可以包括接入网设备的接入网连接标识。在第四用户请求消息中可以携带第三用户请求消息或者携带第三用户请求消息中的具体数据。
S1103：移动管理实体向接入网设备发送第四用户应答消息，相应的，接入网设备接收第四用户应答消息，第四用户应答消息包括接入网连接标识。
移动管理实体接收到第四用户请求消息后，根据用户临时标识即可和其它网络实体(如会话管理实体、用户面实体等)对第四用户请求消息中携带终端设备的业务数据进行处理，并生成业务响应数据。
对终端设备的业务数据进行处理后，移动管理实体可以根据第四用户请求消息携带的移动管理连接标识和自身记录的接入网连接标识和移动管理连接标识的关联关系，确定接入网连接标识。根据接入网连接标识，移动管理实体即可向接入网设备发送第四用户应答消息。在该第四用户应答消息中包括接入网连接标识和业务响应数据，可选地，还可以包括移动管理连接标识。
S1104：接入网设备向终端设备发送第三用户应答消息，相应的，终端设备接收第三用户应答消息，第三用户应答消息包括无线连接标识。
接入网设备接收到第四用户应答消息后，可以根据第四用户应答消息携带的接入网连接标识，以及自身记录的无线连接标识和接入网连接标识的关联关系，确定与接入网连接标识关联的无线连接标识。根据无线连接标识，接入网设备即可向终端设备发送第三用户应答消息，其中第三用户应答消息可用于转发第四用户应答消息。
需要理解的是，接入网设备接收到来自终端设备的第三用户请求消息后，是根据记录的接入网连接标识与接入管理连接标识的关联关系，或接入网连接标识与移动管理连接标识的关联关系来发送第二用户请求消息，或第四用户请求消息的。并不感知发送的消息的目的是接入管理实体(即与移动管理实体间接模式连接)，还是移动管理实体(即与移动管理实体间直接模式连接)。
情况三：接入网设备和移动管理实体通过间接模式连接情况下，由移动管理实体发起网络请求消息，终端设备和网络设备进行消息的交互过程。
参照图12所示的通信方法示意图之六，该方法包括：
S1201：移动管理实体向接入管理实体发送第一网络请求消息，相应的，接入管理实体接收第一网络请求消息，第一网络请求消息包括接入管理连接标识。
作为一种示例，如图8所示，其他网络实体(如会话管理实体)确定用户网络有业务数据向终端设备发送时，其他网络实体可以向用户上下文寻址实体发送包括终端设备的用 户标识的用户寻址请求消息，其中用户标识可以为终端设备的用户永久标识，如SUPI、还可以是终端设备的用户临时标识，如GUTI，还可以是终端设备的IP地址等。
用户上下文寻址实体根据用户标识，可以查询到终端设备对应的注册信息，如终端设备对应的移动管理实体的信息(如移动管理实体的FQDN，或者IP地址)，以及终端设备的注册状态。用户上下文寻址实体可以向其他网络实体回复携带移动管理实体的信息的用户寻址应答消息，在用户寻址应答消息中还可以携带用户的注册信息。
其他网络实体根据用户寻址应答消息中包括的移动管理实体的信息，即可向对应的移动管理实体发送携带终端设备的用户标识和业务数据的网络请求消息。移动管理实体接收到来自其他网络实体的用户请求消息后，即可根据该终端设备对应的移动管理实体上下文，如根据该终端设备的用户标识关联的接入管理连接标识和移动管理连接标识的关联关系，确定接入管理连接标识。根据接入管理连接标识，移动管理实体即可向接入管理实体发送第一网络请求消息，其中第一网络请求消息可用于转发其它网络实体向移动管理实体发送的用户请求消息。
在第一网络请求消息中包括接入管理连接标识，可选的，还可以包括移动管理连接标识。
S1202：接入管理实体向接入网设备发送第二网络请求消息，相应的，接入网设备接收第二网络请求消息，第二网络请求消息包括接入网连接标识。
接入管理实体接收到第一网络请求消息后，可以根据第一网络请求消息携带的接入管理连接标识，以及自身记录的接入管理连接标识和接入网连接标识的关联关系，确定接入网连接标识。根据接入网连接标识，接入管理实体可以向接入网设备发送第二网络请求消息。其中第二网络请求消息可用于转发第一网络请求消息。
在第一网络请求消息中包括接入网连接标识，可选地，还可以包括接入管理连接标识。
S1203：接入网设备向终端设备发送第三网络请求消息，相应的，终端设备接收第三网络请求消息，第三网络请求消息包括无线连接标识。
接入网设备接收到第二网络请求消息后，可以根据第二网络请求消息携带的接入网连接标识，以及自身记录的无线连接标识和接入网连接标识的关联关系，确定与接入网连接标识关联的无线连接标识。根据无线连接标识，接入网设备即可向终端设备发送第三网络请求消息，其中第三网络请求消息可用于转发第二网络请求消息。
情况四：接入网设备和移动管理实体通过间接模式连接情况下，由移动管理实体发起网络请求消息，终端设备和网络设备进行消息的交互过程。
参照图13所示的通信方法示意图之七，该方法包括：
S1301：移动管理实体向接入网设备发送第四网络请求消息，相应的，接入网设备接收第四网络请求消息，第四网络请求消息包括接入网连接标识。
作为一种示例，如图8所示，其他网络实体(如会话管理实体)确定用户网络有业务数据向终端设备发送时，其他网络实体可以向用户上下文寻址实体发送包括终端设备的用户标识的用户寻址请求消息，其中用户标识可以为终端设备的用户永久标识，如SUPI、还可以是终端设备的用户临时标识，如GUTI，还可以是终端设备的IP地址等。
用户上下文寻址实体根据用户标识，可以查询到终端设备对应的注册信息，如终端设备对应的移动管理实体的信息(如移动管理实体的FQDN，或者IP地址)，以及终端设备 的注册状态。用户上下文寻址实体可以向其他网络实体回复携带移动管理实体的信息的用户寻址应答消息，在用户寻址应答消息中还可以携带用户的注册信息。
其他网络实体根据用户寻址应答消息中包括的移动管理实体的信息，即可向对应的移动管理实体发送携带终端设备的用户标识和业务数据的网络请求消息。移动管理实体接收到来自其他网络实体的用户请求消息后，即可根据该终端设备对应的移动管理实体上下文，如根据该终端设备的用户标识关联的接入网连接标识和移动管理连接标识的关联关系，确定接入网连接标识。根据接入网连接标识，移动管理实体即可向接入网设备发送第四网络请求消息，其中第四网络请求消息可用于转发其它网络实体向移动管理实体发送的用户请求消息。
在第四用户应答消息中包括接入网连接标识，可选地，还可以包括移动管理连接标识。
S1302：接入网设备向终端设备发送第五网络请求消息，相应的，终端设备接收第五网络请求消息，第五网络请求消息包括无线连接标识。
接入网设备接收到第四网络请求消息后，可以根据第四网络请求消息携带的接入网连接标识，以及自身记录的无线连接标识和接入网连接标识的关联关系，确定与接入网连接标识关联的无线连接标识。根据无线连接标识，接入网设备即可向终端设备发送第五网络请求消息，其中第五网络请求消息可用于转发第四网络请求消息。
可以理解的是，为了实现上述实施例中功能，接入网设备、接入管理实体和移动管理实体包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本申请中所公开的实施例描述的各示例的单元及方法步骤，本申请能够以硬件或硬件和计算机软件相结合的形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用场景和设计约束条件。
图14和图15为本申请的实施例提供的可能的通信装置的结构示意图。这些通信装置可以用于实现上述方法实施例中接入网设备、接入管理实体和移动管理实体的功能，因此也能实现上述方法实施例所具备的有益效果。在一种可能的实现中，该通信装置可以是如图2所示的接入网设备，也可以是如图2所示的接入管理实体，还可以是如图2所示的移动管理实体，还可以是应用于接入网设备、接入管理实体或移动管理实体的模块(如芯片)。
如图14所示，通信装置1400包括处理单元1410和接口单元1420，其中接口单元1420还可以为收发单元或输入输出接口。通信装置1400可用于实现上述图4-图13中所示的方法实施例中接入网设备、接入管理实体或移动管理实体的功能。
当通信装置1400用于实现图4-图13中所示的方法实施例中接入管理实体的功能时：
接口单元1420，用于接收来自接入网设备的第一连接请求消息，第一连接请求消息包括用户接入信息，用于请求建立接入网设备至移动管理实体之间的连接；处理单元1410，用于基于第一连接请求消息，通过接口单元1420向移动管理实体发送第二连接请求消息，第二连接请求消息用于请求建立接入管理实体与移动管理实体之间的连接，其中移动管理实体是接入管理实体根据用户接入信息确定的；接口单元1420，还用于接收来自移动管理实体的第二连接响应消息，第二连接响应消息用于指示接入管理实体与移动管理实体之间的连接信息；以及向接入网设备发送第一连接响应消息，第一连接响应消息用于指示接入网设备与接入管理实体之间的连接信息。
在一种可能的设计中，第一连接请求消息还包括接入网设备的接入网连接标识，第二 连接请求消息包括接入管理实体的接入管理连接标识；接入管理实体与移动管理实体之间的连接信息包括接入管理连接标识和移动管理实体的移动管理连接标识的关联关系；接入网设备与接入管理实体之间的连接信息包括接入管理连接标识和接入网连接标识的关联关系。
在一种可能的设计中，用户接入信息包括用户标识和用户网络的信息，处理单元1410基于第一连接请求消息，通过接口单元1420向移动管理实体发送第二连接请求消息时，具体用于根据用户标识和用户网络的信息，确定与用户标识关联、且支持用户网络的移动管理实体，为接收第二连接请求消息的移动管理实体。
在一种可能的设计中，用户接入信息包括用户网络的信息，处理单元1410基于第一连接请求消息，通过接口单元1420向移动管理实体发送第二连接请求消息时，具体用于根据用户网络的信息，确定支持用户网络的移动管理实体的列表；将移动管理实体的列表中的一个移动管理实体，确定为接收第二连接请求消息的移动管理实体。
在一种可能的设计中，第二连接请求消息还包括接入网连接标识，第一连接响应消息还包括接入网连接标识与移动管理连接标识的关联关系。
在一种可能的设计中，接口单元1420，还用于接收来自移动管理实体的第一寻呼请求消息，第一寻呼请求消息包括终端设备的用户标识和用户网络的信息；以及向接入网设备转发第一寻呼请求消息。
在一种可能的设计中，接口单元1420，还用于接收来自接入网设备的第一用户请求消息，第一用户请求消息包括接入管理连接标识；向移动管理实体发送第二用户请求消息，第二用户请求消息包括移动管理连接标识，其中移动管理连接标识是处理单元1410根据接入管理连接标识和移动管理连接标识的关联关系确定的；接口单元1420，还用于接收来自移动管理实体的第二用户应答消息，第二用户应答消息包括接入管理连接标识；以及向接入网设备发送第一用户应答消息，第一用户应答消息包括接入网连接标识，其中接入网连接标识是处理单元1410根据接入管理连接标识和接入网连接标识的关联关系确定的。
在一种可能的设计中，接口单元1420，还用于接收来自移动管理实体第一网络请求消息，第一网络请求消息包括接入管理连接标识；以及向接入网设备发送第二网络请求消息，第二网络请求消息包括接入网连接标识，其中接入网连接标识是处理单元1410根据接入管理连接标识和接入网连接标识的关联关系确定的。
或者，接口单元1420，用于接收来自接入网设备的移动管理实体寻址请求消息，移动管理实体寻址请求消息包括用户接入信息；接口单元1420，还用于向接入网设备发送移动管理实体寻址响应消息，移动管理实体寻址响应消息包括移动管理实体的信息，移动管理实体是处理单元1410根据用户接入信息确定的。
在一种可能的设计中，用户接入信息包括用户标识和用户网络的信息，处理单元1410根据用户接入信息确定移动管理实体时，具体用于根据用户标识和用户网络的信息，确定与用户标识关联、且支持用户网络的移动管理实体。
在一种可能的设计中，用户接入信息包括用户网络的信息，处理单元1410根据用户接入信息确定移动管理实体时，具体用于根据用户网络的信息，确定支持用户网络的移动管理实体的列表；以及将移动管理实体的列表中的一个移动管理实体，确定为移动管理实体寻址响应消息中携带的移动管理实体的信息所指示的移动管理实体。
当通信装置1400用于实现图4-图13中所示的方法实施例中移动管理实体的功能时：
接口单元1420，用于接收来自接入管理实体的第二连接请求消息，第二连接请求消息用于请求建立接入管理实体与移动管理实体之间的连接；处理单元1410，用于确定第二连接响应消息，第二连接响应消息用于指示接入管理实体与移动管理实体之间的连接信息；接口单元1420，还用于发送第二连接响应消息。
在一种可能的设计中，第二连接请求消息包括接入管理实体的接入管理连接标识；接入管理实体与移动管理实体之间的连接信息包括接入管理连接标识和移动管理实体的移动管理连接标识的关联关系。
在一种可能的设计中，接口单元1420，还用于向接入管理实体发送第一寻呼请求消息，第一寻呼请求消息包括终端设备的用户标识和用户网络的信息；或，向接入网设备发送第二寻呼请求消息，第二寻呼请求消息包括终端设备的用户标识和用户网络的信息。
在一种可能的设计中，接口单元1420，还用于接收来自接入管理实体的第二用户请求消息，第二用户请求消息包括移动管理连接标识；以及向接入管理实体发送第二用户应答消息，第二用户应答消息包括接入管理连接标识，其中接入管理连接标识是处理单元1410根据接入管理连接标识和移动管理连接标识的关联关系确定的。
在一种可能的设计中，接口单元1420，还用于向接入管理实体发送第一网络请求消息，第一网络请求消息包括接入管理连接标识，接入管理连接标识是处理单元1410根据接入管理连接标识和移动管理连接标识的关联关系确定的。
或者，接口单元1420，用于接收来自接入网设备的第三连接请求消息，第三连接请求消息用于请求建立接入网设备与移动管理实体之间的连接；处理单元1410，用于确定第三连接响应消息，第三连接响应消息用于指示接入网设备与移动管理实体之间的连接信息；接口单元1420，还用于向接入网设备发送第三连接响应消息。
在一种可能的设计中，第三连接请求消息包括接入网设备的接入网连接标识；接入网设备与移动管理实体之间的连接信息包括移动管理实体的移动管理连接标识和接入网连接标识的关联关系。
在一种可能的设计中，接口单元1420，还用于向接入网设备发送第二寻呼请求消息，第二寻呼请求消息包括终端设备的用户标识和用户网络的信息。
当通信装置1400用于实现图4-图13中所示的方法实施例中接入网设备的功能时：
处理单元1410，用于确定第一连接请求消息，第一连接请求消息包括用户接入信息，用于请求建立接入网设备至移动管理实体之间的连接；接口单元1420，用于向接入管理实体发送第一连接请求消息；以及接收来自接入管理实体的第一连接响应消息，第一连接响应消息用于指示接入网设备与接入管理实体之间的连接信息。
在一种可能的设计中，第一连接请求消息还包括接入网设备的接入网连接标识；接入网设备与接入管理实体之间的连接信息包括接入管理实体的接入管理连接标识和接入网连接标识的关联关系。
在一种可能的设计中，用户接入信息包括用户标识和用户网络的信息。
在一种可能的设计中，第一连接响应消息还包括移动管理实体的移动管理连接标识，处理单元1410，还用于记录移动管理连接标识和接入网设备的接入网连接标识的关联关系。
在一种可能的设计中，接口单元1420，还用于接收来自接入管理实体的第一寻呼请求，第一寻呼请求包括终端设备的用户标识和用户网络的信息；处理单元1410，还用于通过接口单元1420向终端设备发送寻呼消息，寻呼消息包括用户标识和用户网络的信息；或， 接口单元1420，还用于接收来自移动管理实体的第二寻呼请求，第二寻呼请求包括终端设备的用户标识和用户网络的信息；处理单元1410，还用于通过接口单元1420向终端设备发送寻呼消息，寻呼消息包括用户标识和用户网络的信息。
或者，处理单元1410，用于确定第三连接请求消息，第三连接请求消息用于请求建立接入网设备与移动管理实体之间的连接；接口单元1420，用于向移动管理实体发送第三连接请求消息；以及接收来自移动管理实体的第三连接响应消息，第三连接响应消息用于指示接入网设备与移动管理实体之间的连接信息。
在一种可能的设计中，第三连接请求消息包括接入网设备的接入网连接标识；接入网设备与移动管理实体之间的连接信息包括移动管理实体的移动管理连接标识和接入网连接标识的关联关系。
在一种可能的设计中，接口单元1420，还用于向接入管理实体发送移动管理实体寻址请求消息，移动管理实体寻址请求消息包括用户接入信息；以及接收来自接入管理实体的移动管理实体寻址响应消息，移动管理实体寻址响应消息包括移动管理实体的信息。
在一种可能的设计中，用户接入信息包括用户标识和用户网络的信息。
在一种可能的设计中，接口单元1420，还用于接收来自移动管理实体的第二寻呼请求，第二寻呼请求包括终端设备的用户标识和用户网络的信息；处理单元1410，还用于通过接口单元1420向终端设备发送寻呼消息，寻呼消息包括用户标识和用户网络的信息。
如图15所示，本申请还提供一种通信装置1500，包括处理器1510和接口电路1520。处理器1510和接口电路1520之间相互耦合。可以理解的是，接口电路1520可以为收发器、输入输出接口、输入接口、输出接口、通信接口等。可选的，通信装置1500还可以包括存储器1530，用于存储处理器1510执行的指令或存储处理器1510运行指令所需要的输入数据或存储处理器1510运行指令后产生的数据。可选的，存储器1530还可以和处理器1510集成在一起。
当通信装置1500用于实现图4-图13所示的方法时，处理器1510可以用于实现上述处理单元1410的功能，接口电路1520可以用于实现上述接口单元1420的功能。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其它通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、逻辑电路、现场可编程门阵列(field programmable gate array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的方法步骤可以通过硬件的方式来实现，也可以由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器、闪存、只读存储器、可编程只读存储器、可擦除可编程只读存储器、电可擦除可编程只读存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于网络设备或终端设备中。当然，处理器和存储介质也可以作为分立组件存在于网络设备或终端设备中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产 品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序或指令可以从一个网络设备、终端、计算机、服务器或数据中心通过有线或无线方式向另一个网络设备、终端、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，数字视频光盘；还可以是半导体介质，例如，固态硬盘。该计算机可读存储介质可以是易失性或非易失性存储介质，或可包括易失性和非易失性两种类型的存储介质。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
另外，需要理解，在本申请实施例中，“示例的”一词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。

Claims (66)

  1. 一种通信方法，其特征在于，包括：
    接入管理实体接收来自接入网设备的第一连接请求消息，所述第一连接请求消息包括用户接入信息，用于请求建立所述接入网设备至移动管理实体之间的连接；
    所述接入管理实体基于所述第一连接请求消息，向移动管理实体发送第二连接请求消息，所述第二连接请求消息用于请求建立所述接入管理实体与所述移动管理实体之间的连接，其中所述移动管理实体是所述接入管理实体根据所述用户接入信息确定的；
    所述接入管理实体接收来自所述移动管理实体的第二连接响应消息，所述第二连接响应消息用于指示所述接入管理实体与所述移动管理实体之间的连接信息；
    所述接入管理实体向所述接入网设备发送第一连接响应消息，所述第一连接响应消息用于指示所述接入网设备与所述接入管理实体之间的连接信息。
  2. 如权利要求1所述的方法，其特征在于，所述第一连接请求消息还包括所述接入网设备的接入网连接标识，所述第二连接请求消息包括所述接入管理实体的接入管理连接标识；
    所述接入管理实体与所述移动管理实体之间的连接信息包括所述接入管理连接标识和所述移动管理实体的移动管理连接标识的关联关系；
    所述接入网设备与所述接入管理实体之间的连接信息包括所述接入管理连接标识和所述接入网连接标识的关联关系。
  3. 如权利要求2所述的方法，其特征在于，所述用户接入信息包括用户标识和用户网络的信息，所述接入管理实体基于所述第一连接请求消息，向移动管理实体发送第二连接请求消息，包括：
    所述接入管理实体根据所述用户标识和用户网络的信息，确定与所述用户标识关联、且支持所述用户网络的移动管理实体，为接收所述第二连接请求消息的所述移动管理实体。
  4. 如权利要求2所述的方法，其特征在于，所述用户接入信息包括用户网络的信息，所述接入管理实体基于所述第一连接请求消息，向移动管理实体发送第二连接请求消息，包括：
    所述接入管理实体根据所述用户网络的信息，确定支持所述用户网络的至少一个移动管理实体；
    所述接入管理实体将所述至少一个移动管理实体中的一个，确定为接收所述第二连接请求消息的所述移动管理实体。
  5. 如权利要求2-4中任一项所述的方法，其特征在于，所述第一连接响应消息还包括所述移动管理连接标识。
  6. 如权利要求2-5中任一项所述的方法，其特征在于，所述方法还包括：
    所述接入管理实体接收来自所述移动管理实体的第一寻呼请求消息，所述第一寻呼请求消息包括终端设备的用户标识和用户网络的信息；
    所述接入管理实体向所述接入网设备转发所述第一寻呼请求消息。
  7. 如权利要求2-6中任一项所述的方法，其特征在于，所述方法还包括：
    所述接入管理实体接收来自所述接入网设备的第一用户请求消息，所述第一用户请求消息包括所述接入管理连接标识；
    所述接入管理实体向所述移动管理实体发送第二用户请求消息，所述第二用户请求消息包括所述移动管理连接标识，其中所述移动管理连接标识是根据所述接入管理连接标识和所述移动管理连接标识的关联关系确定的；
    所述接入管理实体接收来自所述移动管理实体的第二用户应答消息，所述第二用户应答消息包括所述接入管理连接标识；
    所述接入管理实体向所述接入网设备发送第一用户应答消息，所述第一用户应答消息包括所述接入网连接标识，其中所述接入网连接标识是根据所述接入管理连接标识和所述接入网连接标识的关联关系确定的。
  8. 如权利要求2-7中任一项所述的方法，其特征在于，所述方法还包括：
    所述接入管理实体接收来自所述移动管理实体的第一网络请求消息，所述第一网络请求消息包括所述接入管理连接标识；
    所述接入管理实体向所述接入网设备发送第二网络请求消息，所述第二网络请求消息包括所述接入网连接标识，其中所述接入网连接标识是根据所述接入管理连接标识和所述接入网连接标识的关联关系确定的。
  9. 一种通信方法，其特征在于，包括：
    接入管理实体接收来自接入网设备的移动管理实体寻址请求消息，所述移动管理实体寻址请求消息包括用户接入信息；
    所述接入管理实体向所述接入网设备发送移动管理实体寻址响应消息，所述移动管理实体寻址响应消息包括移动管理实体的信息，所述移动管理实体是接入管理实体根据用户接入信息确定的。
  10. 如权利要求9所述的方法，其特征在于，所述用户接入信息包括用户标识和用户网络的信息，所述接入管理实体根据所述用户接入信息确定所述移动管理实体，包括：
    所述接入管理实体根据所述用户标识和所述用户网络的信息，确定与所述用户标识关联、且支持所述用户网络的移动管理实体。
  11. 如权利要求9所述的方法，其特征在于，所述用户接入信息包括用户网络的信息，所述接入管理实体根据所述用户接入信息确定所述移动管理实体，包括：
    所述接入管理实体根据所述用户网络的信息，确定支持所述用户网络的移动管理实体的列表；
    所述接入管理实体将所述移动管理实体的列表中的一个移动管理实体，确定为所述移动管理实体寻址响应消息中携带的移动管理实体的信息所指示的移动管理实体。
  12. 一种通信方法，其特征在于，包括：
    移动管理实体接收来自接入管理实体的第二连接请求消息，所述第二连接请求消息用于请求建立所述接入管理实体与所述移动管理实体之间的连接；
    所述移动管理实体向所述接入管理实体发送第二连接响应消息，所述第二连接响应消息用于指示所述接入管理实体与所述移动管理实体之间的连接信息。
  13. 如权利要求12所述的方法，其特征在于，所述第二连接请求消息包括所述接入管理实体的接入管理连接标识；
    所述接入管理实体与所述移动管理实体之间的连接信息包括所述接入管理连接标识和所述移动管理实体的移动管理连接标识的关联关系。
  14. 如权利要求13所述的方法，其特征在于，所述方法还包括：
    所述移动管理实体向所述接入管理实体发送第一寻呼请求消息，所述第一寻呼请求消息包括终端设备的用户标识和用户网络的信息。
  15. 如权利要求13或14所述的方法，其特征在于，所述方法还包括：
    所述移动管理实体接收来自所述接入管理实体的第二用户请求消息，所述第二用户请求消息包括所述移动管理连接标识；
    所述移动管理实体向所述接入管理实体发送第二用户应答消息，所述第二用户应答消息包括所述接入管理连接标识，其中所述接入管理连接标识是根据所述接入管理连接标识和所述移动管理连接标识的关联关系确定的。
  16. 如权利要求13-15中任一项所述的方法，其特征在于，所述方法还包括：
    所述移动管理实体向所述接入管理实体发送第一网络请求消息，所述第一网络请求消息包括所述接入管理连接标识，所述接入管理连接标识是根据接入管理连接标识和所述移动管理连接标识的关联关系确定的。
  17. 一种通信方法，其特征在于，包括：
    移动管理实体接收来自接入网设备的第三连接请求消息，所述第三连接请求消息用于请求建立所述接入网设备与所述移动管理实体之间的连接；
    所述移动管理实体向所述接入网设备发送第三连接响应消息，所述第三连接响应消息用于指示所述接入网设备与所述移动管理实体之间的连接信息。
  18. 如权利要求17所述的方法，其特征在于，所述第三连接请求消息包括所述接入网设备的接入网连接标识；
    所述接入网设备与所述移动管理实体之间的连接信息包括所述移动管理实体的移动管理连接标识和所述接入网连接标识的关联关系。
  19. 如权利要求18所述的方法，其特征在于，所述方法还包括：
    所述移动管理实体向所述接入网设备发送第二寻呼请求消息，所述第二寻呼请求消息包括终端设备的用户标识和用户网络的信息。
  20. 一种通信方法，其特征在于，包括：
    接入网设备向接入管理实体发送第一连接请求消息，所述第一连接请求消息包括用户接入信息，用于请求建立接入网设备至移动管理实体之间的连接；
    所述接入网设备接收来自所述接入管理实体的第一连接响应消息，所述第一连接响应消息用于指示所述接入网设备与所述接入管理实体之间的连接信息。
  21. 如权利要求20所述的方法，其特征在于，所述第一连接请求消息还包括所述接入网设备的接入网连接标识；
    所述接入网设备与所述接入管理实体之间的连接信息包括所述接入管理实体的接入管理连接标识和所述接入网连接标识的关联关系。
  22. 如权利要求21所述的方法，其特征在于，所述用户接入信息包括用户标识和用户网络的信息。
  23. 如权利要求21或22所述的方法，其特征在于，所述第一连接响应消息还包括移动管理实体的移动管理连接标识，所述方法还包括：
    所述接入网设备记录所述移动管理连接标识和所述接入网设备的接入网连接标识的关联关系。
  24. 如权利要求21或22所述的方法，其特征在于，所述方法还包括：
    所述接入网设备接收来自所述接入管理实体的第一寻呼请求，所述第一寻呼请求包括终端设备的用户标识和用户网络的信息；
    所述接入网设备向所述终端设备发送寻呼消息，所述寻呼消息包括所述用户标识和用户网络的信息。
  25. 如权利要求23所述的方法，其特征在于，所述方法还包括：
    所述接入网设备接收来自所述移动管理实体的第二寻呼请求，所述第二寻呼请求包括终端设备的用户标识和用户网络的信息；
    所述接入网设备向所述终端设备发送寻呼消息，所述寻呼消息包括所述用户标识和所述用户网络的信息。
  26. 一种通信方法，其特征在于，包括：
    接入网设备向移动管理实体发送第三连接请求消息，所述第三连接请求消息用于请求建立所述接入网设备与所述移动管理实体之间的连接；
    所述接入网设备接收来自所述移动管理实体的第三连接响应消息，所述第三连接响应消息用于指示所述接入网设备与所述移动管理实体之间的连接信息。
  27. 如权利要求26所述的方法，其特征在于，所述第三连接请求消息包括所述接入网设备的接入网连接标识；
    所述接入网设备与所述移动管理实体之间的连接信息包括所述移动管理实体的移动管理连接标识和所述接入网连接标识的关联关系。
  28. 如权利要求26或27所述的方法，其特征在于，所述方法还包括：
    所述接入网设备向接入管理实体发送移动管理实体寻址请求消息，所述移动管理实体寻址请求消息包括用户接入信息；
    所述接入网设备接收来自所述接入管理实体的移动管理实体寻址响应消息，所述移动管理实体寻址响应消息包括所述移动管理实体的信息。
  29. 如权利要求28所述的方法，其特征在于，所述用户接入信息包括用户标识和用户网络的信息。
  30. 如权利要求27所述的方法，其特征在于，所述方法还包括：
    所述接入网设备接收来自所述移动管理实体的第二寻呼请求，所述第二寻呼请求包括终端设备的用户标识和用户网络的信息；
    所述接入网设备向所述终端设备发送寻呼消息，寻呼消息包括用户标识和用户网络的信息。
  31. 一种通信装置，其特征在于，包括接口单元和处理单元；
    所述接口单元，用于接收来自接入网设备的第一连接请求消息，所述第一连接请求消息包括用户接入信息，用于请求建立所述接入网设备至移动管理实体之间的连接；
    所述处理单元，用于基于所述第一连接请求消息，通过所述接口单元向移动管理实体发送第二连接请求消息，所述第二连接请求消息用于请求建立接入管理实体与所述移动管理实体之间的连接，其中所述移动管理实体是所述处理单元根据所述用户接入信息确定的；
    所述接口单元，还用于接收来自所述移动管理实体的第二连接响应消息，所述第二连接响应消息用于指示所述接入管理实体与所述移动管理实体之间的连接信息；以及向所述接入网设备发送第一连接响应消息，所述第一连接响应消息用于指示所述接入网设备与所述接入管理实体之间的连接信息。
  32. 如权利要求31所述的装置，其特征在于，所述第一连接请求消息还包括所述接入网设备的接入网连接标识，所述第二连接请求消息包括所述接入管理实体的接入管理连接标识；
    所述接入管理实体与所述移动管理实体之间的连接信息包括所述接入管理连接标识和所述移动管理实体的移动管理连接标识的关联关系；
    所述接入网设备与所述接入管理实体之间的连接信息包括所述接入管理连接标识和所述接入网连接标识的关联关系。
  33. 如权利要求32所述的装置，其特征在于，所述用户接入信息包括用户标识和用户网络的信息，所述处理单元基于第一连接请求消息，通过所述接口单元向移动管理实体发送第二连接请求消息时，具体用于根据所述用户标识和用户网络的信息，确定与所述用户标识关联、且支持所述用户网络的移动管理实体，为接收所述第二连接请求消息的所述移动管理实体。
  34. 如权利要求32所述的装置，其特征在于，所述用户接入信息包括用户网络的信息，所述处理单元基于第一连接请求消息，通过所述接口单元向移动管理实体发送第二连接请求消息时，具体用于根据所述用户网络的信息，确定支持所述用户网络的至少一个移动管理实体；将所述至少一个移动管理实体中的一个，确定为接收所述第二连接请求消息的所述移动管理实体。
  35. 如权利要求32-34中任一项所述的装置，其特征在于，所述第一连接响应消息还包括所述移动管理连接标识。
  36. 如权利要求32-35中任一项所述的装置，其特征在于，所述接口单元，还用于接收来自所述移动管理实体的第一寻呼请求消息，所述第一寻呼请求消息包括终端设备的用户标识和用户网络的信息；以及向所述接入网设备转发所述第一寻呼请求消息。
  37. 如权利要求32-36中任一项所述的装置，其特征在于，所述接口单元，还用于接收来自所述接入网设备的第一用户请求消息，所述第一用户请求消息包括接入管理连接标识；向所述移动管理实体发送第二用户请求消息，所述第二用户请求消息包括所述移动管理连接标识，其中所述移动管理连接标识是所述处理单元根据所述接入管理连接标识和所述移动管理连接标识的关联关系确定的；
    所述接口单元，还用于接收来自所述移动管理实体的第二用户应答消息，所述第二用户应答消息包括所述接入管理连接标识；以及向所述接入网设备发送第一用户应答消息，所述第一用户应答消息包括所述接入网连接标识，其中所述接入网连接标识是所述处理单元根据所述接入管理连接标识和所述接入网连接标识的关联关系确定的。
  38. 如权利要求32-37中任一项所述的装置，其特征在于，所述接口单元，还用于接收来自所述移动管理实体的第一网络请求消息，所述第一网络请求消息包括所述接入管理连接标识；以及向所述接入网设备发送第二网络请求消息，所述第二网络请求消息包括所述接入网连接标识，其中所述接入网连接标识是所述处理单元根据所述接入管理连接标识和所述接入网连接标识的关联关系确定的。
  39. 一种通信装置，其特征在于，包括接口单元和处理单元；
    所述接口单元，用于接收来自接入网设备的移动管理实体寻址请求消息，所述移动管理实体寻址请求消息包括用户接入信息；
    所述处理单元，用于根据所述用户接入信息确定移动管理实体；
    所述接口单元，还用于向所述接入网设备发送移动管理实体寻址响应消息，所述移动管理实体寻址响应消息包括所述移动管理实体的信息。
  40. 如权利要求39所述的装置，其特征在于，所述用户接入信息包括用户标识和用户网络的信息，所述处理单元根据所述用户接入信息确定移动管理实体时，具体用于根据所述用户标识和所述用户网络的信息，确定与所述用户标识关联、且支持所述用户网络的移动管理实体。
  41. 如权利要求39所述的装置，其特征在于，所述用户接入信息包括用户网络的信息，所述处理单元根据所述用户接入信息确定移动管理实体时，具体用于根据所述用户网络的信息，确定支持所述用户网络的移动管理实体的列表；以及将所述移动管理实体的列表中的一个移动管理实体，确定为所述移动管理实体寻址响应消息中携带的移动管理实体的信息所指示的移动管理实体。
  42. 一种通信装置，其特征在于，包括接口单元和处理单元；
    所述接口单元，用于接收来自接入管理实体的第二连接请求消息，所述第二连接请求消息用于请求建立所述接入管理实体与移动管理实体之间的连接；
    所述处理单元，用于确定第二连接响应消息，所述第二连接响应消息用于指示所述接入管理实体与所述移动管理实体之间的连接信息；
    所述接口单元，还用于向所述接入管理实体发送所述第二连接响应消息。
  43. 如权利要求42所述的装置，其特征在于，所述第二连接请求消息包括所述接入管理实体的接入管理连接标识；
    所述接入管理实体与所述移动管理实体之间的连接信息包括所述接入管理连接标识和所述移动管理实体的移动管理连接标识的关联关系。
  44. 如权利要求43所述的装置，其特征在于，所述接口单元，还用于向所述接入管理实体发送第一寻呼请求消息，所述第一寻呼请求消息包括终端设备的用户标识和用户网络的信息。
  45. 如权利要求43或44所述的装置，其特征在于，所述接口单元，还用于接收来自所述接入管理实体的第二用户请求消息，所述第二用户请求消息包括所述移动管理连接标识；以及向所述接入管理实体发送第二用户应答消息，所述第二用户应答消息包括所述接入管理连接标识，其中所述接入管理连接标识是所述处理单元根据所述接入管理连接标识和所述移动管理连接标识的关联关系确定的。
  46. 如权利要求43-45中任一项所述的装置，其特征在于，所述接口单元，还用于向所述接入管理实体发送第一网络请求消息，所述接第一网络请求消息包括接入管理连接标识，所述接入管理连接标识是所述处理单元根据所述接入管理连接标识和所述移动管理连接标识的关联关系确定的。
  47. 一种通信装置，其特征在于，包括接口单元和处理单元；
    所述接口单元，用于接收来自接入网设备的第三连接请求消息，所述第三连接请求消息用于请求建立所述接入网设备与移动管理实体之间的连接；
    所述处理单元，用于确定第三连接响应消息，所述第三连接响应消息用于指示所述接入网设备与所述移动管理实体之间的连接信息；
    所述接口单元，还用于向所述接入网设备发送所述第三连接响应消息。
  48. 如权利要求47所述的装置，其特征在于，所述第三连接请求消息包括所述接入网 设备的接入网连接标识；
    所述接入网设备与所述移动管理实体之间的连接信息包括所述移动管理实体的移动管理连接标识和所述接入网连接标识的关联关系。
  49. 如权利要求48所述的装置，其特征在于，所述接口单元，还用于向所述接入网设备发送第二寻呼请求消息，所述第二寻呼请求消息包括终端设备的用户标识和用户网络的信息。
  50. 一种通信装置，其特征在于，包括接口单元和处理单元；
    所述处理单元，用于确定第一连接请求消息，所述第一连接请求消息包括用户接入信息，用于请求建立接入网设备至移动管理实体之间的连接；
    所述接口单元，用于向接入管理实体发送所述第一连接请求消息；以及接收来自所述接入管理实体的第一连接响应消息，所述第一连接响应消息用于指示所述接入网设备与所述接入管理实体之间的连接信息。
  51. 如权利要求50所述的装置，其特征在于，所述第一连接请求消息还包括所述接入网设备的接入网连接标识；
    所述接入网设备与所述接入管理实体之间的连接信息包括所述接入管理实体的接入管理连接标识和所述接入网连接标识的关联关系。
  52. 如权利要求51所述的装置，其特征在于，所述用户接入信息包括用户标识和用户网络的信息。
  53. 如权利要求51或52所述的装置，其特征在于，所述第一连接响应消息还包括移动管理实体的移动管理连接标识，所述处理单元，还用于记录所述移动管理连接标识和所述接入网设备的接入网连接标识的关联关系。
  54. 如权利要求51或52所述的装置，其特征在于，所述接口单元，还用于接收来自接入管理实体的第一寻呼请求，所述第一寻呼请求包括终端设备的用户标识和用户网络的信息；
    所述处理单元，还用于通过所述接口单元向终端设备发送寻呼消息，所述寻呼消息包括用户标识和用户网络的信息。
  55. 如权利要求53所述的装置，其特征在于，所述接口单元，还用于接收来自所述移动管理实体的第二寻呼请求，所述第二寻呼请求包括终端设备的用户标识和用户网络的信息；
    所述处理单元，还用于通过所述接口单元向所述终端设备发送寻呼消息，所述寻呼消息包括所述用户标识和所述用户网络的信息。
  56. 一种通信装置，其特征在于，包括接口单元和处理单元；
    所述处理单元，用于确定第三连接请求消息，所述第三连接请求消息用于请求建立接入网设备与移动管理实体之间的连接；
    所述接口单元，用于向移动管理实体发送所述第三连接请求消息；以及接收来自所述移动管理实体的第三连接响应消息，所述第三连接响应消息用于指示所述接入网设备与所述移动管理实体之间的连接信息。
  57. 如权利要求56所述的装置，其特征在于，所述第三连接请求消息包括所述接入网设备的接入网连接标识；
    所述接入网设备与所述移动管理实体之间的连接信息包括所述移动管理实体的移动 管理连接标识和所述接入网连接标识的关联关系。
  58. 如权利要求56或57所述的装置，其特征在于，所述接口单元，还用于向接入管理实体发送移动管理实体寻址请求消息，所述移动管理实体寻址请求消息包括用户接入信息；以及接收来自所述接入管理实体的移动管理实体寻址响应消息，所述移动管理实体寻址响应消息包括所述移动管理实体的信息。
  59. 如权利要求58所述的装置，其特征在于，所述用户接入信息包括用户标识和用户网络的信息。
  60. 如权利要求57所述的装置，其特征在于，所述接口单元，还用于接收来自所述移动管理实体的第二寻呼请求，所述第二寻呼请求包括终端设备的用户标识和用户网络的信息；
    所述处理单元，还用于通过所述接口单元向所述终端设备发送寻呼消息，所述寻呼消息包括用户标识和用户网络的信息。
  61. 一种通信装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器，或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行指令用于实现如权利要求1-30中任一项所述的方法。
  62. 一种计算机程序产品，其特征在于，包含指令，当所述指令被处理器执行，使得如权利要求1-30中任一项所述的方法被实现。
  63. 一种芯片，其特征在于，所述芯片与存储器耦合，用于读取并执行存储器中存储的程序或指令，实现如权利要求1-30中任一项所述的方法。
  64. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序或指令，当所述计算机程序或指令被处理器执行时，使得如权利要求1-30中任一项所述的方法被实现。
  65. 一种通信系统，其特征在于，所述通信系统包括：接入管理实体、移动管理实体和接入网设备；
    所述接入管理实体，用于实现如权利要求1-8中任一项所述的方法；
    所述移动管理实体，用于实现如权利要求12-16中任一项所述的方法；
    所述接入网设备，用于实现如权利要求20-25中任一项所述的方法。
  66. 一种通信系统，其特征在于，所述通信系统包括：接入管理实体、移动管理实体和接入网设备；
    所述接入管理实体，用于实现如权利要求9-11中任一项所述的方法；
    所述移动管理实体，用于实现如权利要求17-19中任一项所述的方法；
    所述接入网设备，用于实现如权利要求26-30中任一项所述的方法。
PCT/CN2023/072021 2022-01-29 2023-01-13 一种通信方法及装置 WO2023143111A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210112910.3A CN116567784A (zh) 2022-01-29 2022-01-29 一种通信方法及装置
CN202210112910.3 2022-01-29

Publications (1)

Publication Number Publication Date
WO2023143111A1 true WO2023143111A1 (zh) 2023-08-03

Family

ID=87470481

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/072021 WO2023143111A1 (zh) 2022-01-29 2023-01-13 一种通信方法及装置

Country Status (2)

Country Link
CN (1) CN116567784A (zh)
WO (1) WO2023143111A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102652455A (zh) * 2009-12-16 2012-08-29 瑞典爱立信有限公司 用于处理s1应用协议信令连接的建立的方法和装置
CN110636639A (zh) * 2018-06-25 2019-12-31 大唐移动通信设备有限公司 一种会话管理方法及装置
CN110650504A (zh) * 2018-06-26 2020-01-03 华为技术有限公司 一种会话处理方法及装置
CN113422694A (zh) * 2021-06-08 2021-09-21 腾讯科技（深圳）有限公司 通信方法、装置、介质及电子设备
WO2021204132A1 (zh) * 2020-04-10 2021-10-14 华为技术有限公司 一种通信方法及通信装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102652455A (zh) * 2009-12-16 2012-08-29 瑞典爱立信有限公司 用于处理s1应用协议信令连接的建立的方法和装置
CN110636639A (zh) * 2018-06-25 2019-12-31 大唐移动通信设备有限公司 一种会话管理方法及装置
CN110650504A (zh) * 2018-06-26 2020-01-03 华为技术有限公司 一种会话处理方法及装置
WO2021204132A1 (zh) * 2020-04-10 2021-10-14 华为技术有限公司 一种通信方法及通信装置
CN113422694A (zh) * 2021-06-08 2021-09-21 腾讯科技（深圳）有限公司 通信方法、装置、介质及电子设备

Also Published As

Publication number Publication date
CN116567784A (zh) 2023-08-08

Similar Documents

Publication Publication Date Title
US10743279B2 (en) Network registration and network slice selection system and method
JP7187580B2 (ja) セッション管理の方法、装置、およびシステム
WO2022012310A1 (zh) 一种通信方法及装置
WO2020168840A1 (zh) 网络节点选择方法及装置
US20230029714A1 (en) Authorization method, policy control function device, and access and mobility management function device
WO2019196811A1 (zh) 通信方法和相关装置
US20230199632A1 (en) Access to Second Network
US20210211859A1 (en) Local Area Network Communication Management Method and Apparatus
US10999768B2 (en) Session context handling method, network element, and terminal device
WO2022017285A1 (zh) 报文转发方法、装置及系统
US11963095B2 (en) Methods and systems for handling network slice admission control for UE
WO2022022322A1 (zh) 访问本地网络的方法和装置
US20240007983A1 (en) Method, device, and system for core network device re-allocation in wireless network
US20230370992A1 (en) Method, device, and system for core network device re-allocation in wireless network
EP4024940A1 (en) Communication method and apparatus
WO2023143111A1 (zh) 一种通信方法及装置
WO2022213799A1 (zh) 一种多播业务的通信方法及装置
WO2023143212A1 (zh) 一种通信方法及装置
WO2023015973A1 (zh) 一种网络切片准入控制方法和装置
WO2023020046A1 (zh) 一种通信方法及通信装置
WO2023197737A1 (zh) 报文发送方法、pin管理方法、通信装置及通信系统
WO2023179331A1 (zh) 一种发送数据包的方法、通信装置及通信系统
WO2023207357A1 (zh) 一种通信方法和通信装置
WO2023185298A1 (zh) 一种组播/广播业务通信的方法、装置以及系统
WO2023016262A1 (zh) 一种通信方法及装置

Legal Events

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

Ref document number: 23745994

Country of ref document: EP

Kind code of ref document: A1