WO2020199991A1 - 通信方法、设备及系统 - Google Patents

通信方法、设备及系统 Download PDF

Info

Publication number
WO2020199991A1
WO2020199991A1 PCT/CN2020/080963 CN2020080963W WO2020199991A1 WO 2020199991 A1 WO2020199991 A1 WO 2020199991A1 CN 2020080963 W CN2020080963 W CN 2020080963W WO 2020199991 A1 WO2020199991 A1 WO 2020199991A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
network
identity
terminal device
cell
Prior art date
Application number
PCT/CN2020/080963
Other languages
English (en)
French (fr)
Inventor
曹龙雨
王耀光
于益俊
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20782702.3A priority Critical patent/EP3930378B1/en
Publication of WO2020199991A1 publication Critical patent/WO2020199991A1/zh
Priority to US17/490,447 priority patent/US11956691B2/en

Links

Images

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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00835—Determination of neighbour cell lists
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H04W40/36—Modification of an existing route due to handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events

Definitions

  • This application relates to the field of communication technology, and in particular to communication methods, equipment and systems.
  • the 3rd generation partnership project (3GPP) standards organization has defined two types of private network models, namely type A (type A) mode and type B (type B).
  • B) Mode the vertical industry private network is independent, and it does not have any interaction requirements with the public land mobile network (PLMN).
  • PLMN public land mobile network
  • the Type A mode it has interworking requirements with PLMN.
  • both factory A and factory B are located in the private network coverage of type A mode.
  • PLMN is required to provide network service guarantee Therefore, the private network of Type A mode and PLMN have intercommunication requirements.
  • the terminal device may be located in the overlapping coverage area of the private network of the type A mode and the PLMN.
  • the terminal device leaves the coverage area of the private network in the type A mode, how the terminal device can switch to the target cell while ensuring service continuity is a problem to be solved urgently.
  • the embodiments of the present application provide a communication method, device, and system, which can make the terminal device switch to the target cell after the terminal device moves out of the coverage of the first private network, while ensuring business continuity.
  • a communication method includes: a first mobility management network element receives a first cell identity and a network identity from a first network element, where the network identity includes the identity of the first private network and the second private network. The identity of the network; the first mobility management network element obtains the information of the second network element according to the first cell identity and the network identity, where the first network element serves the terminal equipment in the first private network, and the second network The element serves the terminal device in the second private network; the first mobility management network element sends the first cell identity and the network identity to the second network element indicated by the information of the second network element, and the first cell
  • the identifier and the network identifier are used to obtain downlink routing information, where the downlink routing information is used to indicate the transmission of downlink data from a first user plane entity in the first private network to a second user plane entity in the second private network. transmission.
  • the terminal device when the terminal device moves out of the coverage of the first private network, it can select the second private network, and the first mobility management network element sends to the second network element in the second private network
  • the first cell identity and network identity of the network can be used to obtain downlink routing information, and the downlink routing information is used to indicate the transmission of downlink data from the first user plane entity in the first private network to the second user plane entity in the second private network. transmission.
  • the first user plane entity receives the downlink data, it can send the downlink data to the second user plane entity according to the downlink data routing information, thereby maintaining service continuity.
  • the first mobility management network element obtains the information of the second network element according to the first cell identity and the network identity, including: the first mobility management network element determines that the first cell identity belongs to the second network element A list of the first tracking area TA allocated by a mobility management network element to the terminal device; the first mobility management network element sends the first cell identity and the network identity, the first cell identity and the network identity to the network storage function network element Information used to determine the second network element; the first mobility management network element receives the information of the second network element from the network storage function network element. That is, in the embodiment of the present application, the first mobility management network element may obtain information of the second network element from the network storage function network element.
  • the communication method further includes: the first mobility management network element receives the second cell identity from the terminal device; the first mobility management network element allocates a first TA list to the terminal device, wherein the first TA list A TA list includes the second cell identifier and the first cell identifier; the first mobility management network element sends the first TA list to the terminal device through the first network element transmission, where the first TA list is used for Identifies the location area where the terminal device is registered. Based on this solution, the terminal device can learn the location area where the terminal device is registered.
  • the first mobility management network element obtains information of the second network element according to the first cell identity and the network identity, including: the first mobility management network element determines that the first cell identity does not belong to the The first TA list allocated by the first mobility management network element to the terminal device; the first mobility management network element sends the first cell identity to the network storage function network element; the first mobility management network element receives the network storage function network element Information about the second mobility management network element, where the second mobility management network element is a mobility management network element that can serve the cell corresponding to the first cell identity; the first mobility management network element sends the information to the second mobility management network element The indicated second mobility management network element sends the first cell identity and the network identity, the first cell identity and the network identity are used to determine the information of the second network element; the first mobility management network element receives the information from the Information about the second network element of the second mobility management network element.
  • the first cell identity may not be allocated by the first mobility management network element.
  • the first mobility management network element needs to obtain the second cell identity from the network storage function network element through the second mobility management network element. Information about the network element.
  • the communication method further includes: the first mobility management network element receives the second cell identity from the terminal device; the first mobility management network element allocates a first TA list to the terminal device, wherein the first TA list A TA list includes the second cell identity; the first mobility management network element sends the first TA list to the terminal device through the first network element transmission, where the first TA list is used to identify the terminal device registered Location area.
  • the terminal device can directly access the network from the private network, and complete the two-level hierarchical registration of the first network element and the first mobility management network element.
  • the communication method further includes: the first mobility management network element receives the downlink routing information from the second network element, where the downlink routing information is allocated by the second user plane entity; The first mobility management network element sends the downlink routing information to the first user plane entity through the first network element. That is to say, in this solution, when the terminal device moves out of the coverage of the first private network and selects the second private network, the second user plane entity in the second private network allocates downlink routing information and transfers the downlink routing information The routing information is sent to the first user plane entity in the first private network.
  • the communication method further includes: the first mobility management network element receives the second cell identity from the terminal device; the first mobility management network element receives the network identity from the unified data management network element; The management network element determines, according to the second cell identifier and the network identifier, that the cell identified by the second cell identifier deploys a private network accessible by the terminal device; the first mobility management network element sends registration rejection information to the terminal device The registration rejection information is used to indicate that the terminal device is registered in a private network accessible by the terminal device. Based on this solution, when the terminal device is in the overlapping coverage area of the public network and the private network accessible by the terminal device, the terminal device selects the public network to reside, and initiates the registration of the terminal device to the public network. After the terminal device receives the registration rejection information, the terminal device can register to the private network accessible by the terminal device.
  • a communication method includes: a first network element obtains a first cell identity and a network identity, the network identity includes an identity of a first private network and an identity of a second private network, the first network The element serves the terminal device in the first private network; the first network element determines, according to the first cell identity, that the area where the terminal device is currently located exceeds the service range of the cell identified by the first cell identity; the first network The element sends the first cell identity and the network identity to the first mobility management network element, where the first cell identity and the network identity are used to obtain downlink routing information, where the downlink routing information is used to indicate that downlink data is transferred from the first Transmission from the first user plane entity in the private network to the second user plane entity in the second private network.
  • the terminal device after the terminal device moves out of the coverage of the first private network, it can select the second private network, and the first network element sends the first cell identity and the first cell identity to the first mobility management network element.
  • the network identifier may be used to obtain downlink routing information, which is used to indicate the transmission of downlink data from the first user plane entity in the first private network to the second user plane entity in the second private network.
  • the first user plane entity receives the downlink data, it can send the downlink data to the second user plane entity according to the downlink data routing information, thereby maintaining service continuity.
  • the communication method further includes: the first network element receives downlink routing information from the first mobility management network element, where the downlink routing information is allocated by the second user plane entity; A network element sends the downlink routing information to the first user plane entity. That is to say, in this solution, when the terminal device moves out of the coverage of the first private network and selects the second private network, the second user plane entity in the second private network allocates downlink routing information and transfers the downlink routing information The routing information is sent to the first user plane entity in the first private network.
  • the communication method further includes: the first network element receives the second cell identity from the terminal device; the first network element sends the second cell identity to the first mobility management network element; the first network The element receives a first tracking area TA list allocated by the first mobility management network element for the terminal device from the first mobility management network element, where the first TA list includes the second cell identity and the first cell identity Or, the first TA list includes the second cell identity; the first network element sends the first TA list to the terminal device, and the first TA list is used to identify the location area registered by the terminal device. Based on this solution, the terminal device can be registered in an accessible private network.
  • the communication method further includes:
  • the first network element sends the identity of the first network element, the cell identity of the serving cell of the first network element, and the network identity of the network where the first network element is located to the network storage function network element for registration to the network storage function Network element. Based on this solution, the registration of the network attribute information of the first network element can be realized, and in the subsequent service processing process, other network function entities can accurately obtain the attribute information of the first network element, thereby ensuring the normal operation of the service.
  • a communication method includes: a first mobility management network element receives a first cell identity and a network identity from the first network element, the network identity includes the identity of the first private network, wherein the The first network element serves the terminal device in the first private network; the first mobility management network element determines that the second mobility management network element is currently the terminal device in the public network according to the first cell identity and the network identity Service; the first mobility management network element determines the centralized unit control plane entity in the public network serving the terminal device; the first mobility management network element sends the first cell identity and the control plane entity to the centralized unit control plane entity in the public network A network identifier, where the first cell identifier and the network identifier are used to obtain downlink routing information, where the downlink routing information is used to indicate that downlink data is transferred from the first user plane entity in the first private network to the first user plane entity in the public network 2.
  • Transmission of user plane entities Because in this solution, when the terminal device moves out of the coverage of the first private network, it can choose to go to the public network, and the first mobility management network element in the public network can send the first mobile management network element to the centralized unit control plane entity in the public network.
  • a cell identity and a network identity, the first cell identity and the network identity are used to obtain downlink routing information, and the downlink routing information is used to indicate that downlink data is transferred from the first user plane entity in the first private network to the first user plane entity in the public network 2.
  • Transmission of user plane entities In this way, when the first user plane entity receives the downlink data, it can send the downlink data to the second user plane entity according to the downlink data routing information, thereby maintaining service continuity.
  • a communication method includes: a first network element obtains a first cell identity and a network identity, the network identity includes an identity of a first private network, wherein the first network element is in the first The private network serves the terminal device; the first network element determines, according to the first cell identifier, that the current area of the terminal device exceeds the service range of the cell identified by the first cell identifier; the first network element moves to the first The management network element sends the first cell identity and the network identity, and the first cell identity and the network identity are used to obtain downlink routing information, where the downlink routing information is used to indicate that downlink data is transferred from the first private network in the first private network.
  • the terminal device After the terminal device moves out of the coverage of the first private network, it can select the public network, and the first network element in the first private network can send the first cell identification to the first mobility management network element.
  • a network identifier where the first cell identifier and the network identifier are used to obtain downlink routing information, and the downlink routing information is used to indicate that downlink data is transferred from a first user plane entity in the first private network to a second user plane entity in the public network Transmission.
  • the first user plane entity receives the downlink data, it can send the downlink data to the second user plane entity according to the downlink data routing information, thereby maintaining service continuity.
  • a communication method includes: a first network element determines a terminal identity of a terminal device, a paging cell, and a centralized unit control plane entity corresponding to the paging cell; The centralized unit control plane entity corresponding to the paging cell sends a paging message, and the paging message includes the terminal identifier and the information of the paging cell. Based on this solution, the first network element can implement paging processing for idle state terminal devices.
  • the first network element determines the terminal identification of the terminal device, the paging cell, and the centralized unit control plane entity corresponding to the paging cell, including: the first network element receives the first user plane The event report of the network element, the event report includes the terminal device Internet Protocol IP address information in the packet header; the first network element determines the terminal identification, paging cell, and paging cell of the terminal device based on the terminal device IP address information in the packet header The control plane entity of the centralized unit corresponding to the paging cell.
  • the paging method provided in the embodiment of the present application can be triggered by data.
  • the first network element determines the terminal identity of the terminal device, the paging cell, and the centralized unit control plane entity corresponding to the paging cell, including: the first network element receives an idle state terminal device Signaling processing request message; the first network element determines the terminal identity of the terminal device, the paging cell, and the centralized unit control plane entity corresponding to the paging cell according to the signaling processing request message.
  • the paging method provided in the embodiment of the present application can be triggered by signaling.
  • the method further includes: if the first network element does not receive the service request of the terminal device after being paged multiple times or within a preset time, the first network element manages to the first mobility The network element sends a paging optimization request, and the paging optimization request is used for the first mobility management network element to expand the paging range. Based on this solution, the first mobility management network element can perform a wider range of paging processing on the paging of the terminal device.
  • a communication device for implementing the above-mentioned various methods.
  • the communication device may be the first mobility management network element in the first aspect or the third aspect, or an apparatus including the first mobility management network element; or, the communication device may be the second or fourth aspect or The first network element in the fifth aspect, or a device including the above-mentioned first network element.
  • the communication device includes a module, unit, or means corresponding to the foregoing method, and the module, unit, or means can be implemented by hardware, software, or hardware execution of corresponding software.
  • the hardware or software includes one or more modules or units corresponding to the above-mentioned functions.
  • a communication device including: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the communication device can execute the communication method described in the first aspect.
  • the communication device may be the first mobility management network element in the first aspect or the third aspect, or an apparatus including the first mobility management network element; or, the communication device may be the second or fourth aspect or The first network element in the fifth aspect, or a device including the above-mentioned first network element.
  • a communication device including: a processor; the processor is configured to couple with a memory, and after reading an instruction in the memory, execute any one of the first to fifth aspects according to the instruction.
  • the communication device may be the first mobility management network element in the first aspect or the third aspect, or an apparatus including the first mobility management network element; or, the communication device may be the second or fourth aspect or The first network element in the fifth aspect, or a device including the above-mentioned first network element.
  • a computer-readable storage medium stores instructions that, when run on a computer, enable the computer to execute any one of the above-mentioned first to fifth aspects.
  • a computer program product containing instructions which when running on a computer, enables the computer to execute the communication method described in any one of the first to fifth aspects.
  • a communication device for example, the communication device may be a chip or a chip system
  • the communication device includes a processor, and is configured to implement any one of the first to fifth aspects mentioned above. Function.
  • the communication device further includes a memory, and the memory is used to store necessary program instructions and data.
  • the communication device is a chip system, it may be composed of chips, or may include chips and other discrete devices.
  • a communication system in a twelfth aspect, includes a first mobility management network element and a first network element; wherein the first network element is used to obtain a first cell identity and a network identity, and the network identity includes The identity of the first private network and the identity of the second private network.
  • the first network element serves the terminal device in the first private network; the first network element is also used to determine the current location of the terminal device based on the first cell identity The area exceeds the service range of the cell identified by the first cell identity; the first network element is also used to send the first cell identity and the network identity to the first mobility management network element; the first mobility management network element, It is used to receive the first cell identity and the network identity from the first network element; the first mobility management network element is also used to obtain information about the second network element according to the first cell identity and the network identity, where: The second network element serves the terminal device in the second private network; the first mobility management network element is also used to send the first cell identifier and the second network element indicated by the information of the second network element The network identifier, the first cell identifier, and the network identifier are used to obtain downlink routing information, where the downlink routing information is used to indicate that downlink data is transferred from the first user plane entity in the first private network to the second private network The second user plane entity in the transmission.
  • the terminal device when the terminal device moves out of the coverage of the first private network, it can select the second private network, and the first mobility management network element sends to the second network element in the second private network
  • the first cell identity and network identity of the network can be used to obtain downlink routing information, and the downlink routing information is used to indicate the transmission of downlink data from the first user plane entity in the first private network to the second user plane entity in the second private network. transmission.
  • the first user plane entity receives the downlink data, it can send the downlink data to the second user plane entity according to the downlink data routing information, thereby maintaining service continuity.
  • a communication system in a thirteenth aspect, includes a first mobility management network element and a first network element; wherein the first network element is used to obtain a first cell identity and a network identity, and the network identity includes The identity of the first private network, where the first network element serves the terminal device in the first private network; the first network element is also used to determine that the area where the terminal device is currently located exceeds The service range of the cell identified by the first cell identity; the first network element is also used to send the first cell identity and the network identity to the first mobility management network element; the first mobility management network element is used to receive The first cell identity and the network identity from the first network element; the first mobility management network element is also used to determine that the second mobility management network element is currently in the public network according to the first cell identity and the network identity Serving the terminal device; the first mobility management network element is also used to determine the centralized unit control plane entity in the public network that serves the terminal device; the first mobility management network element is also used to provide centralized information to the public network The unit control plane entity send
  • the terminal device when it moves out of the coverage of the first private network, it can choose to go to the public network, and the first mobility management network element in the public network can send the first mobile management network element to the centralized unit control plane entity in the public network.
  • a cell identity and a network identity, the first cell identity and the network identity are used to obtain downlink routing information, and the downlink routing information is used to indicate that downlink data is transferred from the first user plane entity in the first private network to the first user plane entity in the public network 2. Transmission of user plane entities. In this way, when the first user plane entity receives the downlink data, it can send the downlink data to the second user plane entity according to the downlink data routing information, thereby maintaining service continuity.
  • Fig. 1 is a schematic diagram of a mobile scenario of an existing user terminal
  • Figure 2 is a schematic diagram of the existing PLMN and private network deployment in Type A mode
  • Fig. 3 is a schematic diagram 1 of a communication system provided by an embodiment of the application.
  • Figure 4 is a schematic diagram of a CN-CP network element of a 5G network provided by an embodiment of the application;
  • FIG. 5 is a schematic diagram of the connection and structure of network elements in a private network provided by an embodiment of the application.
  • Figure 6 is a second schematic diagram of a communication system provided by an embodiment of this application.
  • FIG. 7 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 8a is a first schematic diagram of the flow of a communication method provided by an embodiment of this application.
  • FIG. 8b is a schematic diagram 1 of the interaction flow of the communication method provided by the embodiment of this application.
  • FIG. 9a is a second schematic diagram of the flow of a communication method provided by an embodiment of this application.
  • FIG. 9b is a second schematic diagram of the interaction process of the communication method provided by the embodiment of this application.
  • FIG. 10 is a schematic diagram of a process of registering a DCF network element with an NRF network element according to an embodiment of the application
  • Figure 11 is a schematic diagram of a registration scheme provided by an embodiment of the application.
  • FIG. 12 is a schematic diagram 1 of the registration method process provided by an embodiment of the application.
  • FIG. 13 is a second schematic diagram of the registration method process provided by an embodiment of this application.
  • FIG. 14 is a schematic diagram 1 of the flow of a paging method provided by an embodiment of this application.
  • FIG. 15 is a second schematic diagram of the flow of the paging method provided by an embodiment of this application.
  • FIG. 16 is a schematic structural diagram of a first mobility management network element provided by an embodiment of this application.
  • FIG. 17 is a schematic structural diagram of a first network element provided by an embodiment of this application.
  • At least one item (a) refers to any combination of these items, including any combination of a single item (a) or plural items (a).
  • at least one item (a) of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple .
  • words such as “first” and “second” are used to distinguish the same items or similar items with substantially the same function and effect.
  • words such as “first” and “second” do not limit the quantity and order of execution, and words such as “first” and “second” do not limit the difference.
  • words such as “exemplary” or “for example” are used as examples, illustrations, or illustrations. Any embodiment or design solution described as “exemplary” or “for example” in the embodiments of the present application should not be construed as being more preferable or advantageous than other embodiments or design solutions.
  • words such as “exemplary” or “for example” are used to present related concepts in a specific manner to facilitate understanding.
  • the communication system 30 includes a public network (for example, a PLMN), a first private network (private network), and a second private network.
  • a public network for example, a PLMN
  • a first private network private network
  • a second private network is both private networks of type A mode.
  • the private network in the application embodiment may also be called a non-public network (non-public network).
  • the public network may include core network-control plane (CN-CP) network elements and core network-user plane (core network-user plane, CN-UP) network elements (Not shown) and RAN equipment (not shown).
  • the first private network may include a first network element (for example, the first distributed control function (DCF) network element in Figure 3) and a first radio access network (RAN) equipment .
  • the first RAN device includes a first centralized unit-control plane (CU-CP) entity, a first distributed unit (DU) entity, and a first user plane entity (for example, it may be a graph
  • the second private network may include a second network element (for example, the second DCF network element in FIG.
  • the second RAN device It includes a second CU-CP entity, a second DU entity, and a second user plane entity (for example, the second EGW in Figure 3).
  • the CN-CP network elements in the public network are connected to the first private network.
  • the first DCF network element in the first private network is connected to the first CU-CP entity in the first private network.
  • the first CU-CP entity is connected to the first EGW and the first DU entity in the first private network.
  • the second DCF network element in the second private network is connected to the second CU-CP entity in the second private network.
  • the second CU-CP entity in the private network is respectively connected to the second EGW and the second DU entity in the second private network.
  • Figure 3 describes the terminal device moving from the coverage area of the first private network to the coverage area of the second private network. Since the DCF1 network element does not know the network topology of the target area where the terminal device is located, the terminal device is required to register The public network cooperates to complete the mobile handover processing.
  • the CN-CP network element in the embodiment of the present application may include a mobility management network element, a unified data management network element, a session management network element, a network storage function network element, or an authentication function network element, etc.
  • the mobility management network element is mainly used for mobility management in the mobile network, such as user location update, user registration network, user switching, etc.
  • Session management network elements mainly provide session management functions, including user equipment (UE) Internet protocol (IP) address allocation, user plane function (UPF) entity selection, or policy and charging control ( Policy and Charging Control (PCC) policy execution and other functions.
  • UE user equipment
  • IP Internet protocol
  • UPF user plane function
  • PCC Policy and Charging Control
  • Network storage function network element mainly provides network function (NF) registration or discovery function, maintenance and management of NF state (including cell/PLMN/radio access type (RAT) supported by NF) and NF support The type of service and other functions.
  • the unified data management network element is mainly used to process user identification, access authentication, registration, or mobility management.
  • the authentication function network element is mainly used for authentication and authentication.
  • the mobility management network element may be an access and mobility management function (AMF) network element, and the session management network
  • the element may be a session management function (SMF) network element
  • the authentication function network element may be an authentication server function (authentication server function, AUSF) network element
  • the unified data management network element may be a unified data management (unified data management, UDM) network element
  • the network storage function network element may be a network storage function (network repository function, NRF) network element.
  • the mobility management network element, the unified data management network element, the session management network element, the network storage function network element, or the authentication function network element may be other respectively, which is not specifically limited in the embodiment of the present application.
  • CN-CP network elements such as AMF network elements, SMF network elements, UDM network elements, AUSF network elements, or NRF network elements in the embodiments of the present application may interact with service-oriented interfaces.
  • the service-oriented interface provided by the AMF network element can be Namf
  • the service-oriented interface provided by the SMF network element can be Nsmf
  • the service-oriented interface provided by the UDM network element can be Nudm
  • the servicing interface provided externally can be Nnrf
  • the servicing interface provided externally by the AUSF network element can be Nausf.
  • 5G system architecture 5G system architecture
  • the CN-UP network element in the embodiment of the present application may include a user plane entity.
  • the user plane entity is mainly used to perform the forwarding of user data packets according to the routing rules of the session management network element.
  • the user plane entity may be a UPF entity; in other networks in the future, the user plane entity may be other, which is not specifically limited in the embodiment of the present application.
  • the DCF network element in the embodiment of this application (including the first DCF network element in FIG. 3, the second DCF network element in FIG. 3, or other DCF network elements in subsequent embodiments) is responsible for the non-access layer (non-access layer).
  • -access stratum, NAS) analysis and encryption DCF supports controlled user data transmission, local mobility management, session management, billing, legal interception, local user UE IP address allocation, paging, or local service capability opening, etc. .
  • the CU-CP entity in the embodiment of this application (including the first CU-CP entity in FIG. 3, the second CU-CP entity in FIG. 3, or other CU-CP entities in subsequent embodiments)
  • the CP entity is included in the RAN CP and is responsible for the radio resource control function.
  • the radio resource control function includes system message broadcasting, radio resource control (radio resource control, RRC) connection management (such as RRC connection establishment/reconfiguration/release), mobile Performance management (such as measurement control, measurement reporting, handover), control plane signaling encryption and decryption, or packet data unit (PDU) session resource (session resource) parameter analysis, etc.
  • the EGW entities in the embodiments of the present application may be classified according to the protocol layer of the wireless network.
  • the packet data convergence protocol-user plane (PDCP-U) protocol layer and the service data adaptation protocol stack (service data adaptation protocol, SDAP) protocol layer can be set in the EGW Entity.
  • PDCP-U is responsible for user plane data encryption and decryption, integrity protection, or data forwarding in order; SDAP enhances support for mapping IP data packets to data radio bears (data radio bear, DRB) based on packet filters )on.
  • the DU entities in the embodiments of the present application may be classified according to the protocol layer of the wireless network.
  • the functions of the radio link control (RLC) protocol layer, the media access control (MAC) protocol layer, and the physical (PHY) protocol layer can be set in the DU entity in.
  • the RAN CP of the first RAN device or the second RAN device in the embodiment of the present application may also include a radio network management function (RNMF) entity, and the RNMF entity includes RAN service-oriented NF management function, RAN function control (such as handover decision, paging and other functions), or interface communication function.
  • RNMF radio network management function
  • the DU entity and the RAN CP can be connected through the F1-C interface, and the DU entity and the EGW entity can be connected through the F1-U interface.
  • the EGW entity and the RANCP entity They can be connected through the E1 interface, and the RAN CP entity and the DCF network element are connected through the N2 interface.
  • the RAN CP in the case that the RAN CP only includes the CU-CP entity, the RAN CP in the embodiment of the present application can be replaced with the CU-CP entity, which is described in a unified manner here, and will not be repeated below.
  • the communication system 60 includes a public network (for example, a PLMN) and a first private network.
  • the first private network is a type A private network.
  • the public network may include a CN-CP network element, a CN-UP network element, and a second RAN device.
  • the second RAN device may include a second CU-CP entity, a CU-UP entity, and a second DU entity.
  • the first private network may include a first network element (for example, the first DCF network element in FIG. 6) and a first RAN device.
  • the first RAN device includes a first CU-CP entity, a first DU entity, and a first user plane entity (for example, it may be the first EGW in FIG. 6).
  • the first DCF network element in the first private network is connected to the first CU-CP entity in the first private network, and the first CU-CP entity in the first private network is respectively connected to the first EGW in the first private network And the first DU entity.
  • the first DCF network element in the first private network is also connected to the CN-CP network element in the public network, and the CN-CP network element in the public network is connected to the second CU-CP entity in the public network.
  • the CU-CP entity is respectively connected to the CU-UP entity and the second DU entity in the public network, and the CN-UP network element in the public network is connected to the CU-UP entity in the public network.
  • FIG. 6 describes the movement of the terminal device from the coverage area of the first private network to the coverage area of the public network. Since the DCF1 network element does not know the network topology of the target area where the terminal device is located, the public network registered by the terminal device is required to cooperate to complete the mobile handover process.
  • CN-CP network element CN-UP network element
  • DCF network element DCF network element
  • CU-UP entity CU-UP entity
  • EGW EGW
  • DU entity DU entity
  • the CU-UP entity in the embodiment of the present application is responsible for the user plane function, and mainly includes the SDAP protocol layer and the PDCP user plane (PDCP user plane, PDCP-U) protocol layer.
  • PDCP user plane PDCP user plane
  • PDCP-U PDCP user plane
  • the terminal device in the embodiment of the present application may be a device used to implement a wireless communication function, such as a terminal or a chip that can be used in a terminal.
  • the terminal may be a user equipment (UE), an access terminal, a terminal unit, a terminal station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, and wireless communication in a 5G network or a future evolved PLMN.
  • the access terminal can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices or wearable devices, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, industrial control (industrial) Wireless terminal in control), wireless terminal in self-driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transportation safety (transportation safety) Terminal, wireless terminal in smart city, wireless terminal in smart home, etc.
  • the terminal can be mobile or fixed.
  • the RAN device in the embodiment of the present application is a device that connects a terminal device to a wireless network, and may be an evolved Node B (eNB or eNB) in long term evolution (LTE). eNodeB); or the base station in the 5G network or the future evolution of the PLMN, the broadband network service gateway
  • the base stations in the embodiments of the present application may include various forms of base stations, such as macro base stations, micro base stations (also called small stations), relay stations, access points, etc., which are not specifically limited in the embodiments of the present application.
  • the mobility management network element (such as the first AMF network element in the subsequent method embodiment) or the first network element in the embodiment of the present application may also be called a communication device, which may be a general-purpose device or a Special equipment, this embodiment of the application does not specifically limit this.
  • the related functions of the mobility management network element or the first network element in the embodiment of the present application can be implemented by one device, or by multiple devices, or by one or more functions in one device.
  • Module implementation this embodiment of the application does not specifically limit this. It is understandable that the above functions can be network elements in hardware devices, software functions running on dedicated hardware, or a combination of hardware and software, or instantiated on a platform (for example, a cloud platform) Virtualization function.
  • FIG. 7 is a schematic structural diagram of a communication device 700 provided by an embodiment of this application.
  • the communication device 700 includes one or more processors 701, a communication line 702, and at least one communication interface (in FIG. 7 it is only an example that includes a communication interface 704 and a processor 701 as an example), optional
  • the memory 703 may also be included.
  • the processor 701 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more programs used to control the execution of the program of this application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication line 702 may include a path for connecting different components.
  • the communication interface 704 may be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, and wireless local area networks (WLAN).
  • the transceiver module may be a device such as a transceiver or a transceiver.
  • the communication interface 704 may also be a transceiver circuit located in the processor 701 to implement signal input and signal output of the processor.
  • the memory 703 may be a device having a storage function.
  • it can be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types that can store information and instructions
  • Dynamic storage devices can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), or other optical disk storage, optical disc storage ( Including compact discs, laser discs, optical discs, digital universal discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and can be stored by a computer Any other media taken, but not limited to this.
  • the memory can exist independently and is connected to the processor through the communication line 702. The memory can also be integrated with the processor.
  • the memory 703 is used to store computer-executed instructions for executing the solution of the present application, and the processor 701 controls the execution.
  • the processor 701 is configured to execute computer-executable instructions stored in the memory 703, so as to implement the communication method provided in the embodiment of the present application.
  • the processor 701 may also perform processing related functions in the communication method provided in the following embodiments of the present application, and the communication interface 704 is responsible for communicating with other devices or communication networks.
  • the embodiment does not specifically limit this.
  • the computer-executable instructions in the embodiments of the present application may also be referred to as application program code, which is not specifically limited in the embodiments of the present application.
  • the processor 701 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 7.
  • the communication device 700 may include multiple processors, such as the processor 701 and the processor 708 in FIG. 7. Each of these processors can be a single-CPU (single-CPU) processor or a multi-core (multi-CPU) processor.
  • the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (for example, computer program instructions).
  • the communication device 700 may further include an output device 705 and an input device 706.
  • the output device 705 communicates with the processor 701 and can display information in a variety of ways.
  • the output device 705 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector (projector) Wait.
  • the input device 706 communicates with the processor 701 and can receive user input in a variety of ways.
  • the input device 706 may be a mouse, a keyboard, a touch screen device, or a sensor device.
  • the aforementioned communication device 700 may sometimes be referred to as a communication device, which may be a general-purpose device or a special-purpose device.
  • the communication device 700 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, the foregoing terminal device, the foregoing network device, or a picture 7 similar structure equipment.
  • PDA personal digital assistant
  • the embodiment of the present application does not limit the type of the communication device 700.
  • the terminal device can access multiple private networks in Type A mode, and the terminal device moves from the coverage area of the first private network to the coverage area of the second private network (the scenario shown in Figure 3), as shown in Figure 8a
  • a communication method provided by an embodiment of this application includes the following steps S801a-S803a:
  • the first mobility management network element receives a first cell identity and a network identity from the first network element, where the network identity includes the identity of the first private network and the identity of the second private network.
  • the first mobility management network element obtains information of the second network element according to the first cell identity and the network identity.
  • the first network element serves the terminal device in the first private network
  • the second network element serves the terminal device in the second private network
  • the first mobility management network element sends the first cell identity and the network identity to the second network element indicated by the information of the second network element.
  • the first cell identifier and the network identifier are used to obtain downlink routing information, where the downlink routing information is used to indicate that downlink data is transferred from a first user plane entity in the first private network to a second user plane in the second private network Physical transmission.
  • the terminal device can be switched to the target cell while ensuring service continuity.
  • the specific implementation of this solution will be elaborated in detail through the interaction process between network elements shown in FIG. 8b, which will not be repeated here.
  • the first mobility management network element is the first AMF network element
  • the first network element is the first DCF network element in Figure 3
  • the second network element is the second DCF network element in Figure 3.
  • the first user plane entity is the first EGW in FIG. 3, and the second user plane entity is the second EGW in FIG. 3.
  • a communication method provided by an embodiment of this application includes the following step:
  • the first CU-CP entity in the first private network determines that it is necessary to perform handover processing on the terminal device based on the measurement report reported by the terminal device.
  • the first CU-CP entity determines that it needs to perform handover processing on the terminal device, it can further determine the target cell to be handed over.
  • the target cell is exemplarily taken as the first Take a cell as an example.
  • the first CU-CP entity sends a first handover (HO) request message to the first DCF network element.
  • the first DCF network element receives the first handover request message from the first CU-CP entity.
  • the first handover request message includes a first cell identity, and the first cell identity is used to identify the first cell.
  • the first handover request message may also include a terminal device identifier (such as 5G-Globally Unique Temporary UE Identity (GUTI) or System Architecture Evolution (SAE) temporary mobile user identity ( SAE temporary mobile subscriber identity, S-TMSI), terminal device context, data network name (DNN), quality of services (QoS) file (profile) and its corresponding packet filter (packet filter) )
  • a terminal device identifier such as 5G-Globally Unique Temporary UE Identity (GUTI) or System Architecture Evolution (SAE) temporary mobile user identity ( SAE temporary mobile subscriber identity, S-TMSI), terminal device context, data network name (DNN), quality of services (QoS) file (profile) and its corresponding packet filter (packet filter)
  • DNN identifies the data network name of the service accessed by the terminal device.
  • QoS profile is QoS parameter information sent to RAN network functions (including CU entity or DU entity, etc.), including allocation and retention priority (ARP), guaranteed flow bit rate (GFBR), maximum Flow bit rate (maximum flow bit rate, MFBR), maximum packet loss rate (maximum packet loss rate, MPLR), etc.
  • ARP allocation and retention priority
  • GFBR guaranteed flow bit rate
  • MFBR maximum Flow bit rate
  • MPLR maximum packet loss rate
  • the first DCF network element determines, according to the first cell identifier, that the area where the terminal device is currently located exceeds the service range of the cell identified by the first cell identifier.
  • the first DCF network element sends a second handover request message to the first AMF network element, and the first AMF network element receives the second handover request message from the first DCF network element.
  • the second handover request message includes the parameters and the network identifier in the first handover request message.
  • the network identifier includes the identifier of the private network that the terminal device can access.
  • the network identifier includes the identifier of the first private network and the identifier of the second private network as an example for description.
  • the first AMF network element After the first AMF network element obtains the first cell identity and the network identity, it can be determined according to the first cell identity and the network identity whether the first cell identified by the first cell identity is deployed with a DCF network element, the following exemplary Provides two implementation methods.
  • the communication method further includes the following steps S805a-S807a:
  • the first AMF network element determines that the first cell identity belongs to a first tracking area (TA) list allocated by the first AMF network element to the terminal device.
  • TA tracking area
  • the first AMF network element may allocate a first TA list to the terminal device during the registration process, and the first TA list identifies the location area where the terminal device is registered. For specific implementation, please refer to the subsequent registration process, which will not be repeated here.
  • the first AMF network element sends a first network service query request message to the NRF network element.
  • the NRF network element receives the first network service query request message from the first AMF network element.
  • the first network service query request message includes a network function (NF) type (ie, DCF), the above-mentioned first cell identity, and a network identity.
  • NF network function
  • the first network service query request message in the embodiment of the present application may also be replaced with a first NF service request (service request) message, which is not specifically limited here.
  • the NRF network element determines that a DCF network element is deployed in the first cell identified by the first cell identifier, and based on the network identifier, determines that the deployed DCF network element supports a private network that the terminal device can access.
  • the NRF network element determines whether a DCF network element is deployed in the first cell identified by the first cell identifier, and based on the network identifier, determines whether the deployed DCF network element supports a private network accessible by the terminal device. If the NRF network element determines that a DCF network element is deployed in the first cell identified by the first cell identity, and based on the network identity, it is determined that the deployed DCF network element supports the private network accessible by the terminal device, the NRF network element sends the first AMF network element Send the first network service query response message. The first AMF network element receives the first network service query response message from the NRF network element. The first network service query response message includes the information of the second DCF network element. Wherein, the information of the second DCF network element is used to indicate the second DCF network element.
  • the information of the second DCF network element may include the IP address of the second DCF network element, which is not specifically limited here.
  • the NRF network element may also send a network service query response message to the first AMF network element.
  • the network service query response message does not include the information of the DCF network element, which is not specifically limited in the embodiment of the present application.
  • the first network service query response message in the embodiment of the present application may also be replaced with a first NF service response (service response) message, which is not specifically limited here.
  • the communication method further includes the following steps S805b-S811b:
  • the first AMF network element determines that the first cell identity does not belong to the first TA list allocated to the terminal device by the first AMF network element.
  • the first AMF network element may allocate a first TA list to the terminal device during the registration process, and the first TA list identifies the location area where the terminal device is registered. For specific implementation, please refer to the subsequent registration process, which will not be repeated here.
  • the first AMF network element sends a second network service query request message to the NRF network element.
  • the NRF network element receives the second network service query request message from the first AMF network element.
  • the second network service query request message includes the above-mentioned first cell identifier and NF type (ie, AMF).
  • the second network service query request message in the embodiment of the present application may also be replaced with a second NF service request message, which is not specifically limited here.
  • the NRF network element determines that there is a mobility management network element that can serve the first cell identified by the first cell identity.
  • the NRF network element determines whether there is a mobility management network element that can serve the first cell identified by the first cell identity. If it exists, the NRF network element sends a second network service query response message to the first AMF network element. The first AMF network element receives the second network service query response message from the NRF network element. Wherein, assuming that the mobility management network element capable of serving the first cell identified by the first cell identity is the second AMF network element, the second network service query response message may include the information of the second AMF network element. The information of the second AMF network element is used to indicate the second AMF network element.
  • the information of the second AMF network element may include, for example, the IP address of the second AMF network element, which is not specifically limited here.
  • the NRF network element may also send a network service query response message to the first AMF network element.
  • the network service query response message does not include the information of the AMF network element, which is not specifically limited in the embodiment of the present application.
  • the first AMF network element sends a first N14 message to the second AMF network element indicated by the information of the second AMF network element.
  • the second AMF network element receives the first N14 message from the first AMF network element.
  • the first N14 message includes the first cell identity and the network identity.
  • the second AMF network element sends a third network service query request message to the NRF network element.
  • the NRF network element receives the third network service query request message from the second AMF network element.
  • the third network service query request message includes the NF type (ie, DCF), the above-mentioned first cell identity and network identity.
  • the third network service query request message in the embodiment of the present application may also be replaced with a third NF service request (service request) message, which is not specifically limited here.
  • the NRF network element determines that a DCF network element is deployed in the first cell identified by the first cell identifier, and based on the network identifier, determines that the deployed DCF network element supports a private network that the terminal device can access.
  • the NRF network element determines whether a DCF network element is deployed in the first cell identified by the first cell identifier, and based on the network identifier, determines whether the deployed DCF network element supports a private network accessible by the terminal device. If the NRF network element determines that a DCF network element is deployed in the first cell identified by the first cell identity, and based on the network identity, it is determined that the deployed DCF network element supports the private network accessible to the terminal device, the NRF network element sends the second AMF network element Send the third network service query response message. The second AMF network element receives the third network service query response message from the NRF network element. The third network service query response message includes the information of the second DCF network element. Wherein, the information of the second DCF network element is used to indicate the second DCF network element.
  • the NRF network element may also send a network service query response message to the first AMF network element.
  • the network service query response message does not include the information of the DCF network element, which is not specifically limited in the embodiment of the present application.
  • the information of the second DCF network element may include the IP address of the second DCF network element, which is not specifically limited here.
  • the third network service query response message in the embodiment of the present application can also be replaced with a third NF service response message, which is not specifically limited here.
  • the second AMF network element sends a second N14 message to the first AMF network element.
  • the first AMF network element receives the second N14 message from the second AMF network element.
  • the second N14 message includes information of the second DCF network element.
  • the communication method provided in the embodiment of the present application may further include the following steps:
  • the first AMF network element sends a third handover request message to the second DCF network element indicated by the information of the second DCF network element.
  • the second DCF network element receives the third handover request message from the first AMF network element.
  • the third handover request message includes parameters in the second handover request message, such as the first cell identity and the network identity.
  • the second DCF network element determines the CU-CP entity serving the first cell, which is assumed to be the second CU-CP entity here.
  • the second DCF network element may be based on the first cell identity, RAT type (that is, the current access mode of the terminal device, such as LTE or new radio (NR)) or PLMN information, etc.
  • the information determines the CU-CP entity serving the first cell.
  • the second DCF network element sends a fourth handover request message to the second CU-CP entity.
  • the second CU-CP entity receives the fourth handover request message from the second DCF network element.
  • the fourth handover request message includes parameters in the third handover request message, such as the first cell identity and network identity.
  • the second CU-CP entity determines the EGW serving the first cell, which is assumed to be the second EGW here.
  • the second CU-CP entity may select the EGW serving the first cell according to information such as the identity of the first cell, which is not specifically limited herein.
  • the second CU-CP entity initiates session resource setup (session resource setup) to the second EGW, so that the second EGW allocates downlink routing information, and sends the downlink routing information to the second CU-CP entity.
  • the second CU-CP entity receives the downlink routing information from the second EGW.
  • the downlink routing information is used to indicate the transmission of downlink data from the first user plane entity in the first private network to the second user plane entity in the second private network, where the first user plane entity may correspond to the figure The first EGW in 3, the second user plane entity here may correspond to the second EGW in FIG. 3.
  • the downlink routing information in the embodiment of the present application may include the MAC address or IP address of the second EGW, which is not specifically limited here.
  • the second CU-CP entity After completing the resource establishment of the second EGW and the second DU entity, the second CU-CP entity sends a fourth handover request acknowledgement (HO request ack) message to the second DCF network element.
  • the first DCF network element receives the fourth handover request confirmation message from the second CU-CP entity.
  • the fourth handover request confirmation message includes downlink routing information allocated by the second EGW.
  • the second DCF network element sends a third handover request confirmation message to the first AMF network element.
  • the first AMF network element receives the third handover request confirmation message from the second DCF network element.
  • the third handover request confirmation message includes downlink routing information allocated by the second EGW.
  • the first AMF network element sends a second handover request confirmation message to the first DCF network element.
  • the first DCF network element receives the second handover request confirmation message from the first AMF network element.
  • the second handover request confirmation message includes downlink routing information allocated by the second EGW.
  • the second handover request confirmation message may also include parameter information such as a packet filter, which is not specifically limited here.
  • the first DCF network element sends a HO command message to the first CU-CP entity.
  • the first CU-CP entity receives the handover command message from the first DCF network element.
  • the handover command message includes downlink routing information allocated by the second EGW.
  • the switching command message is used to confirm that the switching process has been performed.
  • the first CU-CP entity sends a handover command message to the first EGW.
  • the first EGW receives the handover command message from the first CU-CP entity.
  • the handover command message includes downlink routing information allocated by the second EGW.
  • the switching command message is used to confirm that the switching process has been performed.
  • the first EGW when it receives the downlink data, it can send the downlink data to the second EGW according to the downlink data routing information, thereby maintaining service continuity.
  • the first CU-CP entity sends a handover command message to the terminal device through the first DU entity.
  • the terminal device receives the handover command message from the first CU-CP entity through the first DU entity.
  • the handover command message includes downlink routing information allocated by the second EGW.
  • the switching command message is used to confirm that the switching process has been performed.
  • the terminal device After receiving the handover command message, the terminal device confirms that the handover is complete, and sends a handover command acknowledgement (HO command ack) message to the second CU-CP entity through the second DU entity.
  • the second CU-CP entity receives the handover command confirmation message from the terminal device through the second DU entity.
  • the terminal device after the terminal device moves out of the coverage of the first private network, it can select the second private network, and the second EGW in the second private network can be allocated for downlink Routing information, and send the downlink routing information to the first EGW in the first private network, and the downlink routing information is used to indicate the downlink data from the first EGW in the first private network to the second EGW in the second private network Transmission.
  • the first EGW receives the downlink data, it can send the downlink data to the second EGW according to the downlink data routing information, thereby maintaining service continuity.
  • the actions of the first AMF network element or the first DCF network element in the above steps S801 to S825 can be executed by the processor 701 in the communication device 700 shown in FIG. 7 calling the application program code stored in the memory 703.
  • the embodiment does not impose any limitation on this.
  • the communication method includes the following steps S901a-S904a:
  • the first mobility management network element receives a first cell identity and a network identity from the first network element, where the network identity includes the identity of the first private network, where the first network element serves the terminal device in the first private network.
  • the first mobility management network element determines, according to the first cell identity and the network identity, that the second mobility management network element currently serves the terminal device in the public network.
  • the first mobility management network element determines a centralized unit control plane entity in the public network serving the terminal device.
  • the first mobility management network element sends a first cell identity and a network identity to a centralized unit control plane entity in the public network, where the first cell identity and network identity are used to obtain downlink routing information, where the downlink routing information is used to indicate downlink Data is transmitted from the first user plane entity in the first private network to the second user plane entity in the public network.
  • the terminal device can be switched to the target cell while ensuring service continuity.
  • the specific implementation of this solution will be described in detail through the interaction process between the network elements shown in FIG. 9b, which will not be repeated here.
  • the first mobility management network element is the first AMF network element
  • the second mobility management network element is the second AMF network element
  • the first network element is the first DCF network element in Figure 6
  • the centralized unit The control plane entity is the second CU-CP entity in Figure 6
  • the first user plane entity is the first EGW in Figure 6
  • the second user plane entity is the CU-UP entity in Figure 6 as an example, as shown in Figure 9b.
  • another communication method provided in this embodiment of the application includes the following steps:
  • S901-S904 are the same as steps S801-S804 in the embodiment shown in FIG. 8b.
  • steps S801-S804 are the same as steps S801-S804 in the embodiment shown in FIG. 8b.
  • the first AMF network element After the first AMF network element obtains the first cell identity and the network identity, it can be determined according to the first cell identity and the network identity whether the first cell identified by the first cell identity is deployed with a DCF network element, the following exemplary Provides two implementation methods.
  • the communication method further includes the following steps S905a-S907a:
  • S905a-S906a are the same as steps S805a-S806a in the embodiment shown in FIG. 8b.
  • steps S805a-S806a are the same as steps S805a-S806a in the embodiment shown in FIG. 8b.
  • the NRF network element determines that a DCF network element is deployed in the first cell identified by the first cell identifier, but there is no private network to which the DCF network element supports terminal devices; or the NRF network element determines that the first cell identifier is identified No DCF network elements are deployed in the first cell.
  • the NRF network element determines whether a DCF network element is deployed in the first cell identified by the first cell identifier, and based on the network identifier, determines whether the deployed DCF network element supports a private network accessible by the terminal device. If the NRF network element determines that a DCF network element is deployed in the first cell identified by the first cell identifier, but there is no private network to which the DCF network element supports terminal devices; or, if the NRF network element determines that the first cell identifier is identified No DCF network elements are deployed in the first cell.
  • the NRF network element sends a first network service query response message to the first AMF network element.
  • the first AMF network element receives the first network service query response message from the NRF network element. Wherein, the first network service query response message does not include the information of the DCF network element.
  • the NRF network element determines that the DCF network element is deployed in the first cell identified by the first cell identifier, and based on the network identifier, it is determined that the deployed DCF network element supports the private network that the terminal device can access, continue to perform as shown in Figure 8b The relevant procedures in the embodiment will not be repeated here.
  • the first network service query response message in the embodiment of the present application may also be replaced with the first NF service response message, which is not specifically limited here.
  • the communication method further includes the following steps S905b-S911b:
  • S905b-S909b are the same as steps S805b-S809b in the embodiment shown in FIG. 8b.
  • steps S805b-S809b are the same as steps S805b-S809b in the embodiment shown in FIG. 8b.
  • the NRF network element determines that a DCF network element is deployed in the first cell identified by the first cell identifier, but there is no private network to which the DCF network element supports terminal equipment; or the NRF network element determines that the first cell identifier is identified No DCF network elements are deployed in the first cell.
  • the NRF network element determines whether a DCF network element is deployed in the first cell identified by the first cell identifier, and based on the network identifier, determines whether the deployed DCF network element supports a private network accessible by the terminal device. If the NRF network element determines that a DCF network element is deployed in the first cell identified by the first cell identifier, but there is no private network to which the DCF network element supports terminal devices; or, if the NRF network element determines that the first cell identifier is identified No DCF network elements are deployed in the first cell.
  • the NRF network element sends a third network service query response message to the second AMF network element.
  • the second AMF network element receives the third network service query response message from the NRF network element. Wherein, the third network service query response message does not include the information of the DCF network element.
  • the NRF network element determines that the DCF network element is deployed in the first cell identified by the first cell identifier, and based on the network identifier, it is determined that the deployed DCF network element supports the private network that the terminal device can access, continue to perform as shown in Figure 8b The relevant procedures in the embodiment will not be repeated here.
  • the second AMF network element sends a second N14 message to the first AMF network element.
  • the first AMF network element receives the second N14 message from the second AMF network element.
  • the second N14 message does not include DCF network element information.
  • the AMF1 network element since the AMF1 network element has not obtained the information of the DCF network element, it can be determined that the first AMF network element (corresponding to the first cell identity) belongs to the first AMF network element assigned to the terminal device. In the case of a TA list) or the second AMF network element (corresponding to the case where the first cell identity does not belong to the first TA list allocated by the first AMF network element for the terminal device) serves the terminal device. Further, the embodiment of the application provides The communication method may also include the following steps:
  • the first AMF network element determines the CU-CP entity serving the first cell, which is assumed to be the second CU-CP entity here.
  • the first AMF network element may determine the CU-CP entity serving the first cell according to information such as the first cell identity, the RAT type (that is, the current access mode of the terminal device), or PLMN information.
  • the first AMF network element sends a third handover request message to the second CU-CP entity.
  • the second CU-CP entity receives the third handover request message from the first AMF network element.
  • the third handover request message includes parameters in the second handover request message, such as the first cell identity and the network identity.
  • the second CU-CP entity determines the CU-UP entity serving the first cell.
  • the second CU-CP entity may select the CU-UP entity serving the first cell according to information such as the identity of the first cell, which is not specifically limited here.
  • the second CU-CP entity initiates session resource establishment to the CU-UP entity, so that the CU-UP entity allocates downlink routing information, and sends the downlink routing information to the second CU-CP entity.
  • the second CU-CP entity receives the downlink routing information from the CU-UP entity.
  • the downlink routing information is used to indicate the transmission of downlink data from the first user plane entity in the first private network to the second user plane entity in the second private network, where the first user plane entity may correspond to the figure The first EGW in 6, and the second user plane entity here may correspond to the CU-UP entity in FIG. 6.
  • the downlink routing information in the embodiment of the present application may include the MAC address or IP address of the CU-UP entity, which is not specifically limited here.
  • S917 DU resource establishment is completed between the second CU-CP entity and the second DU entity.
  • the second CU-CP entity After completing the resource establishment of the CU-UP entity and the second DU entity, the second CU-CP entity sends a third handover request confirmation message to the first AMF network element.
  • the first AMF network element receives the third handover request confirmation message from the second CU-CP entity.
  • the third handover request confirmation message includes downlink routing information allocated by the CU-UP entity.
  • the first AMF network element sends a second handover request confirmation message to the first DCF network element.
  • the first DCF network element receives the second handover request confirmation message from the first AMF network element.
  • the second handover request confirmation message includes downlink routing information allocated by the CU-UP entity.
  • the second handover request confirmation message may also include parameter information such as a packet filter, which is not specifically limited here.
  • the first DCF network element sends a handover command message to the first CU-CP entity.
  • the first CU-CP entity receives the handover command message from the first DCF network element.
  • the handover command message includes downlink routing information allocated by the second EGW.
  • the switching command message is used to confirm that the switching process has been performed.
  • the first CU-CP entity sends a handover command message to the first EGW.
  • the first EGW receives the handover command message from the first CU-CP entity.
  • the handover command message includes downlink routing information allocated by the CU-UP entity.
  • the switching command message is used to confirm that the switching process has been performed.
  • the first EGW when the first EGW receives the downlink data, it can send the downlink data to the CU-UP entity according to the downlink data routing information, thereby maintaining service continuity.
  • the first CU-CP entity sends a handover command message to the terminal device through the first DU entity.
  • the terminal device receives the handover command message from the first CU-CP entity through the first DU entity.
  • the handover command message includes downlink routing information allocated by the CU-UP entity.
  • the switching command message is used to confirm that the switching process has been performed.
  • the terminal device After receiving the handover command message, the terminal device confirms that the handover is complete, and sends a handover command confirmation message to the second CU-CP entity through the second DU entity.
  • the second CU-CP entity receives the handover command confirmation message from the terminal device through the second DU entity.
  • the terminal device after the terminal device moves out of the coverage of the first private network, it can select the public network, and the CU-UP entity in the public network can allocate downlink routing information,
  • the downlink routing information is sent to the first EGW in the first private network, and the downlink routing information is used to indicate the transmission of downlink data from the first EGW in the first private network to the CU-UP entity in the public network.
  • the first EGW receives the downlink data, it can send the downlink data to the CU-UP entity according to the downlink data routing information, thereby maintaining service continuity.
  • the actions of the first AMF network element or the first DCF network element in the above steps S901 to S923 can be executed by the processor 701 in the communication device 700 shown in FIG. 7 calling the application program code stored in the memory 703.
  • the embodiment does not impose any limitation on this.
  • a schematic flowchart of a DCF network element registration with an NRF network element includes the following steps:
  • S1001 after the DCF network element is deployed and configured online, sends an NF registration request to the NRF network element.
  • the NRF network element receives the NF registration request from the DCF network element.
  • the NF registration request includes information such as the identity of the DCF network element (such as the name of the DCF network element), the cell identity and network identity served by the DCF network element, and the network identity is used to identify the network type where the DCF network element is located.
  • the identity of the DCF network element such as the name of the DCF network element
  • the cell identity and network identity served by the DCF network element and the network identity is used to identify the network type where the DCF network element is located.
  • the network identity is used to identify the network type where the DCF network element is located.
  • a private network in type A mode or a private network enterprise to which it belongs, such as an enterprise A network, the specific form is not limited in the embodiment of this application.
  • the NRF network element stores the registration information of the DCF network element, so that subsequent other NF queries call the DCF network element service.
  • the NRF network element After completing the information registration management of the DCF network element, the NRF network element sends an NF registration response to the DCF network element. The DCF network element receives the NF registration response from the NRF network element.
  • the NF registration response is used to confirm that the service registration of the DCF network element is completed.
  • the registration of the network attribute information of the DCF network element can be realized, and in the subsequent service processing process, other NFs can accurately obtain the attribute information of the DCF network element, thereby ensuring the normal operation of the service.
  • the actions of the DCF network element in the above steps S1001 to S1003 can be executed by the processor 701 in the communication device 700 shown in FIG. 7 calling the application code stored in the memory 703, and this embodiment does not impose any limitation on this.
  • the terminal device needs to register before the mobility handover of the terminal device occurs.
  • the terminal equipment of the private network of the type A mode also needs the public network to provide network services for it to ensure Business continuity. Therefore, in order to be able to obtain the business services of the private network of the type A mode and the business services of the public network, the terminal device needs to be registered on the private and public networks of the type A mode at the same time.
  • the embodiment of the present application may provide two methods for registering terminal devices.
  • One solution is for the terminal device to register through the DU entity, CU-CP entity and DCF network element in the private network, and one solution is for the terminal device to register through the DU entity and CU-CP entity in the public network, as shown in Figure 11. Show.
  • the two registration schemes for terminal equipment are described in detail below.
  • the terminal device is in the coverage area of the private network in type A mode
  • the terminal device registers with the DCF network element in the private network through the private network in type A mode
  • the DCF network element obtains the allowable terminal device Access network information, and based on this information, determine whether it is necessary to perform registration to the CN-CP of the public network (such as PLMN).
  • this solution needs to modify the cell selection strategy of the terminal equipment. That is, the cell selected by the terminal device is a cell of a private network, such as a cell of a private network in type A mode, to ensure that the terminal device can directly access the private network that it can access.
  • the terminal device when it performs cell selection, it can be based on the received system information block (SIB) message (the SIB message includes the network identifier of the private network in the type A mode) and the list of accessible network identifiers ( It is stored in a subscriber identity module (SIM) card, preferably in a cell of a private network of type A mode, and completes the establishment of an RRC connection.
  • SIB system information block
  • SIM subscriber identity module
  • the terminal device sends a first registration request (registration request) to the DCF network element in the private network through the DU entity and the CU-CP in the private network.
  • the DCF network element receives the first registration request from the terminal device.
  • the first registration request includes information such as registration PDU, the cell identifier of the cell where the terminal device is currently located (herein referred to as the second cell identifier), and the RAT type.
  • the DU entity and the CU-CP entity in step S1201 are selected in the RRC connection establishment process when the terminal device initially accesses the network, and wireless resource connections have been established between the terminal device and these network entities. Therefore, the terminal device can directly send the first registration request through the established RRC connection, which is explained here in a unified manner, and will not be described in detail below.
  • the DCF network element selects the AUSF network element.
  • the DCF network element can select the AUSF network element by querying the NRF, which is not specifically limited here.
  • DCF network element terminal equipment and AUSF network element perform authentication and authentication, so that the terminal device sends the relevant security context to the DCF network element, and then the DCF network element can initiate access stratum (AS) or NAS security Process, activate the AS or NAS security mechanism.
  • AS access stratum
  • NAS security Process activate the AS or NAS security mechanism.
  • the DCF network element obtains the access and mobility related subscription data of the terminal device from the UDM network element.
  • the subscription data may include subscription information such as a private network identifier accessible by the terminal device.
  • the DCF network element performs the location registration management of the terminal device and is the terminal device Assign temporary identifiers and create terminal device context for the terminal device.
  • the context of the terminal device includes the above-mentioned second cell identity and the temporary identity allocated by the DCF network element to the terminal device.
  • the DCF network element may query the NRF network element to obtain the information of the AMF network element serving the current cell, and send a second registration request to the AMF network element.
  • the AMF network element receives the second registration request from the DCF network element.
  • the second registration request includes the context of the terminal device.
  • the second registration request is used to register relevant location information of the terminal device with the AMF network element.
  • the AMF network element performs location management of the terminal device and allocates a TA list to the terminal device, where the TA list is used to identify the location area where the terminal device is registered.
  • the TA list includes one or more cell identities, and the one or more cell identities include the foregoing second cell identity.
  • the AMF network element sends a second registration response to the DCF network element.
  • the DCF network element receives the second registration response from the AMF network element.
  • the second registration response includes the above TA list.
  • the DCF network element sends an initial context setup request (initiate UE context setup request) message to the CU-CP entity after completing related processing such as context creation of the terminal device.
  • the CU-CP entity receives the initial context establishment request message from the DCF network element.
  • the initial context establishment request message may include registration acceptance PDU, 5G-GUTI, handover restriction list (such as cell list or PLMN list, etc.), UE-aggregate maximum bit rate (aggregate maximum bit rate, AMBR) Or information such as the ID of the DCF network element.
  • 5G-GUTI is a new identifier assigned by the DCF network element to the terminal equipment, and the identifier of the DCF network element is used to uniquely identify the DCF network element.
  • the initial context establishment request message may also include the foregoing TA list.
  • the CU-CP entity sends a registration acceptance (registration accept) message to the terminal device through the DU entity.
  • the terminal device receives the registration acceptance message from the CU-CP entity.
  • the registration acceptance message includes one or more of the foregoing TA list, 5G-GUTI, or UE-AMBR, which is not specifically limited in the embodiment of the present application.
  • the terminal device sends a registration complete (registration complete) message to the DCF network element through the DU entity and the CU-CP entity.
  • the DCF network element receives the registration completion message from the terminal device.
  • the registration completion message is used to indicate that the registration is completed.
  • terminal equipment can be directly connected to the network from the private network, and the two-level hierarchical registration of DCF network elements and AMF network elements can be completed.
  • the actions of the DCF network element or the AMF network element in the above steps S1201 to S1211 can be executed by the processor 701 in the communication device 700 shown in FIG. 7 calling the application program code stored in the memory 703, which is not done in this embodiment. Any restrictions.
  • the terminal device is in the coverage area of the private network in Type A mode, but the public network (such as the PLMN network) is selected for registration.
  • the AMF network element rejects the registration request of the terminal device and instructs it Re-select the cell and initiate registration.
  • FIG. 13 a schematic diagram of another terminal device registration process provided by this embodiment of the application includes the following steps:
  • the terminal device sends a registration request to the AMF network element in the public network through the DU entity and the CU-CP entity in the public network.
  • the AMF network element receives the registration request from the terminal device.
  • the registration request includes information such as the registration PDU, the cell identity of the cell where the terminal device is currently located (here marked as the second cell identity), and the RAT type.
  • the DU entity and the CU-CP entity in step S1301 are selected in the RRC connection establishment process when the terminal device initially accesses the network, and a radio resource connection has been established between the terminal device and these network entities. Therefore, the terminal device can directly send the registration request through the established RRC connection, which is explained here in a unified manner, and will not be repeated in the following.
  • the AMF network element selects the AUSF network element.
  • the AMF network element can select the AUSF network element by querying the NRF, which is not specifically limited here.
  • AMF network element perform authentication and authentication, so that the terminal device sends the relevant security context to the AMF network element, and the AMF network element can initiate the AS or NAS security process and activate the AS or NAS security mechanism .
  • the AMF network element can request the original AMF (old AMF) network element to obtain the terminal device through a context transfer message
  • the context of is not specifically limited here.
  • the AMF network element obtains the access and mobility related subscription data of the terminal device from the UDM network element.
  • the subscription data may include subscription information such as a private network identifier accessible by the terminal device.
  • the AMF network element determines that the subscription data includes the private network identifier that the terminal device can access, and the area where the terminal device is located is deployed with the private network that the terminal device can access.
  • the AMF network element determines that the subscription data does not include the private network identifier that the terminal device can access; or, if the AMF network element determines that the subscription data does not include the private network that the terminal device can access If the terminal device is not deployed in the area where the terminal device is located, the accessible private network contracted by the terminal device is not deployed, and the AMF network element refers to the existing registration process to continue to perform the subsequent steps of the terminal device registration process, which will not be repeated here.
  • the AMF network element sends a registration response to the terminal device through the CU-CP entity and the DU entity.
  • the terminal device receives the registration response from the AMF network element.
  • the registration response includes registration rejection information.
  • the registration rejection information is used to instruct the terminal device to register in a private network accessible by the terminal device.
  • the registration rejection message may include a registration reason value, and the registration reason value is re-attach to instruct the terminal device to register to a private network accessible by the terminal device.
  • S1307 The terminal device re-initiates the registration process. Refer to steps S1201-S1211 in the embodiment shown in FIG. 12, which will not be repeated here.
  • the terminal device when the terminal device is in the overlapping coverage area of the public network and the private network accessible by the terminal device, the terminal device selects the public network to reside, and initiates the registration of the terminal device to the public network. In the subsequent re-registration process of the terminal device, the terminal device can be registered in the private network accessible by the terminal device.
  • the actions of the DCF network element or the AMF network element in the above steps S1301 to S1307 can be executed by the processor 701 in the communication device 700 shown in FIG. 7 calling the application program code stored in the memory 703, which is not done in this embodiment. Any restrictions.
  • the embodiments of the present application may also provide a paging processing flow for idle state terminal devices.
  • the DCF network element is responsible for initiating paging for the terminal device. If the DCF network element cannot page the terminal device in its service area, it will further trigger a request to the AMF network element for paging optimization processing, such as expansion Paging range.
  • paging optimization processing such as expansion Paging range.
  • a data-triggered paging method provided by this embodiment of the application includes the following steps:
  • the EGW When the EGW receives a downlink data packet, it parses the downlink data packet to obtain header information, and performs matching based on the IP quintuple in the header information and a packet filter installed on the EGW (that is, the SDAP function). Although the packet filter can be matched, if the EGW does not match the DRB, the EGW cannot send the downlink data packet to the terminal device through the matched packet filter and DRB. Then, the EGW buffers the received downlink data packets, and sends an event report (event report) message to the DCF network element through the CU-CP entity, and the DCF network element receives the event report message from the EGW.
  • an event report event report
  • the event report message includes UE IP address information in the packet header of the downlink data packet.
  • the event report message in the embodiment of the present application may further include an IP quintuple (IP tuple), which includes a source IP address, a source port, a destination IP address, a destination port, and a protocol type.
  • IP tuple IP quintuple
  • the DCF network element determines the terminal identifier of the terminal device, the paging cell, and the CU-CP entity and DU entity corresponding to the paging cell according to the UE IP address information in the downlink data packet header.
  • the DCF network element after the DCF network element receives the event report message from the EGW, it can look up the locally saved context of the terminal device to determine the identity of the terminal device corresponding to the UE IP address information (such as 5G-GUTI or S-TMSI, etc.) paging cell and CU-CP entity and DU entity corresponding to the paging cell.
  • the UE IP address information such as 5G-GUTI or S-TMSI, etc.
  • the DCF network element sends a paging (paging request) request message to the corresponding CU-CP entity.
  • the CU-CP entity receives the paging request message from the DCF network element.
  • the paging request message includes information such as the identification of the terminal device and the paging area.
  • the CU-CP entity in step S1401 and the CU-CP entity determined in step S1402 are the same CU-CP entity as an example for description.
  • the two CU-CP entities It may also be a different CU-CP entity, which is not specifically limited in the embodiment of this application.
  • the CU-CP entity sends a paging request message to the terminal device through the DU entity.
  • the terminal device receives the paging request message from the CU-CP entity.
  • the DCF network element If the DCF network element does not receive a reply (such as a service request) from the terminal device after being paged multiple times or within a certain period of time, the DCF network element sends a paging optimization request to the AMF network element.
  • the AMF network element receives the paging optimization request from the DCF network element.
  • the paging optimization request is used to request the AMF network element to expand the paging range.
  • S1406 The AMF network element initiates paging to the terminal device in an even larger range (such as the entire network) in the TA list registered by the terminal device.
  • the DCF network element can implement paging processing for terminal equipment in an idle state, and at the same time, the centralized AMF network element can perform paging processing on a wider range of paging for terminal equipment.
  • the actions of the DCF network element or the AMF network element in the above steps S1401 to S1406 can be executed by the processor 701 in the communication device 700 shown in FIG. 7 calling the application code stored in the memory 703, which is not done in this embodiment. Any restrictions.
  • a signaling-triggered paging method provided in an embodiment of this application includes the following steps:
  • the DCF network element determines the terminal identifier of the terminal device, the paging cell, and the CU-CP corresponding to the paging cell according to the signaling processing request message Entity and DU entity.
  • the DCF network element sends a paging request message to the corresponding CU-CP entity.
  • the CU-CP entity receives the paging request message from the DCF network element.
  • the paging message includes information such as the identification of the terminal device and the paging area.
  • S1503-S1505 are the same as steps S1404-S1406 in the embodiment shown in FIG. 14.
  • steps S1404-S1406 are the same as steps S1404-S1406 in the embodiment shown in FIG. 14.
  • the DCF network element can implement paging processing for terminal equipment in an idle state, and at the same time, the centralized AMF network element can perform paging processing on a wider range of paging for terminal equipment.
  • the actions of the DCF network element or the AMF network element in the above steps S1501 to S1505 can be executed by the processor 701 in the communication device 700 shown in FIG. 7 calling the application program code stored in the memory 703, which is not done in this embodiment. Any restrictions.
  • the methods and/or steps implemented by the first network element can also be implemented by components (such as chips or circuits) that can be used for the first network element, and the first mobile management network element
  • the methods and/or steps implemented can also be implemented by components that can be used in the first mobility management network element.
  • an embodiment of the present application also provides a communication device, which is used to implement the foregoing various methods.
  • the communication device may be the first network element in the foregoing method embodiment, or a device including the foregoing first network element, or a component that can be used in the first network element; or, the communication device may be the foregoing method embodiment
  • the communication device includes 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. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiments of the present application may divide the communication device into functional modules according to the foregoing method embodiments.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 16 shows a schematic structural diagram of a first mobility management network element 160.
  • the first mobility management network element 160 includes a transceiver module 1601 and a processing module 1602.
  • the transceiver module 1601 may also be referred to as a transceiver unit to implement a transceiver function, for example, it may be a transceiver circuit, a transceiver, a transceiver or a communication interface.
  • the transceiver module 1601 is configured to receive the first cell identification and the network identification from the first network element, the network identification includes the identification of the first private network and the identification of the second private network;
  • the processing module 1602 is configured to receive the first cell identification and the network identification Network identification to obtain information about the second network element, where the first network element serves terminal equipment in the first private network, and the second network element serves terminal equipment in the second private network;
  • the transceiver module 1601 is also used for Send the first cell identity and network identity to the second network element indicated by the information of the second network element, where the first cell identity and network identity are used to obtain downlink routing information, where the downlink routing information is used to indicate that the downlink data is transferred from the first Transmission from the first user plane entity in the private network to the second user plane entity in the second private network.
  • the processing module 1602 is configured to obtain information about the second network element according to the first cell identifier and the network identifier, and includes: a processing module 1602, configured to determine that the first cell identifier belongs to the first mobility management network element and allocate it to the terminal device The first TA list; the first cell identification and network identification are sent to the network storage function network element through the transceiver module 1601, the first cell identification and network identification are used to determine the information of the second network element; the transceiver module 1601 receives the information from the network storage Information of the second network element of the functional network element.
  • the transceiver module 1601 is also used to receive the second cell identity from the terminal device; the processing module 1602 is also used to allocate a first TA list to the terminal device, where the first TA list includes the second cell identity and the first Cell identification; the transceiver module 1601 is also used to send a first TA list to the terminal device through the first network element, where the first TA list is used to identify the location area where the terminal device is registered.
  • the processing module 1602 is configured to obtain information of the second network element according to the first cell identifier and the network identifier, and includes: a processing module 1602, configured to determine that the first cell identifier does not belong to the first mobility management network element as a terminal device The first assigned TA list; the first cell identification is sent to the network storage function network element through the transceiver module 1601; the second mobility management network element information from the network storage function network element is received through the transceiver module 1601, where the second mobility management The network element is a mobility management network element that can serve the cell corresponding to the first cell identity; the first cell identity and network identity are sent to the second mobility management network element indicated by the second mobility management network element through the transceiver module 1601, and the first cell The identifier and the network identifier are used to determine the information of the second network element; the information of the second network element from the second mobility management network element is received through the transceiver module 1601.
  • processing module 1602 is further configured to receive the second cell identifier from the terminal device; the processing module 1602 is also configured to allocate a first TA list to the terminal device, wherein the first TA list includes the second cell identifier; transceiver module 1601. It is also configured to send a first TA list to a terminal device by sending a first network element, where the first TA list is used to identify a location area registered by the terminal device.
  • the transceiver module 1601 is also used to receive downlink routing information from the second network element, where the downlink routing information is allocated by the second user plane entity; the transceiver module 1601 is also used to communicate to the first network element The first user plane entity sends downlink routing information.
  • the transceiving module 1601 is also used to receive the second cell identity from the terminal device; the transceiving module 1601 is further used to receive the network identity from the unified data management network element; the processing module 1602 is also used to receive the second cell identity and The network identifier determines that the cell identified by the second cell identifier is deployed with a private network accessible to the terminal device; the transceiver module 1601 is also used to send registration rejection information to the terminal device, and the registration rejection information is used to instruct the terminal device to register with the terminal device Accessible private network.
  • the transceiver module 1601 is configured to receive a first cell identity and a network identity from a first network element, where the network identity includes the identity of the first private network, where the first network element serves the terminal device in the first private network; processing module 1602, used to determine, according to the first cell identity and network identity, that the second mobility management network element currently serves the terminal device in the public network; the processing module 1602 is also used to determine the centralized unit control in the public network serving the terminal device Plane entity; the transceiver module 1601 is also used to send a first cell identity and a network identity to a centralized unit control plane entity in the public network, the first cell identity and network identity are used to obtain downlink routing information, where the downlink routing information is used Indicate the transmission of downlink data from the first user plane entity in the private network to the second user plane entity in the public network.
  • the first mobility management network element 160 is presented in the form of dividing various functional modules in an integrated manner.
  • the "module” here can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and/or other devices that can provide the above-mentioned functions.
  • the first mobility management network element 160 may take the form of the communication device 700 shown in FIG. 7.
  • the processor 701 in the communication device 700 shown in FIG. 7 may invoke the computer execution instruction stored in the memory 703 to make the communication device 700 execute the communication method in the foregoing method embodiment.
  • the functions/implementation process of the transceiver module 1601 and the processing module 1602 in FIG. 16 may be implemented by the processor 701 in the communication device 700 shown in FIG. 7 calling a computer execution instruction stored in the memory 703.
  • the function/implementation process of the processing module 1602 in FIG. 16 can be implemented by the processor 701 in the communication device 700 shown in FIG. 7 calling a computer execution instruction stored in the memory 703, and the function of the transceiver module 1601 in FIG. /The realization process can be realized through the communication interface 704 in the communication device 700 shown in FIG. 7.
  • the first mobility management network element 160 provided in this embodiment can perform the above-mentioned communication method, the technical effects that can be obtained can refer to the above-mentioned method embodiment, which will not be repeated here.
  • FIG. 17 shows a schematic structural diagram of a first network element 170.
  • the first network element 170 includes a transceiver module 1701 and a processing module 1702.
  • the transceiver module 1701 may also be referred to as a transceiver unit to implement a transceiver function, for example, it may be a transceiver circuit, a transceiver, a transceiver or a communication interface.
  • the processing module 1702 is configured to obtain a first cell identity and a network identity.
  • the network identity includes the identity of the first private network and the identity of the second private network.
  • the first network element serves the terminal device in the first private network; the processing module 1702 , Is also used to determine, according to the first cell identity, that the current area of the terminal device is beyond the service range of the cell identified by the first cell identity; the transceiver module 1701 is used to send the first cell identity and the first cell identity to the first mobility management network element
  • the network identifier, the first cell identifier and the network identifier are used to obtain downlink routing information, where the downlink routing information is used to indicate that the downlink data is transferred from the first user plane entity in the first private network to the second user plane in the second private network Physical transmission.
  • the transceiver module 1701 is also used to receive downlink routing information from the first mobility management network element, where the downlink routing information is allocated by the second user plane entity; the transceiver module 1701 is also used to send information to the first user The plane entity sends downlink routing information.
  • the transceiver module 1701 is also used to receive the second cell identity from the terminal device; the transceiver module 1701 is also used to send the second cell identity to the first mobility management network element; the transceiver module 1701 is also used to receive the second cell identity from the first mobile management network element;
  • the mobility management network element receives a first TA list allocated by the first mobility management network element to the terminal device, where the first TA list includes the second cell identifier and the first cell identifier; or the first TA list includes the second cell Identification; the transceiver module 1701 is also used to send a first TA list to the terminal device, the first TA list is used to identify the location area registered by the terminal device.
  • the transceiver module 1701 is further configured to send the identity of the first network element, the cell identity of the serving cell of the first network element, and the network identity of the network where the first network element is located to the network storage function network element, for registering with the network Storage function network element.
  • the processing module 1702 is used to obtain the first cell identity and the network identity, the network identity includes the identity of the first private network, where the first network element serves the terminal device in the first private network; the processing module 1702 is also used to The first cell identifier determines that the current area of the terminal device exceeds the service range of the cell identified by the first cell identifier; the transceiver module 1701 is configured to send the first cell identifier and the network identifier to the first mobility management network element.
  • the cell identifier and the network identifier are used to obtain downlink routing information, where the downlink routing information is used to indicate the transmission of downlink data from the first user plane entity in the first private network to the second user plane entity in the public network.
  • the first network element 170 is presented in the form of dividing various functional modules in an integrated manner.
  • the "module” here can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and/or other devices that can provide the above-mentioned functions.
  • the first network element 170 may take the form of the communication device 700 shown in FIG. 7.
  • the processor 701 in the communication device 700 shown in FIG. 7 may invoke the computer execution instruction stored in the memory 703 to make the communication device 700 execute the communication method in the foregoing method embodiment.
  • the functions/implementation process of the transceiver module 1701 and the processing module 1702 in FIG. 17 may be implemented by the processor 701 in the communication device 700 shown in FIG. 7 calling a computer execution instruction stored in the memory 703.
  • the function/implementation process of the processing module 1702 in FIG. 17 can be implemented by the processor 701 in the communication device 700 shown in FIG. 7 calling a computer execution instruction stored in the memory 703, and the function of the transceiver module 1701 in FIG. /The realization process can be realized through the communication interface 704 in the communication device 700 shown in FIG. 7.
  • the first network element 170 provided in this embodiment can perform the above-mentioned communication method, the technical effects that can be obtained can refer to the above-mentioned method embodiment, and will not be repeated here.
  • one or more of the above modules or units can be implemented by software, hardware or a combination of both.
  • the software exists in the form of computer program instructions and is stored in the memory, and the processor can be used to execute the program instructions and implement the above method flow.
  • the processor can be built in SoC (system on chip) or ASIC, or it can be an independent semiconductor chip.
  • SoC system on chip
  • ASIC application specific integrated circuit
  • the processor's internal processing is used to execute software instructions for calculations or processing, and may further include necessary hardware accelerators, such as field programmable gate array (FPGA), PLD (programmable logic device) , Or a logic circuit that implements dedicated logic operations.
  • FPGA field programmable gate array
  • PLD programmable logic device
  • the hardware can be a CPU, a microprocessor, a digital signal processing (digital signal processing, DSP) chip, a microcontroller unit (MCU), an artificial intelligence processor, an ASIC, Any one or any combination of SoC, FPGA, PLD, dedicated digital circuit, hardware accelerator, or non-integrated discrete device can run necessary software or do not rely on software to perform the above method flow.
  • DSP digital signal processing
  • MCU microcontroller unit
  • an artificial intelligence processor an ASIC
  • Any one or any combination of SoC, FPGA, PLD, dedicated digital circuit, hardware accelerator, or non-integrated discrete device can run necessary software or do not rely on software to perform the above method flow.
  • an embodiment of the present application further provides a communication device (for example, the communication device may be a chip or a chip system), and the communication device includes a processor for implementing the method in any of the foregoing method embodiments.
  • the communication device also includes a memory.
  • the memory is used to store necessary program instructions and data, and the processor can call the program code stored in the memory to instruct the communication device to execute the method in any of the foregoing method embodiments.
  • the memory may not be in the communication device.
  • the communication device is a chip system, it may be composed of a chip, or may include a chip and other discrete devices, which is not specifically limited in the embodiment of the present application.
  • the computer may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • a software program it may be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or may include one or more data storage devices such as servers and data centers that can be integrated with the medium.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Landscapes

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

Abstract

本申请实施例提供通信方法、设备及系统，可以在终端设备移动出第一私网的覆盖范围之后，使得终端设备切换到正确的目标小区，同时保证业务连续性。方法包括：第一移动管理网元接收来自第一网元的第一小区标识和网络标识，网络标识包括第一私网的标识和第二私网的标识；第一移动管理网元根据第一小区标识和网络标识，获取第二网元的信息，第一网元在第一私网中为终端设备服务，第二网元在第二私网中为终端设备服务；第一移动管理网元向第二网元的信息所指示的第二网元发送第一小区标识和网络标识，第一小区标识和网络标识用于获取下行路由信息，下行路由信息用于指示下行数据由第一私网中的第一用户面实体至第二私网中的第二用户面实体的传输。

Description

通信方法、设备及系统
本申请要求于2019年03月30日提交国家知识产权局、申请号为201910254004.5、申请名称为“通信方法、设备及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及通信方法、设备及系统。
背景技术
为了满足垂直行业私网场景需求多样化，第三代合作伙伴计划(3rd generation partnership project，3GPP)标准组织定义了两个类型的私网模式，即类型A(type A)模式和类型B(type B)模式。其中，在类型B模式中，垂直行业私网网络是独立的，其与公共陆地移动网络(public land mobile network，PLMN)无任何交互需求。而对于类型A模式，其与PLMN有互通需求。比如，如图1所示，工厂A和工厂B均位于类型A模式的私网的覆盖范围内，当企业用户离开工厂A，前往工厂B时，为了保证业务连续性，需要PLMN提供网络服务保证，因此类型A模式的私网与PLMN有互通需求。
但是，如图2所示，通常情况下，PLMN与类型A模式的私网的网络覆盖是重叠的，此时终端设备可能位于类型A模式的私网和PLMN的重叠覆盖区。然而，若终端设备离开类型A模式的私网的覆盖区，此时终端设备如何切换到目标小区，同时保证业务连续性，是目前亟待解决的问题。
发明内容
本申请实施例提供通信方法、设备及系统，可以在终端设备移动出第一私网的覆盖范围之后，使得终端设备切换到目标小区，同时保证业务连续性。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，提供了一种通信方法，该方法包括：第一移动管理网元接收来自第一网元的第一小区标识和网络标识，该网络标识包括第一私网的标识和第二私网的标识；第一移动管理网元根据该第一小区标识和该网络标识，获取第二网元的信息，其中，第一网元在该第一私网中为终端设备服务，第二网元在该第二私网中为该终端设备服务；第一移动管理网元向该第二网元的信息所指示的第二网元发送该第一小区标识和该网络标识，该第一小区标识和该网络标识用于获取下行路由信息，其中，该下行路由信息用于指示下行数据由该第一私网中的第一用户面实体至该第二私网中的第二用户面实体的传输。
基于该方案，由于该方案中，当终端设备移动出第一私网的覆盖范围之后，可以选择到第二私网，并且第一移动管理网元发送至第二私网中的第二网元的第一小区标识和网络标识可以用于获取下行路由信息，该下行路由信息用于指示下行数据由第一私网中的第一用户面实体至第二私网中的第二用户面实体的传输。这样，第一用户面实体接收到下行数据时，可以按照下行数据路由信息将下行数据发送给第二用户面实 体，从而保持业务的连续性。
在一种可能的设计中，第一移动管理网元根据该第一小区标识和该网络标识，获取第二网元的信息，包括：第一移动管理网元确定该第一小区标识属于该第一移动管理网元为该终端设备分配的第一跟踪区TA列表；第一移动管理网元向网络存储功能网元发送该第一小区标识和该网络标识，该第一小区标识和该网络标识用于确定该第二网元的信息；第一移动管理网元接收来自该网络存储功能网元的该第二网元的信息。也就是说，本申请实施例中，第一移动管理网元可以从网络存储功能网元获取第二网元的信息。
在一种可能的设计中，该通信方法还包括：第一移动管理网元从该终端设备接收第二小区标识；第一移动管理网元为该终端设备分配第一TA列表，其中，该第一TA列表中包括该第二小区标识和该第一小区标识；第一移动管理网元通过该第一网元发送向该终端设备发送该第一TA列表，其中，该第一TA列表用于标识该终端设备注册的位置区域。基于该方案，终端设备可以获知该终端设备注册的位置区域。
在一种可能的设计中，第一移动管理网元根据该第一小区标识和该网络标识，获取第二网元的信息，包括：第一移动管理网元确定该第一小区标识不属于该第一移动管理网元为该终端设备分配的第一TA列表；第一移动管理网元向网络存储功能网元发送该第一小区标识；第一移动管理网元接收来自该网络存储功能网元的第二移动管理网元的信息，其中，该第二移动管理网元为能够服务该第一小区标识对应的小区的移动管理网元；第一移动管理网元向该第二移动管理网元所指示的该第二移动管理网元发送该第一小区标识和该网络标识，该第一小区标识和该网络标识用于确定该第二网元的信息；第一移动管理网元接收来自该第二移动管理网元的该第二网元的信息。也就是说，本申请实施例中，第一小区标识可以不是第一移动管理网元分配的，此时第一移动管理网元需要通过第二移动管理网元从网络存储功能网元获取第二网元的信息。
在一种可能的设计中，该通信方法还包括：第一移动管理网元从该终端设备接收第二小区标识；第一移动管理网元为该终端设备分配第一TA列表，其中，该第一TA列表中包括该第二小区标识；第一移动管理网元通过该第一网元发送向该终端设备发送该第一TA列表，其中，该第一TA列表用于标识该终端设备注册的位置区域。基于该方案，可以实现终端设备直接从私网接入网络，并完成第一网元和第一移动管理网元的两级分层注册。
在一种可能的设计中，该通信方法还包括：第一移动管理网元接收来自该第二网元的该下行路由信息，其中，该下行路由信息是由该第二用户面实体分配的；第一移动管理网元通过该第一网元向该第一用户面实体发送该下行路由信息。也就是说，该方案中，当终端设备移动出第一私网的覆盖范围，选择到第二私网之后，由第二私网中的第二用户面实体分配下行路由信息，并将该下行路由信息发送至第一私网中的第一用户面实体。
在一种可能的设计中，该通信方法还包括：第一移动管理网元从该终端设备接收第二小区标识；第一移动管理网元从统一数据管理网元接收该网络标识；第一移动管理网元根据该第二小区标识和该网络标识，确定该第二小区标识所标识的小区部署了 该终端设备可接入的私网；第一移动管理网元向该终端设备发送注册拒绝信息，该注册拒绝信息用于指示该终端设备注册到该终端设备可接入的私网中。基于该方案，当终端设备处在公网和终端设备可接入的私网的重叠覆盖区时，终端设备选择了公网进行了驻留，并向公网发起了终端设备的注册。在终端设备接收到注册拒绝信息之后，终端设备可以注册到终端设备可接入的私网中。
第二方面，提供了一种通信方法，该方法包括：第一网元获取第一小区标识和网络标识，该网络标识包括第一私网的标识和第二私网的标识，该第一网元在该第一私网中为终端设备服务；第一网元根据该第一小区标识，确定该终端设备当前所在的区域超出了该第一小区标识所标识的小区的服务范围；第一网元向第一移动管理网元发送该第一小区标识和该网络标识，该第一小区标识和该网络标识用于获取下行路由信息，其中，该下行路由信息用于指示下行数据由该第一私网中的第一用户面实体至该第二私网中的第二用户面实体的传输。基于该方案，由于该方案中，当终端设备移动出第一私网的覆盖范围之后，可以选择到第二私网，并且第一网元发送至第一移动管理网元的第一小区标识和网络标识可以用于获取下行路由信息，该下行路由信息用于指示下行数据由第一私网中的第一用户面实体至第二私网中的第二用户面实体的传输。这样，第一用户面实体接收到下行数据时，可以按照下行数据路由信息将下行数据发送给第二用户面实体，从而保持业务的连续性。
在一种可能的设计中，该通信方法还包括：第一网元接收来自该第一移动管理网元的下行路由信息，其中，该下行路由信息是由该第二用户面实体分配的；第一网元向该第一用户面实体发送该下行路由信息。也就是说，该方案中，当终端设备移动出第一私网的覆盖范围，选择到第二私网之后，由第二私网中的第二用户面实体分配下行路由信息，并将该下行路由信息发送至第一私网中的第一用户面实体。
在一种可能的设计中，该通信方法还包括：第一网元从该终端设备接收第二小区标识；第一网元向该第一移动管理网元发送该第二小区标识；第一网元从该第一移动管理网元接收该第一移动管理网元为该终端设备分配的第一跟踪区TA列表，其中，该第一TA列表中包括该第二小区标识和该第一小区标识；或者，该第一TA列表中包括该第二小区标识；第一网元向该终端设备发送该第一TA列表，该第一TA列表用于标识该终端设备注册的位置区域。基于该方案，可以使得终端设备注册到可接入的私网中。
在一种可能的设计中，该通信方法还包括：
该第一网元向网络存储功能网元发送该第一网元的标识、该第一网元服务小区的小区标识和该第一网元所在网络的网络标识，用于注册到该网络存储功能网元。基于该方案，可以实现第一网元的网络属性信息注册，进而在后续业务处理过程中，其他网络功能实体能够准确获取第一网元的属性信息，从而保证业务正常进行。
第三方面，提供了一种通信方法，该方法包括：第一移动管理网元接收来自第一网元的第一小区标识和网络标识，该网络标识包括第一私网的标识，其中，该第一网元在该第一私网中为终端设备服务；第一移动管理网元根据该第一小区标识和该网络标识，确定当前由第二移动管理网元在公网中为该终端设备服务；第一移动管理网元确定服务该终端设备的该公网中的集中单元控制面实体；第一移动管理网元向该公网 中的集中单元控制面实体发送该第一小区标识和该网络标识，该第一小区标识和该网络标识用于获取下行路由信息，其中，该下行路由信息用于指示下行数据由该第一私网中的第一用户面实体至该公网中的第二用户面实体的传输。由于该方案中，当终端设备移动出第一私网的覆盖范围之后，可以选择到公网，并且公网中的第一移动管理网元可以向该公网中的集中单元控制面实体发送第一小区标识和网络标识，该第一小区标识和该网络标识用于获取下行路由信息，该下行路由信息用于指示下行数据由第一私网中的第一用户面实体至公网中的第二用户面实体的传输。这样，第一用户面实体接收到下行数据时，可以按照下行数据路由信息将下行数据发送给第二用户面实体，从而保持业务的连续性。
第四方面，提供了一种通信方法，该方法包括：第一网元获取第一小区标识和网络标识，该网络标识包括第一私网的标识，其中，该第一网元在该第一私网中为终端设备服务；第一网元根据该第一小区标识，确定该终端设备当前所在的区域超出了该第一小区标识所标识的小区的服务范围；第一网元向第一移动管理网元发送该第一小区标识和该网络标识，该第一小区标识和该网络标识用于获取下行路由信息，其中，该下行路由信息用于指示下行数据由该第一私网中的第一用户面实体至公网中的第二用户面实体的传输。由于该方案中，当终端设备移动出第一私网的覆盖范围之后，可以选择到公网，并且第一私网中的第一网元可以向第一移动管理网元发送第一小区标识该网络标识，该第一小区标识和该网络标识用于获取下行路由信息，该下行路由信息用于指示下行数据由第一私网中的第一用户面实体至公网中的第二用户面实体的传输。这样，第一用户面实体接收到下行数据时，可以按照下行数据路由信息将下行数据发送给第二用户面实体，从而保持业务的连续性。
第五方面，提供了一种通信方法，该通信方法包括：第一网元确定终端设备的终端标识、寻呼小区以及与该寻呼小区对应的集中单元控制面实体；第一网元向与该寻呼小区对应的集中单元控制面实体发送寻呼消息，该寻呼消息包括该终端标识和该寻呼小区的信息。基于该方案，第一网元可以实现对空闲态终端设备的寻呼处理。
在一种可能的设计中，第一网元确定该终端设备的终端标识、寻呼小区以及与该寻呼小区对应的集中单元控制面实体，包括：第一网元接收来自该第一用户面网元的事件报告，该事件报告包括数据包包头的终端设备互联网协议IP地址信息；第一网元根据该数据包包头的终端设备IP地址信息，确定该终端设备的终端标识、寻呼小区以及与该寻呼小区对应的集中单元控制面实体。也就是说，本申请实施例提供的寻呼方法可以通过数据触发。
在一种可能的设计中，第一网元确定该终端设备的终端标识、寻呼小区以及与该寻呼小区对应的集中单元控制面实体，包括：第一网元接收针对空闲态终端设备的信令处理请求消息；第一网元根据该信令处理请求消息，确定该终端设备的终端标识、寻呼小区以及与该寻呼小区对应的集中单元控制面实体。也就是说，本申请实施例提供的寻呼方法可以通过信令触发。
在一种可能的设计中，该方法还包括：若该第一网元在寻呼多次或者预设时间内未接收到该终端设备的业务请求，该第一网元向该第一移动管理网元发送寻呼优化请求，该寻呼优化请求用于该第一移动管理网元扩大寻呼范围。基于该方案，第一移动 管理网元可以对终端设备的寻呼进行更大范围的寻呼处理。
第六方面，提供了一种通信设备用于实现上述各种方法。该通信设备可以为上述第一方面或第三方面中的第一移动管理网元，或者包含上述第一移动管理网元的装置；或者，该通信设备可以为上述第二方面或第四方面或第五方面中的第一网元，或者包含上述第一网元的装置。所述通信设备包括实现上述方法相应的模块、单元、或手段(means),该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
第七方面，提供了一种通信设备，包括：处理器和存储器；该存储器用于存储计算机指令，当该处理器执行该指令时，以使该通信设备执行上述第一方面所述的通信方法。该通信设备可以为上述第一方面或第三方面中的第一移动管理网元，或者包含上述第一移动管理网元的装置；或者，该通信设备可以为上述第二方面或第四方面或第五方面中的第一网元，或者包含上述第一网元的装置。
第八方面，提供了一种通信设备，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述第一方面至第五方面中任一方面所述的通信方法。该通信设备可以为上述第一方面或第三方面中的第一移动管理网元，或者包含上述第一移动管理网元的装置；或者，该通信设备可以为上述第二方面或第四方面或第五方面中的第一网元，或者包含上述第一网元的装置。
第九方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行如上述第一方面至第五方面中任一方面所述的通信方法。
第十方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行如上述第一方面至第五方面中任一方面所述的通信方法。
第十一方面，提供了一种通信设备(例如，该通信设备可以是芯片或芯片系统)，该通信设备包括处理器，用于实现上述第一方面至第五方面中任一方面中所涉及的功能。在一种可能的设计中，该通信设备还包括存储器，该存储器，用于保存必要的程序指令和数据。该通信设备是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第六方面至第十一方面中任一种设计方式所带来的技术效果可参见上述第一方面或第二方面或第三方面或第四方面或第五方面中不同设计方式所带来的技术效果，此处不再赘述。
第十二方面，提供了一种通信系统，该通信系统包括第一移动管理网元和第一网元；其中，第一网元，用于获取第一小区标识和网络标识，该网络标识包括第一私网的标识和第二私网的标识，该第一网元在该第一私网中为终端设备服务；第一网元，还用于根据第一小区标识，确定终端设备当前所在的区域超出了该第一小区标识所标识的小区的服务范围；第一网元，还用于向第一移动管理网元发送该第一小区标识和该网络标识；第一移动管理网元，用于接收来自第一网元的该第一小区标识和该网络标识；第一移动管理网元，还用于根据该第一小区标识和该网络标识，获取第二网元的信息，其中，该第二网元在该第二私网中为该终端设备服务；第一移动管理网元，还用于向该第二网元的信息所指示的第二网元发送该第一小区标识和该网络标识，该 第一小区标识和该网络标识用于获取下行路由信息，其中，该下行路由信息用于指示下行数据由该第一私网中的第一用户面实体至该第二私网中的第二用户面实体的传输。基于该方案，由于该方案中，当终端设备移动出第一私网的覆盖范围之后，可以选择到第二私网，并且第一移动管理网元发送至第二私网中的第二网元的第一小区标识和网络标识可以用于获取下行路由信息，该下行路由信息用于指示下行数据由第一私网中的第一用户面实体至第二私网中的第二用户面实体的传输。这样，第一用户面实体接收到下行数据时，可以按照下行数据路由信息将下行数据发送给第二用户面实体，从而保持业务的连续性。
第十三方面，提供了一种通信系统，该通信系统包括第一移动管理网元和第一网元；其中，第一网元，用于获取第一小区标识和网络标识，该网络标识包括第一私网的标识，其中，该第一网元在该第一私网中为终端设备服务；第一网元，还用于根据该第一小区标识，确定该终端设备当前所在的区域超出了该第一小区标识所标识的小区的服务范围；第一网元，还用于向第一移动管理网元发送该第一小区标识和该网络标识；第一移动管理网元，用于接收来自第一网元的该第一小区标识和该网络标识；第一移动管理网元，还用于根据该第一小区标识和该网络标识，确定当前由第二移动管理网元在公网中为该终端设备服务；第一移动管理网元，还用于确定服务该终端设备的该公网中的集中单元控制面实体；第一移动管理网元，还用于向该公网中的集中单元控制面实体发送该第一小区标识和该网络标识，该第一小区标识和该网络标识用于获取下行路由信息，其中，该下行路由信息用于指示下行数据由该第一私网中的第一用户面实体至该公网中的第二用户面实体的传输。由于该方案中，当终端设备移动出第一私网的覆盖范围之后，可以选择到公网，并且公网中的第一移动管理网元可以向该公网中的集中单元控制面实体发送第一小区标识和网络标识，该第一小区标识和该网络标识用于获取下行路由信息，该下行路由信息用于指示下行数据由第一私网中的第一用户面实体至公网中的第二用户面实体的传输。这样，第一用户面实体接收到下行数据时，可以按照下行数据路由信息将下行数据发送给第二用户面实体，从而保持业务的连续性。
附图说明
图1为现有的用户终端移动场景示意图；
图2为现有的PLMN和类型A模式的私网的部署示意图；
图3为本申请实施例提供的通信系统示意图一；
图4为本申请实施例提供的5G网络的CN-CP网元示意图；
图5为本申请实施例提供的私网中的网元的连接与结构示意图；
图6为本申请实施例提供的通信系统示意图二；
图7为本申请实施例提供的通信设备的结构示意图；
图8a为本申请实施例提供的通信方法流程示意图一；
图8b为本申请实施例提供的通信方法交互流程示意图一；
图9a为本申请实施例提供的通信方法流程示意图二；
图9b为本申请实施例提供的通信方法交互流程示意图二；
图10为本申请实施例提供的一种DCF网元向NRF网元注册的流程示意图；
图11为本申请实施例提供的注册方案示意图；
图12为本申请实施例提供的注册方法流程示意图一；
图13为本申请实施例提供的注册方法流程示意图二；
图14为本申请实施例提供的寻呼方法流程示意图一；
图15为本申请实施例提供的寻呼方法流程示意图二；
图16为本申请实施例提供的第一移动管理网元的结构示意图；
图17为本申请实施例提供的第一网元的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。同时，在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
此外，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
如图3所示，为本申请实施例提供的一种通信系统30。该通信系统30包括公网(例如可以为PLMN)、第一私网(private network)和第二私网。其中，第一私网和第二私网均为类型A模式的私网。需要说明的是，申请实施例中的私网也可以称为非公网(non-public network)。
示例性的，如图3所示，公网中可以包括核心网控制面(core network-control plane，CN-CP)网元、核心网用户面(core network-user plane，CN-UP)网元(未示出)和RAN设备(未示出)。第一私网中可以包括第一网元(例如可以为图3中的第一分布式控制功能(distributed control function，DCF)网元)和第一无线接入网(radio access network，RAN)设备。其中第一RAN设备中包括第一集中式单元控制面(central unit-control plane，CU-CP)实体、第一分布式单元(distributed unit，DU)实体和第一用户面实体(例如可以为图3中的第一边缘网关(edge gateway，EGW)。第二私 网中可以包括第二网元(例如可以为图3中的第二DCF网元)和第二RAN设备。其中第二RAN设备中包括第二CU-CP实体、第二DU实体和第二用户面实体(例如可以为图3中的第二EGW)。其中，公网中的CN-CP网元分别连接第一私网中的第一DCF网元和第二私网中的第二DCF网元。第一私网中的第一DCF网元连接第一私网中的第一CU-CP实体，第一私网中的第一CU-CP实体分别连接第一私网中的第一EGW和第一DU实体。第二私网中的第二DCF网元连接第二私网中的第二CU-CP实体，第二私网中的第二CU-CP实体分别连接第二私网中的第二EGW和第二DU实体。
其中，图3描述的是终端设备从第一私网的覆盖区域移动到第二私网的覆盖区域，由于DCF1网元并不知道终端设备所在的目标区域的网络拓扑，因此需要终端设备注册的公网协同完成移动切换处理。
其中，本申请实施例中的CN-CP网元可以包括移动管理网元、统一数据管理网元、会话管理网元、网络存储功能网元或者认证功能网元等。移动管理网元主要用于移动网络中的移动性管理，如用户位置更新、用户注册网络、用户切换等。会话管理网元主要提供会话管理功能，包括用户设备(user equipment，UE)互联网协议(internet protocol，IP)地址分配，用户面功能(user plane function，UPF)实体选择、或者策略和计费控制(Policy and Charging Control，PCC)策略执行等功能。网络存储功能网元主要提供网络功能(network function，NF)注册或发现功能，维护管理NF状态(包括NF支持的小区/PLMN/无线接入类型(radio access type，RAT)等信息)及NF支持的服务类型等功能。统一数据管理网元主要用于处理用户标识、接入鉴权、注册、或移动性管理等。认证功能网元元主要用于认证鉴权等。
示例性的，如图4所示，在第五代(5rd generation，5G)中，移动管理网元可以为接入和移动性管理功能(access and mobility management function，AMF)网元，会话管理网元可以为会话管理功能(session management function，SMF)网元，认证功能网元可以为认证服务器功能(authentication server function，AUSF)网元，统一数据管理网元可以为统一数据管理(unified data management，UDM)网元，网络存储功能网元可以为网络存储功能(network repository function，NRF)网元。当然，在未来其他网络中，移动管理网元、统一数据管理网元、会话管理网元、网络存储功能网元或者认证功能网元可以分别为其他，本申请实施例对此不作具体限定。
可选的，本申请实施例中的AMF网元、SMF网元、UDM网元、AUSF网元、或者NRF网元等CN-CP网元可以采用服务化接口进行交互。比如，如图4所示，AMF网元对外提供的服务化接口可以为Namf；SMF网元对外提供的服务化接口可以为Nsmf；UDM网元对外提供的服务化接口可以为Nudm；NRF网元对外提供的服务化接口可以为Nnrf；AUSF网元对外提供的服务化接口可以为Nausf。相关描述可以参考23501标准中的5G系统架构(5G system architecture)，在此不予赘述。
其中，本申请实施例中的CN-UP网元可以包括用户面实体。其中，用户面实体主要用于根据会话管理网元的路由规则执行用户数据包的转发。在5G网络中，用户面实体可以为UPF实体；在未来其他网络中，用户面实体可以为其他，本申请实施例对此不作具体限定。
其中，本申请实施例中的DCF网元(包括图3中的第一DCF网元、图3中的第 二DCF网元或者后续实施例中的其他DCF网元)负责非接入层(non-access stratum，NAS)解析和加解密、DCF支持控制类用户数据传输、本地移动性管理、会话管理、计费、合法监听、本地用户的UE IP地址分配、寻呼、或本地业务能力开放等。
其中，如图5所示，本申请实施例中的CU-CP实体(包括图3中的第一CU-CP实体、图3中的第二CU-CP实体或者后续实施例中的其他CU-CP实体)包含在RAN CP中，负责无线资源控制功能，该无线资源控制功能包括系统消息广播，无线资源控制(radio resource control，RRC)连接管理(如RRC连接建立/重配/释放)，移动性管理(如测量控制、测量上报、切换)，控制面信令的加解密，或者分组数据单元(packet data unit，PDU)会话资源(session resource)参数解析等。
其中，本申请实施例中的EGW实体(包括图3中的第一EGW实体、图3中的第二EGW实体或者后续实施例中的其他EGW实体)可以根据无线网络的协议层划分。例如，如图5所示，分组数据汇聚协议用户面(packet data convergence protocol-user plane，PDCP-U)协议层和业务数据适配协议栈(service data adaptation protocol，SDAP)协议层可以设置在EGW实体中。其中，PDCP-U负责用户面数据加解密、完整性保护，或者数据按序转发等功能；SDAP增强支持基于包过滤器(packet filter)将IP数据包映射到数据无线承载(data radio bear，DRB)上。
其中，本申请实施例中的DU实体(包括图3中的第一DU实体、图3中的第二DU实体或者后续实施例中的其他DU实体)可以根据无线网络的协议层划分。例如如图5所示，无线链路控制(radio link control，RLC)协议层，媒体接入控制(media access control，MAC)协议层，物理(physical，PHY)协议层的功能可以设置在DU实体中。
可以理解，上述对EGW实体和DU实体处理功能按照这种协议层的划分仅仅是一种举例，也可以按照其他的方式进行划分，本申请实施例对此不作具体限定。
可选的，如图5所示，本申请实施例中的第一RAN设备或第二RAN设备的RAN CP中还可以包括无线网络管理功能(radio network management function，RNMF)实体，该RNMF实体包括RAN服务化NF管理功能，RAN功能控制(如切换决策，寻呼等功能)，或接口通信功能。
此外，如图5所示，本申请实施例中，DU实体和RAN CP之间可以通过F1-C接口连接，DU实体和EGW实体之间可以通过F1-U接口连接，EGW实体和RAN CP实体之间可以通过E1口连接，RAN CP实体和DCF网元之间通过N2接口连接。其中，在RAN CP仅包括CU-CP实体的情况下，本申请实施例中的RAN CP可以替换为CU-CP实体，在此统一说明，以下不再赘述。
可选的，如图6所示，为本申请实施例提供的另一种通信系统60。该通信系统60包括公网(例如可以为PLMN)和第一私网。其中，第一私网为类型A模式的私网。
示例性的，如图6所示，公网中可以包括CN-CP网元、CN-UP网元和第二RAN设备。其中，第二RAN设备中可以包括第二CU-CP实体、CU-UP实体和第二DU实体。第一私网中可以包括第一网元(例如可以为图6中的第一DCF网元)和第一RAN设备。其中第一RAN设备中包括第一CU-CP实体、第一DU实体和第一用户面实体(例如可以为图6中的第一EGW)。其中，第一私网中的第一DCF网元连接第一私网中的第一CU-CP实体，第一私网中的第一CU-CP实体分别连接第一私网中的第一 EGW和第一DU实体。第一私网中的第一DCF网元还连接公网中的CN-CP网元，公网中的CN-CP网元连接公网中的第二CU-CP实体，公网中的第二CU-CP实体分别连接公网中的CU-UP实体和第二DU实体，公网中的CN-UP网元连接公网中的CU-UP实体。
其中，图6描述的是终端设备从第一私网的覆盖区域移动到公网的覆盖区域。由于DCF1网元并不知道终端设备所在的目标区域的网络拓扑，因此需要终端设备注册的公网协同完成移动切换处理。
其中，本申请实施例中的CN-CP网元、CN-UP网元、DCF网元、CU-UP实体、EGW、DU实体的相关描述可参考图4或图5所示的实施例，在此不再赘述。
其中，本申请实施例中的CU-UP实体负责用户面功能，主要包含SDAP协议层和PDCP用户面(PDCP user plane，PDCP-U)协议层，相关描述可参考现有技术，在此不再赘述。
可选的，本申请实施例中的终端设备，可以是用于实现无线通信功能的设备，例如终端或者可用于终端中的芯片等。其中，终端可以是5G网络或者未来演进的PLMN中的用户设备(user equipment，UE)、接入终端、终端单元、终端站、移动站、移动台、远方站、远程终端、移动设备、无线通信设备、终端代理或终端装置等。接入终端可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备或可穿戴设备，虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。终端可以是移动的，也可以是固定的。
可选的，本申请实施例中的RAN设备，是一种将终端设备接入到无线网络的设备，可以是长期演进(long term evolution，LTE)中的演进型基站(evolutional Node B，eNB或eNodeB)；或者5G网络或者未来演进的PLMN中的基站，宽带网络业务网关
(broadband network gateway，BNG)，汇聚交换机或非3GPP接入设备等，本申请实施例对此不作具体限定。其中，本申请实施例中的基站可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等，本申请实施例对此不作具体限定。
可选的，本申请实施例中的移动管理网元(如后续方法实施例中的第一AMF网元)或第一网元也可以称之为通信设备，其可以是一个通用设备或者是一个专用设备，本申请实施例对此不作具体限定。
可选的，本申请实施例中的移动管理网元或第一网元的相关功能可以由一个设备实现，也可以由多个设备共同实现，还可以是由一个设备内的一个或多个功能模块实现，本申请实施例对此不作具体限定。可以理解的是，上述功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是硬件与软件的结合，或 者是平台(例如，云平台)上实例化的虚拟化功能。
例如，本申请实施例中的移动管理网元或第一网元的相关功能可以通过图7中的通信设备700来实现。图7所示为本申请实施例提供的通信设备700的结构示意图。该通信设备700包括一个或多个处理器701，通信线路702，以及至少一个通信接口(图7中仅是示例性的以包括通信接口704，以及一个处理器701为例进行说明)，可选的还可以包括存储器703。
处理器701可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路702可包括一通路，用于连接不同组件之间。
通信接口704，可以是收发模块用于与其他设备或通信网络通信，如以太网，RAN，无线局域网(wireless local area networks，WLAN)等。例如，所述收发模块可以是收发器、收发机一类的装置。可选的，所述通信接口704也可以是位于处理器701内的收发电路，用以实现处理器的信号输入和信号输出。
存储器703可以是具有存储功能的装置。例如可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路702与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器703用于存储执行本申请方案的计算机执行指令，并由处理器701来控制执行。处理器701用于执行存储器703中存储的计算机执行指令，从而实现本申请实施例中提供的通信方法。
或者，可选的，本申请实施例中，也可以是处理器701执行本申请下述实施例提供的通信方法中的处理相关的功能，通信接口704负责与其他设备或通信网络通信，本申请实施例对此不作具体限定。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器701可以包括一个或多个CPU，例如图7中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信设备700可以包括多个处理器，例如图7中的处理器701和处理器708。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，通信设备700还可以包括输出设备705和输入设备706。输出设备705和处理器701通信，可以以多种方式来显示信息。例如，输 出设备705可以是液晶显示器(liquid crystal display，LCD)，发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备706和处理器701通信，可以以多种方式接收用户的输入。例如，输入设备706可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的通信设备700有时也可以称为通信装置，其可以是一个通用设备或者是一个专用设备。例如通信设备700可以是台式机、便携式电脑、网络服务器、掌上电脑(personal digital assistant，PDA)、移动手机、平板电脑、无线终端设备、嵌入式设备、上述终端设备，上述网络设备、或具有图7中类似结构的设备。本申请实施例不限定通信设备700的类型。
下面将结合图3至图7对本申请实施例提供的通信方法进行具体阐述。
需要说明的是，本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等只是一个示例，具体实现中也可以是其他的名字，本申请实施例对此不作具体限定。
首先，假设终端设备可以接入多个类型A模式的私网，终端设备从第一私网的覆盖区域移动到第二私网的覆盖区域(如图3所示的场景)，则如图8a所示，为本申请实施例提供的一种通信方法，该通信方法包括如下步骤S801a-S803a：
S801a、第一移动管理网元接收来自第一网元的第一小区标识和网络标识，该网络标识包括第一私网的标识和第二私网的标识。
S802a、第一移动管理网元根据第一小区标识和网络标识，获取第二网元的信息。
其中，第一网元在第一私网中为终端设备服务，第二网元在第二私网中为终端设备服务。
S803a、第一移动管理网元向第二网元的信息所指示的第二网元发送第一小区标识和网络标识。该第一小区标识和该网络标识用于获取下行路由信息，其中，该下行路由信息用于指示下行数据由第一私网中的第一用户面实体至第二私网中的第二用户面实体的传输。
基于该通信系统，可以在终端设备移动出第一私网的覆盖范围之后，使得终端设备切换到目标小区，同时保证业务连续性。其中，该方案的具体实现将通过图8b所示的网元之间的交互流程进行详细阐述，在此不再赘述。
以公网为5G网络，第一移动管理网元为第一AMF网元，第一网元为图3中的第一DCF网元，第二网元为图3中的第二DCF网元，第一用户面实体为图3中的第一EGW，第二用户面实体为图3中的第二EGW为例，如图8b所示，为本申请实施例提供的一种通信方法，包括如下步骤：
S801、第一私网中的第一CU-CP实体基于终端设备上报的测量报告，确定需要对终端设备执行切换处理。
其中，本申请实施例中，第一CU-CP实体确定需要对终端设备执行切换处理之后，可以进一步确定将切换到的目标小区(target cell)，本申请实施例示例性的以目标小区为第一小区为例进行说明。
S802、第一CU-CP实体向第一DCF网元发送第一切换(handover，HO)请求消息。第一DCF网元接收来自第一CU-CP实体的第一切换请求消息。
其中，该第一切换请求消息包括第一小区标识，该第一小区标识用于标识第一小区。
可选的，该第一切换请求消息还可以包括终端设备标识(如5G-全球唯一临时UE标识(globally unique temporary UE identity，GUTI)或系统架构演进(system architecture evolution，SAE)临时移动用户标识(SAE temporary mobile subscriber identity，S-TMSI))、终端设备上下文、数据网络名称(data network name，DNN)、服务质量(quality of services，QoS)文件(profile)及其对应的包过滤器(packet filter)等信息，本申请实施例对此不作具体限定。其中，DNN标识终端设备访问的业务的数据网络名称。QoS profile是发送给RAN网络功能(包括CU实体或DU实体等)的QoS参数信息，包括分配保持优先级(allocation and retention priority，ARP)、保证流比特率(guaranteed flow bit rate，GFBR)、最大流比特率(maximum flow bit rate，MFBR)、最大丢包率(maximum packet loss rate，MPLR)等。
S803、第一DCF网元根据第一小区标识，确定终端设备当前所在的区域超出了第一小区标识所标识的小区的服务范围。
S804、第一DCF网元向第一AMF网元发送第二切换请求消息，第一AMF网元接收来自第一DCF网元的第二切换请求消息。
其中，该第二切换请求消息包括第一切换请求消息中的参数和网络标识。该网络标识包括终端设备可接入的私网的标识。本申请实施例以网络标识包括第一私网的标识和第二私网的标识为例进行说明。
其中，在第一AMF网元获取第一小区标识和网络标识之后，可以根据第一小区标识和网络标识，确定第一小区标识所标识的第一小区是否部署了DCF网元，下面示例性的提供两种实现方式。
一种可能的实现方式中，如图8b所示，该通信方法还包括如下步骤S805a-S807a：
S805a、第一AMF网元确定第一小区标识属于第一AMF网元为终端设备分配的第一跟踪区(tracking area，TA)列表。
其中，第一AMF网元可以在注册过程中为终端设备分配第一TA列表，第一TA列表标识终端设备注册的位置区，具体实现可参考后续的注册流程，在此不再赘述。
S806a、第一AMF网元向NRF网元发送第一网络服务查询请求消息。NRF网元接收来自第一AMF网元的第一网络服务查询请求消息。
其中，该第一网络服务查询请求消息包括网络功能(network function，NF)类型(即DCF)、上述第一小区标识和网络标识。
可选的，本申请实施例中的第一网络服务查询请求消息也可以替换为第一NF服务请求(service request)消息，在此不作具体限定。
S807a、NRF网元确定第一小区标识所标识的第一小区部署了DCF网元，且基于网络标识确定部署的DCF网元支持终端设备可接入的私网。
例如，NRF网元确定第一小区标识所标识的第一小区是否部署了DCF网元，且基于网络标识确定部署的DCF网元是否支持终端设备可接入的私网。若NRF网元确定第一小区标识所标识的第一小区部署了DCF网元，且基于网络标识确定部署的DCF网元支持终端设备可接入的私网，NRF网元向第一AMF网元发送第一网络服务查询 响应消息。第一AMF网元接收来自NRF网元的第一网络服务查询响应消息。该第一网络服务查询响应消息包括第二DCF网元的信息。其中，第二DCF网元的信息用于指示第二DCF网元。
可选的，本申请实施例中，第二DCF网元的信息可以包括第二DCF网元的IP地址，在此不作具体限定。
当然，若NRF网元确定第一小区标识所标识的第一小区部署了DCF网元，但是不存在DCF网元支持终端设备可接入的私网；或者，若NRF网元确定第一小区标识所标识的第一小区未部署DCF网元，此时NRF网元也可以向第一AMF网元发送网络服务查询响应消息。该网络服务查询响应消息不包括DCF网元的信息，本申请实施例对此不作具体限定。
可选的，本申请实施例中的第一网络服务查询响应消息也可以替换为第一NF服务响应(service response)消息，在此不作具体限定。
或者，另一种可能的实现方式中，如图8b所示，该通信方法还包括如下步骤S805b-S811b：
S805b、第一AMF网元确定第一小区标识不属于第一AMF网元为终端设备分配的第一TA列表。
其中，第一AMF网元可以在注册过程中为终端设备分配第一TA列表，第一TA列表标识终端设备注册的位置区，具体实现可参考后续的注册流程，在此不再赘述。
S806b、第一AMF网元向NRF网元发送第二网络服务查询请求消息。NRF网元接收来自第一AMF网元的第二网络服务查询请求消息。
其中，该第二网络服务查询请求消息包括上述第一小区标识和NF类型(即AMF)。
可选的，本申请实施例中的第二网络服务查询请求消息也可以替换为第二NF服务请求消息，在此不作具体限定。
S807b、NRF网元确定存在能够服务第一小区标识所标识的第一小区的移动管理网元。
例如，NRF网元确定是否存在能够服务第一小区标识所标识的第一小区的移动管理网元。若存在，NRF网元向第一AMF网元发送第二网络服务查询响应消息。第一AMF网元接收来自NRF网元的第二网络服务查询响应消息。其中，假设能够服务第一小区标识所标识的第一小区的移动管理网元为第二AMF网元，则该第二网络服务查询响应消息可以包括第二AMF网元的信息。该第二AMF网元的信息用于指示第二AMF网元。
可选的，本申请实施例中，第二AMF网元的信息例如可以包括第二AMF网元的IP地址，在此不作具体限定。
当然，若NRF网元确定不存在能够服务第一小区标识所标识的第一小区的移动管理网元，NRF网元也可以向第一AMF网元发送网络服务查询响应消息。该网络服务查询响应消息不包括AMF网元的信息，本申请实施例对此不作具体限定。
S808b、第一AMF网元向第二AMF网元的信息所指示的第二AMF网元发送第一N14消息。第二AMF网元接收来自第一AMF网元的第一N14消息。
其中，该第一N14消息包括第一小区标识和网络标识。
S809b、第二AMF网元向NRF网元发送第三网络服务查询请求消息。NRF网元接收来自第二AMF网元的第三网络服务查询请求消息。
其中，该第三网络服务查询请求消息包括NF类型(即DCF)、上述第一小区标识和网络标识。
可选的，本申请实施例中的第三网络服务查询请求消息也可以替换为第三NF服务请求(service request)消息，在此不作具体限定。
S810b、NRF网元确定第一小区标识所标识的第一小区部署了DCF网元，且基于网络标识确定部署的DCF网元支持终端设备可接入的私网。
例如，NRF网元确定第一小区标识所标识的第一小区是否部署了DCF网元，且基于网络标识确定部署的DCF网元是否支持终端设备可接入的私网。若NRF网元确定第一小区标识所标识的第一小区部署了DCF网元，且基于网络标识确定部署的DCF网元支持终端设备可接入的私网，NRF网元向第二AMF网元发送第三网络服务查询响应消息。第二AMF网元接收来自NRF网元的第三网络服务查询响应消息。该第三网络服务查询响应消息包括第二DCF网元的信息。其中，第二DCF网元的信息用于指示第二DCF网元。
当然，若NRF网元确定第一小区标识所标识的第一小区部署了DCF网元，但是不存在DCF网元支持终端设备可接入的私网；或者，若NRF网元确定第一小区标识所标识的第一小区未部署DCF网元，此时NRF网元也可以向第一AMF网元发送网络服务查询响应消息。该网络服务查询响应消息不包括DCF网元的信息，本申请实施例对此不作具体限定。
可选的，本申请实施例中，第二DCF网元的信息可以包括第二DCF网元的IP地址，在此不作具体限定。
可选的，本申请实施例中的第三网络服务查询响应消息也可以替换为第三NF服务响应消息，在此不作具体限定。
S811b、第二AMF网元向第一AMF网元发送第二N14消息。第一AMF网元接收来自第二AMF网元的第二N14消息。
其中，第二N14消息包括第二DCF网元的信息。
进一步的，本申请实施例中，在AMF1网元获取第二DCF网元的信息之后，本申请实施例提供的通信方法还可以包括如下步骤：
S812、第一AMF网元向第二DCF网元的信息所指示的第二DCF网元发送第三切换请求消息。第二DCF网元接收来自第一AMF网元的第三切换请求消息。
其中，该第三切换请求消息包括第二切换请求消息中的参数，如第一小区标识和网络标识。
S813、第二DCF网元确定服务第一小区的CU-CP实体，这里假设为第二CU-CP实体。
可选的，本申请实施例中，第二DCF网元可以根据第一小区标识、RAT类型(即终端设备当前的接入制式，如LTE或新空口(new radio，NR))或者PLMN信息等信息确定服务第一小区的CU-CP实体。
S814、第二DCF网元向第二CU-CP实体发送第四切换请求消息。第二CU-CP实 体接收来自第二DCF网元的第四切换请求消息。
其中，该第四切换请求消息包括第三切换请求消息中的参数，如第一小区标识和网络标识。
S815、第二CU-CP实体确定服务第一小区的EGW，这里假设为第二EGW。
可选的，本申请实施例中，第二CU-CP实体可以根据第一小区标识等信息选择服务第一小区的EGW，在此不作具体限定。
S816、第二CU-CP实体向第二EGW发起会话资源建立(session resource setup)，使得第二EGW分配下行路由信息，并将该下行路由信息发送给第二CU-CP实体。第二CU-CP实体接收来自第二EGW的下行路由信息。
其中，该下行路由信息用于指示下行数据由第一私网中的第一用户面实体至第二私网中的第二用户面实体的传输，其中，这里的第一用户面实体可以对应图3中的第一EGW，这里的第二用户面实体可以对应图3中的第二EGW。
可选的，本申请实施例中的下行路由信息可以包括第二EGW的MAC地址或IP地址，在此不作具体限定。
S817、第二CU-CP实体完成和第二EGW的会话资源建立配置之后，确定服务第一小区的DU实体，这里假设为第二DU实体。
S818、第二CU-CP实体与第二DU实体之间完成DU资源建立。
S819、第二CU-CP实体完成第二EGW和第二DU实体的资源建立之后，向第二DCF网元发送第四切换请求确认(HO request ack)消息。第一DCF网元接收来自第二CU-CP实体的第四切换请求确认消息。
其中，该第四切换请求确认消息包括第二EGW分配的下行路由信息。
S820、第二DCF网元向第一AMF网元发送第三切换请求确认消息。第一AMF网元接收来自第二DCF网元的第三切换请求确认消息。
其中，该第三切换请求确认消息包括第二EGW分配的下行路由信息。
S821、第一AMF网元向第一DCF网元发送第二切换请求确认消息。第一DCF网元接收来自第一AMF网元的第二切换请求确认消息。
其中，该第二切换请求确认消息包括第二EGW分配的下行路由信息。
可选的，该第二切换请求确认消息中还可以包括包过滤器等参数信息，在此不作具体限定。
S822、第一DCF网元向第一CU-CP实体发送切换命令(HO command)消息。第一CU-CP实体接收来自第一DCF网元的切换命令消息。
其中，该切换命令消息包括第二EGW分配的下行路由信息。该切换命令消息用于确认已经执行切换处理。
S823、第一CU-CP实体向第一EGW发送切换命令消息。第一EGW接收来自第一CU-CP实体的切换命令消息。
其中，该切换命令消息包括第二EGW分配的下行路由信息。该切换命令消息用于确认已经执行切换处理。
这样，第一EGW接收到下行数据时，可以按照下行数据路由信息将下行数据发送给第二EGW，从而保持业务的连续性。
S824、第一CU-CP实体通过第一DU实体向终端设备发送切换命令消息。终端设备通过第一DU实体接收来自第一CU-CP实体的切换命令消息。
其中，该切换命令消息包括第二EGW分配的下行路由信息。该切换命令消息用于确认已经执行切换处理。
S825、终端设备接收到切换命令消息之后，确认切换完成，并通过第二DU实体向第二CU-CP实体发送切换命令确认(HO command ack)消息。第二CU-CP实体通过第二DU实体接收来自终端设备的切换命令确认消息。
基于本申请实施例提供的通信方法，由于该方案中，当终端设备移动出第一私网的覆盖范围之后，可以选择到第二私网，并且第二私网中的第二EGW可以分配下行路由信息，并将该下行路由信息发送至第一私网中的第一EGW，该下行路由信息用于指示下行数据由第一私网中的第一EGW至第二私网中的第二EGW的传输。这样，第一EGW接收到下行数据时，可以按照下行数据路由信息将下行数据发送给第二EGW，从而保持业务的连续性。
其中，上述步骤S801至S825中的第一AMF网元或者第一DCF网元的动作可以由图7所示的通信设备700中的处理器701调用存储器703中存储的应用程序代码来执行，本实施例对此不作任何限制。
假设终端设备从类型A模式的私网移动到目标区域之后，目标区域没有部署终端设备可接入的私网，即终端设备从第一私网的覆盖区域移动到公网的覆盖区域(如图6所示的场景)，则如图9a所示，为本申请实施例提供的一种通信方法，该通信方法包括如下步骤S901a-S904a：
S901a、第一移动管理网元接收来自第一网元的第一小区标识和网络标识，网络标识包括第一私网的标识，其中，第一网元在第一私网中为终端设备服务。
S902a、第一移动管理网元根据第一小区标识和网络标识，确定当前由第二移动管理网元在公网中为终端设备服务。
S903a、第一移动管理网元确定服务该终端设备的公网中的集中单元控制面实体。
S904a、第一移动管理网元向公网中的集中单元控制面实体发送第一小区标识和网络标识，第一小区标识和网络标识用于获取下行路由信息，其中，下行路由信息用于指示下行数据由第一私网中的第一用户面实体至公网中的第二用户面实体的传输。
基于该通信系统，可以在终端设备移动出第一私网的覆盖范围之后，使得终端设备切换到目标小区，同时保证业务连续性。其中，该方案的具体实现将通过图9b所示的网元之间的交互流程进行详细阐述，在此不再赘述。
以公网为5G网络，第一移动管理网元为第一AMF网元，第二移动管理网元为第二AMF网元，第一网元为图6中的第一DCF网元，集中单元控制面实体为图6中的第二CU-CP实体，第一用户面实体为图6中的第一EGW，第二用户面实体为图6中的CU-UP实体为例，如图9b所示，为本申请实施例提供的另一种通信方法，包括如下步骤：
S901-S904、同图8b所示的实施例中的步骤S801-S804，相关描述可参考图8b所示的实施例，在此不再赘述。
其中，在第一AMF网元获取第一小区标识和网络标识之后，可以根据第一小区 标识和网络标识，确定第一小区标识所标识的第一小区是否部署了DCF网元，下面示例性的提供两种实现方式。
一种可能的实现方式中，如图9b所示，该通信方法还包括如下步骤S905a-S907a：
S905a-S906a、同图8b所示的实施例中的步骤S805a-S806a，相关描述可参考图8b所示的实施例，在此不再赘述。
S907a、NRF网元确定第一小区标识所标识的第一小区部署了DCF网元，但是不存在DCF网元支持终端设备可接入的私网；或者，NRF网元确定第一小区标识所标识的第一小区未部署DCF网元。
例如，NRF网元确定第一小区标识所标识的第一小区是否部署了DCF网元，且基于网络标识确定部署的DCF网元是否支持终端设备可接入的私网。若NRF网元确定第一小区标识所标识的第一小区部署了DCF网元，但是不存在DCF网元支持终端设备可接入的私网；或者，若NRF网元确定第一小区标识所标识的第一小区未部署DCF网元。NRF网元向第一AMF网元发送第一网络服务查询响应消息。第一AMF网元接收来自NRF网元的第一网络服务查询响应消息。其中，该第一网络服务查询响应消息中不包括DCF网元的信息。
当然，若NRF网元确定第一小区标识所标识的第一小区部署了DCF网元，且基于网络标识确定部署的DCF网元支持终端设备可接入的私网，继续执行图8b所示的实施例中的相关流程，在此不再赘述。
可选的，本申请实施例中的第一网络服务查询响应消息也可以替换为第一NF服务响应消息，在此不作具体限定。
或者，另一种可能的实现方式中，如图8b所示，该通信方法还包括如下步骤S905b-S911b：
S905b-S909b、同图8b所示的实施例中的步骤S805b-S809b，相关描述可参考图8b所示的实施例，在此不再赘述。
S910b、NRF网元确定第一小区标识所标识的第一小区部署了DCF网元，但是不存在DCF网元支持终端设备可接入的私网；或者，NRF网元确定第一小区标识所标识的第一小区未部署DCF网元。
例如，NRF网元确定第一小区标识所标识的第一小区是否部署了DCF网元，且基于网络标识确定部署的DCF网元是否支持终端设备可接入的私网。若NRF网元确定第一小区标识所标识的第一小区部署了DCF网元，但是不存在DCF网元支持终端设备可接入的私网；或者，若NRF网元确定第一小区标识所标识的第一小区未部署DCF网元。NRF网元向第二AMF网元发送第三网络服务查询响应消息。第二AMF网元接收来自NRF网元的第三网络服务查询响应消息。其中，该第三网络服务查询响应消息中不包括DCF网元的信息。
当然，若NRF网元确定第一小区标识所标识的第一小区部署了DCF网元，且基于网络标识确定部署的DCF网元支持终端设备可接入的私网，继续执行图8b所示的实施例中的相关流程，在此不再赘述。
S911b、第二AMF网元向第一AMF网元发送第二N14消息。第一AMF网元接收来自第二AMF网元的第二N14消息。
其中，第二N14消息不包括DCF网元的信息。
进一步的，本申请实施例中，由于AMF1网元未获取到DCF网元的信息，因此可以确定当前由第一AMF网元(对应第一小区标识属于第一AMF网元为终端设备分配的第一TA列表的情况)或者第二AMF网元(对应第一小区标识不属于第一AMF网元为终端设备分配的第一TA列表的情况)为终端设备服务，进一步的，本申请实施例提供的通信方法还可以包括如下步骤：
S912、第一AMF网元确定服务第一小区的CU-CP实体，这里假设为第二CU-CP实体。
可选的，本申请实施例中，第一AMF网元可以根据第一小区标识、RAT类型(即终端设备当前的接入制式)或者PLMN信息等信息确定服务第一小区的CU-CP实体。
S913、第一AMF网元向第二CU-CP实体发送第三切换请求消息。第二CU-CP实体接收来自第一AMF网元的第三切换请求消息。
其中，该第三切换请求消息包括第二切换请求消息中的参数，如第一小区标识和网络标识。
S914、第二CU-CP实体确定服务第一小区的CU-UP实体。
可选的，本申请实施例中，第二CU-CP实体可以根据第一小区标识等信息选择服务第一小区的CU-UP实体，在此不作具体限定。
S915、第二CU-CP实体向CU-UP实体发起会话资源建立，使得CU-UP实体分配下行路由信息，并将该下行路由信息发送给第二CU-CP实体。第二CU-CP实体接收来自CU-UP实体的下行路由信息。
其中，该下行路由信息用于指示下行数据由第一私网中的第一用户面实体至第二私网中的第二用户面实体的传输，其中，这里的第一用户面实体可以对应图6中的第一EGW，这里的第二用户面实体可以对应图6中的CU-UP实体。
可选的，本申请实施例中的下行路由信息可以包括CU-UP实体的MAC地址或IP地址，在此不作具体限定。
S916、第二CU-CP实体完成和CU-UP实体的会话资源建立配置之后，确定服务第一小区的DU实体，这里假设为第二DU实体。
S917、第二CU-CP实体与第二DU实体之间完成DU资源建立。
S918、第二CU-CP实体完成CU-UP实体和第二DU实体的资源建立之后，向第一AMF网元发送第三切换请求确认消息。第一AMF网元接收来自第二CU-CP实体的第三切换请求确认消息。
其中，该第三切换请求确认消息包括CU-UP实体分配的下行路由信息。
S919、第一AMF网元向第一DCF网元发送第二切换请求确认消息。第一DCF网元接收来自第一AMF网元的第二切换请求确认消息。
其中，该第二切换请求确认消息包括CU-UP实体分配的下行路由信息。
可选的，该第二切换请求确认消息中还可以包括包过滤器等参数信息，在此不作具体限定。
S920、第一DCF网元向第一CU-CP实体发送切换命令消息。第一CU-CP实体接收来自第一DCF网元的切换命令消息。
其中，该切换命令消息包括第二EGW分配的下行路由信息。该切换命令消息用于确认已经执行切换处理。
S921、第一CU-CP实体向第一EGW发送切换命令消息。第一EGW接收来自第一CU-CP实体的切换命令消息。
其中，该切换命令消息包括CU-UP实体分配的下行路由信息。该切换命令消息用于确认已经执行切换处理。
这样，第一EGW接收到下行数据时，可以按照下行数据路由信息将下行数据发送给CU-UP实体，从而保持业务的连续性。
S922、第一CU-CP实体通过第一DU实体向终端设备发送切换命令消息。终端设备通过第一DU实体接收来自第一CU-CP实体的切换命令消息。
其中，该切换命令消息包括CU-UP实体分配的下行路由信息。该切换命令消息用于确认已经执行切换处理。
S923、终端设备接收到切换命令消息之后，确认切换完成，并通过第二DU实体向第二CU-CP实体发送切换命令确认消息。第二CU-CP实体通过第二DU实体接收来自终端设备的切换命令确认消息。
基于本申请实施例提供的通信方法，由于该方案中，当终端设备移动出第一私网的覆盖范围之后，可以选择到公网，并且公网中的CU-UP实体可以分配下行路由信息，并将该下行路由信息发送至第一私网中的第一EGW，该下行路由信息用于指示下行数据由第一私网中的第一EGW至公网中的CU-UP实体的传输。这样，第一EGW接收到下行数据时，可以按照下行数据路由信息将下行数据发送给CU-UP实体，从而保持业务的连续性。
其中，上述步骤S901至S923中的第一AMF网元或者第一DCF网元的动作可以由图7所示的通信设备700中的处理器701调用存储器703中存储的应用程序代码来执行，本实施例对此不作任何限制。
本申请实施例中，在终端设备发生移动性切换之前，当网络中的DCF网元部署上线后，DCF网元需要向NRF网元进行服务注册，并将其相关属性信息(如其服务区，标识或名称等)发送给NRF网元登记保存，进而在后续其他业务处理流程中，网络中的其他NF即可通过查询NRF网元来获取DCF网元的信息，如上述图8b或图9b所示的实施例中，第一AMF网元或第二AMF网元可以从NRF网元中查询DCF网元的信息。示例性的，如图10所示，为本申请实施例提供的一种DCF网元向NRF网元注册的流程示意图，包括如下步骤：
S1001、DCF网元上线部署配置之后，向NRF网元发送NF注册请求。NRF网元接收来自DCF网元的NF注册请求。
其中，该NF注册请求包括DCF网元的标识(如DCF网元的名字)、DCF网元服务的小区标识和网络标识等信息，其中，网络标识用于识别DCF网元所处的网络类型，如类型A模式的私网，或所属的私网企业，如A企业网络，具体形式本申请实施例不作限定。
S1002、NRF网元存储DCF网元的注册信息，以使得后续其他NF查询调用该DCF网元服务。
S1003、NRF网元完成DCF网元的信息注册管理后，向DCF网元发送NF注册响应。DCF网元接收来自NRF网元的NF注册响应。
其中，该NF注册响应用于确认完成DCF网元的服务注册。
基于该方案，可以实现DCF网元的网络属性信息注册，进而在后续业务处理过程中，其他NF能够准确获取DCF网元的属性信息，从而保证业务正常进行。
其中，上述步骤S1001至S1003中DCF网元的动作可以由图7所示的通信设备700中的处理器701调用存储器703中存储的应用程序代码来执行，本实施例对此不作任何限制。
本申请实施例中，在终端设备发生移动性切换之前，终端设备需要进行注册。根据现有技术中对类型A模式的私网的定义，虽然类型A模式的私网只提供私网业务服务，但类型A模式的私网的终端设备也需要公网为其提供网络服务以保证业务连续性。因此，为了能够获得类型A模式的私网的业务服务和公网网络的业务服务，终端设备需在类型A模式的私网和公网同时注册。基于图2所示的私网部署场景，本申请实施例可以提供两种终端设备注册的方法。一种方案为终端设备通过私网中的DU实体、CU-CP实体和DCF网元进行注册，一种方案为终端设备通过公网中的DU实体和CU-CP实体进行注册，如图11所示。下面对终端设备的这两种注册方案进行详细说明。
一种可能的实现方式中，终端设备处于类型A模式的私网的覆盖区，终端设备通过类型A模式的私网向私网中的DCF网元进行注册，DCF网元获取终端设备的可允许接入的网络信息，并基于此信息判断是否需要执行到公网(如PLMN)的CN-CP进行注册。其中，该方案需要修改终端设备的小区选择策略。即终端设备选择小区是，优选私网的小区，如类型A模式的私网的小区，以保证终端设备能够直接接入到其可接入的私网中。具体的，终端设备执行小区选择时，可以基于接收的系统信息块(system information block，SIB)消息(SIB消息中包括类型A模式的私网的网络标识)和其可接入的网络标识列表(客户识别模块(subscriber identity module，SIM)卡中保存的)，优选类型A模式的私网的小区驻留，并完成RRC连接建立。在RRC连接建立完成之后，示例性的，如图12所示，为本申请实施例提供的一种终端设备注册的流程示意图，包括如下步骤：
S1201、终端设备通过私网中的DU实体和CU-CP向私网中的DCF网元发送第一注册请求(registration request)。DCF网元接收来自终端设备的第一注册请求。
其中，该第一注册请求包括注册PDU、终端设备当前所处小区的小区标识(这里记为第二小区标识)和RAT类型等信息。
需要说明的是，步骤S1201中的DU实体和CU-CP实体是终端设备初始接入网络时的RRC连接建立流程中选择好的，且终端设备和这些网络实体之间已经建立了无线资源连接，因此终端设备可以通过建立好的RRC连接直接发送第一注册请求，在此统一说明，以下不再赘述。
S1202、DCF网元选择AUSF网元。
可选的，本申请实施例中，DCF网元可以通过向NRF查询进行AUSF网元的选择，在此不作具体限定。
S1203、DCF网元与终端设备和AUSF网元之间执行认证鉴权，使得终端设备将相关安全上下文发送给DCF网元，进而DCF网元可以发起接入层(access stratum，AS)或NAS安全流程，激活AS或NAS安全机制。
S1204、DCF网元从UDM网元获取终端设备的接入和移动性相关签约数据。
可选的，该签约数据中可以包括终端设备可接入的私网标识等签约信息。
S1205、若签约数据中包括终端设备可接入的私网标识，且终端设备所在区域部署了终端设备签约的可接入的私网，DCF网元执行终端设备的位置注册管理，以及为终端设备分配临时标识，以及为终端设备创建终端设备的上下文。
其中，终端设备的上下文中包括上述第二小区标识和DCF网元为该终端设备分配的临时标识等。
S1206、DCF网元可通过向NRF网元查询以获取服务当前小区的AMF网元的信息，并向AMF网元发送第二注册请求。AMF网元接收来自DCF网元的第二注册请求。
其中，该第二注册请求中包括终端设备的上下文。该第二注册请求用于向AMF网元注册终端设备的相关位置信息。
S1207、AMF网元执行对终端设备的位置管理、并为终端设备分配TA列表，该TA列表用于标识终端设备注册的位置区域。
其中，本申请实施例中，该TA列表中包括一个或多个小区标识，该一个或多个小区标识中包括上述第二小区标识。
S1208、AMF网元向DCF网元发送第二注册响应。DCF网元接收来自AMF网元的第二注册响应。
其中，该第二注册响应包括上述TA列表。
S1209、DCF网元完成终端设备的上下文创建等相关处理之后，向CU-CP实体发送初始上下文建立请求(initiate UE context setup request)消息。CU-CP实体接收来自DCF网元的初始上下文建立请求消息。
其中，该初始上下文建立请求消息中可以包括注册接受PDU、5G-GUTI、切换限制(handover restriction)列表(如小区列表或PLMN列表等)、UE-聚合最大比特率(aggregate maximum bit rate，AMBR)或者DCF网元的标识等信息。5G-GUTI是DCF网元为终端设备分配的新标识，DCF网元的标识用于唯一识别DCF网元。
可选的，该初始上下文建立请求消息还可以包括上述TA列表。
S1210、CU-CP实体通过DU实体向终端设备发送注册接受(registration accept)消息。终端设备接收来自CU-CP实体的注册接受消息。
可选的，该注册接受消息包括上述TA列表、5G-GUTI或UE-AMBR中的一项或多项，本申请实施例对此不作具体限定。
S1211、终端设备通过DU实体和CU-CP实体向DCF网元发送注册完成(registration complete)消息。DCF网元接收来自终端设备的注册完成消息。
其中，该注册完成消息用于指示注册完成。
基于该方案，可以实现终端设备直接从私网接入网络，并完成DCF网元和AMF网元的两级分层注册。
其中，上述步骤S1201至S1211中DCF网元或AMF网元的动作可以由图7所示 的通信设备700中的处理器701调用存储器703中存储的应用程序代码来执行，本实施例对此不作任何限制。
另一种可能的实现方式中，终端设备处于类型A模式的私网的覆盖区，但选择了公网(如PLMN网络)进行注册，此时AMF网元拒绝终端设备的注册请求，并指示其重新进行小区选择并发起注册。示例性的，如图13所示，为本申请实施例提供的另一种终端设备注册的流程示意图，包括如下步骤：
S1301、终端设备通过公网中的DU实体和CU-CP实体向公网中的AMF网元发送注册请求。AMF网元接收来自终端设备的注册请求。
其中，该注册请求包括注册PDU、终端设备当前所处小区的小区标识(这里记为第二小区标识)和RAT类型等信息。
需要说明的是，步骤S1301中的DU实体和CU-CP实体是终端设备初始接入网络时的RRC连接建立流程中选择好的，且终端设备和这些网络实体之间已经建立了无线资源连接，因此终端设备可以通过建立好的RRC连接直接发送注册请求，在此统一说明，以下不再赘述。
S1302、AMF网元选择AUSF网元。
可选的，本申请实施例中，AMF网元可以通过向NRF查询进行AUSF网元的选择，在此不作具体限定。
S1303、AMF网元与终端设备和AUSF网元之间执行认证鉴权，使得终端设备将相关安全上下文发送给AMF网元，进而AMF网元可以发起AS或NAS安全流程，激活AS或NAS安全机制。
可选的，本申请实施例中，若终端设备之前已经在公网中注册过，则该AMF网元可以通过上下文传输(context transfer)消息向原来的AMF(old AMF)网元请求获取终端设备的上下文，在此不作具体限定。
S1304、AMF网元从UDM网元获取终端设备的接入和移动性相关签约数据。
可选的，该签约数据中可以包括终端设备可接入的私网标识等签约信息。
S1305、AMF网元确定签约数据中包括终端设备可接入的私网标识，且终端设备所在区域部署了终端设备签约的可接入的私网。
可选的，本申请实施例中，若AMF网元确定签约数据中不包括终端设备可接入的私网标识；或者，若AMF网元确定签约数据中不包括终端设备可接入的私网标识，但是终端设备所在区域未部署终端设备签约的可接入的私网，则AMF网元参照现有的注册流程继续执行终端设备注册流程的后续步骤，在此不予赘述。
S1306、AMF网元通过CU-CP实体和DU实体向终端设备发送注册响应。终端设备接收来自AMF网元的注册响应。
其中，该注册响应包括注册拒绝信息。该注册拒绝信息用于指示终端设备注册到终端设备可接入的私网中。
可选的，本申请实施例中，该注册拒绝消息可以包括注册原因值，该注册原因值为重附着(re-attach)，以指示终端设备注册到终端设备可接入的私网中。
S1307、终端设备重新发起注册流程，参考图12所示的实施例中的步骤S1201-S1211，在此不再赘述。
基于该方案，当终端设备处在公网和终端设备可接入的私网的重叠覆盖区时，终端设备选择了公网进行了驻留，并向公网发起了终端设备的注册。后续终端设备的重注册流程中，终端设备可以注册到终端设备可接入的私网中。
其中，上述步骤S1301至S1307中DCF网元或AMF网元的动作可以由图7所示的通信设备700中的处理器701调用存储器703中存储的应用程序代码来执行，本实施例对此不作任何限制。
本申请实施例还可以提供针对空闲态终端设备的寻呼处理流程。该寻呼流程中，由DCF网元负责发起针对终端设备的寻呼，若DCF网元在其服务区内寻呼不到终端设备，则进一步触发向AMF网元请求寻呼优化处理，如扩大寻呼范围。下面示例性的提供两种实现方式。
一种可能的实现方式中，如图14所示，为本申请实施例提供的一种数据触发的寻呼方法，包括如下步骤：
S1401、当EGW收到下行数据包时，解析下行数据包获得包头信息，并基于包头信息中的IP五元组和EGW(即SDAP功能)上安装的包过滤器(packet filter)进行匹配。虽然能够匹配到包过滤器，但是若EGW没有DRB与之匹配，此时EGW无法通过匹配到的包过滤器以及DRB将下行数据包发送给终端设备。于是，EGW缓存接收到的下行数据包，并通过CU-CP实体向DCF网元发送事件上报(event report)消息，DCF网元接收来自EGW的事件上报消息。
其中，该事件上报消息包括下行数据包包头的UE IP地址信息。
可选的，本申请实施例中的事件上报消息还可以包括IP五元组(IP tuple)，该IP五元组中包括源IP地址、源端口、目的IP地址、目的端口和协议类型。
S1402、DCF网元根据下行数据包包头的UE IP地址信息，确定终端设备的终端标识、寻呼小区以及与寻呼小区对应的CU-CP实体和DU实体。
可选的，本申请实施例中，DCF网元接收到来自EGW的事件上报消息之后，可以查找本地保存的终端设备的上下文以确定UE IP地址信息对应的终端设备的标识(如5G-GUTI或者S-TMSI等)寻呼小区以及与寻呼小区对应的CU-CP实体和DU实体。
S1403、DCF网元向对应的CU-CP实体发送寻呼(paging request)请求消息。CU-CP实体接收来自DCF网元的寻呼请求消息。
其中，该寻呼请求消息包括终端设备的标识和寻呼区域等信息。
需要说明的是，本申请实施例以步骤S1401中的CU-CP实体与步骤S1402中确定出的CU-CP实体为同一个CU-CP实体为例进行说明，当然，这两个CU-CP实体也可能是不同的CU-CP实体，本申请实施例对此不作具体限定。
S1404、CU-CP实体通过DU实体向终端设备发送寻呼请求消息。终端设备接收来自CU-CP实体的寻呼请求消息。
S1405、若DCF网元在寻呼多次或一定时间内未收到终端设备的回复(如业务请求(service request))，则DCF网元向AMF网元发送寻呼优化请求。AMF网元接收来自DCF网元的寻呼优化请求。
其中，该寻呼优化请求用于请求AMF网元扩大寻呼范围。
S1406、AMF网元在终端设备注册的TA列表甚至更大的范围(如全网)发起对终端设备的寻呼。
基于该方案，DCF网元可以实现对空闲态终端设备的寻呼处理，同时集中式AMF网元可以对终端设备的寻呼进行更大范围的寻呼处理。
其中，上述步骤S1401至S1406中DCF网元或AMF网元的动作可以由图7所示的通信设备700中的处理器701调用存储器703中存储的应用程序代码来执行，本实施例对此不作任何限制。
或者，另一种可能的实现方式中，如图15所示，为本申请实施例提供的一种信令触发的寻呼方法，包括如下步骤：
S1501、当DCF网元接收到针对空闲态终端设备的信令处理请求消息时，DCF网元根据信令处理请求消息确定终端设备的终端标识、寻呼小区以及与寻呼小区对应的CU-CP实体和DU实体。
S1502、DCF网元向对应的CU-CP实体发送寻呼请求消息。CU-CP实体接收来自DCF网元的寻呼请求消息。
其中，该寻呼消息包括终端设备的标识和寻呼区域等信息。
S1503-S1505、同图14所示的实施例中的步骤S1404-S1406，相关描述可参考图14所示的实施例，在此不再赘述。
基于该方案，DCF网元可以实现对空闲态终端设备的寻呼处理，同时集中式AMF网元可以对终端设备的寻呼进行更大范围的寻呼处理。
其中，上述步骤S1501至S1505中DCF网元或AMF网元的动作可以由图7所示的通信设备700中的处理器701调用存储器703中存储的应用程序代码来执行，本实施例对此不作任何限制。
可以理解的是，以上各个实施例中，由第一网元实现的方法和/或步骤，也可以由可用于第一网元的部件(例如芯片或者电路)实现，由第一移动管理网元实现的方法和/或步骤，也可以由可用于第一移动管理网元的部件实现。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。相应的，本申请实施例还提供了通信设备，该通信设备用于实现上述各种方法。该通信设备可以为上述方法实施例中的第一网元，或者包含上述第一网元的装置，或者为可用于第一网元的部件；或者，该通信设备可以为上述方法实施例中的第一移动管理网元，或者包含上述第一移动管理网元的装置，或者为可用于第一移动管理网元的部件。可以理解的是，该通信设备为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法实施例中对通信设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的 形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，以通信设备为上述方法实施例中的第一移动管理网元为例，图16示出了一种第一移动管理网元160的结构示意图。该第一移动管理网元160包括收发模块1601和处理模块1602。所述收发模块1601，也可以称为收发单元用以实现收发功能，例如可以是收发电路，收发机，收发器或者通信接口。
一种可能的实现方式中：
收发模块1601，用于接收来自第一网元的第一小区标识和网络标识，网络标识包括第一私网的标识和第二私网的标识；处理模块1602，用于根据第一小区标识和网络标识，获取第二网元的信息，其中，第一网元在第一私网中为终端设备服务，第二网元在第二私网中为终端设备服务；收发模块1601，还用于向第二网元的信息所指示的第二网元发送第一小区标识和网络标识，第一小区标识和网络标识用于获取下行路由信息，其中，下行路由信息用于指示下行数据由第一私网中的第一用户面实体至第二私网中的第二用户面实体的传输。
可选的，处理模块1602用于根据第一小区标识和网络标识，获取第二网元的信息，包括：处理模块1602，用于确定第一小区标识属于第一移动管理网元为终端设备分配的第一TA列表；通过收发模块1601向网络存储功能网元发送第一小区标识和网络标识，第一小区标识和网络标识用于确定第二网元的信息；通过收发模块1601接收来自网络存储功能网元的第二网元的信息。
进一步的，收发模块1601，还用于从终端设备接收第二小区标识；处理模块1602，还用于为终端设备分配第一TA列表，其中，第一TA列表中包括第二小区标识和第一小区标识；收发模块1601，还用于通过第一网元发送向终端设备发送第一TA列表，其中，第一TA列表用于标识终端设备注册的位置区域。
可选的，处理模块1602用于根据第一小区标识和网络标识，获取第二网元的信息，包括：处理模块1602，用于确定第一小区标识不属于第一移动管理网元为终端设备分配的第一TA列表；通过收发模块1601向网络存储功能网元发送第一小区标识；通过收发模块1601接收来自网络存储功能网元的第二移动管理网元的信息，其中，第二移动管理网元为能够服务第一小区标识对应的小区的移动管理网元；通过收发模块1601向第二移动管理网元所指示的第二移动管理网元发送第一小区标识和网络标识，第一小区标识和网络标识用于确定第二网元的信息；通过收发模块1601接收来自第二移动管理网元的第二网元的信息。
进一步的，处理模块1602，还用于从终端设备接收第二小区标识；处理模块1602，还用于为终端设备分配第一TA列表，其中，第一TA列表中包括第二小区标识；收发模块1601，还用于通过第一网元发送向终端设备发送第一TA列表，其中，第一TA列表用于标识终端设备注册的位置区域。
可选的，收发模块1601，还用于接收来自第二网元的下行路由信息，其中，下行路由信息是由第二用户面实体分配的；收发模块1601，还用于通过第一网元向第一用户面实体发送下行路由信息。
可选的，收发模块1601，还用于从终端设备接收第二小区标识；收发模块1601， 还用于从统一数据管理网元接收网络标识；处理模块1602，还用于根据第二小区标识和网络标识，确定第二小区标识所标识的小区部署了终端设备可接入的私网；收发模块1601，还用于向终端设备发送注册拒绝信息，注册拒绝信息用于指示终端设备注册到终端设备可接入的私网中。
另一种可能的实现方式中：
收发模块1601，用于接收来自第一网元的第一小区标识和网络标识，网络标识包括第一私网的标识，其中，第一网元在第一私网中为终端设备服务；处理模块1602，用于根据第一小区标识和网络标识，确定当前由第二移动管理网元在公网中为终端设备服务；处理模块1602，还用于确定服务终端设备的公网中的集中单元控制面实体；收发模块1601，还用于向公网中的集中单元控制面实体发送第一小区标识和网络标识，第一小区标识和网络标识用于获取下行路由信息，其中，下行路由信息用于指示下行数据由私网中的第一用户面实体至公网中的第二用户面实体的传输。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该第一移动管理网元160以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该第一移动管理网元160可以采用图7所示的通信设备700的形式。
比如，图7所示的通信设备700中的处理器701可以通过调用存储器703中存储的计算机执行指令，使得通信设备700执行上述方法实施例中的通信方法。
具体的，图16中的收发模块1601和处理模块1602的功能/实现过程可以通过图7所示的通信设备700中的处理器701调用存储器703中存储的计算机执行指令来实现。或者，图16中的处理模块1602的功能/实现过程可以通过图7所示的通信设备700中的处理器701调用存储器703中存储的计算机执行指令来实现，图16中的收发模块1601的功能/实现过程可以通过图7中所示的通信设备700中的通信接口704来实现。
由于本实施例提供的第一移动管理网元160可执行上述的通信方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
或者，比如，以通信设备为上述方法实施例中的第一网元为例，图17示出了一种第一网元170的结构示意图。该第一网元170包括收发模块1701和处理模块1702。所述收发模块1701，也可以称为收发单元用以实现收发功能，例如可以是收发电路，收发机，收发器或者通信接口。
一种可能的实现方式中：
处理模块1702，用于获取第一小区标识和网络标识，网络标识包括第一私网的标识和第二私网的标识，第一网元在第一私网中为终端设备服务；处理模块1702，还用于根据第一小区标识，确定终端设备当前所在的区域超出了第一小区标识所标识的小区的服务范围；收发模块1701，用于向第一移动管理网元发送第一小区标识和网络标识，第一小区标识和网络标识用于获取下行路由信息，其中，下行路由信息用于指示下行数据由第一私网中的第一用户面实体至第二私网中的第二用户面实体的传输。
可选的，收发模块1701，还用于接收来自第一移动管理网元的下行路由信息，其中，下行路由信息是由第二用户面实体分配的；收发模块1701，还用于向第一用户面实体发送下行路由信息。
可选的，收发模块1701，还用于从终端设备接收第二小区标识；收发模块1701，还用于向第一移动管理网元发送第二小区标识；收发模块1701，还用于从第一移动管理网元接收第一移动管理网元为终端设备分配的第一TA列表，其中，第一TA列表中包括第二小区标识和第一小区标识；或者，第一TA列表中包括第二小区标识；收发模块1701，还用于向终端设备发送第一TA列表，第一TA列表用于标识终端设备注册的位置区域。
可选的，收发模块1701，还用于向网络存储功能网元发送第一网元的标识、第一网元服务小区的小区标识和第一网元所在网络的网络标识，用于注册到网络存储功能网元。
另一种可能的实现方式中：
处理模块1702，用于获取第一小区标识和网络标识，网络标识包括第一私网的标识，其中，第一网元在第一私网中为终端设备服务；处理模块1702，还用于根据第一小区标识，确定终端设备当前所在的区域超出了第一小区标识所标识的小区的服务范围；收发模块1701，用于向第一移动管理网元发送第一小区标识和网络标识，第一小区标识和网络标识用于获取下行路由信息，其中，下行路由信息用于指示下行数据由第一私网中的第一用户面实体至公网中的第二用户面实体的传输。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该第一网元170以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该第一网元170可以采用图7所示的通信设备700的形式。
比如，图7所示的通信设备700中的处理器701可以通过调用存储器703中存储的计算机执行指令，使得通信设备700执行上述方法实施例中的通信方法。
具体的，图17中的收发模块1701和处理模块1702的功能/实现过程可以通过图7所示的通信设备700中的处理器701调用存储器703中存储的计算机执行指令来实现。或者，图17中的处理模块1702的功能/实现过程可以通过图7所示的通信设备700中的处理器701调用存储器703中存储的计算机执行指令来实现，图17中的收发模块1701的功能/实现过程可以通过图7中所示的通信设备700中的通信接口704来实现。
由于本实施例提供的第一网元170可执行上述的通信方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
需要说明的是，以上模块或单元的一个或多个可以软件、硬件或二者结合来实现。当以上任一模块或单元以软件实现的时候，所述软件以计算机程序指令的方式存在，并被存储在存储器中，处理器可以用于执行所述程序指令并实现以上方法流程。该处理器可以内置于SoC(片上系统)或ASIC，也可是一个独立的半导体芯片。该处理器 内处理用于执行软件指令以进行运算或处理的核外，还可进一步包括必要的硬件加速器，如现场可编程门阵列(field programmable gate array，FPGA)、PLD(可编程逻辑器件)、或者实现专用逻辑运算的逻辑电路。
当以上模块或单元以硬件实现的时候，该硬件可以是CPU、微处理器、数字信号处理(digital signal processing，DSP)芯片、微控制单元(microcontroller unit，MCU)、人工智能处理器、ASIC、SoC、FPGA、PLD、专用数字电路、硬件加速器或非集成的分立器件中的任一个或任一组合，其可以运行必要的软件或不依赖于软件以执行以上方法流程。
可选的，本申请实施例还提供了一种通信设备(例如，该通信设备可以是芯片或芯片系统)，该通信设备包括处理器，用于实现上述任一方法实施例中的方法。在一种可能的设计中，该通信设备还包括存储器。该存储器，用于保存必要的程序指令和数据，处理器可以调用存储器中存储的程序代码以指令该通信设备执行上述任一方法实施例中的方法。当然，存储器也可以不在该通信设备中。该通信设备是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (29)

  1. 一种通信方法，其特征在于，所述方法包括：
    第一移动管理网元接收来自第一网元的第一小区标识和网络标识，所述网络标识包括第一私网的标识和第二私网的标识；
    所述第一移动管理网元根据所述第一小区标识和所述网络标识，获取第二网元的信息，其中，所述第一网元在所述第一私网中为终端设备服务，所述第二网元在所述第二私网中为所述终端设备服务；
    所述第一移动管理网元向所述第二网元的信息所指示的所述第二网元发送所述第一小区标识和所述网络标识，所述第一小区标识和所述网络标识用于获取下行路由信息，其中，所述下行路由信息用于指示下行数据由所述第一私网中的第一用户面实体至所述第二私网中的第二用户面实体的传输。
  2. 根据权利要求1所述的方法，其特征在于，所述第一移动管理网元根据所述第一小区标识和所述网络标识，获取第二网元的信息，包括：
    所述第一移动管理网元确定所述第一小区标识属于所述第一移动管理网元为所述终端设备分配的第一跟踪区TA列表；
    所述第一移动管理网元向网络存储功能网元发送所述第一小区标识和所述网络标识，所述第一小区标识和所述网络标识用于确定所述第二网元的信息；
    所述第一移动管理网元接收来自所述网络存储功能网元的所述第二网元的信息。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    所述第一移动管理网元从所述终端设备接收第二小区标识；
    所述第一移动管理网元为所述终端设备分配第一TA列表，其中，所述第一TA列表中包括所述第二小区标识和所述第一小区标识；
    所述第一移动管理网元通过所述第一网元发送向所述终端设备发送所述第一TA列表，其中，所述第一TA列表用于标识所述终端设备注册的位置区域。
  4. 根据权利要求1所述的方法，其特征在于，所述第一移动管理网元根据所述第一小区标识和所述网络标识，获取第二网元的信息，包括：
    所述第一移动管理网元确定所述第一小区标识不属于所述第一移动管理网元为所述终端设备分配的第一TA列表；
    所述第一移动管理网元向网络存储功能网元发送所述第一小区标识；
    所述第一移动管理网元接收来自所述网络存储功能网元的第二移动管理网元的信息，其中，所述第二移动管理网元为能够服务所述第一小区标识对应的小区的移动管理网元；
    所述第一移动管理网元向所述第二移动管理网元所指示的所述第二移动管理网元发送所述第一小区标识和所述网络标识，所述第一小区标识和所述网络标识用于确定所述第二网元的信息；
    所述第一移动管理网元接收来自所述第二移动管理网元的所述第二网元的信息。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    所述第一移动管理网元从所述终端设备接收第二小区标识；
    所述第一移动管理网元为所述终端设备分配第一TA列表，其中，所述第一TA 列表中包括所述第二小区标识；
    所述第一移动管理网元通过所述第一网元发送向所述终端设备发送所述第一TA列表，其中，所述第一TA列表用于标识所述终端设备注册的位置区域。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述方法还包括：
    所述第一移动管理网元接收来自所述第二网元的所述下行路由信息，其中，所述下行路由信息是由所述第二用户面实体分配的；
    所述第一移动管理网元通过所述第一网元向所述第一用户面实体发送所述下行路由信息。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述方法还包括：
    所述第一移动管理网元从所述终端设备接收第二小区标识；
    所述第一移动管理网元从统一数据管理网元接收所述网络标识；
    所述第一移动管理网元根据所述第二小区标识和所述网络标识，确定所述第二小区标识所标识的小区部署了所述终端设备可接入的私网；
    所述第一移动管理网元向所述终端设备发送注册拒绝信息，所述注册拒绝信息用于指示所述终端设备注册到所述终端设备可接入的私网中。
  8. 一种通信方法，其特征在于，所述方法包括：
    第一网元获取第一小区标识和网络标识，所述网络标识包括第一私网的标识和第二私网的标识，所述第一网元在所述第一私网中为终端设备服务；
    所述第一网元根据所述第一小区标识，确定所述终端设备当前所在的区域超出了所述第一小区标识所标识的小区的服务范围；
    所述第一网元向第一移动管理网元发送所述第一小区标识和所述网络标识，所述第一小区标识和所述网络标识用于获取下行路由信息，其中，所述下行路由信息用于指示下行数据由所述第一私网中的第一用户面实体至所述第二私网中的第二用户面实体的传输。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述第一网元接收来自所述第一移动管理网元的下行路由信息，其中，所述下行路由信息是由所述第二用户面实体分配的；
    所述第一网元向所述第一用户面实体发送所述下行路由信息。
  10. 根据权利要求8或9所述的方法，其特征在于，所述方法还包括：
    所述第一网元从所述终端设备接收第二小区标识；
    所述第一网元向所述第一移动管理网元发送所述第二小区标识；
    所述第一网元从所述第一移动管理网元接收所述第一移动管理网元为所述终端设备分配的第一跟踪区TA列表，其中，所述第一TA列表中包括所述第二小区标识和所述第一小区标识；或者，所述第一TA列表中包括所述第二小区标识；
    所述第一网元向所述终端设备发送所述第一TA列表，所述第一TA列表用于标识所述终端设备注册的位置区域。
  11. 根据权利要求8-10任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网元向网络存储功能网元发送所述第一网元的标识、所述第一网元服务小区的小区标识和所述第一网元所在网络的网络标识，用于注册到所述网络存储功能 网元。
  12. 一种通信方法，其特征在于，所述方法包括：
    第一移动管理网元接收来自第一网元的第一小区标识和网络标识，所述网络标识包括第一私网的标识，其中，所述第一网元在所述第一私网中为终端设备服务；
    所述第一移动管理网元根据所述第一小区标识和所述网络标识，确定当前由第二移动管理网元在公网中为所述终端设备服务；
    所述第一移动管理网元确定服务所述终端设备的所述公网中的集中单元控制面实体；
    所述第一移动管理网元向所述公网中的集中单元控制面实体发送所述第一小区标识和所述网络标识，所述第一小区标识和所述网络标识用于获取下行路由信息，其中，所述下行路由信息用于指示下行数据由所述第一私网中的第一用户面实体至所述公网中的第二用户面实体的传输。
  13. 一种通信方法，其特征在于，所述方法包括：
    第一网元获取第一小区标识和网络标识，所述网络标识包括第一私网的标识，其中，所述第一网元在所述第一私网中为终端设备服务；
    所述第一网元根据所述第一小区标识，确定所述终端设备当前所在的区域超出了所述第一小区标识所标识的小区的服务范围；
    所述第一网元向第一移动管理网元发送所述第一小区标识和所述网络标识，所述第一小区标识和所述网络标识用于获取下行路由信息，其中，所述下行路由信息用于指示下行数据由所述第一私网中的第一用户面实体至公网中的第二用户面实体的传输。
  14. 一种通信设备，其特征在于，所述通信设备包括：收发模块和处理模块；
    所述收发模块，用于接收来自第一网元的第一小区标识和网络标识，所述网络标识包括第一私网的标识和第二私网的标识；
    所述处理模块，用于根据所述第一小区标识和所述网络标识，获取第二网元的信息，其中，所述第一网元在所述第一私网中为终端设备服务，所述第二网元在所述第二私网中为所述终端设备服务；
    所述收发模块，还用于向所述第二网元的信息所指示的所述第二网元发送所述第一小区标识和所述网络标识，所述第一小区标识和所述网络标识用于获取下行路由信息，其中，所述下行路由信息用于指示下行数据由所述第一私网中的第一用户面实体至所述第二私网中的第二用户面实体的传输。
  15. 根据权利要求14所述的通信设备，其特征在于，所述处理模块用于根据所述第一小区标识和所述网络标识，获取第二网元的信息，包括：
    所述处理模块，用于确定所述第一小区标识属于所述通信设备为所述终端设备分配的第一跟踪区TA列表；通过所述收发模块向网络存储功能网元发送所述第一小区标识和所述网络标识，所述第一小区标识和所述网络标识用于确定所述第二网元的信息；通过所述收发模块接收来自所述网络存储功能网元的所述第二网元的信息。
  16. 根据权利要求15所述的通信设备，其特征在于，
    所述收发模块，还用于从所述终端设备接收第二小区标识；
    所述处理模块，还用于为所述终端设备分配第一TA列表，其中，所述第一TA 列表中包括所述第二小区标识和所述第一小区标识；
    所述收发模块，还用于通过所述第一网元发送向所述终端设备发送所述第一TA列表，其中，所述第一TA列表用于标识所述终端设备注册的位置区域。
  17. 根据权利要求14所述的通信设备，其特征在于，所述处理模块用于根据所述第一小区标识和所述网络标识，获取第二网元的信息，包括：
    所述处理模块，用于确定所述第一小区标识不属于所述通信设备为所述终端设备分配的第一TA列表；通过所述收发模块向网络存储功能网元发送所述第一小区标识；通过所述收发模块接收来自所述网络存储功能网元的第二移动管理网元的信息，其中，所述第二移动管理网元为能够服务所述第一小区标识对应的小区的移动管理网元；通过所述收发模块向所述第二移动管理网元所指示的所述第二移动管理网元发送所述第一小区标识和所述网络标识，所述第一小区标识和所述网络标识用于确定所述第二网元的信息；通过所述收发模块接收来自所述第二移动管理网元的所述第二网元的信息。
  18. 根据权利要求17所述的通信设备，其特征在于，
    所述处理模块，还用于从所述终端设备接收第二小区标识；
    所述处理模块，还用于为所述终端设备分配第一TA列表，其中，所述第一TA列表中包括所述第二小区标识；
    所述收发模块，还用于通过所述第一网元发送向所述终端设备发送所述第一TA列表，其中，所述第一TA列表用于标识所述终端设备注册的位置区域。
  19. 根据权利要求14-18任一项所述的通信设备，其特征在于，
    所述收发模块，还用于接收来自所述第二网元的所述下行路由信息，其中，所述下行路由信息是由所述第二用户面实体分配的；
    所述收发模块，还用于通过所述第一网元向所述第一用户面实体发送所述下行路由信息。
  20. 根据权利要求14-19任一项所述的通信设备，其特征在于，
    所述收发模块，还用于从所述终端设备接收第二小区标识；
    所述收发模块，还用于从统一数据管理网元接收所述网络标识；
    所述处理模块，还用于根据所述第二小区标识和所述网络标识，确定所述第二小区标识所标识的小区部署了所述终端设备可接入的私网；
    所述收发模块，还用于向所述终端设备发送注册拒绝信息，所述注册拒绝信息用于指示所述终端设备注册到所述终端设备可接入的私网中。
  21. 一种通信设备，其特征在于，所述通信设备包括：处理模块和收发模块；
    所述处理模块，用于获取第一小区标识和网络标识，所述网络标识包括第一私网的标识和第二私网的标识，所述通信设备在所述第一私网中为终端设备服务；
    所述处理模块，还用于根据所述第一小区标识，确定所述终端设备当前所在的区域超出了所述第一小区标识所标识的小区的服务范围；
    所述收发模块，用于向第一移动管理网元发送所述第一小区标识和所述网络标识，所述第一小区标识和所述网络标识用于获取下行路由信息，其中，所述下行路由信息用于指示下行数据由所述第一私网中的第一用户面实体至所述第二私网中的第二用户面实体的传输。
  22. 根据权利要求21所述的通信设备，其特征在于，
    所述收发模块，还用于接收来自所述第一移动管理网元的下行路由信息，其中，所述下行路由信息是由所述第二用户面实体分配的；
    所述收发模块，还用于向所述第一用户面实体发送所述下行路由信息。
  23. 根据权利要求21或22所述的通信设备，其特征在于，
    所述收发模块，还用于从所述终端设备接收第二小区标识；
    所述收发模块，还用于向所述第一移动管理网元发送所述第二小区标识；
    所述收发模块，还用于从所述第一移动管理网元接收所述第一移动管理网元为所述终端设备分配的第一跟踪区TA列表，其中，所述第一TA列表中包括所述第二小区标识和所述第一小区标识；或者，所述第一TA列表中包括所述第二小区标识；
    所述收发模块，还用于向所述终端设备发送所述第一TA列表，所述第一TA列表用于标识所述终端设备注册的位置区域。
  24. 根据权利要求21-23任一项所述的通信设备，其特征在于，
    所述收发模块，还用于向网络存储功能网元发送所述通信设备的标识、所述通信设备服务小区的小区标识和所述通信设备所在网络的网络标识，用于注册到所述网络存储功能网元。
  25. 一种通信设备，其特征在于，所述通信设备包括：处理模块和收发模块；
    所述收发模块，用于接收来自第一网元的第一小区标识和网络标识，所述网络标识包括第一私网的标识，其中，所述第一网元在所述第一私网中为终端设备服务；
    所述处理模块，用于根据所述第一小区标识和所述网络标识，确定当前由第二移动管理网元在公网中为所述终端设备服务；
    所述处理模块，还用于确定服务所述终端设备的所述公网中的集中单元控制面实体；
    所述收发模块，还用于向所述公网中的集中单元控制面实体发送所述第一小区标识和所述网络标识，所述第一小区标识和所述网络标识用于获取下行路由信息，其中，所述下行路由信息用于指示下行数据由所述私网中的第一用户面实体至所述公网中的第二用户面实体的传输。
  26. 一种通信设备，其特征在于，所述通信设备包括：处理模块和收发模块；
    所述处理模块，用于获取第一小区标识和网络标识，所述网络标识包括第一私网的标识，其中，所述通信设备在所述第一私网中为终端设备服务；
    所述处理模块，还用于根据所述第一小区标识，确定所述终端设备当前所在的区域超出了所述第一小区标识所标识的小区的服务范围；
    所述收发模块，用于向第一移动管理网元发送所述第一小区标识和所述网络标识，所述第一小区标识和所述网络标识用于获取下行路由信息，其中，所述下行路由信息用于指示下行数据由所述第一私网中的第一用户面实体至公网中的第二用户面实体的传输。
  27. 一种通信系统，其特征在于，所述通信系统包括如权利要求14-20任一项所述的通信设备、以及如权利要求21-24任一项所述的通信设备。
  28. 一种通信系统，其特征在于，所述通信系统包括如权利要求25所述的通信设 备、以及如权利要求26所述的通信设备。
  29. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1-13任意一项所述的方法。
PCT/CN2020/080963 2019-03-30 2020-03-24 通信方法、设备及系统 WO2020199991A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20782702.3A EP3930378B1 (en) 2019-03-30 2020-03-24 Handover from a non-public-network
US17/490,447 US11956691B2 (en) 2019-03-30 2021-09-30 Communication method, device, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910254004.5 2019-03-30
CN201910254004.5A CN111770538B (zh) 2019-03-30 2019-03-30 通信方法、设备及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/490,447 Continuation US11956691B2 (en) 2019-03-30 2021-09-30 Communication method, device, and system

Publications (1)

Publication Number Publication Date
WO2020199991A1 true WO2020199991A1 (zh) 2020-10-08

Family

ID=72664534

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/080963 WO2020199991A1 (zh) 2019-03-30 2020-03-24 通信方法、设备及系统

Country Status (4)

Country Link
US (1) US11956691B2 (zh)
EP (1) EP3930378B1 (zh)
CN (1) CN111770538B (zh)
WO (1) WO2020199991A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3925246B1 (en) * 2019-02-13 2023-04-05 Telefonaktiebolaget LM Ericsson (publ) Method and apparatuses for handling of wireless device subscribed aggregate maximum bitrate (ambr) in wireless communication networks
CN110727633A (zh) * 2019-09-17 2020-01-24 广东高云半导体科技股份有限公司 基于SoC FPGA的边缘人工智能计算系统构架
CN112511980B (zh) * 2020-11-06 2022-09-13 中国联合网络通信集团有限公司 一种通信系统、方法及装置
CN114615737B (zh) * 2020-12-07 2023-09-05 中国移动通信集团设计院有限公司 5g网元注册信息审核方法、装置、电子设备和存储介质
US11671908B2 (en) * 2021-03-30 2023-06-06 Samsung Electronics Co., Ltd. Selecting PLMN in wireless communication system
CN113727329B (zh) * 2021-08-16 2023-05-02 中国联合网络通信集团有限公司 一种通信方法及装置
US20240224345A1 (en) * 2022-12-30 2024-07-04 Dish Wireless L.L.C. Network repository function

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101505510A (zh) * 2008-02-04 2009-08-12 华为技术有限公司 宏小区到私有小区的切换方法及其宏网络系统
CN102984773A (zh) * 2012-11-23 2013-03-20 富春通信股份有限公司 Lte-wlan网间互通下的wlan切换方法及装置
CN107454641A (zh) * 2016-05-31 2017-12-08 上海贝尔股份有限公司 在超密网中实施的通信方法以及相应的装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101656990B (zh) * 2008-08-20 2014-10-22 三星电子株式会社 移动通信系统中支持切换的方法
CN102143536B (zh) * 2010-12-17 2013-11-06 华为终端有限公司 自动切换网络的方法和装置、无线接入设备和中间设备
KR101970627B1 (ko) * 2014-09-30 2019-04-19 후아웨이 테크놀러지 컴퍼니 리미티드 전용 네트워크 핸드오버 방법, 및 전용 네트워크 유형 통지 방법 및 장치
EP3465993A4 (en) * 2016-05-27 2019-12-18 Corning Optical Communications LLC SYSTEM AND METHOD FOR VIRTUAL RADIO CELL
CN110636587B (zh) * 2018-06-22 2022-02-01 维沃移动通信有限公司 处理方法、终端及网元
KR20200077259A (ko) * 2018-12-20 2020-06-30 삼성전자주식회사 네트워크 연결 방법 및 장치

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101505510A (zh) * 2008-02-04 2009-08-12 华为技术有限公司 宏小区到私有小区的切换方法及其宏网络系统
CN102984773A (zh) * 2012-11-23 2013-03-20 富春通信股份有限公司 Lte-wlan网间互通下的wlan切换方法及装置
CN107454641A (zh) * 2016-05-31 2017-12-08 上海贝尔股份有限公司 在超密网中实施的通信方法以及相应的装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3930378A4

Also Published As

Publication number Publication date
EP3930378A1 (en) 2021-12-29
CN111770538B (zh) 2021-10-15
US20220022122A1 (en) 2022-01-20
EP3930378B1 (en) 2024-01-24
EP3930378A4 (en) 2022-04-06
US11956691B2 (en) 2024-04-09
CN111770538A (zh) 2020-10-13

Similar Documents

Publication Publication Date Title
WO2020199991A1 (zh) 通信方法、设备及系统
US11838858B2 (en) System and method for UE context and PDU session context management
US12088501B2 (en) Systems and methods for supporting traffic steering through a service function chain
US11432366B2 (en) Session management method, device, and system
US11026080B2 (en) Policy control function determining method, apparatus, and system
KR102589956B1 (ko) 데이터 전송 방법, 장치, 및 시스템
WO2018153253A1 (zh) 一种选择会话管理功能实体的方法、装置和系统
WO2020248828A1 (zh) 通信方法、装置及系统
WO2020057401A1 (zh) 一种网元选择方法及装置
US20220346190A1 (en) Session Management Method, Device, and System
WO2019128671A1 (zh) 会话建立方法、设备及系统
WO2021042742A1 (zh) 一种通信方法、装置及系统
TW202131752A (zh) 多存取協定資料單元會話升級的處理
KR20210024160A (ko) 통신 방법 및 장치
EP4271043A1 (en) Communication method, apparatus and system
WO2020155972A1 (zh) 一种移动性管理方法及装置
KR20230023759A (ko) 통신 방법 및 장치
WO2020001319A1 (zh) 动态组网方法、设备及系统
CN115915196A (zh) 一种链路状态检测方法、通信装置及通信系统
US20240267336A1 (en) Systems and methods for edge-to-edge quality of service flow control in network slices
WO2023197737A1 (zh) 报文发送方法、pin管理方法、通信装置及通信系统
WO2021159523A1 (zh) 通信方法、装置及系统
WO2020156182A1 (zh) 服务小区信息的更新方法及装置
WO2024027803A1 (zh) 通信方法、装置及系统
WO2024104118A1 (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: 20782702

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020782702

Country of ref document: EP

Effective date: 20210922

NENP Non-entry into the national phase

Ref country code: DE