WO2019076273A1 - 一种切换的方法、移动性管理网元和通信系统 - Google Patents
一种切换的方法、移动性管理网元和通信系统 Download PDFInfo
- Publication number
- WO2019076273A1 WO2019076273A1 PCT/CN2018/110279 CN2018110279W WO2019076273A1 WO 2019076273 A1 WO2019076273 A1 WO 2019076273A1 CN 2018110279 W CN2018110279 W CN 2018110279W WO 2019076273 A1 WO2019076273 A1 WO 2019076273A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network
- mobility management
- terminal device
- identifier
- network element
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims abstract description 65
- 238000000034 method Methods 0.000 title claims abstract description 62
- 238000012545 processing Methods 0.000 claims description 40
- 238000004590 computer program Methods 0.000 claims description 5
- 238000007726 management method Methods 0.000 description 206
- 230000006870 function Effects 0.000 description 36
- 102100035784 Decorin Human genes 0.000 description 21
- 238000013461 design Methods 0.000 description 20
- 238000010586 diagram Methods 0.000 description 15
- 230000003993 interaction Effects 0.000 description 8
- 230000011664 signaling Effects 0.000 description 8
- 230000008569 process Effects 0.000 description 7
- 101150079125 DCN1 gene Proteins 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 102100022887 GTP-binding nuclear protein Ran Human genes 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 238000013523 data management Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/66—Policy and charging system
-
- 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/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
-
- 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/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context 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/0055—Transmission or use of information for re-establishing the radio link
- H04W36/0066—Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network
-
- 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/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
- H04W36/00695—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using split of the control plane or user plane
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/24—Reselection being triggered by specific parameters
- H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
- H04W36/324—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by mobility data, e.g. speed data
-
- 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
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/20—Transfer of user or subscriber data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
Definitions
- the present application relates to the field of wireless communication technologies, and in particular, to a method, a mobility management network element, and a communication system in a wireless communication system.
- the core network can be called Dedicated Core Network (abbreviation: DCN).
- DCN Dedicated Core Network
- the dedicated core network can serve a specific type of terminal device, for example, a machine type communication terminal device is served by a dedicated core network that supports the machine class communication; and can also serve a general type of terminal device, for example, the universal terminal device is supported by a certain universal device.
- Different dedicated core networks include core network devices supporting different terminal device types or service types, such as a mobility management entity (MME), a serving gateway (SGW), a data gateway (PDN Gateway, PGW), and the like.
- MME mobility management entity
- SGW serving gateway
- PGW data gateway
- the DCN helps operators to perform targeted management and maintenance on terminal devices with different usage types, and is dedicated to private networks, thereby improving the efficiency of accessing mobile devices and session management for terminal devices and reducing network maintenance costs.
- the network can slice multiple logical core network network slice instances on the same physical device in the core network through the slicing technology.
- Each core network network slice instance can be customized according to specific business scenarios or user requirements. It can ensure the isolation between network slice instances while satisfying the diversity service.
- the network slice includes Access and Mobility Management Function (AMF), session management function (SMF), and User plane function (UPF). Operators can provide customized network functions by providing free and flexible combination of network performance indicators such as rate, capacity, coverage, delay, reliability, security, and availability to meet the specific requirements of each usage scenario.
- AMF Access and Mobility Management Function
- SMF session management function
- UPF User plane function
- the movement of the terminal device may cause switching between systems, that is, the terminal device moves from the coverage of the 5G system to the coverage of the 4G system.
- the interoperability between 4G system and 5G system is an important guarantee for business continuity between systems. Due to the introduction of the above-mentioned dedicated core network and network slicing, when the terminal device switches from the 5G network to the 4G network, it is necessary to ensure that the terminal device can be served by the correct DCN.
- a vehicle-like communication terminal device that provides services in a 5G system by a core network network slice supporting vehicle-type communication services.
- the 5G network needs to select a DCN in the 4G capable of supporting vehicle-like communication services for the terminal device. Since there may be multiple DCNs supporting different services in the 4G system, if the 5G network selects the wrong DCN for the terminal device, such as universal, the selected DCN may not be able to serve the terminal device, resulting in service interruption of the terminal device. .
- This document describes a handover method, a mobility management network element, and a communication system to implement the problem of selecting a suitable mobility management network element for a terminal device during handover.
- the embodiment of the present invention provides a handover method, including: a mobility management network element of a first network receives a first handover request sent by an access network of a first network, and learns that the terminal device needs to switch to the second network; The mobility management network element of the first network acquires the identifier of the terminal device according to the first handover request; the mobility management network element of the first network determines the target mobility management of the second network according to the identifier of the terminal device a network element; the mobility management network element of the first network sends a second handover request to the target mobility management network element of the second network, requesting to switch the terminal device to the second network.
- the mobility management network element of the first network determines the target mobility management network element of the second network according to the identifier of the terminal device, including: the mobility management network element of the first network according to the The identifier of the terminal device acquires the usage type of the terminal device from the subscription database; the mobility management network element of the first network determines the target mobility management network element of the second network according to the usage type of the terminal device.
- the mobility management network element of the first network determines the target mobility management network element of the second network according to the usage type of the terminal device, including: the mobility management network element of the first network to the DNS Or the NRF sends a query request, carries the usage type of the terminal device, and receives the target mobility management NE information of the second network returned by the DNS or the NRF.
- the mobility management network element of the first network determines the target mobility management network element of the second network according to the identifier of the terminal device, and further includes: the mobility management network element of the first network according to the The identifier of the terminal device acquires the target core network identifier of the second network; the mobility management network element of the first network determines the target mobility management network element of the second network according to the target core network identifier of the second network.
- the mobility management network element of the first network acquires the target core network identifier of the second network according to the identifier of the terminal device, where: the mobility management network element of the first network is configured according to the terminal device
- the identifier of the terminal device is obtained from the context of the terminal device, and the corresponding relationship between the core network identifier and the slice information of the second network is obtained, and the first information is determined according to the slice information of the terminal device and the corresponding relationship.
- the target core network identifier of the second network is obtained from the context of the terminal device, and the corresponding relationship between the core network identifier and the slice information of the second network is obtained, and the first information is determined according to the slice information of the terminal device and the corresponding relationship.
- the mapping between the core network identifier of the second network and the slice information includes: the mobility management network element of the first network sends a request message to the policy control function PCF, and the mobility management network element of the first network receives the The PCF returns a correspondence table between the core network identifier of the second network and the slice information.
- the mobility management network element of the first network may be based on the terminal.
- the slice information of the device, the location information of the terminal device, and the corresponding relationship determine the target core network identifier of the second network.
- the determining the target core network identifier of the second network includes: determining, according to the slice information with the highest priority among the slice information of the terminal device, and the corresponding relationship, determining the target core network identifier of the second network.
- the mobility management network element of the first network acquires the target core network identifier of the second network according to the identifier of the terminal device, including: the mobility management network element of the first network sends the identifier of the terminal device And sending, by the first mobility management network element of the second network, the target core network identifier of the second network returned by the first mobility management network element of the second network according to the terminal device identifier.
- the mobility management network element of the first network obtains the target core network identifier according to the terminal device identifier, including: obtaining the target core network of the second network according to the context of the terminal device identifier querying the terminal device Logo.
- the method further includes: the mobility management network element of the first network receives a registration request of the terminal device, where the registration request includes a core network identifier of a second network of the terminal device.
- the mobility management network element of the first network saves the core network identifier of the second network, and the core network identifier of the second network is saved in the context of the terminal device.
- the mobility management network element of the first network determines, according to the target core network identifier of the second network, the target mobility management network element of the second network, where: the mobility management network element of the first network Sending a query request to the DNS or the NRF, carrying the target core network identifier of the second network, and receiving the target mobility management NE information of the second network returned by the DNS or the NRF.
- the mobility management network element of the first network determines the target mobility management network element of the second network according to the identifier of the terminal device, and includes: the mobility management network element of the first network to the The first mobile management network element of the second network sends a request message, requesting to switch the terminal device to the second network, where the request message carries the identifier of the terminal device, and the first mobile management network that receives the second network The information of the second mobility management network element of the second network returned by the element.
- the present application provides another method for handover, including: a first mobility management network element of a second network receives a request message sent by a mobility management network element of a first network, where the request message carries a terminal device Identifying, according to the identifier of the terminal device, the usage type of the terminal device from the subscription data; the target core network identifier of the second network determined according to the usage type of the terminal device; returning the second to the AMF Determining the target network management network element of the second network according to the target core network identifier of the second network, and returning the target mobility management network element information of the second network to the AMF; or, according to The target core network identifier of the second network determines the target mobility management network element of the second network, and sends the request message to the target mobility management network element of the second network.
- the target mobility management network element information of the second network in the foregoing aspect includes: an identifier of the target mobility management network element, or an access address of the target mobility management network element.
- the first network is a 5G network
- the mobility management network element of the first network is an AMF
- the second network is a 4G network.
- an embodiment of the present invention provides a mobility management network element, where the base station has a mobility management network element in an example of the handover method implemented in the first aspect.
- the functions may be implemented by hardware or by corresponding software implemented by hardware.
- the hardware or software includes one or more units or modules corresponding to the functions described above.
- the structure of the mobility management network element may include a transceiver unit and a processing unit.
- the processing module is configured to support the mobility management network element to perform a corresponding function in the communication method of the first aspect.
- the transceiver unit is configured to support communication between the mobility management network element and other devices.
- the mobility management network element may further include a storage unit for coupling with the processing unit, which stores program instructions and data necessary for the mobility management network element.
- the processing unit may be a processor
- the transmitting unit may be a communication interface
- the storage unit may be a memory.
- an embodiment of the present invention provides a mobility management network element, where the base station has a mobility management network element in an example of the handover method implemented in the second aspect.
- the functions may be implemented by hardware or by corresponding software implemented by hardware.
- the hardware or software includes one or more units or modules corresponding to the functions described above.
- the structure of the mobility management network element may include a transceiver unit and a processing unit.
- the processing module is configured to support the mobility management network element to perform a corresponding function in the communication method of the second aspect.
- the transceiver unit is configured to support communication between the mobility management network element and other devices.
- the mobility management network element may further include a storage unit for coupling with the processing unit, which stores program instructions and data necessary for the mobility management network element.
- the processing unit may be a processor
- the transmitting unit may be a communication interface
- the storage unit may be a memory.
- an embodiment of the present invention provides a communication system, where the system includes the mobility management network element in any of the foregoing aspects.
- the system may further include other devices in the solution provided by the embodiment of the present invention that interact with the mobility management network element, such as an HSS, a UDM.
- the mobility management network element such as an HSS, a UDM.
- the present application further provides a computer readable storage medium having stored therein instructions that, when executed on a computer, cause the computer to perform the method of any of the above aspects.
- the computer may for example be a mobility management network element.
- the application provides a computer program product.
- the computer program product comprises computer software instructions executable by a processor to implement the flow in the switching method of any of the above aspects.
- the present application provides an apparatus comprising a processor for a source base station to implement the functions involved in the above aspects, for example, to generate or process data and/or information involved in the above method.
- the apparatus also includes a memory for storing the necessary program instructions and data.
- the device can be a chip system.
- the chip system can be composed of chips, and can also include chips and other discrete devices.
- the present application describes a handover method, a mobility management network element, and a communication system, which are designed to select a suitable target mobility management network element to provide services for the terminal device, thereby avoiding service interruption of the terminal device.
- FIG. 1 is a schematic diagram of a possible network architecture of the present application
- FIG. 2 is a schematic flowchart of a communication method according to an embodiment of the present application.
- FIG. 3 is a signaling interaction diagram of an embodiment of the present application.
- FIG. 5 is a signaling interaction diagram of handover according to still another embodiment of the present application.
- FIG. 6 is a signaling interaction diagram of handover according to still another embodiment of the present application.
- FIG. 7 is a schematic structural diagram of a network device involved in the embodiment of the present application.
- FIG. 8 is a schematic diagram of another possible structure of a network device involved in the embodiment of the present application.
- FIG. 1 is a schematic diagram of a possible network architecture of an embodiment of the present application.
- the terminal device may be referred to as a user equipment (UE), a mobile station (MS), a mobile terminal (mobile terminal), or a terminal device in a future 5G network, and the terminal device may be wirelessly accessed.
- a radio access network (RAN) communicates with one or more core networks (such as network slices) and can also communicate with another terminal device, such as Device to Device (D2D) or machine to machine (Machine). To Machine, M2M) Communication under the scene.
- D2D Device to Device
- Machine machine to machine
- the terminal device may be a mobile phone (or "cellular" phone) or a computer with a mobile terminal device, etc., for example, the terminal device may also be various handheld devices with wireless communication functions, in-vehicle devices, wearable devices, A computing device, control device, or other processing device connected to a wireless modem.
- the above-mentioned devices are collectively referred to as terminal devices.
- the 4G core network EPC includes a Mobility Management Entity (MME), a Serving Gateway (SGW), a Data Network (PDN Gateway, PGW), and a home subscriber server (HSS).
- MME Mobility Management Entity
- SGW Serving Gateway
- PGW Data Network Gateway
- HSS home subscriber server
- the MME is a control node in the LTE access network and is connected to the 4G RAN through the S1-MME path.
- the MME is responsible for tracking and paging control of the terminal devices in idle mode.
- the SGW is responsible for the routing and forwarding of data packets of the terminal equipment, and is also responsible for the exchange of user plane data when the terminal equipment moves between 4G RANs or between 4G RANs and other 3GPP technologies.
- the PGW is connected to the SGW through the s5 path to implement interface transmission between the terminal device and the external service PDN connection point.
- a terminal device can access multiple service PDNs through multiple PGWs at the same time.
- the function of the HSS (not shown) is a central database containing subscription information related to the terminal device and information related to the subscription.
- the HSS features include: mobility management, support for call and session establishment, user authentication and access authorization.
- 5G core network New Core includes Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Unified Data Management (Unified) Data Management, UDM) Network devices such as network elements.
- the AMF is responsible for the registration process when the terminal device is accessed and the location management during the movement of the terminal device.
- SMF Session Management Function
- UPF User Plane Function
- UDM Unified Data Management
- the AMF is responsible for the registration process when the terminal device is accessed and the location management during the movement of the terminal device.
- the SMF is responsible for the terminal device to initiate the service
- the network side establishes a corresponding session connection, and provides a specific service for the terminal device, in particular, the data packet forwarding policy and the QoS policy are sent to the UPF based on the N4 interface between the SMF and the UPF.
- the UPF is mainly responsible for packet data packet forwarding, quality of service (QoS) control, and accounting information statistics.
- the UDM is
- the 5G RAN when a handover between a 5G system and a 4G system occurs, the 5G RAN notifies the AMF that a handover needs to occur due to the movement of the terminal device. If the AMF confirms that the area needs to be switched to the 4G system, the AMF selects an MME, sends a handover request to the MME, and sends the context of the terminal device to the selected MME in the handover request, and the MME completes the subsequent handover procedure. For example, a 4G system context of a terminal device and a 4G bearer are established. However, how the AMF determines the MME is not described in detail in the prior art.
- the carrier network deploys a 5G core network in the area A, which includes two network slices, which are a slice 1 of a service vehicle type terminal device and a slice 2 of a service machine type terminal device.
- the network slice contains network functions such as AMF, SMF and UPF.
- the operator also deployed only the 4G core network in Area B, including two DCNs, DCN 1 serving the vehicle-type terminal equipment and DCN 2 serving the mobile broadband terminal equipment.
- the DCN includes network elements such as MME, SGW, and PGW.
- There is currently a terminal device of the vehicle type that provides service to the slice 1 in the area A access 5G system.
- the terminal device When the terminal device moves from the area A to the area B, it is necessary to switch the terminal device from the 5G system to the 4G system. Since the 4G system deploys two DCNs, DCN 1 can serve vehicle-type terminal equipment, while DCN 2 cannot. Therefore, in order to ensure the continuity of the service of the terminal device at the time of handover, the terminal device should be switched from Slice 1 to DCN 1. However, according to the prior art, the AMF in Slice 1 may incorrectly select the MME in DCN 2, causing DCN 2 to fail to serve the terminal device.
- FIG. 2 is a schematic flowchart diagram of a communication method according to an embodiment of the present application.
- Step S201 The access network of the first network sends a first handover request to the mobility management network element of the first network.
- the first network may be a 5G network
- the second network may be a 4G network.
- the mobility management network element of the first network is an AMF
- the mobility management network element of the second network is an MME.
- the first handover request carries an interface identifier or an identifier of the terminal device.
- the interface identifier may be a channel identifier between the access network and the mobility management network element, such as an interface identifier (S1-ID, N2-ID).
- the identifier of the terminal device is an identifier that can identify or identify the terminal device in the network, and may be a permanent identifier of the terminal device, such as a Permanent Permanent Identifier (SUPI), or a temporary identifier of the terminal device, for example, 5G- GUTI.
- SUPI Permanent Permanent Identifier
- 5G- GUTI 5G- GUTI
- the first handover request may further carry a mobility management network element indicating that the first network is notified, the terminal device needs to be handed over to the second network, or carries an identifier of the target area (eg, a target access network node identifier) .
- a mobility management network element indicating that the first network is notified, the terminal device needs to be handed over to the second network, or carries an identifier of the target area (eg, a target access network node identifier) .
- the first handover request may further carry location information of the terminal device.
- the first handover request may further carry a target PLMN ID.
- Step S202 the mobility management network element of the first network learns that the terminal device needs to switch to the second network
- the first handover request may directly indicate that the terminal device needs to switch to the second network, or the mobility management network element of the first network may learn that the terminal device needs to switch to the second network according to the identifier of the first handover request carrying the target area.
- Step S203 The mobility management network element of the first network acquires the identifier of the terminal device according to the first handover request.
- the mobility management network element determines the identifier of the terminal device according to the correspondence between the interface identifier and the terminal device identifier.
- the mobility management network element directly obtains the identifier of the terminal device.
- Step S204 the mobility management network element of the first network determines a target mobility management network element of the second network according to the identifier of the terminal device;
- the mobility management network element of the first network acquires the usage type of the terminal device from the subscription database according to the identifier of the terminal device; the mobility management network element of the first network is used according to the usage type of the terminal device Determining a target mobility management network element of the second network.
- the mobility management network element of the first network may send a query request to a domain name server (DNS) or a network repository function (NRF), and carry the type of use of the terminal device;
- DNS domain name server
- NRF network repository function
- the usage type of the terminal device is a type defined by the terminal device according to the service type and/or the terminal device capability of the terminal device in the 4G network, and may be, for example, the terminal device Usage Type.
- the contract type data using the type as the user is saved in the contract database.
- the mobility management network element of the first network acquires the target core network identifier of the second network of the terminal device according to the identifier of the terminal device, and determines the target mobility management of the second network according to the target core network identifier of the second network.
- Network element For example, the mobility management network element of the first network obtains the target of the second network corresponding to the target core network identifier of the second network by querying the DNS server or the Network Repository Function (NRF) according to the target core network identifier of the second network.
- Mobile management network element information may be an identifier of the mobility management network element, an access address of the mobility management network element, and the like.
- the core network identifier is used to identify the core network.
- the DCN-ID may be used for identification.
- the common core network and the dedicated core network will be assigned different DCN-IDs to distinguish.
- the acquiring process of acquiring the target core network identifier of the second network of the terminal device according to the identifier of the terminal device may be implemented by any one of the following three manners:
- the mobility management network element of the first network acquires the slice information of the terminal device from the context of the terminal device according to the identifier of the terminal device, and obtains the correspondence between the core network identifier and the slice information of the second network, according to the slice information of the terminal device. And the corresponding relationship, determining a target core network identifier of the second network.
- the slice information is used to identify a network slice that is accessed or subscribed by the terminal device, for example, a type of a slice or an identifier of a slice, which may be a subscription.
- the mobility management network element of the first network may obtain the slice information of the terminal device in the registration process of the terminal device, and save the information in the context of the terminal device, and the specific process is not described herein.
- the mobility management network element of the first network may use the slice information with the highest priority among the slice information of the terminal device. And the corresponding relationship, determining a target core network identifier of the second network.
- the step may obtain the slice information of the terminal device from the context of the terminal device according to the identifier of the terminal device, and the step of obtaining the correspondence between the core network identifier and the slice information of the second network may be performed without a sequence, or may be performed simultaneously. .
- the mobility management network element of the first network obtains the correspondence between the core network identifier and the slice information of the second network, and may be implemented in the following manner: the mobility management network element of the first network acquires the core network identifier of the second network from the PCF. Correspondence with slice information. For example, the mobility management network element of the first network sends a request message to the PCF, and the PCF returns a response message to the mobility management network element of the first network, where the response message includes a correspondence table between the core network identifier and the slice information.
- the mobility management network element of the first network may be sliced according to the terminal device.
- the information, the location information of the terminal device, and the corresponding relationship determine the target core network identifier of the second network.
- the correspondence table between the core network identifier and the slice information may include, but is not limited to, a correspondence table between the core network identifier of the second network and the slice information of the first network, for example, a core network identifier and slice information that may include the third network. and many more.
- the mobility management network element of the first network acquires the PLMN ID of the second network (for example, the first handover request of S201 carries the PLMN ID of the second network)
- the mobility management network element of the first network sends the PCF to the PCF.
- the sending request message may carry the PLMN ID of the second network
- the PCF returns a correspondence table between the core network identifier and the slice information of the second network.
- the correspondence table can be specifically referred to Table 2:
- the mobility management network element of the first network obtains the target core network identifier of the second network from the context of the terminal device according to the terminal device identifier.
- the home network HPLMN of the terminal device is pre-configured with a core network identifier (including but not limited to the core network identifier of the second network) that the terminal device can access, and is stored in the terminal device device or the SIM card.
- a core network identifier including but not limited to the core network identifier of the second network
- the pre-configured core network identifier that can be accessed is sent to the mobility management network element of the first network (for example, by using a registration request message), the mobility management network element of the first network.
- the core network identifier that the terminal device can access is saved in the context of the terminal device.
- the mobility management network element of the first network may obtain the target core network identifier of the second network from the context of the saved terminal device according to the identifier of the terminal device.
- the third type the mobility management network element of the first network sends the terminal device identifier to the first mobility management network element of the second network, and the first mobility management network element that receives the second network returns according to the terminal device identifier.
- the target core network identifier of the second network is the target core network identifier of the second network.
- the first mobility management network element of the second network may be a special default mobility management network element of the second network, or may be a mobility management of a second network arbitrarily selected by the mobility management network element of the first network. Network element.
- the mobility management network element of the first network sends a request message (for example, a second handover request or a query request) to the first mobility management network element of the second network, where the request message includes the identifier of the terminal device;
- the first mobility management network element acquires the usage type of the terminal device from the subscription data according to the identifier of the terminal device.
- the first mobility management network element sends a subscription data query request to the HSS, where the terminal device is included.
- the identifier, the HSS returns the subscription data information of the corresponding terminal device to the first mobility management network element, and the subscription data includes the usage type of the terminal device.
- the first mobility management network element acquires the target of the second network of the terminal device according to the usage type.
- the core network identifier (refer to the description in the prior art); the first mobility management network element returns the target core network identifier of the second network to the mobility management network element of the first network.
- Manner 3 The mobility management network element of the first network sends a request message (for example, a second handover request or a query request) to the first mobility management network element of the second network, requesting to switch the terminal device to the location
- a request message for example, a second handover request or a query request
- the second network where the request message carries the identifier of the terminal device, and receives the information of the second mobility management network element of the second network returned by the first mobility management network element of the second network.
- the first mobility management network element of the second network receives the request message sent by the mobility management network element of the first network, where the request message carries the identifier of the terminal device; and the first mobility management network element of the second network according to the The identifier of the terminal device acquires the usage type of the terminal device from the subscription data; the target network identifier of the second network determined by the first mobility management network element of the second network according to the usage type of the terminal device, according to the second The target core network identifier of the network determines the target mobility management network element of the second network, returns information of the target mobility management network element of the second network to the mobility management network element of the first network, or may also send the request message to The target mobile management network element of the second network.
- the manner in which the first mobility management network element returns the information of the target mobility management network element of the second network to the mobility management network element of the first network further includes: if the first mobility management network element can support the target of the second network The core network, the first mobility management network element performs subsequent handover steps. If the first mobility management network element cannot support the target core network of the second network, the first mobility management network element further determines a mobility management network element of the second network corresponding to the target core network identifier of the second network as the target mobile Manage network elements.
- the correspondence between the mobility management network element of the second network and the core network identifier of the second network is configured on the Default MME.
- Step S205 The mobility management network element of the first network sends a second handover request to the target mobility management network element of the second network, requesting to switch the terminal device to the second network.
- the mobility management network element of the first network acquires a session context (SM Context) of the terminal device from the SMF, and obtains a mobility management context of the terminal device according to the saved terminal device context of the mobility management network element of the first network.
- SM Context session context
- MM Context mobility management network element of the first network sends a second handover request to the target mobility management network element of the second network, where the second handover request carries the SM Context and the MM Context element of the terminal device.
- Step S206 the target mobility management network element of the second network completes the subsequent handover step, for example, establishing a context and a bearer for the terminal device in the second network.
- the mobility management network element of the second network can be found for the terminal device to serve the terminal device, so that the service interruption of the terminal device can be avoided.
- FIG. 1 Based on the network architecture of FIG. 1, FIG. 3, FIG. 4, FIG. 5, and FIG. 6 will describe the method described in FIG. 2 in detail in conjunction with the specific embodiments of the present application.
- FIG. 3 is a signaling interaction diagram of an embodiment of the present application, where the first network takes 5G as an example, and the second network takes 4G as an example.
- the mobility management network element of the first network takes AMF as an example, and the second network moves.
- the management network element is described by taking the MME as an example. It can be understood that the AMF can be replaced with the mobility management network element of the first network, and the target MME can be replaced with the target mobility management network element of the second network, including:
- 301-303 can refer to steps 201-203,
- the AMF requests a network policy from the PCF, and obtains a correspondence table between the slice information and the DCN.
- the PLMN ID is included in the network request.
- the effect of including the PLMN ID is that the PCF determines the correspondence table corresponding to the PLMN according to the PLMN of the target network to which the terminal device moves.
- the PCF returns a response message to the AMF, which includes a correspondence table between the slice information slice and the DCN.
- the PCF returns a correspondence table between the slice information and the DCN corresponding to the PLMN ID.
- the AMF determines the DCN ID according to the slice information of the terminal device saved by itself, (for example, Requested NSSAI/Allowed NSSAI), and the correspondence table between the slice information slice and the DCN.
- the AMF also determines the DCN ID based on the target location of the terminal device.
- the AMF queries the DNS server or the Network Repository Function (NRF) according to the DCN-ID to obtain the information of the target MME corresponding to the DCN ID.
- NRF Network Repository Function
- the information of the target MME may be, for example, an identifier of the MME, an access address of the MME, and the like.
- the AMF sends a handover request, such as a Relocation Request, to the target MME.
- the request NSSAI/Allowed NSSAI may have multiple. In this case, the priority needs to be defined for the slice.
- the AMF first selects the slice information with the highest priority, that is, the Request NSSAI/Allowed NSSAI with the highest priority.
- the AMF determines the DCN-ID corresponding thereto according to the correspondence table.
- the first network uses 5G as an example, and the second network uses 4G as an example.
- the mobility management network element of the first network uses AMF as an example, and second.
- the first mobile management network element of the network takes the default MME as an example, and the target mobile management network element of the second network uses the target MME as an example.
- the AMF can be replaced with the mobile management network element of the first network, the default MM.
- the target MME may be replaced with the first mobility management network element of the second network, and the target MME may be replaced with the target mobility management network element of the second network, including:
- 401-403 can refer to steps 201-203,
- the AMF selects a Default MME and forwards the handover request to the Default MME.
- the switching request contains the identity of the terminal device.
- the Default MME may be a special default MME in the 4G network, or may be an MME arbitrarily selected by the AMF, and the MME may not be able to serve the terminal device.
- the MME sends a subscription data query request to the HSS, which includes the identifier of the terminal device.
- the HSS returns the subscription data information of the corresponding terminal device to the Default MME, where the subscription data includes the Usage Type of the terminal device.
- the MME determines the DCN-ID (prior art) based on the Usage Type of the terminal device. If the Default MME can support the DCN-ID, the Default MME receives the handover request message sent by the AMF and performs a subsequent handover procedure. If the Default MME cannot support the DCN-ID, the Default MME determines a corresponding MME network element according to the DCN-ID. The mapping between the MME network element and the DCN-ID is configured on the Default MME.
- the MME sends a redirect message to the AMF, including the information of the MME network element determined in step 4, such as the MME ID or the access address of the MME.
- the method further includes a cause value, and the AMF is required to resend the handover request to the MME network element specified in the redirect message. 408b.
- the AMF resends the handover request to the designated MME network element.
- it also carries the context.
- the MME directly sends the handover request received from the AMF to the MME network element determined in step 407.
- the first network uses 5G as an example
- the second network uses 4G as an example.
- the mobility management network element of the first network uses AMF as an example, and second.
- the target mobility management network element of the network is described by taking the target MME as an example. It can be understood that the AMF can be replaced with the mobility management network element of the first network, and the target MME can be replaced with the target mobility management network element of the second network, including:
- the terminal device side is configured with the DCN-ID by the HPLMN, and is saved in the terminal device device or the SIM card.
- the pre-configured DCN-ID is included in a registration request, such as a Registration Request, and sent to the AMF.
- AMF saves the DCN-ID.
- the AMF queries the DNS server or the NRF according to the saved DCN-ID to obtain the information of the target MME, such as the identifier of the MME, the access address of the MME, and the like.
- the AMF sends the handover request directly to the target MME.
- the first network uses 5G as an example
- the second network uses 4G as an example.
- the mobility management network element of the first network uses AMF as an example.
- the target mobility management network element of the second network is described by taking the target MME as an example. It can be understood that the AMF can be replaced with the mobility management network element of the first network, and the target mobility management network element that can be replaced by the target MME as the second network includes:
- the AMF obtains the terminal device Usage Type. Specifically, the AMF may query the subscription database, such as an HSS or a UDM, according to the terminal device identification request. The subscription database returns the subscription data of the terminal device, including the Usage Type of the terminal device.
- the subscription database such as an HSS or a UDM
- the AMF selects the target MME according to the terminal device Usage Type. Specifically, the AMF sends a query request to the DNS or the NRF, including the terminal device Usage Type, and the DNS or the NRF returns the identifier or the access address of the MME according to the terminal device Usage Type.
- the AMF sends a handover request to the target MME.
- the embodiment of the present application may perform the function module division on the mobility management network element of the first network and the first mobility management network element of the second network according to the foregoing method examples of FIG. 2 to FIG. 6, for example, corresponding functions may be performed.
- Dividing individual function modules can also integrate two or more functions into one processing module.
- the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.
- FIG. 7 is a schematic structural diagram of a network device involved in the embodiment of the present application, for example, a mobility management network element of a first network, and a first network of the second network.
- the mobility management network element is configured to implement the functions of the mobility management network element of the first network in the method embodiment of FIG. 2 to FIG.
- the mobility management network element of the first network may include: a communication unit 701, and a processing unit 702.
- the communication unit 701 is configured to support the transmission and reception of information between the mobility management network element of the first network and other network elements in the foregoing embodiment.
- the processing unit 702 performs various processing functions.
- the communication unit 701 is configured to support the mobile management network element of the first network to implement the function of transmitting and receiving information in steps 201, 205, 304, 305, 308, 401, 408a, 408b, 502, 503 or 504 in FIG. 2 to FIG. 6;
- the mobility management network element supporting the first network implements the steps 202, 203, 204, 306, 307, 407, or 502 in FIG. 2 to FIG. 6, or the functions processed in the related steps, etc.; optionally, the movement of the first network
- the management network element may further include a storage unit 703 for storing program codes and data of the mobility management network element of the first network.
- FIG. 7 is also a schematic structural diagram of a first mobility management network element of the second network involved in the embodiment of the present application, for implementing the first mobility of the second network in the method embodiment of FIG. 2 to FIG. Manage network elements.
- the first mobility management network element of the second network may include: a communication unit 701, and a processing unit 702.
- the communication unit 701 is configured to support the first mobility management network element of the second network and other network elements in the foregoing embodiment. Send and receive information.
- the processing unit 702 performs various processing functions.
- the communication unit 701 is configured to support the first mobility management network element of the second network to perform steps 404, 405, 406, or 408c in FIG. 2 to FIG. 6; the processing unit 702 is configured to support the first of the second network.
- the mobile management network element performs steps 407 and the like in FIG. 2 to FIG. 6; optionally, the first mobility management network element of the second network may further include a storage unit 703, where the storage unit 703 is configured to store the second network. Program code and data of the first mobility management network element.
- the processing unit 702 in FIG. 7 can be a processor or a controller, such as a central processing unit (CPU), a general-purpose processor, and a digital signal processor (DSP).
- DSP digital signal processor
- ASIC Application-Specific Integrated Circuit
- FPGA Field Programmable Gate Array
- the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
- the communication unit 701 can be a transceiving interface.
- the storage unit 703 can be a memory.
- the processing unit 702 is a processor
- the receiving unit 701 and the sending unit 703 may be a transceiver as a transceiver
- the storage unit is a memory
- the NF warehouse management function component involved in the embodiment of the present application the first mobility management of the second network
- the network element can be the network device shown in FIG.
- the network device may include a transceiver interface 801, a processor 802, a memory 803, and a bus 804.
- the transceiver interface 801, the processor 802, and the memory 803 are connected to each other through a bus 804.
- the bus 804 may be a PCI bus or an EISA bus.
- the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 8, but it does not mean that there is only one bus or one type of bus.
- the functions described herein can be implemented in hardware, software, firmware, or any combination thereof.
- the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
- Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
- a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请涉及无线通信技术领域,尤其涉及一种切换的方法,包括:第一网络的移动管理网元接收接入网发送的第一切换请求,获知终端设备需要切换到第二网络;根据第一切换请求获取所述终端设备的标识;所述第一网络的移动管理网元根据所述终端设备的标识确定第二网络的目标移动管理网元;所述第一网络的移动管理网元向所述第二网络的目标移动管理网元发送第二切换请求,请求将所述终端设备切换到所述第二网络。
Description
本申请要求在2017年10月17日提交中国国家知识产权局、申请号为201710977957.5、发明名称为“一种切换的方法、移动性管理网元和通信系统”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及无线通信技术领域,尤其涉及无线通信系统中的切换的方法、移动性管理网元和通信系统。
在4G系统中,运营商为不同的类型的终端设备(例如,移动宽带类通信,Mobile Broadband Communication,机器类通信Machine Type Communication,车辆类通信Vehicle type communication,公共安全通信Public Safety Communication等)部署不同的核心网,可以称之为专用核心网(Dedicated Core Network,缩写:DCN)。专用核心网可以服务于特定类型的终端设备,例如机器类通信终端设备由某个支持机器类通信的专用核心网服务;也可以服务于通用类型的终端设备,例如通用终端设备由某个支持通用业务的缺省专用核心网服务。不同的专用核心网中包括支持不同终端设备类型或业务类型的核心网设备,如移动管理实体(mobility management entity,MME),服务网关(serving gateway,SGW),数据网关(PDN Gateway,PGW)等。DCN有助于运营商对具有不同使用类型的终端设备进行有针对性的管理与维护,专网专用,从而提升对终端设备接入移动管理与会话管理的效率,降低网络的维护成本。
在5G系统中,网络可以通过切片技术在核心网的同一套物理设备切分出多个逻辑的核心网网络切片实例,每个核心网网络切片实例可以根据具体的商业场景或用户需求做定制化,在满足多样性业务的同时可以保证网络切片实例之间的相互隔离。网络切片中包含接入和移动管理功能(Access and Mobility Management Function,AMF),会话管理功能(英session management Function,SMF),用户面功能(User plane function,UPF)等。运营商可以通过对速率、容量、覆盖率、延迟、可靠性、安全性和可用性等网络性能指标进行自由灵活组合,提供定制化的网络功能,从而满足各个使用场景的具体要求。
在实际使用场景中,终端设备的移动可能会导致系统间的切换,即终端设备从5G系统覆盖范围内移动到4G系统的覆盖范围。其中,4G系统与5G系统之间的互操作是系统间业务连续性的重要保证。由于上述专用核心网和网络切片的引入,终端设备在从5G网络切换到4G网络时,需要保证终端设备能够被正确的DCN来服务。例如车辆类通信终端设备,终端设备在5G系统中由支持车辆类通信业务的核心网网络切片提供服务。当终端设备从5G移动到4G时,5G网络需要为终端设备选择4G中能够支持车辆类通信业务的DCN。由于4G系统中可能存在多个支持不同业务的DCN,如果5G网络为终端设备选择了错误的DCN,例如通用,可能会导致所选的DCN无法为该终端设备服务,从而导致 终端设备的业务中断。
发明内容
本文描述了一种切换的方法、移动性管理网元和通信系统,以实现在切换时,为终端设备选择合适的移动管理网元的问题。
第一方面,本发明实施例提供了一种切换方法,包括:第一网络的移动管理网元接收第一网络的接入网发送的第一切换请求,获知终端设备需要切换到第二网络;所述第一网络的移动管理网元根据所述第一切换请求获取所述终端设备的标识;所述第一网络的移动管理网元根据所述终端设备的标识确定第二网络的目标移动管理网元;所述第一网络的移动管理网元向所述第二网络的目标移动管理网元发送第二切换请求,请求将所述终端设备切换到所述第二网络。
在一个可能的设计中,所述第一网络的移动管理网元根据所述终端设备的标识确定第二网络的目标移动管理网元,包括:所述第一网络的移动管理网元根据所述终端设备的标识从签约数据库获取所述终端设备的使用类型;所述第一网络的移动管理网元根据所述终端设备的使用类型确定所述第二网络的目标移动管理网元。
在一个可能的设计中,所述第一网络的移动管理网元根据所述终端设备的使用类型确定第二网络的目标移动管理网元,包括:所述第一网络的移动管理网元向DNS或NRF发送查询请求,携带所述终端设备的使用类型;接收所述DNS或NRF返回的所述第二网络的目标移动管理网元信息。
在一个可能的设计中,所述第一网络的移动管理网元根据所述终端设备的标识确定第二网络的目标移动管理网元,还包括:所述第一网络的移动管理网元根据所述终端设备的标识获取第二网络的目标核心网标识;所述第一网络的移动管理网元根据所述第二网络的目标核心网标识确定第二网络的目标移动管理网元。
在一个可能的设计中,所述第一网络的移动管理网元根据所述终端设备的标识获取第二网络的目标核心网标识包括:所述第一网络的移动管理网元根据所述终端设备的标识从所述终端设备的上下文中获取所述终端设备的切片信息,获取第二网络的核心网标识与切片信息的对应关系,根据所述终端设备的切片信息以及所述对应关系,确定第二网络的目标核心网标识。
在一个可能的设计中,获取第二网络的核心网标识与切片信息的对应关系包括:第一网络的移动管理网元向策略控制功能PCF发送请求消息,第一网络的移动管理网元接收所述PCF返回第二网络的核心网标识与切片信息的对应关系表。
在一个可能的设计中,如果第一切换请求中还携带终端设备的位置信息,核心网标识与切片信息的对应关系表中也还包括位置信息,则第一网络的移动管理网元可以根据终端设备的切片信息,终端设备的位置信息,和所述对应关系确定第二网络的目标核心网标识。
在一个可能的设计中,如果所述终端设备的切片信息为多个,且所述终端设备的多个切片信息配置有优先级信息,则根据所述终端设备的切片信息,以及所述对应关系,确定第二网络的目标核心网标识的步骤包括:根据所述终端设备的切片信息中优先级最高的切片信息,以及所述对应关系,确定所述第二网络的目标核心网标识。
在一个可能的设计中,第一网络的移动管理网元根据所述终端设备标识获取第二网络 的目标核心网标识,包括:所述第一网络的移动管理网元将所述终端设备标识发送给第二网络的第一移动管理网元,接收所述第二网络的第一移动管理网元根据终端设备标识返回的第二网络的目标核心网标识。
在一个可能的设计中,所述第一网络的移动管理网元根据所述终端设备标识获取目标核心网标识,包括:根据所述终端设备标识查询终端设备的上下文获得第二网络的目标核心网标识。
在一个可能的设计中,所述方法还包括:所述第一网络的移动管理网元接收所述终端设备的注册请求,所述注册请求中包含所述终端设备的第二网络的核心网标识;所述第一网络的移动管理网元保存所述第二网络的核心网标识,所述第二网络的核心网标识保存在所述终端设备的上下文中。
在一个可能的设计中,所述第一网络的移动管理网元根据所述第二网络的目标核心网标识确定第二网络的目标移动管理网元包括:所述第一网络的移动管理网元向DNS或者NRF发送查询请求,携带所述第二网络的目标核心网标识;接收所述DNS或者NRF返回的所述第二网络的目标移动管理网元信息。
在一个可能的设计中,所述第一网络的移动管理网元根据所述终端设备的标识确定第二网络的目标移动管理网元包括:所述第一网络的移动管理网元向所述第二网络的第一移动管理网元发送请求消息,请求将所述终端设备切换到所述第二网络,所述请求消息中携带终端设备的标识;接收所述第二网络的第一移动管理网元返回的第二网络的第二移动管理网元的信息。
第二方面,本申请提供了另一种切换的方法,包括:第二网络的第一移动管理网元接收第一网络的移动管理网元发送的请求消息,所述请求消息中携带终端设备的标识;根据所述终端设备的标识从签约数据中获取所述终端设备的使用类型;根据所述终端设备的使用类型确定的第二网络的目标核心网标识;向所述AMF返回所述第二网络的目标核心网标识,或者,根据第二网络的目标核心网标识确定第二网络的目标移动管理网元,向所述AMF返回所述第二网络的目标移动管理网元信息;或者,根据第二网络的目标核心网标识确定第二网络的目标移动管理网元,将所述请求消息发送给所述第二网络的目标移动管理网元。
在一个可能的设计中,上述方面的第二网络的目标移动管理网元信息包括:目标移动管理网元的标识,或者目标移动管理网元的访问地址。
在一个可能的设计中,其特征在于,第一网络为5G网络,第一网络的移动管理网元为AMF,第二网络为4G网络。
第三方面,本发明实施例提供一种移动性管理网元,该基站具有实现第一方面所述的切换方法示例中移动性管理网元。所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一个可能的设计中,移动性管理网元的结构中可包括收发单元、处理单元所述处理模块被配置为支持移动性管理网元执行第一方面所述通信方法中相应的功能。所述收发单元用于支持移动性管理网元与其他设备之间的通信。所述移动性管理网元还可以包括存储单元,所述存储单元用于与处理单元耦合,其保存移动性管理网元必要的程序指令和数据。作为示例,处理单元可以为处理器,接发单元可以为通信接口,存储单元可以为存储器。
第四方面,本发明实施例提供一种移动性管理网元,该基站具有实现第二方面所述的切换方法示例中移动性管理网元。所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一个可能的设计中,移动性管理网元的结构中可包括收发单元、处理单元所述处理模块被配置为支持移动性管理网元执行第二方面所述通信方法中相应的功能。所述收发单元用于支持移动性管理网元与其他设备之间的通信。所述移动性管理网元还可以包括存储单元,所述存储单元用于与处理单元耦合,其保存移动性管理网元必要的程序指令和数据。作为示例,处理单元可以为处理器,接发单元可以为通信接口,存储单元可以为存储器。
第五方面,本发明实施例提供了一种通信系统,该系统包括上述任一方面所述的移动性管理网元。
在一个可能的设计中,该系统还可以包括本发明实施例提供的方案中与该移动性管理网元进行交互的其他设备,例如HSS,UDM。
第六方面,本申请还提供一种计算机可读存储介质,所述计算机可读存储介质中存储有指令,当其在计算机上运行时,使得计算机执行上述任一方面所述的方法。所述计算机例如可以是移动性管理网元。
第七方面,本申请提供了一种计算机程序产品。该计算机程序产品包括计算机软件指令,该计算机软件指令可通过处理器进行加载来实现上述任一方面中任意一项的切换方法中的流程。
第八方面,本申请提供一种装置,该装置包括处理器,用于源基站实现上述方面中所涉及的功能,例如,生成或处理上述方法中所涉及的数据和/或信息。
在一个可能的设计中,所述装置还包括存储器,所述存储器,用于保存必要的程序指令和数据。
在一个可能的设计中,该装置可以是芯片系统。
在一个可能的设计中,该芯片系统,可以由芯片构成,也可以包括芯片和其他分立器件。
相较于现有技术,本申请描述了一种切换方法、移动性管理网元和通信系统,旨在选择合适的目标移动性管理网元为终端设备提供服务,从而避免终端设备的业务中断。
下面将参照所示附图对本申请实施例进行更详细的描述。
图1为本申请的一种可能的网络架构示意图;
图2为本申请一个实施例的通信方法的流程示意图;
图3为本申请一个实施例的信令交互图;
图4为本申请另一个实施例的切换的信令交互图;
图5为本申请又一个实施例的切换的信令交互图;
图6为本申请又一个实施例的切换的信令交互图;
图7为本申请实施例中所涉及的网络设备的一种可能的结构示意图;
图8为本申请实施例中所涉及的网络设备的另一种可能的结构示意图。
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚地描述。
图1所示为本申请实施例一种可能的网络架构图。
终端设备,可以称之为用户设备(user equipment,UE)、移动台(mobile station,MS)、移动终端设备(mobile terminal)或未来5G网络中的终端设备等,该终端设备可以经无线接入网(radio access network,RAN)与一个或多个核心网(例如网络切片)进行通信,也可以与另一终端设备进行通信,如设备对设备(Device to Device,D2D)或机器对机器(Machine to Machine,M2M)场景下的通信。例如,终端设备可以是移动电话(或称为“蜂窝”电话)或具有移动终端设备的计算机等,例如,终端设备还可以是各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备、控制设备或连接到无线调制解调器的其它处理设备。为方便描述,本申请中,上面提到的设备统称为终端设备。4G核心网EPC包括移动管理网元(Mobility Management Entity,MME),服务网关(Serving Gateway,SGW),数据网络(PDN Gateway,PGW),归属用户服务器(home subscriber server,HSS)等网络设备。MME是LTE接入网络中的控制节点,通过S1-MME路径与4G RAN相连。MME负责对空闲模式下的终端设备进行跟踪和寻呼控制。SGW负责终端设备的数据包的路由和转发,同时也负责终端设备在4G RAN之间或4G RAN与其他3GPP技术之间移动时的用户面数据的交换。PGW通过s5路径与SGW相连,实现终端设备与外部的业务PDN连接点的接口传输。一个终端设备可以同时通过多个PGW访问多个业务PDN。HSS(图未示)的功能为一个中央数据库,包含与终端设备相关的签约信息以及与订阅相关的信息。HSS的功能包括:移动性管理,呼叫和会话建立的支持,用户认证和访问授权。
5G核心网New Core包括接入和移动性管理功能(Access and Mobility Management Function,AMF),会话管理功能(Session Management Function,SMF),用户面功能(User Plane Function,UPF),统一数据管理(Unified Data Management,UDM)网元等网络设备。AMF负责终端设备接入时的注册流程及终端设备移动过程中的位置管理。SMF负责终端设备发起业务时网络侧建立相应的会话连接,为终端设备提供具体服务,尤其是基于SMF与UPF之间的N4接口向UPF下发数据包转发策略、QoS策略等。UPF主要负责分组数据包的转发、服务质量(Quality of Service,QoS)控制、计费信息统计等。UDM是一个数据库,保存与终端设备相关的签约信息。PCF是网络中的策略控制功能,保存网络的本地策略或漫游策略等。
现有技术中,当发生5G系统与4G系统的切换时,5G RAN通知AMF由于终端设备的移动需要发生切换。AMF确认需要切换到4G系统的区域,则AMF选择一个MME,向该MME发送切换请求,并将终端设备的上下文包含在切换请求中发送给所选的MME,由该MME完成后续的切换步骤,例如建立终端设备的4G系统上下文以及4G承载等。但现有技术中没有详细描述AMF如何确定MME。
现有技术中存在下述问题:运营商网络在区域A部署了5G核心网,其中包含了两个网络切片,分别是服务车辆类终端设备的Slice 1和服务机器类终端设备的Slice 2。网络切片中包含AMF,SMF和UPF等网络功能。运营商同时在区域B只部署了4G核心网,其中包括了两个DCN,分别是服务车辆类终端设备的DCN 1和服务移动宽带终端设备的 DCN 2。DCN中包含MME,SGW和PGW等网元。当前有一个车辆类的终端设备在区域A接入5G系统中的Slice 1提供服务。当该终端设备从区域A移动到区域B时,需要将终端设备从5G系统切换到4G系统。由于4G系统部署了两个DCN,其中DCN 1能够服务车辆类终端设备,而DCN 2则不能。因此为保证终端设备在切换时的业务连续,应当将终端设备从Slice 1切换到DCN 1。但根据现有技术,Slice 1中的AMF可能会错误的选择DCN 2中的MME,导致DCN 2无法服务该终端设备。
基于图1的网络架构,图2所示为本申请一个实施例的通信方法的流程示意图。
步骤S201,第一网络的接入网向第一网络的移动管理网元发送第一切换请求;
其中,第一网络可以是5G网络,第二网络可以是4G网络,则第一网络的移动管理网元是AMF,第二网络的移动管理网元是MME。
其中,第一切换请求中携带接口标识或者终端设备的标识。
接口标识可以是接入网和移动管理网元之间的信道标识,例如接口标识(S1-ID,N2-ID)。
终端设备的标识是在网络中能够标识或识别终端设备的标识,具体可以是终端设备的永久标识,例如永久签约标识(Subscription Permanent Identifier,SUPI),也可以是终端设备的临时标识,例如5G-GUTI。
可选的,所述第一切换请求中还可以进一步携带指示通知第一网络的移动管理网元该终端设备需要切换到第二网络,或者携带目标区域的标识(例如目标接入网节点标识)。
可选的,所述第一切换请求中还可以携带终端设备的位置信息。
可选的,所述第一切换请求中还可以携带目标PLMN ID。
步骤S202,第一网络的移动管理网元获知终端设备需要切换到第二网络;
具体的,第一切换请求可以直接指示终端设备需要切换到第二网络,或者第一网络的移动管理网元可以根据第一切换请求中携带目标区域的标识获知终端设备需要切换到第二网络。
步骤S203,第一网络的移动管理网元根据第一切换请求获取所述终端设备的标识;
如果第一切换请求中携带的是接口标识,则移动管理网元根据接口标识和终端设备标识的对应关系确定终端设备的标识。
如果第一切换请求中携带的是终端设备的标识,则移动管理网元直接获取终端设备的标识。
步骤S204,所述第一网络的移动管理网元根据所述终端设备的标识确定第二网络的目标移动管理网元;
具体的,可以通过以下三种方式中任一实现:
方式一:所述第一网络的移动管理网元根据所述终端设备的标识从签约数据库获取所述终端设备的使用类型;所述第一网络的移动管理网元根据所述终端设备的使用类型确定第二网络的目标移动管理网元。例如,所述第一网络的移动管理网元可以向网域名称服务器(domain name server,DNS)或网络功能库(Network Repository Function,NRF)发送查询请求,携带所述终端设备的使用类型;接收所述DNS或NRF返回的所述第二网络的目标移动管理网元信息。
其中,终端设备的使用类型是4G网络中根据终端设备的业务种类和/或终端设备能力 为终端设备定义的类型,例如可以是终端设备Usage Type。使用类型作为用户的签约数据保存在签约数据库中。
方式二:第一网络的移动管理网元根据所述终端设备的标识获取终端设备的第二网络的目标核心网标识,根据所述第二网络的目标核心网标识确定第二网络的目标移动管理网元。例如:第一网络的移动管理网元根据第二网络的目标核心网标识查询DNS服务器或者网络功能库(Network Repository Function,NRF)获得与第二网络的目标核心网标识对应的第二网络的目标移动管理网元的信息。其中移动管理网元的信息可以是移动管理网元的标识,移动管理网元的访问地址等等。
其中,核心网标识用于标识核心网,具体的,可以采用DCN-ID进行标识。其中,通用的核心网和专用的核心网会分配不同DCN-ID用以区别。
具体的,根据所述终端设备的标识获取终端设备的第二网络的目标核心网标识的获取过程可以通过以下三种方式中的以下任一实现:
第1种,第一网络的移动管理网元根据终端设备标识从终端设备的上下文中获取终端设备的切片信息,获取第二网络的核心网标识与切片信息的对应关系,根据终端设备的切片信息以及该对应关系,确定第二网络的目标核心网标识。
其中,切片信息:标识终端设备接入的或签约的网络切片,例如切片的类型或切片的标识,具体可以是subscribed。第一网络的移动管理网元可以在终端设备的注册过程中获得终端设备的切片信息,并保存在终端设备的上下文中,相关的具体过程不在赘述。可选的,如果所述终端设备的切片信息为多个且切片信息对应有优先级信息,则第一网络的移动管理网元可以根据所述终端设备的切片信息中优先级最高的切片信息,以及所述对应关系,确定所述第二网络的目标核心网标识。
可以理解的是,步骤根据终端设备标识从终端设备的上下文中获取终端设备的切片信息,和步骤获取第二网络的核心网标识与切片信息的对应关系之间可以没有先后顺序,也可以同时执行。
具体的,第一网络的移动管理网元获取第二网络的核心网标识与切片信息的对应关系,可以通过以下方式实现:第一网络的移动管理网元从PCF获取第二网络的核心网标识与切片信息的对应关系。例如,第一网络的移动管理网元向PCF发送请求消息,PCF向第一网络的移动管理网元返回响应消息,响应消息中包含核心网标识与切片信息的对应关系表。
可选的,如果第一切换请求中还携带终端设备的位置信息,核心网标识与切片信息的对应关系表中也还包括位置信息,则第一网络的移动管理网元可以根据终端设备的切片信息,终端设备的位置信息,和所述对应关系确定第二网络的目标核心网标识。
核心网标识与切片信息的对应关系表具体可以参考表1所示:
表1
核心网标识与切片信息的对应关系表,可以包含但不限于第二网络的核心网标识与第一网络的切片信息的对应关系表,例如还有可以包含第三网络的核心网标识与切片信息等等。
可选的,如果第一网络的移动管理网元获取了第二网络的PLMN ID(例如,S201的第一切换请求中携带第二网络的PLMN ID),第一网络的移动管理网元向PCF发送请求消息中可以携带第二网络的PLMN ID,则PCF返回的是第二网络的核心网标识与切片信息的对应关系表。例如从PLMN A的第一网络,切换到PLMN B的第二网络,则对应关系表具体可以参考表2所示:
表2
第2种,第一网络的移动管理网元根据所述终端设备标识从终端设备的上下文获得第二网络的目标核心网标识。
例如:终端设备的归属网络HPLMN为其预配置了终端设备可以接入的核心网标识(包含但不限于第二网络的核心网标识),保存在终端设备设备或者SIM卡中。终端设备在向网络发起注册时,将预配置的可以接入的核心网标识发送给第一网络的移动管理网元(例如,通过注册请求消息registration request message),第一网络的移动管理网元将终端设备可以接入的核心网标识保存在终端设备的上下文中。当终端设备需要切换到第二网络时,第一网络的移动管理网元则可以根据终端设备的标识从保存的终端设备的上下文 中获取第二网络的目标核心网标识。
第3种,第一网络的移动管理网元将所述终端设备标识发送给第二网络的第一移动管理网元,接收所述第二网络的第一移动管理网元根据终端设备标识返回的第二网络的目标核心网标识。
其中,第二网络的第一移动管理网元可以是第二网络的中一个特殊的缺省移动管理网元,也可以是第一网络的移动管理网元任意选择的一个第二网络的移动管理网元。
具体的:第一网络的移动管理网元向第二网络的第一移动管理网元发送请求消息(例如,第二切换请求或者查询请求),请求消息中包含终端设备的标识;第二网络的第一移动管理网元根据所述终端设备的标识从签约数据中获取所述的终端设备的使用类型Usage type(例如,第一移动管理网元向HSS发送签约数据查询请求,其中包含终端设备的标识,HSS向第一移动管理网元返回对应终端设备的签约数据信息,签约数据中包含终端设备的使用类型);第一移动管理网元根据所述使用类型获取终端设备的第二网络的目标核心网标识(该步骤可以参考现有技术中的描述);第一移动管理网元返回第二网络的目标核心网标识给第一网络的移动管理网元。
方式三:所述第一网络的移动管理网元向所述第二网络的第一移动管理网元发送请求消息(例如,第二切换请求或者查询请求),请求将所述终端设备切换到所述第二网络,所述请求消息中携带终端设备的标识;接收所述第二网络的第一移动管理网元返回的第二网络的第二移动管理网元的信息。
具体的,第二网络的第一移动管理网元接收第一网络的移动管理网元发送的请求消息,所述请求消息中携带终端设备的标识;第二网络的第一移动管理网元根据所述终端设备的标识从签约数据中获取所述终端设备的使用类型;第二网络的第一移动管理网元根据所述终端设备的使用类型确定的第二网络的目标核心网标识,根据第二网络的目标核心网标识确定第二网络的目标移动管理网元,向第一网络的移动管理网元返回所述第二网络的目标移动管理网元的信息或者也可以将所述请求消息发送给所述第二网络的目标移动管理网元。
可选的,第一移动管理网元返回第二网络的目标移动管理网元的信息给第一网络的移动管理网元的方式还包括:如果第一移动管理网元能够支持第二网络的目标核心网,则第一移动管理网元执行后续的切换步骤。如果第一移动管理网元不能支持该第二网络的目标核心网,第一移动管理网元再确定一个与该第二网络的目标核心网标识对应的第二网络的移动管理网元作为目标移动管理网元。第二网络的移动管理网元与第二网络的核心网标识的对应关系配置在Default MME上。
步骤S205,所述第一网络的移动管理网元向所述第二网络的目标移动管理网元发送第二切换请求,请求将所述终端设备切换到所述第二网络。
具体的,第一网络的移动管理网元从SMF获取终端设备的会话上下文(SM Context),并同时根据第一网络的移动管理网元自身的保存的终端设备上下文获得终端设备的移动管理上下文(MM Context),第一网络的移动管理网元向所述第二网络的目标移动管理网元发送第二切换请求,所述第二切换请求携带终端设备的SM Context和MM Context元。
步骤S206,第二网络的目标移动管理网元完成后续的切换步骤,例如在第二网络中为终端设备建立上下文以及承载等。
通过本申请的实施例,可以为终端设备找到合适的第二网络的移动性管理网元为该终端设备服务,从而可以避免终端设备的业务中断。
基于图1的网络架构,图3,图4,图5,图6将分别结合本申请具体实施例来详细描述图2所描述的方法。
图3为本申请一个实施例的信令交互图,其中,第一网络以5G为例,第二网络以4G为例,第一网络的移动管理网元以AMF为例,第二网络的移动管理网元以MME为例进行说明,可以理解,AMF可以被替换为第一网络的移动管理网元,目标MME可以被替换为第二网络的目标移动管理网元,包括:
301-303可以参考步骤201-203,
304.AMF向PCF请求网络策略,获取切片信息和DCN的对应关系表。
可选的,网络请求中包含PLMN ID。包含PLMN ID的效果在于根据终端设备所移动到的目标网络的PLMN,便于PCF确定与该PLMN对应的对应关系表
305.PCF向AMF返回响应消息,其中包含切片信息切片和DCN的对应关系表。
可选的,如果网络请求中包含PLMN ID,则PCF返回与该PLMN ID对应的切片信息和DCN的对应关系表。
306.AMF根据自身保存的终端设备的切片信息,(例如Requested NSSAI/Allowed NSSAI),以及上述切片信息切片和DCN的对应关系表,确定DCN ID。
具体的过程,可以参见实施例2中方式二中的描述。
可选的,AMF还要根据终端设备的目标移动位置,确定DCN ID。
307.AMF根据DCN-ID查询DNS服务器或者网络功能库(Network Repository Function,NRF)获得与DCN ID对应的目标MME的信息。
目标MME的信息,例如可以是MME的标识,MME的访问地址等等。
308.AMF向该目标MME发送切换请求,如Relocation Request。
其中:Request NSSAI/Allowed NSSAI可能有多个,在这种情况下需要为切片定义优先级,则切换时AMF首先选择优先级最高的切片信息,即优先级最高的Request NSSAI/Allowed NSSAI。AMF再根据对应关系表确定与之对应的DCN-ID。
图4为本申请另一个实施例的切换的信令交互图,其中,第一网络以5G为例,第二网络以4G为例,第一网络的移动管理网元以AMF为例,第二网络的第一移动管理网元以default MME为例,第二网络的目标移动管理网元以目标MME为例进行说明,可以理解,AMF可以被替换为第一网络的移动管理网元,default MM可以被替换为第二网络的第一移动管理网元,目标MME可以被替换为第二网络的目标移动管理网元,包括:
401-403可以参考步骤201-203,
404.AMF选择一个Default MME,并将切换请求转发给Default MME。切换请求中包含终端设备的标识。
可选的,还携带上下文。
其中,Default MME可以是4G网络中一个特殊的缺省MME,也可以是AMF任意选择的一个MME,该MME不一定能够服务该终端设备。
405.Default MME向HSS发送签约数据查询请求,其中包含终端设备的标识。
406.HSS向Default MME返回对应终端设备的签约数据信息,签约数据中包含终端设备的Usage Type。
407.Default MME根据终端设备的Usage Type确定DCN-ID(现有技术)。如果Default MME能够支持该DCN-ID,则Default MME接收AMF发送的切换请求消息,并执行后续的切换步骤。如果Default MME不能支持该DCN-ID,Default MME再根据DCN-ID确定一个与对应的MME网元。MME网元与DCN-ID的对应关系配置在Default MME上。
408a.Default MME向AMF发送重定向消息,其中包括步骤4中确定的MME网元的信息,例如MME ID或者MME的访问地址等。可选的,还包括一个原因值,通知AMF需要将切换请求重新发送给重定向消息中指定的MME网元;408b.AMF接收该消息后,将切换请求重新发送给所指定的MME网元。可选的,还携带上下文。
或者
408c.Default MME将从AMF接收到的切换请求直接发送给步骤407中确定的MME网元。
图5为本申请又一个实施例的切换的信令交互图,其中,第一网络以5G为例,第二网络以4G为例,第一网络的移动管理网元以AMF为例,第二网络的目标移动管理网元以目标MME为例进行说明,可以理解,AMF可以被替换为第一网络的移动管理网元,目标MME可以被替换为第二网络的目标移动管理网元,包括:
501.终端设备侧由HPLMN为其配置了DCN-ID,保存在终端设备设备或者SIM卡中
502.终端设备在向网络发起注册时,会将预配置的DCN-ID包含在注册请求如Registration Request中发送给AMF。AMF将DCN-ID保存。
503.当切换发生时(参见步骤201-203),AMF根据保存的DCN-ID查询DNS服务器或者NRF获得目标MME的信息,如MME的标识,MME的访问地址等。
504.AMF将切换请求直接发送给目标MME。
图6为为本申请又一个实施例的切换的信令交互图,其中,第一网络以5G为例,第二网络以4G为例,第一网络的移动管理网元以AMF为例,第二网络的目标移动管理网元以目标MME为例进行说明,可以理解,AMF可以被替换为第一网络的移动管理网元,目标MME可以被替换为第二网络的目标移动管理网元包括:
601.切换流程发生时(参见步骤201-203),AMF获取终端设备Usage Type。具体可以是AMF根据终端设备标识请求查询签约数据库,如HSS或UDM。签约数据库返回终端设备的签约数据,其中包括终端设备的Usage Type。
602.AMF根据终端设备Usage Type选择目标MME。具体可以是,AMF向DNS或者NRF发送查询请求,其中包括终端设备Usage Type,DNS或者NRF根据终端设备Usage Type返回MME的标识或者访问地址。
603.AMF将切换请求发送给目标MME。
本申请实施例可以根据上述图2至图6的方法示例、下面对第一网络的移动管理网元、第二网络的第一移动管理网元进行功能模块的划分,例如,可以对应各个功能划分各个功能模块,也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。需要说明的是,本申请实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式.
在采用对应各个功能划分各个功能模块的情况下,图7为本申请实施例中所涉及的网络设备的一种可能的结构示意图,例如第一网络的移动管理网元,第二网络的第一移动管理网元,用于实现图2至图6的方法实施例中第一网络的移动管理网元的功能。
该第一网络的移动管理网元可以包括:通信单元701、处理单元702;其中,通信单元701用于支持第一网络的移动管理网元与上述实施例中的其他网元之间收发信息。所述处理单元702执行各种处理功能。例如,通信单元701用于支持第一网络的移动管理网元实现图2至图6中的步骤201,205,304,305,308,401,408a,408b,502,503或504等相关的步骤中收发信息的功能;处理单元702用于支持第一网络的移动管理网元实现图2至图6中的步骤202,203,204,306,307,407,或502,或步骤等相关的步骤中处理的功能等;可选的,第一网络的移动管理网元还可以包括存储单元703,存储单元703用于存储第一网络的移动管理网元的程序代码和数据。
图7还可以作为本申请实施例中所涉及第二网络的第一移动管理网元的一种可能的结构示意图,用于实现图2至图6的方法实施例中第二网络的第一移动管理网元。该第二网络的第一移动管理网元可以包括:通信单元701、处理单元702;其中,通信单元701用于支持第二网络的第一移动管理网元与上述实施例中的其他网元之间收发信息。所述处理单元702执行各种处理功能。例如,通信单元701用于用于支持第二网络的第一移动管理网元执行图2至图6中的步骤404,405,406,或408c等相关的步骤;处理单元702用于支持第二网络的第一移动管理网元执行图2至图6中的步骤407等相关的步骤;可选的,第二网络的第一移动管理网元还可以包括存储单元703,存储单元703用于存储第二网络的第一移动管理网元的程序代码和数据。
可以理解的是,图7中的处理单元702可以是处理器或控制器,例如可以是中央处理器(Central Processing Unit,CPU),通用处理器,数字信号处理器(Digital Signal Processor,DSP),专用集成电路(Application-Specific Integrated Circuit,ASIC),现场可编程门阵列(Field Programmable Gate Array,FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框,模块和电路。所述处理器也可以是实现计算功能的组合,例如包含一个或多个微处理器组合,DSP和微处理器的组合等等。通信单元701可以是收发接口。存储单元703可以是存储器。
当处理单元702为处理器,接收单元701和发送单元703可以是收发器为收发器,存储单元为存储器时,本申请实施例所涉及的NF仓库管理功能组件,第二网络的第一移动管理网元可以为图8所示的网络设备。
如图8所示,该网络设备可包括:收发接口801、处理器802、存储器803以及总线 804。其中,收发接口801、处理器802、存储器803通过总线804相互连接;总线804可以是PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示,图8中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
本领域技术人员应该可以意识到,在上述一个或多个示例中,本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时,可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质,其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式,对本申请的目的、技术方案和有益效果进行了进一步详细说明,所应理解的是,以上所述仅为本申请的具体实施方式而已,并不用于限定本申请的保护范围,凡在本申请的技术方案的基础之上,所做的任何修改、等同替换、改进等,均应包括在本申请的保护范围之内。
Claims (40)
- 一种切换的方法,其特征在于,包括:第一网络的移动管理网元接收第一网络的接入网发送的第一切换请求,获知终端设备需要切换到第二网络;所述第一网络的移动管理网元根据所述第一切换请求获取所述终端设备的标识;所述第一网络的移动管理网元根据所述终端设备的标识确定第二网络的目标移动管理网元;所述第一网络的移动管理网元向所述第二网络的目标移动管理网元发送第二切换请求,请求将所述终端设备切换到所述第二网络。
- 如权利要求1所述的方法,其特征在于,所述第一网络的移动管理网元根据所述终端设备的标识确定第二网络的目标移动管理网元,包括:所述第一网络的移动管理网元根据所述终端设备的标识从签约数据库获取所述终端设备的使用类型;所述第一网络的移动管理网元根据所述终端设备的使用类型确定所述第二网络的目标移动管理网元。
- 如权利要求2所述的方法,所述第一网络的移动管理网元根据所述终端设备的使用类型确定第二网络的目标移动管理网元,其特征在于,包括:所述第一网络的移动管理网元向网域名称服务器DNS或网络功能库NRF发送查询请求,携带所述终端设备的使用类型;接收所述DNS或NRF返回的所述第二网络的目标移动管理网元信息。
- 如权利要求1所述的方法,其特征在于,所述第一网络的移动管理网元根据所述终端设备的标识确定第二网络的目标移动管理网元,还包括:所述第一网络的移动管理网元根据所述终端设备的标识获取第二网络的目标核心网标识;所述第一网络的移动管理网元根据所述第二网络的目标核心网标识确定第二网络的目标移动管理网元。
- 如权利要求4所述的方法,其特征在于,所述第一网络的移动管理网元根据所述终端设备的标识获取第二网络的目标核心网标识包括:所述第一网络的移动管理网元根据所述终端设备的标识从所述终端设备的上下文中获取所述终端设备的切片信息,获取第二网络的核心网标识与切片信息的对应关系,根据所述终端设备的切片信息以及所述对应关系,确定第二网络的目标核心网标识。
- 如权利要求5所述的方法,其特征在于,获取第二网络的核心网标识与切片信息的对应关系包括:第一网络的移动管理网元向策略控制功能PCF发送请求消息,第一网络的移动管理网元接收所述PCF返回第二网络的核心网标识与切片信息的对应关系表。
- 如权利要求5或6所述的方法,其特征在于,如果所述终端设备的切片信息为多个,且所述终端设备的多个切片信息配置有优先级信息,则根据所述终端设备的切片信息,以及所述对应关系,确定第二网络的目标核心网标识的步骤包括:根据所述终端设备的切片信息中优先级最高的切片信息,以及所述对应关系,确定所述第二网络的目标核心网标识。
- 如权利要求4所述的方法,其特征在于,第一网络的移动管理网元根据所述终端设备标识获取第二网络的目标核心网标识,包括:所述第一网络的移动管理网元将所述终端设备标识发送给第二网络的第一移动管理网元,接收所述第二网络的第一移动管理网元根据终端设备标识返回的第二网络的目标核心网标识。
- 如权利要求4所述的方法,其特征在于,所述第一网络的移动管理网元根据所述终端设备标识获取目标核心网标识,包括:根据所述终端设备标识查询终端设备的上下文获得第二网络的目标核心网标识。
- 如权利要求9所述的方法,所述方法还包括:所述第一网络的移动管理网元接收所述终端设备的注册请求,所述注册请求中包含所述终端设备的第二网络的核心网标识;所述第一网络的移动管理网元保存所述第二网络的核心网标识,所述第二网络的核心网标识保存在所述终端设备的上下文中。
- 如权利要求4-10任一所述的方法,其特征在于,所述第一网络的移动管理网元根据所述第二网络的目标核心网标识确定第二网络的目标移动管理网元包括:所述第一网络的移动管理网元向网域名称服务器DNS或者网络功能库NRF发送查询请求,携带所述第二网络的目标核心网标识;接收所述DNS或者NRF返回的所述第二网络的目标移动管理网元信息。
- 如权利要求1所述的方法,其特征在于,所述第一网络的移动管理网元根据所述终端设备的标识确定第二网络的目标移动管理网元包括:所述第一网络的移动管理网元向所述第二网络的第一移动管理网元发送请求消息,请求将所述终端设备切换到所述第二网络,所述请求消息中携带终端设备的标识;接收所述第二网络的第一移动管理网元返回的第二网络的第二移动管理网元的信息。
- 一种切换的方法,其特征在于,包括:第二网络的第一移动管理网元接收第一网络的移动管理网元发送的请求消息,所述请求消息中携带终端设备的标识;根据所述终端设备的标识从签约数据中获取所述终端设备的使用类型;根据所述终端设备的使用类型确定的第二网络的目标核心网标识;向所述AMF返回所述第二网络的目标核心网标识,或者,根据第二网络的目标核心网标识确定第二网络的目标移动管理网元,向所述AMF返回所述第二网络的目标移动管理网元信息;或者,根据第二网络的目标核心网标识确定第二网络的目标移动管理网元,将所述请求消息发送给所述第二网络的目标移动管理网元。
- 如权利要求3,11或13任一所述的方法,第二网络的目标移动管理网元信息包括:目标移动管理网元的标识,或者目标移动管理网元的访问地址。
- 如权利要求1-14任一所述的方法,其特征在于,第一网络为5G网络,第一网络的移动管理网元为AMF,第二网络为4G网络,第二网络的移动管理网元为MME。
- 一种移动管理网元,属于第一网络,其特征在于,包括:通信单元和处理单元;所述通信单元用于接收第一网络的接入网发送的第一切换请求,获知终端设备需要切换到第二网络;所述处理单元用于根据所述第一切换请求获取所述终端设备的标识;根据所述终端设备的标识确定第二网络的目标移动管理网元;所述通信单元还用于向所述第二网络的目标移动管理网元发送第二切换请求,请求将所述终端设备切换到所述第二网络。
- 如权利要求16所述的移动管理网元,其特征在于,所述通信单元用于根据所述终端设备的标识从签约数据库获取所述终端设备的使用类型,所述处理单元用于根据所述终端设备的使用类型确定第二网络的目标移动管理网元。
- 如权利要求17所述的移动管理网元,其特征在于,所述通信单元用于根据所述终端设备的标识从签约数据库获取所述终端设备的使用类型包括:所述通信单元用于向网域名称服务器DNS或网络功能库NRF发送查询请求,携带所述终端设备的使用类型;接收所述DNS或NRF返回的所述第二网络的目标移动管理网元信息。
- 如权利要求16所述的移动管理网元,其特征在于,根据所述终端设备的标识确定第二网络的目标移动管理网元,包括:所述处理单元用于根据所述终端设备的标识获取第二网络的目标核心网标识,根据所述第二网络的目标核心网标识确定第二网络的目标移动管理网元。
- 如权利要求19所述的移动管理网元,其特征在于,所述处理单元用于根据所述终端设备的标识获取第二网络的目标核心网标识包括:所述处理单元用于根据所述终端设备的标识从所述终端设备的上下文中获取所述终端设备的切片信息,获取第二网络的核心网标识与切片信息的对应关系,根据所述终端设备的切片信息以及所述对应关系,确定第二网络的目标核心网标识。
- 如权利要求20所述的移动管理网元,其特征在于,所述处理单元用于获取第二网络的核心网标识与切片信息的对应关系包括:所述处理单元用于通过通信单元向策略控制功能PCF发送请求消息,接收所述PCF返回第二网络的核心网标识与切片信息的对应关系表。
- 如权利要求20或21所述的移动管理网元,其特征在于,如果所述终端设备的切片信息为多个,且所述终端设备的多个切片信息配置有优先级信息,则根据所述终端设备的切片信息,以及所述对应关系,确定第二网络的目标核心网标识的步骤包括:所述处理单元用于根据所述终端设备的切片信息中优先级最高的切片信息,以及所述 对应关系,确定所述第二网络的目标核心网标识。
- 如权利要求19所述的移动管理网元,其特征在于,所述通信单元用于根据所述终端设备标识获取第二网络的目标核心网标识,包括:所述通信单元用于通过所述通信单元将所述终端设备标识发送给第二网络的第一移动管理网元,接收所述第二网络的第一移动管理网元根据终端设备标识返回的第二网络的目标核心网标识。
- 如权利要求19所述的移动管理网元,其特征在于,所述通信单元用于根据所述终端设备标识获取目标核心网标识,包括:所述通信单元用于根据所述终端设备标识查询终端设备的上下文获得第二网络的目标核心网标识。
- 如权利要求24所述的移动管理网元,所述通信单元还用于接收所述终端设备的注册请求,所述注册请求中包含所述终端设备的第二网络的核心网标识;所述处理单元保存所述第二网络的核心网标识,所述第二网络的核心网标识保存在所述终端设备的上下文中。
- 如权利要求19-25任一所述的移动管理网元,其特征在于,所述处理单元用于根据所述第二网络的目标核心网标识确定第二网络的目标移动管理网元包括:所述处理单元用于通过通信单元向网域名称服务器DNS或者网络功能库NRF发送查询请求,携带所述第二网络的目标核心网标识,接收所述DNS或者NRF返回的所述第二网络的目标移动管理网元信息。
- 如权利要求16所述的移动管理网元,其特征在于,所述处理单元用于根据所述终端设备的标识确定第二网络的目标移动管理网元包括:所述处理单元用于通过通信单元向所述第二网络的第一移动管理网元发送请求消息,请求将所述终端设备切换到所述第二网络,所述请求消息中携带终端设备的标识,接收所述第二网络的第一移动管理网元返回的第二网络的第二移动管理网元的信息。
- 一种移动管理网元,属于第二网络,其特征在于,包括:通信单元和处理单元;所述通信单元用于接收第一网络的移动管理网元发送的请求消息,所述请求消息中携带终端设备的标识;所述处理单元用于根据所述终端设备的标识从签约数据中获取所述终端设备的使用类型;根据所述终端设备的使用类型确定的第二网络的目标核心网标识;所述通信单元还用于向所述AMF返回所述第二网络的目标核心网标识,或者,所述处理单元用于根据第二网络的目标核心网标识确定第二网络的目标移动管理网元,所述通信单元还用于向所述AMF返回所述第二网络的目标移动管理网元信息;或者,所述处理单元用于根据第二网络的目标核心网标识确定第二网络的目标移动管理网元,所述通信单元还用于将所述请求消息发送给所述第二网络的目标移动管理网元。
- 如权利要求18,26或28任一所述的移动管理网元,第二网络的目标移动管理网元信息包括:目标移动管理网元的标识,或者目标移动管理网元的访问地址。
- 一种通信系统,包括如权利要求16-27任一所述的移动性管理网元,和/或,如权 利要求28-29任一所述的移动性管理网元。
- 一种移动管理网元,其特征在于,包括:通信接口和至少一个处理器,所述通信接口和所述至少一个处理器通过线路互联,所述通信接口用于执行权利要求1到12任一项所述的方法中,在所述移动管理网元侧进行消息接收和发送的操作;所述至少一个处理器调用指令,执行权利要求1到12任一项所述的方法中,在所述移动管理网元侧进行的消息处理或控制操作。
- 一种移动管理网元,其特征在于,包括通信接口和至少一个处理器,所述通信接口和所述至少一个处理器通过线路互联,所述通信接口用于执行权利要求13到15任一项所述的方法中,在所述移动管理网元侧进行消息接收和发送的操作;所述至少一个处理器调用指令,执行权利要求13到15任一项所述的方法中,在所述移动管理网元侧进行的消息处理或控制操作。
- 一种芯片系统,其特征在于,包括:所述芯片系统包括至少一个处理器,和接口电路,所述接口电路和所述至少一个处理器通过线路互联,所述处理器通过运行指令,以执行权利要求1到15任一项所述的方法。
- 一种移动管理网元,用于执行1到12项任一项所述方法。
- 一种移动管理网元,用于执行13到15项任一项所述方法。
- 一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机执行上述1到12任一项所述的方法。
- 一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机执行上述13到15项任一项所述的方法。
- 一种计算机可读存储介质,包括指令,当其在计算机上运行时,使得计算机执行如权利要求1到12任一项所述的方法。
- 一种计算机可读存储介质,包括指令,当其在计算机上运行时,使得计算机执行如权利要求13到15任一项所述的方法。
- 一种通信系统,包括如权利要求31任一所述的移动性管理网元,和/或,如权利要求32任一所述的移动性管理网元。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP18868323.9A EP3691178B1 (en) | 2017-10-17 | 2018-10-15 | Handover method and mobility management network element |
US16/850,547 US11356919B2 (en) | 2017-10-17 | 2020-04-16 | Handover method, mobility management network element, and communications system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710977957.5A CN109673003B (zh) | 2017-10-17 | 2017-10-17 | 一种切换的方法、移动性管理网元和通信系统 |
CN201710977957.5 | 2017-10-17 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/850,547 Continuation US11356919B2 (en) | 2017-10-17 | 2020-04-16 | Handover method, mobility management network element, and communications system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019076273A1 true WO2019076273A1 (zh) | 2019-04-25 |
Family
ID=66141422
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/110279 WO2019076273A1 (zh) | 2017-10-17 | 2018-10-15 | 一种切换的方法、移动性管理网元和通信系统 |
Country Status (4)
Country | Link |
---|---|
US (1) | US11356919B2 (zh) |
EP (1) | EP3691178B1 (zh) |
CN (1) | CN109673003B (zh) |
WO (1) | WO2019076273A1 (zh) |
Cited By (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10778527B2 (en) | 2018-10-31 | 2020-09-15 | Oracle International Corporation | Methods, systems, and computer readable media for providing a service proxy function in a telecommunications network core using a service-based architecture |
US10791044B1 (en) | 2019-03-29 | 2020-09-29 | Oracle International Corporation | Methods, system, and computer readable media for handling multiple versions of same service provided by producer network functions (NFs) |
US10819636B1 (en) | 2019-06-26 | 2020-10-27 | Oracle International Corporation | Methods, systems, and computer readable media for producer network function (NF) service instance wide egress rate limiting at service communication proxy (SCP) |
CN111885185A (zh) * | 2020-07-29 | 2020-11-03 | 中国联合网络通信集团有限公司 | 一种资源调度方法及装置 |
US10945120B2 (en) | 2019-02-27 | 2021-03-09 | Oracle International Corporation | Methods, systems, and computer readable media for dynamically provisioning and using public land mobile network (PLMN) location mappings in service capability exposure function (SCEF) or network exposure function (NEF) |
US11082393B2 (en) | 2019-08-29 | 2021-08-03 | Oracle International Corporation | Methods, systems, and computer readable media for actively discovering and tracking addresses associated with 5G and non-5G service endpoints |
US11159359B2 (en) | 2019-06-26 | 2021-10-26 | Oracle International Corporation | Methods, systems, and computer readable media for diameter-peer-wide egress rate limiting at diameter relay agent (DRA) |
US11224009B2 (en) | 2019-12-30 | 2022-01-11 | Oracle International Corporation | Methods, systems, and computer readable media for enabling transport quality of service (QoS) in 5G networks |
US11252093B2 (en) | 2019-06-26 | 2022-02-15 | Oracle International Corporation | Methods, systems, and computer readable media for policing access point name-aggregate maximum bit rate (APN-AMBR) across packet data network gateway data plane (P-GW DP) worker instances |
US11271846B2 (en) | 2018-10-22 | 2022-03-08 | Oracle International Corporation | Methods, systems, and computer readable media for locality-based selection and routing of traffic to producer network functions (NFs) |
US11323413B2 (en) | 2019-08-29 | 2022-05-03 | Oracle International Corporation | Methods, systems, and computer readable media for actively discovering and tracking addresses associated with 4G service endpoints |
WO2022155915A1 (zh) * | 2021-01-22 | 2022-07-28 | 华为技术有限公司 | 网络互通的方法及装置 |
US11496954B2 (en) | 2021-03-13 | 2022-11-08 | Oracle International Corporation | Methods, systems, and computer readable media for supporting multiple preferred localities for network function (NF) discovery and selection procedures |
US11528334B2 (en) | 2020-07-31 | 2022-12-13 | Oracle International Corporation | Methods, systems, and computer readable media for preferred network function (NF) location routing using service communications proxy (SCP) |
US11570262B2 (en) | 2020-10-28 | 2023-01-31 | Oracle International Corporation | Methods, systems, and computer readable media for rank processing for network function selection |
US11855956B2 (en) | 2022-02-15 | 2023-12-26 | Oracle International Corporation | Methods, systems, and computer readable media for providing network function (NF) repository function (NRF) with configurable producer NF internet protocol (IP) address mapping |
US11895080B2 (en) | 2021-06-23 | 2024-02-06 | Oracle International Corporation | Methods, systems, and computer readable media for resolution of inter-network domain names |
US11979369B2 (en) | 2021-09-21 | 2024-05-07 | Oracle International Corporation | Methods, systems, and computer readable media for providing for optimized service-based interface (SBI) communications by performing network function (NF) fully qualified domain name (FQDN) resolution at NF repository function (NRF) |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110831110B (zh) * | 2018-08-07 | 2020-11-17 | 华为技术有限公司 | 接入方法、切换方法、设备及系统 |
CN112055421B (zh) * | 2019-06-06 | 2022-09-02 | 华为技术有限公司 | 基于预配置drb的终端设备标识的处理方法及装置 |
CN112105014B (zh) * | 2019-06-17 | 2023-06-20 | 中国电信股份有限公司 | 4g与5g网络互操作的方法、装置、系统及设备 |
CN112188469B (zh) * | 2019-07-01 | 2022-08-02 | 中国电信股份有限公司 | 策略控制方法、装置及计算机可读存储介质 |
CN112333778B (zh) * | 2019-08-05 | 2022-02-08 | 华为技术有限公司 | 一种终端定位方法、装置及系统 |
CN110677926A (zh) * | 2019-09-27 | 2020-01-10 | Tcl移动通信科技(宁波)有限公司 | 移动通信网络的连接方法、装置、存储介质及服务器 |
US11234115B2 (en) * | 2020-02-14 | 2022-01-25 | Cisco Technology, Inc. | Techniques to facilitate mobility management entity (MME) identification for user equipment context transfer |
US11516718B2 (en) * | 2020-07-09 | 2022-11-29 | At&T Intellectual Property I, L.P. | Dynamic discovery of network functions in mobility interworking across radio access technologies |
JP7290181B2 (ja) * | 2020-07-17 | 2023-06-13 | 日本電気株式会社 | 基地局装置、amf、通信装置、及び方法 |
CN115604696A (zh) * | 2021-07-07 | 2023-01-13 | 华为技术有限公司(Cn) | 执行在线签约的方法和装置 |
CN113691936B (zh) * | 2021-08-25 | 2023-03-24 | 中国联合网络通信集团有限公司 | 基于共享基站的终端接入方法和共享基站 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101540988A (zh) * | 2008-03-19 | 2009-09-23 | 华为技术有限公司 | 网络切换方法和系统 |
CN103228016A (zh) * | 2013-05-02 | 2013-07-31 | 中国联合网络通信集团有限公司 | 基于小区切换的数据处理方法、设备和系统 |
CN103298050A (zh) * | 2012-02-29 | 2013-09-11 | 中兴通讯股份有限公司 | 语音业务的切换方法及装置 |
US20150296449A1 (en) * | 2012-12-28 | 2015-10-15 | Huawei Technologies Co., Ltd. | Method and device for network selection from shared network |
CN107040481A (zh) * | 2016-02-04 | 2017-08-11 | 中兴通讯股份有限公司 | 一种网络切片选择方法、策略生成方法及网络节点 |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101426243B (zh) * | 2007-10-30 | 2010-11-03 | 大唐移动通信设备有限公司 | 系统切换的方法、通信系统 |
CN101795475A (zh) * | 2009-02-02 | 2010-08-04 | 华为技术有限公司 | 一种在lte中进行跨plmn切换的方法及装置 |
CN101841824A (zh) * | 2009-03-17 | 2010-09-22 | 大唐移动通信设备有限公司 | 一种实现小区切换的方法、系统和中继设备 |
US8305877B2 (en) * | 2009-09-10 | 2012-11-06 | Tyco Electronics Subsea Communications Llc | System and method for distributed fault sensing and recovery |
CN102104867B (zh) * | 2010-04-07 | 2014-06-18 | 电信科学技术研究院 | 一种切换过程中寻址核心网节点的方法及其装置 |
CN102378359B (zh) * | 2010-08-24 | 2016-02-10 | 中兴通讯股份有限公司 | 一种网元信息获取方法和系统 |
EP2856801B1 (en) * | 2012-05-30 | 2019-04-24 | Nokia Technologies Oy | Method and apparatus for providing notification of a network access technology switching event |
US9232531B2 (en) * | 2012-10-22 | 2016-01-05 | Qualcomm Incorporated | Prioritization of users for switching between co-existence wireless systems |
WO2015013924A1 (zh) * | 2013-07-31 | 2015-02-05 | 华为技术有限公司 | 切换方法、基站和用户设备 |
US10257078B2 (en) * | 2016-04-01 | 2019-04-09 | Qualcomm Incorporated | Interworking with legacy radio access technologies for connectivity to next generation core network |
EP3506677B1 (en) * | 2016-09-30 | 2021-03-31 | Huawei Technologies Co., Ltd. | Method and device for establishing bearer |
EP3952448B1 (en) * | 2016-11-04 | 2023-04-05 | Huawei Technologies Co., Ltd. | Inter-network change method and terminal |
WO2018126461A1 (zh) * | 2017-01-06 | 2018-07-12 | 华为技术有限公司 | 一种网络切换方法及相关设备 |
US10524166B2 (en) * | 2017-01-09 | 2019-12-31 | Lg Electronics Inc. | Method for interworking between networks in wireless communication system and apparatus thereof |
MX2019011128A (es) * | 2017-03-21 | 2019-11-05 | Ericsson Telefon Ab L M | Metodo y nodo para administrar traspasos en redes 5g. |
CN111201811A (zh) * | 2017-10-09 | 2020-05-26 | 瑞典爱立信有限公司 | 建立用于无线通信设备的分组数据传送的连接的方法 |
CA3071180A1 (en) * | 2017-10-16 | 2019-04-25 | Ntt Docomo, Inc. | Communication system, communication control device, and communication method |
US10681593B2 (en) * | 2017-11-30 | 2020-06-09 | At&T Intellectual Property I, L.P. | Session transfer for packet data network connection |
-
2017
- 2017-10-17 CN CN201710977957.5A patent/CN109673003B/zh active Active
-
2018
- 2018-10-15 EP EP18868323.9A patent/EP3691178B1/en active Active
- 2018-10-15 WO PCT/CN2018/110279 patent/WO2019076273A1/zh unknown
-
2020
- 2020-04-16 US US16/850,547 patent/US11356919B2/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101540988A (zh) * | 2008-03-19 | 2009-09-23 | 华为技术有限公司 | 网络切换方法和系统 |
CN103298050A (zh) * | 2012-02-29 | 2013-09-11 | 中兴通讯股份有限公司 | 语音业务的切换方法及装置 |
US20150296449A1 (en) * | 2012-12-28 | 2015-10-15 | Huawei Technologies Co., Ltd. | Method and device for network selection from shared network |
CN103228016A (zh) * | 2013-05-02 | 2013-07-31 | 中国联合网络通信集团有限公司 | 基于小区切换的数据处理方法、设备和系统 |
CN107040481A (zh) * | 2016-02-04 | 2017-08-11 | 中兴通讯股份有限公司 | 一种网络切片选择方法、策略生成方法及网络节点 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3691178A4 |
Cited By (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11271846B2 (en) | 2018-10-22 | 2022-03-08 | Oracle International Corporation | Methods, systems, and computer readable media for locality-based selection and routing of traffic to producer network functions (NFs) |
US10778527B2 (en) | 2018-10-31 | 2020-09-15 | Oracle International Corporation | Methods, systems, and computer readable media for providing a service proxy function in a telecommunications network core using a service-based architecture |
US10945120B2 (en) | 2019-02-27 | 2021-03-09 | Oracle International Corporation | Methods, systems, and computer readable media for dynamically provisioning and using public land mobile network (PLMN) location mappings in service capability exposure function (SCEF) or network exposure function (NEF) |
US10791044B1 (en) | 2019-03-29 | 2020-09-29 | Oracle International Corporation | Methods, system, and computer readable media for handling multiple versions of same service provided by producer network functions (NFs) |
US11252093B2 (en) | 2019-06-26 | 2022-02-15 | Oracle International Corporation | Methods, systems, and computer readable media for policing access point name-aggregate maximum bit rate (APN-AMBR) across packet data network gateway data plane (P-GW DP) worker instances |
US11159359B2 (en) | 2019-06-26 | 2021-10-26 | Oracle International Corporation | Methods, systems, and computer readable media for diameter-peer-wide egress rate limiting at diameter relay agent (DRA) |
US10819636B1 (en) | 2019-06-26 | 2020-10-27 | Oracle International Corporation | Methods, systems, and computer readable media for producer network function (NF) service instance wide egress rate limiting at service communication proxy (SCP) |
US11323413B2 (en) | 2019-08-29 | 2022-05-03 | Oracle International Corporation | Methods, systems, and computer readable media for actively discovering and tracking addresses associated with 4G service endpoints |
US11082393B2 (en) | 2019-08-29 | 2021-08-03 | Oracle International Corporation | Methods, systems, and computer readable media for actively discovering and tracking addresses associated with 5G and non-5G service endpoints |
US11224009B2 (en) | 2019-12-30 | 2022-01-11 | Oracle International Corporation | Methods, systems, and computer readable media for enabling transport quality of service (QoS) in 5G networks |
CN111885185A (zh) * | 2020-07-29 | 2020-11-03 | 中国联合网络通信集团有限公司 | 一种资源调度方法及装置 |
US11528334B2 (en) | 2020-07-31 | 2022-12-13 | Oracle International Corporation | Methods, systems, and computer readable media for preferred network function (NF) location routing using service communications proxy (SCP) |
US11570262B2 (en) | 2020-10-28 | 2023-01-31 | Oracle International Corporation | Methods, systems, and computer readable media for rank processing for network function selection |
WO2022155915A1 (zh) * | 2021-01-22 | 2022-07-28 | 华为技术有限公司 | 网络互通的方法及装置 |
US11496954B2 (en) | 2021-03-13 | 2022-11-08 | Oracle International Corporation | Methods, systems, and computer readable media for supporting multiple preferred localities for network function (NF) discovery and selection procedures |
US11895080B2 (en) | 2021-06-23 | 2024-02-06 | Oracle International Corporation | Methods, systems, and computer readable media for resolution of inter-network domain names |
US11979369B2 (en) | 2021-09-21 | 2024-05-07 | Oracle International Corporation | Methods, systems, and computer readable media for providing for optimized service-based interface (SBI) communications by performing network function (NF) fully qualified domain name (FQDN) resolution at NF repository function (NRF) |
US11855956B2 (en) | 2022-02-15 | 2023-12-26 | Oracle International Corporation | Methods, systems, and computer readable media for providing network function (NF) repository function (NRF) with configurable producer NF internet protocol (IP) address mapping |
Also Published As
Publication number | Publication date |
---|---|
US20200245218A1 (en) | 2020-07-30 |
CN109673003B (zh) | 2021-10-26 |
CN109673003A (zh) | 2019-04-23 |
EP3691178A1 (en) | 2020-08-05 |
EP3691178A4 (en) | 2020-12-02 |
US11356919B2 (en) | 2022-06-07 |
EP3691178B1 (en) | 2022-04-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019076273A1 (zh) | 一种切换的方法、移动性管理网元和通信系统 | |
JP7013498B2 (ja) | データスケジューリング方法、基地局およびシステム | |
JP7139382B2 (ja) | 無線通信方法及びデバイス | |
US11653296B2 (en) | Isolated network slice selection | |
CN109561423B (zh) | 一种接入目标小区的方法以及装置 | |
EP3402253B1 (en) | Core network control plane device selection method and apparatus | |
US20200107257A1 (en) | Network selection method and base station | |
EP2428001B1 (en) | Method for supporting pdn gw selection | |
JP7016960B2 (ja) | 無線通信方法及び装置 | |
EP3820192B1 (en) | Communication method, access network device, and terminal device | |
CN111935788A (zh) | 一种通信方法、装置及相关设备 | |
CN113785552B (zh) | 会话管理功能选择 | |
US20190349721A1 (en) | Short message transmission method, device, and system | |
TW201914350A (zh) | 用於尋呼的方法、存取網路設備、終端設備和核心網路設備 | |
US20240098148A1 (en) | Restoration of a pdn connection at pgw failure | |
CN101835134B (zh) | S101隧道重定向的方法和相关装置 | |
TW202007199A (zh) | 一種核心網選擇方法及裝置、終端設備、網路設備 | |
WO2007117825A2 (en) | Method for routing calls in a mobile communication network | |
RU2772653C2 (ru) | Способ связи, исходная базовая станция, целевая базовая станция, устройство базовой сети и оконечное устройство | |
KR101817267B1 (ko) | 이기종 망에서 음성 서비스를 제공하기 위한 페이징 장치 및 방법 | |
CN116456321A (zh) | 一种通信方法和通信装置 | |
CN103582083A (zh) | Lte网络共享时cdma网络的选择方法、终端和基站 | |
KR20120076977A (ko) | 호 재시도 방법 및 그를 위한 이동통신 시스템 | |
EP3900302A1 (en) | Cellular telecommunications network | |
WO2007103620A2 (en) | Method for routing calls in a mobile communication network |
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: 18868323 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2018868323 Country of ref document: EP Effective date: 20200430 |