[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2019061039A1 - 切换网络的方法、终端设备和网络设备 - Google Patents

切换网络的方法、终端设备和网络设备 Download PDF

Info

Publication number
WO2019061039A1
WO2019061039A1 PCT/CN2017/103532 CN2017103532W WO2019061039A1 WO 2019061039 A1 WO2019061039 A1 WO 2019061039A1 CN 2017103532 W CN2017103532 W CN 2017103532W WO 2019061039 A1 WO2019061039 A1 WO 2019061039A1
Authority
WO
WIPO (PCT)
Prior art keywords
core network
terminal device
network
configuration
pdcp
Prior art date
Application number
PCT/CN2017/103532
Other languages
English (en)
French (fr)
Inventor
杨宁
刘建华
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN201780050353.4A priority Critical patent/CN109792396B/zh
Priority to PCT/CN2017/103532 priority patent/WO2019061039A1/zh
Priority to EP17923980.1A priority patent/EP3499804B1/en
Priority to US16/340,844 priority patent/US20190268820A1/en
Publication of WO2019061039A1 publication Critical patent/WO2019061039A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/12Reselecting a serving backbone network switching or routing node
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/0813Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0083Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00837Determination of triggering parameters for hand-off
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/14Reselecting a network or an air interface
    • H04W36/144Reselecting a network or an air interface over a different radio air interface technology
    • H04W36/1443Reselecting a network or an air interface over a different radio air interface technology between licensed networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/34Reselection control
    • H04W36/36Reselection control by user or terminal equipment
    • H04W36/362Conditional handover
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/27Transitions between radio resource control [RRC] states
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/08Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W80/00Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02Data link layer protocols

Definitions

  • the present application relates to the field of communications, and more particularly, to a method, a terminal device, and a network device for switching networks.
  • LTE Long Term Evolution
  • E-UTRA Evolved-Universal Terrestrial Radio Access
  • the terminal equipment in the same LTE cell can access only the Evolved Packet Core (EPC), or only the 5G core network, or can simultaneously access the EPC and the 5G core network.
  • EPC Evolved Packet Core
  • the terminal device needs to switch from one core network to another core network, where a large number of signaling interaction processes are involved, and therefore, for the terminal device, how to implement core network switching to reduce signaling Overhead is an issue that needs to be addressed.
  • the embodiment of the present application provides a method for switching a network, a terminal device, and a network device, which can reduce signaling overhead when the core network is switched.
  • a method for switching a network including:
  • the terminal device determines that it needs to switch from the first core network to the second core network
  • the terminal device performs protocol layer configuration according to the core network type of the first core network and the second core network.
  • the determining, by the terminal device, the need to switch from the first core network to the second core network includes:
  • the terminal device determines that it is required to switch from the first core network to the second core network according to current service requirements.
  • the determining, by the terminal device, the need to switch from the first core network to the second core network includes:
  • the terminal device determines that the first core network needs to be handed over to the second core network, when the triggering instruction of the network device is received, where the triggering instruction is used to notify the terminal device from the The first core network switches to the second core network.
  • the method further comprises:
  • the terminal device receives the triggering instruction sent by the network device.
  • the network device is an access network device or a core network device.
  • the triggering instruction is S1 signaling, N2/N3 signaling, or radio resource control RRC signaling.
  • the method further includes:
  • the terminal device acquires system information of the second core network.
  • the acquiring, by the terminal device, system information of the second core network includes:
  • the terminal device receives a broadcast message sent by the access network device, and acquires system information of the second core network from the broadcast message.
  • the acquiring, by the terminal device, system information of the second core network includes:
  • the terminal device performs protocol layer configuration according to the core network type of the first core network and the second core network, including:
  • the terminal device updates the PDCP layer configuration corresponding to the packet data convergence protocol corresponding to the first core network to the second core network.
  • the PDCP layer is configured to update the protocol version of the PDCP layer corresponding to the first core network to the protocol version of the PDCP layer corresponding to the second core network, and update the RRC layer configuration corresponding to the first core network to An RRC layer configuration corresponding to the second core network, and switching the entity of the non-access stratum NAS from the first NAS entity supporting the first core network to the second NAS entity supporting the second core network.
  • the method further comprises:
  • the terminal device does not perform reconfiguration of the radio link control RLC layer, the medium access control MAC layer, and the physical layer PHY.
  • the terminal device may perform only the PDCP layer and the RRC reconfiguration.
  • the reconfiguration of the RLC layer, the MAC layer, and the PHY layer is not required, which is beneficial to reducing the signaling overhead of the terminal device when performing network handover.
  • the first core network is a core network of a long-term evolution LTE system
  • the second core network is a core network of a new wireless NR system
  • the protocol version of the PDCP layer corresponding to the first core network is updated to the protocol version of the PDCP layer corresponding to the second core network, including:
  • the terminal device updates the LTE PDCP to the NR PDCP, where the LTE PDCP is a protocol version of the PDCP layer corresponding to the first core network, and the NR PDCP is a protocol of the PDCP layer corresponding to the second core network. version.
  • the first core network is a core network of an LTE system
  • the second core network is a core network of an NR system
  • the first The RRC layer configuration corresponding to the core network is updated to the RRC layer configuration corresponding to the second core network, including:
  • the terminal device adds the configuration of the service data adaptation SDAP layer to the RRC layer configuration corresponding to the first core network, and adds the configuration of the user plane UP function.
  • the first core network is a core network of an NR system
  • the second core network is a core network of an LTE system
  • the first The protocol version of the PDCP layer corresponding to the core network is updated to the protocol version of the PDCP layer corresponding to the second core network, including:
  • the terminal device updates the NR PDCP to the LTE PDCP, where the NR PDCP is a protocol version of the PDCP layer corresponding to the first core network, and the LTE PDCP is a protocol of the PDCP layer corresponding to the second core network. version.
  • the first core network is a core network of an NR system
  • the second core network is a core network of an LTE system
  • the first The RRC layer configuration corresponding to the core network is updated to the RRC layer configuration corresponding to the second core network, including:
  • the terminal device deletes the configuration of the SDAP layer and deletes the configuration of the user plane UP function on the basis of the RRC layer configuration corresponding to the first core network.
  • the terminal device is in accordance with the The core network type of the first core network and the second core network are configured by the protocol layer, including:
  • the terminal device does not update the PDCP layer of the terminal device and the protocol version of the RRC layer.
  • the terminal device performs protocol layer configuration according to the core network type of the first core network and the second core network, including:
  • the terminal device may not need to update the PDCP layer and the RRC protocol in the case that the access network before and after the handover of the terminal device does not change, and the core network type does not change.
  • the version does not need to reconfigure the RLC layer, the MAC layer, and the PHY layer, which is beneficial to reducing the signaling overhead of the terminal device when performing network switching.
  • the method further comprises:
  • the terminal device sends a request message to the access network device, where the request message is used to request to acquire a PDCP layer configuration corresponding to the second core network and a protocol version of the PDCP layer.
  • the method further comprises:
  • the terminal device sends a NAS message to the second core network, where the NAS message is used to trigger the second core network to initiate a protocol data unit PDU session establishment process.
  • a method for switching a network including:
  • the network device determines that the terminal device needs to be handed over from the first core network to the second core network
  • the triggering instruction is used to notify the terminal device to switch from the first core network to the second core network.
  • the determining, by the network device, that the terminal device needs to be switched from the first core network to the second core network includes:
  • the network device determines that the terminal device needs to be handed over from the first core network to the second core network according to a current load situation.
  • the network device is an access network device or a core network device.
  • the triggering instruction is S1 signaling, N2/N3 signaling, or radio resource control RRC signaling.
  • a terminal device for performing the above first aspect or the first aspect The method in any possible implementation.
  • the terminal device comprises means for performing the method of any of the above-described first aspect or any of the possible implementations of the first aspect.
  • a network device for performing the method of any of the foregoing second aspect or any of the possible implementations of the second aspect.
  • the network device comprises means for performing the method of any of the above-described second or second aspects of the second aspect.
  • a terminal device comprising: a memory, a processor, an input interface, and an output interface.
  • the memory, the processor, the input interface, and the output interface are connected by a bus system.
  • the memory is for storing instructions for executing the memory stored instructions for performing the method of any of the first aspect or the first aspect of the first aspect.
  • a network device comprising: a memory, a processor, an input interface, and an output interface.
  • the memory, the processor, the input interface, and the output interface are connected by a bus system.
  • the memory is for storing instructions for executing the memory stored instructions for performing the method of any of the above-described second aspect or any of the possible implementations of the second aspect.
  • a computer storage medium for storing computer software instructions for performing the method of any of the above first aspect or any of the possible implementations of the first aspect, comprising program.
  • a computer storage medium for storing computer software instructions for performing the method of any of the above-described second aspect or any of the possible implementations of the second aspect, comprising program.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any of the first aspect or the optional implementation of the first aspect.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any of the alternative aspects of the second aspect or the second aspect.
  • FIG. 1 is a schematic diagram of a communication system in accordance with an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a method for switching a network according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a method for switching a network according to another embodiment of the present application.
  • FIG. 4 is a schematic interaction diagram of a method of switching a network according to still another embodiment of the present application.
  • FIG. 5 is a schematic interaction diagram of a method of switching a network according to still another embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of a terminal device according to another embodiment of the present application.
  • FIG. 9 is a schematic block diagram of a network device according to another embodiment of the present application.
  • system and “network” are used interchangeably herein.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the character "/" in this article generally indicates that the contextual object is an "or" relationship.
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • FIG. 1 shows a wireless communication system 100 to which an embodiment of the present application is applied.
  • the wireless communication system 100 can include an access network device 110.
  • Access network device 100 can be a device that communicates with a terminal device.
  • Access network device 100 can provide communication coverage for a particular geographic area and can communicate with terminal devices (e.g., UEs) located within the coverage area.
  • terminal devices e.g., UEs
  • the access network device 100 may be an evolved base station (eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (CRAN).
  • eNB evolved base station
  • CRAN cloud radio access network
  • the network device may be a relay station, an access point, an in-vehicle device, a wearable device, a network side device in a future 5G network, or a network device in a publicly available Public Land Mobile Network (PLMN).
  • PLMN Public Land Mobile Network
  • the wireless communication system 100 also includes at least one terminal device 120 located within the coverage of the access network device 110.
  • Terminal device 120 can be mobile or fixed.
  • the terminal device 120 may refer to an access terminal, a user equipment (User Equipment, UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, and a wireless communication.
  • Letter device user agent or user device.
  • the access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), with wireless communication.
  • the communication system 100 may further include at least two core network devices, for example, the core network device 130 and the core network device 140 shown in FIG. 1, and the core network device 130 and the core network device 140 may be the same type of core network, or It may also be a different type of core network.
  • the core network device 130 is a core network device of an LTE system, for example, an EPC
  • the core network device 140 may be a core network device or the like in a 5G system.
  • different core networks may share access network devices, that is, the access network devices may communicate with core network devices of different networks.
  • the 5G system or network may also be referred to as a New Radio (NR) system or a network.
  • NR New Radio
  • the terminal device needs to be switched from the source core network to the target core network, and the source core network and the target core network may be the same type of core network, or may be different types of core networks.
  • the source core network is an EPC
  • the target core network is a core network of a 5G system (abbreviated as 5GC).
  • the terminal device is first released between the EPC and the source cell.
  • the Protocol Data Unit (PDN) is connected, and then establishes a PDU session with the 5GC and the target cell.
  • the terminal device releases the old RRC connection and establishes a new one.
  • the RRC may cause additional signaling overhead.
  • the embodiment of the present application provides a method for switching a network, which can reduce signaling overhead when the network is switched.
  • FIG. 2 is a schematic flowchart of a method 200 for switching a network provided by an embodiment of the present application.
  • the method 200 can be applied to the wireless communication system 100 described above, but the embodiment of the present application is not limited thereto.
  • the method 200 includes the following:
  • the terminal device determines that it is required to switch from the first core network to the second core network.
  • the first core network ie, the source core network
  • the second core network ie, the target core network
  • shares the access network device that is, the access network device can communicate with the core network device of the first core network and the second core network, or the terminal device can be considered as Before and after the handover, the access network that is accessed does not change (or the serving cell does not change).
  • the first core network and the second core network may be core networks of the same type, or may be different types of core networks, for example, the first core network.
  • the core network of the LTE system that is, the EPC
  • the second core network is the core network of the 5G system
  • the first core network is the core network of the 5G system
  • the second core network is the EPC, etc.
  • the embodiment does not limit this.
  • the determining, by the terminal device, that the switching from the first core network to the second core network is determined by the terminal device itself, or may be determined based on a triggering instruction of the network device, where
  • the network device may be a core network device, or may be an access network device, and the triggering command may be S1 signaling, N2/N3 signaling, or RRC signaling, and the like.
  • S210 may include:
  • the terminal device determines that it is required to switch from the first core network to the second core network according to current service requirements.
  • the terminal device may determine that the second core network that supports the current service requirement needs to be switched when the currently accessed first core network does not support the current service requirement.
  • the first core network currently accessed by the terminal device is 5GC, and the terminal device wants to transmit (Multimedia Broadcast and Multicast Service (MBMS) service, Vehicle to Vehicle (V2V)).
  • MBMS Multimedia Broadcast and Multicast Service
  • V2V Vehicle to Vehicle
  • the terminal device determines that it needs to switch to the EPC to support the current service requirement of the terminal device.
  • the terminal device is based on The switching of service requirements may also occur in the same type of core network.
  • the first core network is 5GC
  • the second core network is also 5GC.
  • the first core network does not support the first service that the terminal device currently wants to access, and the second core network supports the first service, where the terminal device can determine that the first core network needs to be Switching to the second core network.
  • the method 200 further includes:
  • the terminal device acquires system information of the second core network.
  • the terminal device may receive a broadcast message sent by the access network device, and obtain system information of the second core network from the broadcast message. Or the terminal device requests to acquire system information of the second core network by sending RRC signaling to the access network device.
  • the terminal device may obtain, according to the system information of the second core network, a protocol layer version (for example, a protocol version of the PDCP layer, and the like) corresponding to the second core network, and configuration information of the RRC layer.
  • a protocol layer version for example, a protocol version of the PDCP layer, and the like
  • the system information of the second core network may be carried in a broadcast message sent by the access network device, and the terminal device may obtain system information of the second core network by receiving a broadcast message, or The terminal device may also acquire system information of the second core network by sending RRC signaling to the access network device.
  • the terminal device may obtain the service type information supported by the second core network according to the broadcast message sent by the access network device, so that the terminal device determines which core network to switch to.
  • S210 may include:
  • the terminal device determines that the first core network needs to be handed over to the second core network, when the triggering instruction of the network device is received, where the triggering instruction is used to notify the terminal device from the The first core network switches to the second core network.
  • the terminal device may perform network switching based on the triggering instruction of the network device, and the triggering instruction may be used to instruct the terminal device to switch from the first core network to the second core network.
  • the triggering instruction may be S1 signaling, N2/N3 signaling, or RRC signaling, etc., that is, the terminal device may trigger an instruction in S1 signaling, N2/N3 signaling, or RRC signaling.
  • the triggering instruction of the network device may be sent based on a specific redirection policy.
  • the network device is a core network device, and the core network device may determine, according to load information of the core network side, that the terminal device needs to be handed over from the first core network to the first core network.
  • the network device is an access network device, the access network device may determine, according to load information on the access network side, that the terminal device needs to be handed over from the first core network to the first core network.
  • the terminal device performs protocol layer configuration according to the core network types of the first core network and the second core network.
  • the terminal device may perform related configuration of the protocol layer according to whether the core network types of the first core network and the second core network are the same. For example, if the first core network and the The core network type of the second core network is the same, that is, before and after the handover, the access network is unchanged (or the serving cell is unchanged), and the core network type is unchanged. In this case, the terminal device does not need to perform wireless. Reconfiguration of the Link Control (RLC) layer, the Media Access Control (MAC) layer, and the Physical Layer (PHY), and the terminal device does not need to update the packet data convergence protocol. (Packet Data Convergence Protocol, PDCP) layer, and protocol version of the Radio Resource Control (RRC) layer. Optionally, the terminal device may need to update some configuration information of the PDCP layer or the RRC layer, for example, Key, etc.
  • RLC Link Control
  • MAC Media Access Control
  • PHY Physical Layer
  • the terminal device does not need to update the packet data convergence protocol.
  • PDCP Packet Data Con
  • the terminal device needs to update a non-access stratum (NAS) entity, and may also trigger layer-to-layer interaction.
  • NAS non-access stratum
  • the NAS layer needs to notify the RRC layer to reconfigure the PDCP layer configuration, and add or delete.
  • S220 may include:
  • the terminal device updates the PDCP layer configuration corresponding to the packet data convergence protocol corresponding to the first core network to the second core network.
  • the PDCP layer is configured to update the protocol version of the PDCP layer corresponding to the first core network to the protocol version of the PDCP layer corresponding to the second core network, and update the RRC layer configuration corresponding to the first core network to An RRC layer configuration corresponding to the second core network, and switching the entity of the non-access stratum NAS from the first NAS entity supporting the first core network to the second NAS entity supporting the second core network.
  • the terminal device does not need to update the configurations of the RLC layer, the MAC layer, and the PHY, but only The following updates are required:
  • the terminal device needs to switch the NAS entity from the first NAS entity corresponding to the first core network to the second NAS entity corresponding to the second core network, for example, if the first core network is the core of the LTE system.
  • the second core network is a core network of a 5G system, and the terminal device needs to switch the EPC NAS entity to a 5GC NAS; or, if the first core network is a core network of a 5G system, the second core
  • the network is the core network of the LTE system, and the terminal device needs to switch the 5GC NAS entity to the EPC NAS.
  • the terminal device needs to update the protocol version of the PDCP, that is, the protocol version of the PDCP layer corresponding to the first core network is updated to the protocol version of the PDCP layer corresponding to the second core network.
  • the terminal device may update the LTE PDCP to the NR PDCP, where the LTE PDCP is The protocol version of the PDCP layer corresponding to the first core network, where the NR PDCP is a protocol version of the PDCP layer corresponding to the second core network.
  • the terminal device updates the NR PDCP to an LTE PDCP, where the NR PDCP is the a protocol version of the PDCP layer corresponding to the first core network, where the LTE PDCP is a protocol version of the PDCP layer corresponding to the second core network.
  • the terminal device needs to perform reconfiguration of the PDCP layer, so that the configuration of the updated PDCP layer can be adapted to the second core network.
  • the terminal device may further perform an update of the RRC layer configuration.
  • the first core network is a core network of the LTE system
  • the second core network is The core network of the NR system
  • the RRC layer configuration of the NR system supports the Service Data Adaptation Layer (SDAP) function, and the User Plane (UP) function. Therefore, the core network of the LTE system is switched to the 5G.
  • the terminal device needs to add a configuration of the SDAP layer and a configuration of the UP function.
  • the terminal device needs to delete the configuration of the SDAP layer and the configuration of the UP function.
  • the terminal device in a case where the access network before and after the handover of the terminal device does not change, and the core network type changes, the terminal device may only need to perform PDCP layer and RRC reconfiguration. Without reconfiguration of the RLC layer, the MAC layer, and the PHY layer; in the case where the access network before and after the handover of the terminal device does not change, and the core network type does not change, the terminal device may not need to update the PDCP.
  • the protocol version of the layer and the RRC does not need to be reconfigured by the RLC layer, the MAC layer, and the PHY layer, which is advantageous for reducing the signaling overhead of the terminal device when performing network handover.
  • the method 200 further includes:
  • the terminal device sends a NAS message to the second core network, where the NAS message is used to trigger the second core network to initiate a protocol data unit PDU session establishment process.
  • the terminal device may send the second core to the second core.
  • the heart network sends a NAS message, triggering the second core network to initiate a PDU session establishment process or a PDN connection establishment process.
  • FIG. 3 is a schematic flowchart of a method 300 for switching a network according to another embodiment of the present application.
  • the method 300 may be performed by an access network device or a core network device in the communication system shown in FIG. 1, as shown in FIG.
  • the method 300 includes the following:
  • the network device determines that the terminal device needs to be switched from the first core network to the second core network.
  • the network device sends a triggering instruction to the terminal device, where the triggering instruction is used to notify the terminal device to switch from the first core network to the second core network.
  • the determining, by the network device, that the terminal device needs to be switched from the first core network to the second core network includes:
  • the network device determines that the terminal device needs to be handed over from the first core network to the second core network according to a current load situation.
  • the network device is a core network device of the first core network, and the network device may determine, when the load of the first core network is heavy, that the terminal device needs to be switched from the first core network to the The second core network, or the network device is an access network device, and the access network device may determine that the terminal device needs to be from the first core network when the load of the first core network is heavy.
  • the access network device may also obtain a load condition of a core network to which the connection is established, so that the access network device may perform the loading according to a load condition of the core network.
  • the terminal device performs network switching.
  • the network device is an access network device or a core network device.
  • the triggering instruction is S1 signaling, N2/N3 signaling, or radio resource control RRC signaling.
  • the method embodiment of the present application is described in detail from the perspective of the terminal device and the network device, and the following is a description of the embodiment according to the present application from the perspective of device interaction with reference to FIG. 4 and FIG. The method of switching networks.
  • FIG. 4 and FIG. 5 are an example of the core network (ie, 5GC) that is switched from the core network (ie, EPC) of the LTE system to the core network (ie, 5GC) of the LTE system, but the embodiment of the present application is not limited. herein.
  • the core network that is currently connected to the terminal device is an EPC, that is, the source core network is the first core network, and the target core network, that is, the second core network is 5GC, that is, before and after the handover, the core network.
  • EPC electronic circuitry
  • target core network that is, the second core network
  • 5GC 5GC
  • FIG. 4 the difference between FIG. 4 and FIG. 5 is that, in FIG. 4, the network switching performed by the terminal device is triggered by the terminal device.
  • the network switching performed by the terminal device is triggered by the network device, and the network device may be a core network device or access. Network equipment.
  • the method 20 can include the following:
  • the terminal device determines that it is required to switch from the first core network to the second core network
  • the terminal device may determine that it is required to switch from the first core network to the second core network according to factors such as its own service requirements.
  • the terminal device After the terminal device determines that it needs to switch from the first core network to the second core network, further, in S22, the terminal device switches the NAS entity from the EPC NAS entity to the 5GC NAS entity.
  • the terminal device may further perform reconfiguration of the PDCP layer and the RRC layer. Before performing the reconfiguration of the PDCP layer and the RRC layer, in S23, the terminal device acquires system information of the 5GC. Specifically, the terminal device may receive the broadcast message or send the RRC signaling from the access network device. Get system information of 5GC.
  • the system information of the 5GC includes the protocol version of the PDCP layer and the related configuration information of the RRC layer.
  • the protocol version of the PDCP layer is the protocol version of the PDCP layer corresponding to the 5GC.
  • the implementation process of S23 may be preceded by S21, or may be after S21.
  • the above information needs to be obtained first.
  • the terminal device updates the protocol version and configuration of the PDCP layer, and adds the configuration of the SDAP layer and the configuration of the UP function (for example, integrity protection) at the RRC layer.
  • the terminal device may send a NAS message to the 5GC to trigger the 5GC to initiate a PDU session establishment process.
  • the method 30 can include the following:
  • the network switching performed by the terminal device is based on a triggering instruction of the network device.
  • the EPC determines that the terminal device needs to switch from the first core network to the second core network
  • the EPC device may determine, according to its own load information, that the terminal device needs to be handed over from the first core network to the second core network.
  • the EPC sends a triggering instruction to the terminal device, to instruct the terminal device to switch from the first core network to the second core network.
  • the triggering instruction S1 signaling, or N2/N3 signaling is used for an instruction or message for communication between the terminal device and the core network.
  • the network switching of the terminal device may be performed based on the trigger of the access network device.
  • the ng-eNB determines that the terminal device needs to be switched from the first core network to the second core.
  • network For example, the ng-eNB may determine, according to its own load information, that the terminal device needs to be handed over from the first core network to the second core network.
  • the ng-eNB sends a triggering instruction to the terminal device, instructing the terminal device to switch from the first core network to the second core network.
  • the triggering command may be RRC.
  • the signaling or the message used for the communication between the terminal device and the access network device is not limited in this embodiment of the present application.
  • the terminal device After receiving the triggering instruction of the EPC or the ng-eNB, the terminal device determines that the first core network needs to be handed over to the second core network. Further, in S35, the terminal device sends the NAS entity from the EPC NAS. The entity switches to the 5GC NAS entity.
  • the terminal device may further perform reconfiguration of the PDCP layer and the RRC layer. Before performing the reconfiguration of the PDCP layer and the RRC layer, in S36, the terminal device acquires system information of the 5GC. Specifically, the terminal device may receive the broadcast message or send the RRC signaling from the access network device. Get system information of 5GC.
  • the system information of the 5GC includes the protocol version of the PDCP layer and the related configuration information of the RRC layer.
  • the protocol version of the PDCP layer is the protocol version of the PDCP layer corresponding to the 5GC.
  • the implementation process of S36 may be preceded by S31 to S34, or may be after S31 to S34, which is not limited by the embodiment of the present application.
  • S31 to S34 the implementation process of S36 may be preceded by S31 to S34, or may be after S31 to S34, which is not limited by the embodiment of the present application.
  • the terminal device updates the protocol version and configuration of the PDCP layer, and adds a configuration of the SDAP layer and a configuration of the UP function (for example, integrity protection) at the RRC layer.
  • the terminal device may send a NAS message to the 5GC to trigger the 5GC to initiate a PDU session establishment process.
  • the embodiment of the method of the present application is described in detail below with reference to FIG. 2 to FIG. 5 .
  • the device embodiment of the present application is described in detail below with reference to FIG. 6 to FIG. 9 . It should be understood that the device embodiment and the method embodiment correspond to each other, similarly. The description of the method can be referred to the method embodiment.
  • FIG. 6 shows a schematic block diagram of a terminal device 400 in accordance with an embodiment of the present application.
  • the terminal device 400 includes:
  • a determining module 410 configured to determine that a switch from the first core network to the second core network is required
  • the configuration module 420 is configured to perform protocol layer configuration according to the core network types of the first core network and the second core network.
  • the determining module 410 is specifically configured to:
  • the determining module 410 is specifically configured to:
  • Determining that a handover from the first core network to the second core network is determined, where the triggering instruction is used to notify the terminal device from the first core network. Switching to the second core network.
  • the terminal device 400 further includes:
  • the first receiving module is configured to receive the triggering command sent by the network device.
  • the network device is an access network device or a core network device.
  • the triggering instruction is S1 signaling, N2/N3 signaling, or radio resource control RRC signaling.
  • the terminal device further includes:
  • an obtaining module configured to acquire system information of the second core network.
  • the terminal device 400 further includes:
  • the second receiving module is configured to receive a broadcast message sent by the access network device, and obtain system information of the second core network from the broadcast message.
  • the terminal device 400 further includes:
  • a first sending module configured to send first RRC signaling to the access network device
  • a third receiving module configured to receive second RRC signaling that is returned by the access network device
  • the obtaining module is specifically configured to:
  • the configuration module 420 is specifically configured to:
  • the PDCP layer configuration corresponding to the packet data convergence protocol corresponding to the first core network is updated to the PDCP corresponding to the second core network.
  • a layer configuration the protocol version of the PDCP layer corresponding to the first core network is updated to a protocol version of the PDCP layer corresponding to the second core network, and the RRC layer configuration corresponding to the first core network is updated to the The RRC layer configuration corresponding to the second core network, and the entity of the non-access stratum NAS is switched from the first NAS entity supporting the first core network to the second NAS entity supporting the second core network.
  • the configuration module 420 is further configured to:
  • the reconfiguration of the radio link control RLC layer, the medium access control MAC layer, and the physical layer PHY is not performed.
  • the configuration module 420 is specifically configured to:
  • the LTE PDCP is a protocol version of the PDCP layer corresponding to the first core network
  • the NR PDCP is a protocol version of the PDCP layer corresponding to the second core network.
  • the configuration module 420 is specifically configured to:
  • the configuration of the service data is adapted to the SDAP layer, and the configuration of the user plane UP function is added.
  • the configuration module 420 is specifically configured to:
  • the NR PDCP is a protocol version of the PDCP layer corresponding to the first core network
  • the LTE PDCP is a protocol version of the PDCP layer corresponding to the second core network.
  • the configuration module 420 is specifically configured to:
  • the configuration of the SDAP layer is deleted, and the configuration of the user plane UP function is deleted.
  • the configuration module 420 is specifically configured to:
  • the PDCP layer of the terminal device and the protocol version of the RRC layer are not updated.
  • the configuration module 420 is specifically configured to:
  • the terminal device 400 further includes:
  • a second sending module configured to send a request message to the access network device, where the request message is used to request to obtain a PDCP layer configuration corresponding to the second core network and a protocol version of the PDCP layer.
  • the terminal device 400 further includes:
  • a third sending module configured to send a NAS message to the second core network, where the NAS message is used to trigger the second core network to initiate a protocol data unit PDU session establishment process.
  • terminal device 400 may correspond to the terminal device in the method embodiment of the present application, and the foregoing and other operations and/or functions of the respective units in the terminal device 400 respectively implement the method shown in FIG. 2 . 200, or the method 20 shown in FIG. 4, or the corresponding process of the terminal device in the method 30 shown in FIG. 5, for brevity, no further details are provided herein.
  • FIG. 7 shows a schematic block diagram of a network device 500 in accordance with an embodiment of the present application.
  • the network device 500 includes:
  • a determining module 510 configured to determine that the terminal device needs to be switched from the first core network to the second core network
  • the communication module 520 is configured to send a triggering instruction to the terminal device, where the triggering instruction is used to notify the terminal device to switch from the first core network to the second core network.
  • the determining module 510 is specifically configured to:
  • the network device is an access network device or a core network device.
  • the triggering instruction is S1 signaling, N2/N3 signaling, or radio resource control RRC signaling.
  • the network device 500 may correspond to the access network device in the method embodiment of the present application, and the foregoing and other operations and/or functions of the respective units in the network device 500 are respectively implemented in FIG.
  • the corresponding process of the method 300, or the method 20 shown in FIG. 4, or the network device in the method 30 shown in FIG. 5 is omitted here for brevity.
  • the embodiment of the present application further provides a terminal device 600, which may be the terminal device 400 in FIG. 6, which can be used to perform the method 200 in FIG. 2, or as shown in FIG. The method 20, or the content of the terminal device corresponding to the method 30 shown in FIG.
  • the terminal device 600 includes an input interface 610, an output interface 620, a processor 630, and a memory 640.
  • the input interface 610, the output interface 620, the processor 630, and the memory 640 can be connected through a bus system.
  • the memory 640 is used to store programs, instructions or code.
  • the processor 630 is configured to execute a program, an instruction or a code in the memory 640 to control the input interface 610 to receive a signal, control the output interface 620 to send a signal, and complete the operations in the foregoing method embodiments.
  • the processor 630 may be a central processing unit ("CPU"), and the processor 630 may also be other general-purpose processors, digital signal processors (DSPs). , an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, and the like.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 640 can include read only memory and random access memory and provides instructions and data to the processor 630. A portion of the memory 640 can also include a non-volatile random access memory. For example, the memory 640 can also store information of the device type.
  • each content of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 630 or an instruction in a form of software.
  • the content of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 640, and the processor 630 reads the information in the memory 640 and combines the hardware to complete the contents of the above method. To avoid repetition, it will not be described in detail here.
  • the first receiving module, the second receiving module, the third receiving module, and the first sending module, the second sending module, and the third sending module in the terminal device 400 shown in FIG. 6 can be used in FIG. 8.
  • the input interface 610 and the output interface 620 are implemented.
  • the determining module 410, the configuration module 420, and the obtaining module in the terminal device 400 shown in FIG. 6 can use the processor 630 of FIG. achieve.
  • the embodiment of the present application further provides a network device 700, which may be the network device 500 in FIG. 7, which can be used to perform the method 300 in FIG. 3, or as shown in FIG. Method 20, or the content of the network device corresponding to method 30 shown in FIG.
  • the network device 700 includes an input interface 710, an output interface 720, a processor 730, and a memory 740.
  • the input interface 710, the output interface 720, the processor 730, and the memory 740 can be connected by a bus system.
  • the memory 740 is configured to store programs, instructions or code.
  • the processor 730 is configured to execute a program, an instruction or a code in the memory 740 to control the input interface 710 to receive a signal, control the output interface 720 to send a signal, and complete the operations in the foregoing method embodiments.
  • the processor 730 may be a central processing unit (“CPU"), and the processor 730 may also be other general-purpose processors, digital signal processors (DSPs). , an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, and the like.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 740 can include read only memory and random access memory and provides instructions and data to the processor 730. A portion of the memory 740 can also include a non-volatile random access memory. For example, the memory 740 can also store information of the device type.
  • each content of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 730 or an instruction in a form of software.
  • the content of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 740, and the processor 730 reads the information in the memory 740 and combines its hardware to perform the contents of the above method. To avoid repetition, it will not be described in detail here.
  • the communication module 520 in the network device 500 shown in FIG. 7 can be implemented by using the input interface 710 and the output interface 720 of FIG. 9.
  • the determining module 510 in the network device 500 can use the processor 730 of FIG. achieve.
  • the embodiment of the present application further provides a computer readable storage medium storing one or more programs, the one or more programs including instructions, when the portable electronic device is included in a plurality of applications When executed, the portable electronic device can be caused to perform the method of the embodiment shown in Figures 2 through 5.
  • the embodiment of the present application also proposes a computer program comprising instructions which, when executed by a computer, enable the computer to execute the corresponding flow of the method of the embodiment shown in Figures 2 to 5.
  • the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the execution order of each process should be determined by its function and internal logic, and should not be applied to this application.
  • the implementation of the embodiments constitutes any limitation.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated in one unit. In the unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

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

Abstract

本申请实施例提供了一种切换网络的方法、终端设备和网络设备,能够降低核心网切换时的信令开销。该方法包括:终端设备确定需要从第一核心网切换至第二核心网;所述终端设备根据所述第一核心网和所述第二核心网的核心网类型,进行协议层的配置。

Description

切换网络的方法、终端设备和网络设备 技术领域
本申请涉及通信领域,并且更具体地,涉及一种切换网络的方法、终端设备和网络设备。
背景技术
随着5G技术的发展,长期演进(Long Term Evolution,LTE)系统,将支持通用陆地无线接入(Evolved-Universal Terrestrial Radio Access,E-UTRA)系统接入到5G核心网中,或者说将LTE系统接入到5G核心网中,是从4G网络到5G网络的过渡和混合部署方案。
在这种网络中,同一个LTE小区中的终端设备,可以只接入演进分组核心网络(Evolved Packet Core,EPC),或只接入5G核心网,或者也可以同时接入EPC和5G核心网。
在一些情况下,所述终端设备需要从一个核心网切换至另一核心网,其中,涉及大量的信令交互过程,因此,对于终端设备而言,如何实现核心网的切换,以降低信令开销是一项亟需解决的问题。
发明内容
本申请实施例提供一种切换网络的方法、终端设备和网络设备,能够降低核心网切换时的信令开销。
第一方面,提供了一种切换网络的方法,包括:
终端设备确定需要从第一核心网切换至第二核心网;
所述终端设备根据所述第一核心网和所述第二核心网的核心网类型,进行协议层的配置。
结合第一方面,在第一方面的某些实现方式中,所述终端设备确定需要从第一核心网切换至第二核心网,包括:
所述终端设备根据当前的业务需求,确定需要从所述第一核心网切换至所述第二核心网。
结合第一方面,在第一方面的某些实现方式中,所述终端设备确定需要从第一核心网切换至第二核心网,包括:
所述终端设备在接收到网络设备的触发指令的情况下,确定需要从所述第一核心网切换至所述第二核心网,其中,所述触发指令用于通知所述终端设备从所述第一核心网切换至所述第二核心网。
结合第一方面,在第一方面的某些实现方式中,所述方法还包括:
所述终端设备接收所述网络设备发送的所述触发指令。
结合第一方面,在第一方面的某些实现方式中,所述网络设备为接入网设备或核心网设备。
结合第一方面,在第一方面的某些实现方式中,所述触发指令为S1信令、N2/N3信令或无线资源控制RRC信令。
结合第一方面,在第一方面的某些实现方式中,若所述第一核心网和所述第二核心网为不同类型的核心网,所述方法还包括:
所述终端设备获取所述第二核心网的系统信息。
结合第一方面,在第一方面的某些实现方式中,所述终端设备获取所述第二核心网的系统信息,包括:
所述终端设备接收接入网设备发送的广播消息,从所述广播消息中获取所述第二核心网的系统信息。
结合第一方面,在第一方面的某些实现方式中,所述终端设备获取所述第二核心网的系统信息,包括:
所述终端设备向接入网设备发送第一RRC信令;
所述终端设备接收所述接入网设备回复的第二RRC信令,从所述第二RRC信令中获取所述第二核心网的系统信息。
结合第一方面,在第一方面的某些实现方式中,所述终端设备根据所述第一核心网和所述第二核心网的核心网类型,进行协议层的配置,包括:
若所述第一核心网和所述第二核心网为不同类型的核心网,所述终端设备将所述第一核心网对应的分组数据汇聚协议PDCP层配置更新为所述第二核心网对应的PDCP层配置,将所述第一核心网对应的PDCP层的协议版本更新为所述第二核心网对应的PDCP层的协议版本,将所述第一核心网对应的RRC层配置更新为所述第二核心网对应的RRC层配置,以及将非接入层NAS的实体从支持所述第一核心网的第一NAS实体切换为支持所述第二核心网的第二NAS实体。
结合第一方面,在第一方面的某些实现方式中,所述方法还包括:
所述终端设备不进行无线链路控制RLC层、媒体接入控制MAC层以及物理层PHY的重新配置。
因此,本申请实施例的切换网络的方法,在终端设备切换前后的接入网不发生变化,并且核心网类型发生变化的情况下,所述终端设备可以仅进行PDCP层和RRC的重新配置,而不需要进行RLC层、MAC层和PHY层的重新配置,有利于降低终端设备在进行网络切换时的信令开销。
结合第一方面,在第一方面的某些实现方式中,若所述第一核心网为长期演进LTE系统的核心网,所述第二核心网为新无线NR系统的核心网,所述将所述第一核心网对应的PDCP层的协议版本更新为所述第二核心网对应的PDCP层的协议版本,包括:
所述终端设备将LTE PDCP更新为NR PDCP,其中,所述LTE PDCP为所述第一核心网对应的PDCP层的协议版本,所述NR PDCP为所述第二核心网对应的PDCP层的协议版本。
结合第一方面,在第一方面的某些实现方式中,若所述第一核心网为LTE系统的核心网,所述第二核心网为NR系统的核心网,所述将所述第一核心网对应的RRC层配置更新为所述第二核心网对应的RRC层配置,包括:
所述终端设备在所述第一核心网对应的RRC层配置的基础上,新增业务数据适配SDAP层的配置,并新增用户平面UP功能的配置。
结合第一方面,在第一方面的某些实现方式中,若所述第一核心网为NR系统的核心网,所述第二核心网为LTE系统的核心网,所述将所述第一核心网对应的PDCP层的协议版本更新为所述第二核心网对应的PDCP层的协议版本,包括:
所述终端设备将NR PDCP更新为LTE PDCP,其中,所述NR PDCP为所述第一核心网对应的PDCP层的协议版本,所述LTE PDCP为所述第二核心网对应的PDCP层的协议版本。
结合第一方面,在第一方面的某些实现方式中,若所述第一核心网为NR系统的核心网,所述第二核心网为LTE系统的核心网,所述将所述第一核心网对应的RRC层配置更新为所述第二核心网对应的RRC层配置,包括:
所述终端设备在所述第一核心网对应的RRC层配置的基础上,删除SDAP层的配置,并删除用户平面UP功能的配置。
结合第一方面,在第一方面的某些实现方式中,所述终端设备根据所述 第一核心网和所述第二核心网的核心网类型,进行协议层的配置,包括:
若所述第一核心网和所述第二核心网为同一类型的核心网,所述终端设备不更新所述终端设备的PDCP层以及RRC层的协议版本。
结合第一方面,在第一方面的某些实现方式中,所述终端设备根据所述第一核心网和所述第二核心网的核心网类型,进行协议层的配置,包括:
将所述第一核心网对应的PDCP层的配置更新为所述第二核心网对应的PDCP层的配置,和/或将所述第一核心网对应的RRC层的配置更新为所述第二核心网对应的RRC层的配置。
因此,本申请实施例的切换网络的方法,在终端设备切换前后的接入网不发生变化,并且核心网类型不发生变化的情况下,所述终端设备可以不需要更新PDCP层和RRC的协议版本,并且不需要重新配置RLC层、MAC层和PHY层,有利于降低终端设备在进行网络切换时的信令开销。
结合第一方面,在第一方面的某些实现方式中,所述方法还包括:
所述终端设备向接入网设备发送请求消息,所述请求消息用于请求获取所述第二核心网对应的PDCP层配置和PDCP层的协议版本。
结合第一方面,在第一方面的某些实现方式中,所述方法还包括:
所述终端设备向所述第二核心网发送NAS消息,所述NAS消息用于触发所述第二核心网发起协议数据单元PDU会话建立过程。
第二方面,提供了一种切换网络的方法,包括:
网络设备确定终端设备需要从第一核心网切换至第二核心网;
所述网络设备向所述终端设备发送触发指令,所述触发指令用于通知所述终端设备从所述第一核心网切换至所述第二核心网。
结合第二方面,在第二方面的某些实现方式中,所述网络设备确定终端设备需要从第一核心网切换至第二核心网,包括:
所述网络设备根据当前的负载情况,确定所述终端设备需要从所述第一核心网切换至所述第二核心网。
结合第二方面,在第二方面的某些实现方式中,所述网络设备为接入网设备或核心网设备。
结合第二方面,在第二方面的某些实现方式中,所述触发指令为S1信令、N2/N3信令或无线资源控制RRC信令。
第三方面,提供了一种终端设备,用于执行上述第一方面或第一方面的 任意可能的实现方式中的方法。具体地,该终端设备包括用于执行上述第一方面或第一方面的任意可能的实现方式中的方法的单元。
第四方面,提供了一种网络设备,用于执行上述第二方面或第二方面的任意可能的实现方式中的方法。具体地,该网络设备包括用于执行上述第二方面或第二方面的任意可能的实现方式中的方法的单元。
第五方面,提供了一种终端设备,该终端设备包括:存储器、处理器、输入接口和输出接口。其中,存储器、处理器、输入接口和输出接口通过总线系统相连。该存储器用于存储指令,该处理器用于执行该存储器存储的指令,用于执行上述第一方面或第一方面的任意可能的实现方式中的方法。
第六方面,提供了一种网络设备,该网络设备包括:存储器、处理器、输入接口和输出接口。其中,存储器、处理器、输入接口和输出接口通过总线系统相连。该存储器用于存储指令,该处理器用于执行该存储器存储的指令,用于执行上述第二方面或第二方面的任意可能的实现方式中的方法。
第七方面,提供了一种计算机存储介质,用于储存为执行上述第一方面或第一方面的任意可能的实现方式中的方法所用的计算机软件指令,其包含用于执行上述方面所设计的程序。
第八方面,提供了一种计算机存储介质,用于储存为执行上述第二方面或第二方面的任意可能的实现方式中的方法所用的计算机软件指令,其包含用于执行上述方面所设计的程序。
第九方面,提供了一种包括指令的计算机程序产品,当其在计算机上运行时,使得计算机执行上述第一方面或第一方面的任一可选的实现方式中的方法。
第十方面,提供了一种包括指令的计算机程序产品,当其在计算机上运行时,使得计算机执行上述第二方面或第二方面的任一可选的实现方式中的方法。
附图说明
图1是根据本申请实施例的通信系统的示意性图。
图2是根据本申请实施例的切换网络的方法的示意性流程图。
图3是根据本申请另一实施例的切换网络的方法的示意性流程图。
图4是根据本申请再一实施例的切换网络的方法的示意性交互图。
图5是根据本申请再一实施例的切换网络的方法的示意性交互图。
图6是根据本申请实施例的终端设备的示意性框图。
图7是根据本申请实施例的网络设备的示意性框图。
图8是根据本申请另一实施例的终端设备的示意性框图。
图9是根据本申请另一实施例的网络设备的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行描述。
应理解,本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或”的关系。
本申请实施例的技术方案可以应用于各种通信系统,例如:长期演进(Long Term Evolution,简称为“LTE”)系统、LTE频分双工(Frequency Division Duplex,简称为“FDD”)系统、LTE时分双工(Time Division Duplex,简称为“TDD”)未来的5G系统等。
图1示出了本申请实施例应用的无线通信系统100。该无线通信系统100可以包括接入网设备110。接入网设备100可以是与终端设备通信的设备。接入网设备100可以为特定的地理区域提供通信覆盖,并且可以与位于该覆盖区域内的终端设备(例如UE)进行通信。可选地,该接入网设备100可以是LTE系统中的演进型基站(Evolutional Node B,eNB或eNodeB),或者是云无线接入网络(Cloud Radio Access Network,CRAN)中的无线控制器,或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备、未来5G网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network,PLMN)中的网络设备等。
该无线通信系统100还包括位于接入网设备110覆盖范围内的至少一个终端设备120。终端设备120可以是移动的或固定的。可选地,终端设备120可以指接入终端、用户设备(User Equipment,UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通 信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol,SIP)电话、无线本地环路(Wireless Local Loop,WLL)站、个人数字处理(Personal Digital Assistant,PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、未来5G网络中的终端设备或者未来演进的PLMN中的终端设备等。
该通信系统100还可以包括至少两个核心网设备,例如,图1所示的核心网设备130和核心网设备140,该核心网设备130和核心网设备140可以为同一类型的核心网,或者也可以为不同类型的核心网,例如,所述核心网设备130为LTE系统的核心网设备,例如,EPC,所述核心网设备140可以为5G系统中的核心网设备等。
需要说明的是,在本申请实施例中,不同的核心网络可以共享接入网设备,即接入网设备可以跟不同网络的核心网设备进行通信。
可选地,在本申请实施例中,5G系统或网络还可以称为新无线(New Radio,NR)系统或网络。
如上文所述,在一些情况下,终端设备需要从源核心网切换至目标核心网,所述源核心网和所述目标核心网可以为同一类型的核心网,也可以为不同类型的核心网,例如,源核心网为EPC,目标核心网为5G系统的核心网(简称5GC),当需要从EPC切换至5GC时,在现有技术中,终端设备会首先释放与EPC以及源小区之间的协议数据单元(Protocol Data Unit,PDN)连接,然后建立与5GC和目标小区之间的PDU会话(session),但是,如果切换前后服务小区没有发生变化,终端设备释放旧的RRC连接,建立新的RRC可能会造成额外的信令开销。
有鉴于此,本申请实施例提出一种切换网络的方法,能够减小网络切换时的信令开销。
图2示意性地示出了本申请实施例提供的切换网络的方法200的示意性流程图。该方法200可以应用于上述无线通信系统100,但本申请实施例不限于此。
如图2所示,该方法200包括以下内容:
S210,终端设备确定需要从第一核心网切换至第二核心网。
需要说明的是,在本申请实施例中,所述第一核心网(即源核心网)和 所述第二核心网(即目标核心网)共享接入网设备,即接入网设备可以与第一核心网和第二核心网的核心网设备进行通信,或者也可以认为所述终端设备在切换前后,接入的接入网不变(或者说,服务小区不变)。
可选地,在本申请实施例中,所述第一核心网和所述第二核心网可以为同一类型的核心网,或者也可以为不同类型的核心网,例如,所述第一核心网为LTE系统的核心网,即EPC,所述第二核心网为5G系统的核心网,或者,所述第一核心网为5G系统的核心网,所述第二核心网为EPC等,本申请实施例对此不作限定。
可选地,所述终端设备确定需要从所述第一核心网切换至所述第二核心网可以是所述终端设备自身确定的,或者也可以是基于网络设备的触发指令确定的,这里,网络设备可以为核心网设备,或者也可以为接入网设备,所述触发指令可以为S1信令、N2/N3信令或RRC信令等,本申请实施例对此不作限定。
可选地,作为一个实施例,S210可以包括:
所述终端设备根据当前的业务需求,确定需要从所述第一核心网切换至所述第二核心网。
具体地,所述终端设备可以在当前接入的第一核心网不支持当前的业务需求时,确定需要切换至支持当前业务需求的第二核心网。例如,所述终端设备当前接入的第一核心网为5GC,所述终端设备想要传输(广播多播业务(Multimedia Broadcast and Multicast Service,MBMS)业务、车辆到车辆(Vehicle to Vehicle,V2V)业务或车辆到其他设备(Vehicle to Everything,V2X)业务等5GC不支持的业务时,所述终端设备确定需要切换至EPC,以支持所述终端设备当前的业务需求。或者,所述终端设备基于业务需求的切换,也可以发生在同一类型的核心网中,例如,第一核心网为5GC,所述第二核心网也为5GC,但是,这两个核心网支持的业务类型存在差异,若所述第一核心网不支持所述终端设备当前想要接入的第一业务,所述第二核心网支持所述第一业务,那么所述终端设备可以确定需要从所述第一核心网切换至所述第二核心网。
可选地,在一些实施例中,若所述第一核心网和所述第二核心网的核心网类型不同,所述方法200还包括:
所述终端设备获取所述第二核心网的系统信息。
可选地,所述终端设备可以接收接入网设备发送的广播消息,从所述广播消息中获取所述第二核心网的系统信息。或所述终端设备通过向接入网设备发送RRC信令,请求获取所述第二核心网的系统信息。所述终端设备可以根据所述第二核心网的系统信息获取所述第二核心网对应的协议层版本(例如,PDCP层的协议版本等)和RRC层的配置信息。
也就是说,所述第二核心网的系统信息可以携带于所述接入网设备发送的广播消息中,所述终端设备可以通过接收广播消息获取所述第二核心网的系统信息,或者,所述终端设备也可以通过向接入网设备发送RRC信令的方法,获取所述第二核心网的系统信息。
可选地,所述终端设备也可以根据所述接入网设备发送的广播消息,获取所述第二核心网支持的业务类型信息,以便于所述终端设备决定切换至哪个核心网。
可选地,作为另一个实施例,S210可以包括:
所述终端设备在接收到网络设备的触发指令的情况下,确定需要从所述第一核心网切换至所述第二核心网,其中,所述触发指令用于通知所述终端设备从所述第一核心网切换至所述第二核心网。
也就是说,终端设备可以是基于网络设备的触发指令进行网络切换的,所述触发指令可以用于指示所述终端设备从所述第一核心网切换至所述第二核心网。可选地,所述触发指令可以为S1信令、N2/N3信令或RRC信令等,即所述终端设备可以在S1信令、N2/N3信令或RRC信令等触发指令的情况下,确定需要从所述第一核心网切换至所述第二核心网,进而进行协议层的相关配置。
可选地,所述网络设备的触发指令可以是基于特定的重定向策略发送的。例如,所述网络设备为核心网设备,所述核心网设备可以基于核心网侧的负载信息确定所述终端设备需要从第一核心网切换至所述第一核心网。或者,若所述网络设备为接入网设备,所述接入网设备可以基于接入网侧的负载信息确定所述终端设备需要从第一核心网切换至所述第一核心网。
S220,所述终端设备根据所述第一核心网和所述第二核心网的核心网类型,进行协议层的配置。
可选地,所述终端设备可以根据所述第一核心网和所述第二核心网的核心网类型是否相同,进行协议层的相关配置。例如,若所述第一核心网和所 述第二核心网的核心网类型相同,即切换前后,接入网不变(或者说,服务小区不变),并且核心网类型不变,这种情况下,所述终端设备不需要进行无线链路控制(Radio Link Control,RLC)层、媒体接入控制(Media Access Control,MAC)层和物理层(Physical Layer,PHY)的重新配置,同时所述终端设备也不需要更新分组数据汇聚协议(Packet Data Convergence Protocol,PDCP)层,以及无线资源控制(Radio Resource Control,RRC)层的协议版本,可选地,所述终端设备可能需要更新PDCP层或RRC层的一些配置信息,例如,秘钥等。
可选地,若所述第一核心网和所述第二核心网的核心网类型不同,即切换前后,接入网不变(或者说,服务小区不变),但是核心网类型改变,那么所述终端设备需要更新非接入层(Non Access Stratum,NAS)实体,同时也可以触发层与层之间的交互,例如,NAS层需要通知RRC层重配置PDCP层的配置,以及增加或删除一些RRC层的配置以支持新的核心网类型,以下,结合具体示例进行详细介绍。
可选地,在一个具体的实施例中,S220可以包括:
若所述第一核心网和所述第二核心网为不同类型的核心网,所述终端设备将所述第一核心网对应的分组数据汇聚协议PDCP层配置更新为所述第二核心网对应的PDCP层配置,将所述第一核心网对应的PDCP层的协议版本更新为所述第二核心网对应的PDCP层的协议版本,将所述第一核心网对应的RRC层配置更新为所述第二核心网对应的RRC层配置,以及将非接入层NAS的实体从支持所述第一核心网的第一NAS实体切换为支持所述第二核心网的第二NAS实体。
具体而言,若切换前后的核心网类型不同,即所述第一核心网和第二核心网的核心网类型不同,所述终端设备不需要更新RLC层、MAC层以及PHY的配置,而只需要如下几方面的更新:
第一方面,所述终端设备需要将NAS实体从第一核心网对应的第一NAS实体切换至第二核心网对应的第二NAS实体,例如,若所述第一核心网为LTE系统的核心网,所述第二核心网为5G系统的核心网,所述终端设备需要将EPC NAS实体切换为5GC NAS;或者,若所述第一核心网为5G系统的核心网,所述第二核心网为LTE系统的核心网,所述终端设备需要将5GC NAS实体切换为EPC NAS。
第二方面,所述终端设备需要进行PDCP的协议版本的更新,即将第一核心网对应的PDCP层的协议版本更新为第二核心网对应的PDCP层的协议版本。例如,若所述第一核心网为LTE系统的核心网,所述第二核心网为NR系统的核心网,所述终端设备可以将LTE PDCP更新为NR PDCP,其中,所述LTE PDCP为所述第一核心网对应的PDCP层的协议版本,所述NR PDCP为所述第二核心网对应的PDCP层的协议版本。或者,若所述第一核心网为NR系统的核心网,所述第二核心网为LTE系统的核心网,所述终端设备将NR PDCP更新为LTE PDCP,其中,所述NR PDCP为所述第一核心网对应的PDCP层的协议版本,所述LTE PDCP为所述第二核心网对应的PDCP层的协议版本。
第三方面,所述终端设备需要进行PDCP层的重新配置,以使得更新后的PDCP层的配置能够适配所述第二核心网。
可选地,若切换前后RRC层配置的功能不同,所述终端设备还可以进行RRC层配置的更新,例如,若所述第一核心网为LTE系统的核心网,所述第二核心网为NR系统的核心网,NR系统的RRC层配置支持业务数据适配层(Service Data Adaptation Layer,SDAP)功能,以及用户平面(User Plane,UP)功能,因此,从LTE系统的核心网切换至5G系统的核心网时,所述终端设备需要新增SDAP层的配置,以及UP功能的配置。反之,从NR系统的核心网切换至LTE系统的核心网时,所述终端设备需要删除SDAP层的配置,以及UP功能的配置。
因此,本申请实施例的切换网络的方法,在终端设备切换前后的接入网不发生变化,并且核心网类型发生变化的情况下,所述终端设备可以仅需要进行PDCP层和RRC的重新配置,而不需要进行RLC层、MAC层和PHY层的重新配置;在终端设备切换前后的接入网不发生变化,并且核心网类型不发生变化的情况下,所述终端设备可以不需要更新PDCP层和RRC的协议版本,并且不需要进行RLC层、MAC层和PHY层的重新配置,有利于降低终端设备在进行网络切换时的信令开销。
可选地,在一些实施例中,所述方法200还包括:
所述终端设备向所述第二核心网发送NAS消息,所述NAS消息用于触发所述第二核心网发起协议数据单元PDU会话建立过程。
具体地,在RRC层重新配置完成后,所述终端设备可以向所述第二核 心网发送NAS消息,触发所述第二核心网发起PDU会话建立过程或PDN连接建立过程。
上文结合图2,从终端设备的角度详细描述了根据本申请实施例的切换网络方法,下文结合图3,从网络设备的角度详细描述根据本申请另一实施例的切换网络方法。应理解,网络设备侧的描述与终端设备侧的描述相互对应,相似的描述可以参见上文,为避免重复,此处不再赘述。
图3是根据本申请另一实施例的切换网络的方法300的示意性流程图,该方法300可以由图1所示的通信系统中的接入网设备或核心网设备执行,如图3所示,该方法300包括如下内容:
S310,网络设备确定终端设备需要从第一核心网切换至第二核心网;
S320,所述网络设备向所述终端设备发送触发指令,所述触发指令用于通知所述终端设备从所述第一核心网切换至所述第二核心网。
可选地,在一些实施例中,所述网络设备确定终端设备需要从第一核心网切换至第二核心网,包括:
所述网络设备根据当前的负载情况,确定所述终端设备需要从所述第一核心网切换至所述第二核心网。
例如,所述网络设备为第一核心网的核心网设备,所述网络设备可以在所述第一核心网的负载较重时,确定所述终端设备需要从所述第一核心网切换至所述第二核心网,或者,所述网络设备为接入网设备,所述接入网设备也可以在第一核心网的负载较重时,确定所述终端设备需要从所述第一核心网切换至所述第二核心网,可选地,所述接入网设备还可以获取与其建立连接的核心网的负载情况,以便于所述接入网设备根据核心网的负载情况,对所述终端设备进行网络的切换。
可选地,在一些实施例中,所述网络设备为接入网设备或核心网设备。
可选地,在一些实施例中,所述触发指令为S1信令、N2/N3信令或无线资源控制RRC信令。
上文结合图2至图3,分别从终端设备和网络设备的角度,详细描述了本申请的方法实施例,以下,结合图4和图5,从设备交互的角度,描述根据本申请实施例的切换网络的方法。
应理解,图4和图5是以从LTE系统的核心网(即EPC)切换至5G系统的核心网(即5GC)为例来描述本申请实施例的,但本申请实施例并不限 于此。
在该实施例中,当前与所述终端设备建立连接的核心网为EPC,即源核心网为第一核心网为EPC,目标核心网,即第二核心网为5GC,即切换前后,核心网类型发生改变,其中,ng-eNB为EPC和5GC共享的接入网设备。
图4和图5的区别在于,图4中,终端设备进行网络切换是终端设备触发的,图5中,终端设备进行网络切换是网络设备触发的,该网络设备可以为核心网设备或接入网设备。
如图4所示,该方法20可以包括如下内容:
在S21中,终端设备确定需要从第一核心网切换至第二核心网;
可选地,所述终端设备可以根据自身的业务需求等因素,确定需要从所述第一核心网切换至所述第二核心网。
所述终端设备确定需要从第一核心网切换至第二核心网之后,进一步地,在S22中,所述终端设备将NAS实体从EPC NAS实体切换为5GC NAS实体。
进一步地,所述终端设备还可以进行PDCP层和RRC层的重新配置。在进行PDCP层和RRC层的重新配置之前,在S23中,所述终端设备获取5GC的系统信息,具体地,所述终端设备可以通过接收广播消息或发送RRC信令的方式从接入网设备获取5GC的系统信息。
其中,5GC的系统信息包括PDCP层的协议版本和RRC层的相关配置信息,这里PDCP层的协议版本为5GC对应的PDCP层的协议版本。
可选地,S23的执行过程可以在S21之前,或者也可以在S21之后,本申请实施例对此不作限定。总之,在进行PDCP层和RRC层的重新配置之前,首先需要获取上述信息。
进一步地,在S24中,所述终端设备更新PDCP层的协议版本和配置,以及,在RRC层新增SDAP层的配置,以及UP功能(例如,完整性保护)的配置等。
在完成RRC层配置后,在S25中,所述终端设备可以向5GC发送NAS消息,触发所述5GC发起PDU会话建立过程。
进一步地,在S26中,建立所述终端设备、ng-eNB和5GC之间的PDU会话。
如图5所示,该方法30可以包括如下内容:
在该实施例中,终端设备进行网络切换是基于网络设备的触发指令的。
在S31中,EPC确定终端设备需要从第一核心网切换至第二核心网;
可选地,所述EPC设备可以根据自身的负载信息,确定所述终端设备需要从所述第一核心网切换至所述第二核心网。
进一步地,在S32中,所述EPC向终端设备发送触发指令,指示所述终端设备从所述第一核心网切换至所述第二核心网。
可选地,所述触发指令S1信令,或N2/N3信令等用于终端设备和核心网之间进行通信的指令或消息。
可选地,所述终端设备进行网络切换也可以是基于接入网设备的触发进行的,具体地,在S33中,所述ng-eNB确定终端设备需要从第一核心网切换至第二核心网。例如,所述ng-eNB可以根据自身的负载信息,确定所述终端设备需要从所述第一核心网切换至所述第二核心网。
进一步地,在S34中,ng-eNB向终端设备发送触发指令,,指示所述终端设备从所述第一核心网切换至所述第二核心网,可选地,所述触发指令可以为RRC信令等用于终端设备和接入网设备进行通信的信令或消息,本申请实施例对此不作限定。
所述终端设备在接收到EPC或ng-eNB的触发指令后,确定需要从第一核心网切换至所述第二核心网,进一步地,在S35中,所述终端设备将NAS实体从EPC NAS实体切换为5GC NAS实体。
进一步地,所述终端设备还可以进行PDCP层和RRC层的重新配置。在进行PDCP层和RRC层的重新配置之前,在S36中,所述终端设备获取5GC的系统信息,具体地,所述终端设备可以通过接收广播消息或发送RRC信令的方式从接入网设备获取5GC的系统信息。
其中,5GC的系统信息包括PDCP层的协议版本和RRC层的相关配置信息,这里PDCP层的协议版本为5GC对应的PDCP层的协议版本。
可选地,S36的执行过程可以在S31至S34之前,或者也可以在S31至S34之后,本申请实施例对此不作限定。总之,在进行PDCP层和RRC层的重新配置之前,首先需要获取上述系统信息。
进一步地,在S37中,所述终端设备更新PDCP层的协议版本和配置,以及,在RRC层新增SDAP层的配置,以及UP功能(例如,完整性保护)的配置等。
在完成RRC层配置后,在S38中,所述终端设备可以向5GC发送NAS消息,触发所述5GC发起PDU会话建立过程。
进一步地,在S39中,建立所述终端设备、ng-eNB和5GC之间的PDU会话。
上文结合图2至图5,详细描述了本申请的方法实施例,下文结合图6至图9,详细描述本申请的装置实施例,应理解,装置实施例与方法实施例相互对应,类似的描述可以参照方法实施例。
图6示出了根据本申请实施例的终端设备400的示意性框图。如图6所示,该终端设备400包括:
确定模块410,用于确定需要从第一核心网切换至第二核心网;
配置模块420,用于根据所述第一核心网和所述第二核心网的核心网类型,进行协议层的配置。
可选地,在一些实施例中,所述确定模块410具体用于:
根据当前的业务需求,确定需要从所述第一核心网切换至所述第二核心网。
可选地,在一些实施例中,所述确定模块410具体用于:
在接收到网络设备的触发指令的情况下,确定需要从所述第一核心网切换至所述第二核心网,其中,所述触发指令用于通知所述终端设备从所述第一核心网切换至所述第二核心网。
可选地,在一些实施例中,所述终端设备400还包括:
第一接收模块,用于接收所述网络设备发送的所述触发指令。
可选地,在一些实施例中,所述网络设备为接入网设备或核心网设备。
可选地,在一些实施例中,所述触发指令为S1信令、N2/N3信令或无线资源控制RRC信令。
可选地,在一些实施例中,若所述第一核心网和所述第二核心网为不同类型的核心网,所述终端设备还包括:
获取模块,用于获取所述第二核心网的系统信息。
可选地,在一些实施例中,所述终端设备400还包括:
第二接收模块,用于接收接入网设备发送的广播消息,从所述广播消息中获取所述第二核心网的系统信息。
可选地,在一些实施例中,所述终端设备400还包括:
第一发送模块,用于向接入网设备发送第一RRC信令;
第三接收模块,用于接收所述接入网设备回复的第二RRC信令;
所述获取模块具体用于:
从所述第二RRC信令中获取所述第二核心网的系统信息。
可选地,在一些实施例中,所述配置模块420具体用于:
若所述第一核心网和所述第二核心网为不同类型的核心网,所述将所述第一核心网对应的分组数据汇聚协议PDCP层配置更新为所述第二核心网对应的PDCP层配置,将所述第一核心网对应的PDCP层的协议版本更新为所述第二核心网对应的PDCP层的协议版本,将所述第一核心网对应的RRC层配置更新为所述第二核心网对应的RRC层配置,以及将非接入层NAS的实体从支持所述第一核心网的第一NAS实体切换为支持所述第二核心网的第二NAS实体。
可选地,在一些实施例中,所述配置模块420还用于:
不进行无线链路控制RLC层、媒体接入控制MAC层以及物理层PHY的重新配置。
可选地,在一些实施例中,若所述第一核心网为长期演进LTE系统的核心网,所述第二核心网为新无线NR系统的核心网,所述配置模块420具体用于:
将LTE PDCP更新为NR PDCP,其中,所述LTE PDCP为所述第一核心网对应的PDCP层的协议版本,所述NR PDCP为所述第二核心网对应的PDCP层的协议版本。
可选地,在一些实施例中,若所述第一核心网为LTE系统的核心网,所述第二核心网为NR系统的核心网,所述配置模块420具体用于:
在所述第一核心网对应的RRC层配置的基础上,新增业务数据适配SDAP层的配置,并新增用户平面UP功能的配置。
可选地,在一些实施例中,若所述第一核心网为NR系统的核心网,所述第二核心网为LTE系统的核心网,所述配置模块420具体用于:
将NR PDCP更新为LTE PDCP,其中,所述NR PDCP为所述第一核心网对应的PDCP层的协议版本,所述LTE PDCP为所述第二核心网对应的PDCP层的协议版本。
可选地,在一些实施例中,若所述第一核心网为NR系统的核心网,所 述第二核心网为LTE系统的核心网,所述配置模块420具体用于:
在所述第一核心网对应的RRC层配置的基础上,删除SDAP层的配置,并删除用户平面UP功能的配置。
可选地,在一些实施例中,所述配置模块420具体用于:
若所述第一核心网和所述第二核心网为同一类型的核心网,不更新所述终端设备的PDCP层以及RRC层的协议版本。
可选地,在一些实施例中,所述配置模块420具体用于:
将所述第一核心网对应的PDCP层的配置更新为所述第二核心网对应的PDCP层的配置,和/或将所述第一核心网对应的RRC层的配置更新为所述第二核心网对应的RRC层的配置。
可选地,在一些实施例中,所述终端设备400还包括:
第二发送模块,用于向接入网设备发送请求消息,所述请求消息用于请求获取所述第二核心网对应的PDCP层配置和PDCP层的协议版本。
可选地,在一些实施例中,所述终端设备400还包括:
第三发送模块,用于向所述第二核心网发送NAS消息,所述NAS消息用于触发所述第二核心网发起协议数据单元PDU会话建立过程。
应理解,根据本申请实施例的终端设备400可对应于本申请方法实施例中的终端设备,并且终端设备400中的各个单元的上述和其它操作和/或功能分别为了实现图2所示方法200,或图4所示方法20,或图5所示方法30中终端设备的相应流程,为了简洁,在此不再赘述。
图7示出了根据本申请实施例的网络设备500的示意性框图。如图7所示,该网络设备500包括:
确定模块510,用于确定终端设备需要从第一核心网切换至第二核心网;
通信模块520,用于向所述终端设备发送触发指令,所述触发指令用于通知所述终端设备从所述第一核心网切换至所述第二核心网。
可选地,在一些实施例中,所述确定模块510具体用于:
根据当前的负载情况,确定所述终端设备需要从所述第一核心网切换至所述第二核心网。
可选地,在一些实施例中,所述网络设备为接入网设备或核心网设备。
可选地,在一些实施例中,所述触发指令为S1信令、N2/N3信令或无线资源控制RRC信令。
应理解,根据本申请实施例的网络设备500可对应于本申请方法实施例中的接入网设备,并且网络设备500中的各个单元的上述和其它操作和/或功能分别为了实现图3所示方法300,或图4所示方法20,或图5所示方法30中网络设备的相应流程,为了简洁,在此不再赘述。
如图8所示,本申请实施例还提供了一种终端设备600,该终端设备600可以为图6中的终端设备400,其能够用于执行与图2中方法200,或图4所示方法20,或图5所示方法30对应的终端设备的内容。该终端设备600包括:输入接口610、输出接口620、处理器630以及存储器640,该输入接口610、输出接口620、处理器630和存储器640可以通过总线系统相连。所述存储器640用于存储包括程序、指令或代码。所述处理器630,用于执行所述存储器640中的程序、指令或代码,以控制输入接口610接收信号、控制输出接口620发送信号以及完成前述方法实施例中的操作。
应理解,在本申请实施例中,该处理器630可以是中央处理单元(Central Processing Unit,简称为“CPU”),该处理器630还可以是其他通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
该存储器640可以包括只读存储器和随机存取存储器,并向处理器630提供指令和数据。存储器640的一部分还可以包括非易失性随机存取存储器。例如,存储器640还可以存储设备类型的信息。
在实现过程中,上述方法的各内容可以通过处理器630中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的内容可以直接体现为硬件处理器执行完成,或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器640,处理器630读取存储器640中的信息,结合其硬件完成上述方法的内容。为避免重复,这里不再详细描述。
一个具体的实施方式中,图6所示的终端设备400中的第一接收模块、第二接收模块、第三接收模块以及第一发送模块、第二发送模块和第三发送模块可以用图8的输入接口610和输出接口620实现,图6所示的终端设备400中的确定模块410、配置模块420和获取模块可以用图8的处理器630 实现。
如图9所示,本申请实施例还提供了一种网络设备700,该网络设备700可以为图7中的网络设备500,其能够用于执行与图3中方法300,或图4所示方法20,或图5所示方法30对应的网络设备的内容。该网络设备700包括:输入接口710、输出接口720、处理器730以及存储器740,该输入接口710、输出接口720、处理器730和存储器740可以通过总线系统相连。所述存储器740用于存储包括程序、指令或代码。所述处理器730,用于执行所述存储器740中的程序、指令或代码,以控制输入接口710接收信号、控制输出接口720发送信号以及完成前述方法实施例中的操作。
应理解,在本申请实施例中,该处理器730可以是中央处理单元(Central Processing Unit,简称为“CPU”),该处理器730还可以是其他通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
该存储器740可以包括只读存储器和随机存取存储器,并向处理器730提供指令和数据。存储器740的一部分还可以包括非易失性随机存取存储器。例如,存储器740还可以存储设备类型的信息。
在实现过程中,上述方法的各内容可以通过处理器730中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的内容可以直接体现为硬件处理器执行完成,或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器740,处理器730读取存储器740中的信息,结合其硬件完成上述方法的内容。为避免重复,这里不再详细描述。
一个具体的实施方式中,图7所示的网络设备500中的通信模块520可以用图9的输入接口710和输出接口720实现,网络设备500中的确定模块510可以用图9的处理器730实现。
本申请实施例还提出了一种计算机可读存储介质,该计算机可读存储介质存储一个或多个程序,该一个或多个程序包括指令,该指令当被包括多个应用程序的便携式电子设备执行时,能够使该便携式电子设备执行图2至图5所示实施例的方法。
本申请实施例还提出了一种计算机程序,该计算机程序包括指令,当该计算机程序被计算机执行时,使得计算机可以执行图2至图5所示实施例的方法的相应流程。
应理解,本文中术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或”的关系。
应理解,在本申请实施例的各种实施例中,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统、装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统、装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一 个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(ROM,Read-Only Memory)、随机存取存储器(RAM,Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应所述以权利要求的保护范围为准。

Claims (46)

  1. 一种切换网络的方法,其特征在于,包括:
    终端设备确定需要从第一核心网切换至第二核心网;
    所述终端设备根据所述第一核心网和所述第二核心网的核心网类型,进行协议层的配置。
  2. 根据权利要求1所述的方法,其特征在于,所述终端设备确定需要从第一核心网切换至第二核心网,包括:
    所述终端设备根据当前的业务需求,确定需要从所述第一核心网切换至所述第二核心网。
  3. 根据权利要求1所述的方法,其特征在于,所述终端设备确定需要从第一核心网切换至第二核心网,包括:
    所述终端设备在接收到网络设备的触发指令的情况下,确定需要从所述第一核心网切换至所述第二核心网,其中,所述触发指令用于通知所述终端设备从所述第一核心网切换至所述第二核心网。
  4. 根据权利要求3所述的方法,其特征在于,所述方法还包括:
    所述终端设备接收所述网络设备发送的所述触发指令。
  5. 根据权利要求3或4所述的方法,其特征在于,所述网络设备为接入网设备或核心网设备。
  6. 根据权利要求5所述的方法,其特征在于,所述触发指令为S1信令、N2/N3信令或无线资源控制RRC信令。
  7. 根据权利要求1至6中任一项所述的方法,其特征在于,若所述第一核心网和所述第二核心网为不同类型的核心网,所述方法还包括:
    所述终端设备获取所述第二核心网的系统信息。
  8. 根据权利要求7所述的方法,其特征在于,所述终端设备获取所述第二核心网的系统信息,包括:
    所述终端设备接收接入网设备发送的广播消息,从所述广播消息中获取所述第二核心网的系统信息。
  9. 根据权利要求7所述的方法,其特征在于,所述终端设备获取所述第二核心网的系统信息,包括:
    所述终端设备向接入网设备发送第一RRC信令;
    所述终端设备接收所述接入网设备回复的第二RRC信令,从所述第二 RRC信令中获取所述第二核心网的系统信息。
  10. 根据权利要求1至9中任一项所述的方法,其特征在于,所述终端设备根据所述第一核心网和所述第二核心网的核心网类型,进行协议层的配置,包括:
    若所述第一核心网和所述第二核心网为不同类型的核心网,所述终端设备将所述第一核心网对应的分组数据汇聚协议PDCP层配置更新为所述第二核心网对应的PDCP层配置,将所述第一核心网对应的PDCP层的协议版本更新为所述第二核心网对应的PDCP层的协议版本,将所述第一核心网对应的RRC层配置更新为所述第二核心网对应的RRC层配置,以及将非接入层NAS的实体从支持所述第一核心网的第一NAS实体切换为支持所述第二核心网的第二NAS实体。
  11. 根据权利要求10所述的方法,其特征在于,所述方法还包括:
    所述终端设备不进行无线链路控制RLC层、媒体接入控制MAC层以及物理层PHY的重新配置。
  12. 根据权利要求10或11所述的方法,其特征在于,若所述第一核心网为长期演进LTE系统的核心网,所述第二核心网为新无线NR系统的核心网,所述将所述第一核心网对应的PDCP层的协议版本更新为所述第二核心网对应的PDCP层的协议版本,包括:
    所述终端设备将LTE PDCP更新为NR PDCP,其中,所述LTE PDCP为所述第一核心网对应的PDCP层的协议版本,所述NR PDCP为所述第二核心网对应的PDCP层的协议版本。
  13. 根据权利要求10至12中任一项所述的方法,其特征在于,若所述第一核心网为LTE系统的核心网,所述第二核心网为NR系统的核心网,所述将所述第一核心网对应的RRC层配置更新为所述第二核心网对应的RRC层配置,包括:
    所述终端设备在所述第一核心网对应的RRC层配置的基础上,新增业务数据适配SDAP层的配置,并新增用户平面UP功能的配置。
  14. 根据权利要求10或11所述的方法,其特征在于,若所述第一核心网为NR系统的核心网,所述第二核心网为LTE系统的核心网,所述将所述第一核心网对应的PDCP层的协议版本更新为所述第二核心网对应的PDCP层的协议版本,包括:
    所述终端设备将NR PDCP更新为LTE PDCP,其中,所述NR PDCP为所述第一核心网对应的PDCP层的协议版本,所述LTE PDCP为所述第二核心网对应的PDCP层的协议版本。
  15. 根据权利要求14所述的方法,其特征在于,若所述第一核心网为NR系统的核心网,所述第二核心网为LTE系统的核心网,所述将所述第一核心网对应的RRC层配置更新为所述第二核心网对应的RRC层配置,包括:
    所述终端设备在所述第一核心网对应的RRC层配置的基础上,删除SDAP层的配置,并删除用户平面UP功能的配置。
  16. 根据权利要求1至9中任一项所述的方法,其特征在于,所述终端设备根据所述第一核心网和所述第二核心网的核心网类型,进行协议层的配置,包括:
    若所述第一核心网和所述第二核心网为同一类型的核心网,所述终端设备不更新所述终端设备的PDCP层以及RRC层的协议版本。
  17. 根据权利要求16所述的方法,其特征在于,所述终端设备根据所述第一核心网和所述第二核心网的核心网类型,进行协议层的配置,包括:
    将所述第一核心网对应的PDCP层的配置更新为所述第二核心网对应的PDCP层的配置,和/或将所述第一核心网对应的RRC层的配置更新为所述第二核心网对应的RRC层的配置。
  18. 根据权利要求10至15中任一项所述的方法,其特征在于,所述方法还包括:
    所述终端设备向接入网设备发送请求消息,所述请求消息用于请求获取所述第二核心网对应的PDCP层配置和PDCP层的协议版本。
  19. 根据权利要求1至18中任一项所述的方法,其特征在于,所述方法还包括:
    所述终端设备向所述第二核心网发送NAS消息,所述NAS消息用于触发所述第二核心网发起协议数据单元PDU会话建立过程。
  20. 一种切换网络的方法,其特征在于,包括:
    网络设备确定终端设备需要从第一核心网切换至第二核心网;
    所述网络设备向所述终端设备发送触发指令,所述触发指令用于通知所述终端设备从所述第一核心网切换至所述第二核心网。
  21. 根据权利要求20所述的方法,其特征在于,所述网络设备确定终 端设备需要从第一核心网切换至第二核心网,包括:
    所述网络设备根据当前的负载情况,确定所述终端设备需要从所述第一核心网切换至所述第二核心网。
  22. 根据权利要求20或21所述的方法,其特征在于,所述网络设备为接入网设备或核心网设备。
  23. 根据权利要求22所述的方法,其特征在于,所述触发指令为S1信令、N2/N3信令或无线资源控制RRC信令。
  24. 一种终端设备,其特征在于,包括:
    确定模块,用于确定需要从第一核心网切换至第二核心网;
    配置模块,用于根据所述第一核心网和所述第二核心网的核心网类型,进行协议层的配置。
  25. 根据权利要求24所述的终端设备,其特征在于,所述确定模块具体用于:
    根据当前的业务需求,确定需要从所述第一核心网切换至所述第二核心网。
  26. 根据权利要求24所述的终端设备,其特征在于,所述确定模块具体用于:
    在接收到网络设备的触发指令的情况下,确定需要从所述第一核心网切换至所述第二核心网,其中,所述触发指令用于通知所述终端设备从所述第一核心网切换至所述第二核心网。
  27. 根据权利要求26所述的终端设备,其特征在于,所述终端设备还包括:
    第一接收模块,用于接收所述网络设备发送的所述触发指令。
  28. 根据权利要求26或27所述的终端设备,其特征在于,所述网络设备为接入网设备或核心网设备。
  29. 根据权利要求28所述的终端设备,其特征在于,所述触发指令为S1信令、N2/N3信令或无线资源控制RRC信令。
  30. 根据权利要求24至29中任一项所述的终端设备,其特征在于,若所述第一核心网和所述第二核心网为不同类型的核心网,所述终端设备还包括:
    获取模块,用于获取所述第二核心网的系统信息。
  31. 根据权利要求30所述的终端设备,其特征在于,所述终端设备还包括:
    第二接收模块,用于接收接入网设备发送的广播消息,从所述广播消息中获取所述第二核心网的系统信息。
  32. 根据权利要求30所述的终端设备,其特征在于,所述终端设备还包括:
    第一发送模块,用于向接入网设备发送第一RRC信令;
    第三接收模块,用于接收所述接入网设备回复的第二RRC信令;
    所述获取模块具体用于:
    从所述第二RRC信令中获取所述第二核心网的系统信息。
  33. 根据权利要求24至32中任一项所述的终端设备,其特征在于,所述配置模块具体用于:
    若所述第一核心网和所述第二核心网为不同类型的核心网,所述将所述第一核心网对应的分组数据汇聚协议PDCP层配置更新为所述第二核心网对应的PDCP层配置,将所述第一核心网对应的PDCP层的协议版本更新为所述第二核心网对应的PDCP层的协议版本,将所述第一核心网对应的RRC层配置更新为所述第二核心网对应的RRC层配置,以及将非接入层NAS的实体从支持所述第一核心网的第一NAS实体切换为支持所述第二核心网的第二NAS实体。
  34. 根据权利要求33所述的终端设备,其特征在于,所述配置模块还用于:
    不进行无线链路控制RLC层、媒体接入控制MAC层以及物理层PHY的重新配置。
  35. 根据权利要求33或34所述的终端设备,其特征在于,若所述第一核心网为长期演进LTE系统的核心网,所述第二核心网为新无线NR系统的核心网,所述配置模块具体用于:
    将LTE PDCP更新为NR PDCP,其中,所述LTE PDCP为所述第一核心网对应的PDCP层的协议版本,所述NR PDCP为所述第二核心网对应的PDCP层的协议版本。
  36. 根据权利要求33至35中任一项所述的终端设备,其特征在于,若所述第一核心网为LTE系统的核心网,所述第二核心网为NR系统的核心网, 所述配置模块具体用于:
    在所述第一核心网对应的RRC层配置的基础上,新增业务数据适配SDAP层的配置,并新增用户平面UP功能的配置。
  37. 根据权利要求33或34所述的终端设备,其特征在于,若所述第一核心网为NR系统的核心网,所述第二核心网为LTE系统的核心网,所述配置模块具体用于:
    将NR PDCP更新为LTE PDCP,其中,所述NR PDCP为所述第一核心网对应的PDCP层的协议版本,所述LTE PDCP为所述第二核心网对应的PDCP层的协议版本。
  38. 根据权利要求37所述的终端设备,其特征在于,若所述第一核心网为NR系统的核心网,所述第二核心网为LTE系统的核心网,所述配置模块具体用于:
    在所述第一核心网对应的RRC层配置的基础上,删除SDAP层的配置,并删除用户平面UP功能的配置。
  39. 根据权利要求24至32中任一项所述的终端设备,其特征在于,所述配置模块具体用于:
    若所述第一核心网和所述第二核心网为同一类型的核心网,不更新所述终端设备的PDCP层以及RRC层的协议版本。
  40. 根据权利要求39所述的终端设备,其特征在于,所述配置模块具体用于:
    将所述第一核心网对应的PDCP层的配置更新为所述第二核心网对应的PDCP层的配置,和/或将所述第一核心网对应的RRC层的配置更新为所述第二核心网对应的RRC层的配置。
  41. 根据权利要求33至38中任一项所述的终端设备,其特征在于,所述终端设备还包括:
    第二发送模块,用于向接入网设备发送请求消息,所述请求消息用于请求获取所述第二核心网对应的PDCP层配置和PDCP层的协议版本。
  42. 根据权利要求24至41中任一项所述的终端设备,其特征在于,所述终端设备还包括:
    第三发送模块,用于向所述第二核心网发送NAS消息,所述NAS消息用于触发所述第二核心网发起协议数据单元PDU会话建立过程。
  43. 一种网络设备,其特征在于,包括:
    确定模块,用于确定终端设备需要从第一核心网切换至第二核心网;
    通信模块,用于向所述终端设备发送触发指令,所述触发指令用于通知所述终端设备从所述第一核心网切换至所述第二核心网。
  44. 根据权利要求43所述的网络设备,其特征在于,所述确定模块具体用于:
    根据当前的负载情况,确定所述终端设备需要从所述第一核心网切换至所述第二核心网。
  45. 根据权利要求43或44所述的网络设备,其特征在于,所述网络设备为接入网设备或核心网设备。
  46. 根据权利要求45所述的网络设备,其特征在于,所述触发指令为S1信令、N2/N3信令或无线资源控制RRC信令。
PCT/CN2017/103532 2017-09-26 2017-09-26 切换网络的方法、终端设备和网络设备 WO2019061039A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201780050353.4A CN109792396B (zh) 2017-09-26 2017-09-26 切换网络的方法、终端设备和网络设备
PCT/CN2017/103532 WO2019061039A1 (zh) 2017-09-26 2017-09-26 切换网络的方法、终端设备和网络设备
EP17923980.1A EP3499804B1 (en) 2017-09-26 2017-09-26 Network switching method and terminal device
US16/340,844 US20190268820A1 (en) 2017-09-26 2017-09-26 Network Handover Method, Terminal Device and Network Device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/103532 WO2019061039A1 (zh) 2017-09-26 2017-09-26 切换网络的方法、终端设备和网络设备

Publications (1)

Publication Number Publication Date
WO2019061039A1 true WO2019061039A1 (zh) 2019-04-04

Family

ID=65900287

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/103532 WO2019061039A1 (zh) 2017-09-26 2017-09-26 切换网络的方法、终端设备和网络设备

Country Status (4)

Country Link
US (1) US20190268820A1 (zh)
EP (1) EP3499804B1 (zh)
CN (1) CN109792396B (zh)
WO (1) WO2019061039A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114531714A (zh) * 2019-06-17 2022-05-24 腾讯科技(深圳)有限公司 通信方法、装置、计算机可读介质及电子设备
CN111786847B (zh) * 2020-06-01 2022-03-29 北京电信技术发展产业协会 第五代移动通信终端一致性测试方法和系统
WO2022000496A1 (zh) * 2020-07-03 2022-01-06 华为技术有限公司 一种通信方法及装置
CN114513757B (zh) * 2020-11-17 2024-05-10 维沃移动通信有限公司 信息获取方法、指示方法、装置、相关设备和存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101682415A (zh) * 2007-06-15 2010-03-24 英特尔公司 移动台从第一到第二类型的无线网络的切换
CN101867982A (zh) * 2009-04-17 2010-10-20 中兴通讯股份有限公司 处理终端业务请求的方法、终端、网络基站、系统
CN103442399A (zh) * 2013-08-26 2013-12-11 东莞宇龙通信科技有限公司 网络切换方法、网络切换系统和终端
CN104092579A (zh) * 2014-02-12 2014-10-08 腾讯科技(深圳)有限公司 网络类型的模拟方法及装置
CN105636133A (zh) * 2015-12-30 2016-06-01 深圳市金立通信设备有限公司 一种无线接入点的配置方法及基站
US20170034808A1 (en) * 2013-12-27 2017-02-02 Sharp Kabushiki Kaisha Terminal device, base station apparatus, and method

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101925121B (zh) * 2009-06-10 2014-03-19 中兴通讯股份有限公司 一种分组数据汇聚协议层重建的方法和装置
CN102123457B (zh) * 2010-01-11 2016-04-13 中兴通讯股份有限公司 切换方法及终端
CN102892167A (zh) * 2012-09-19 2013-01-23 邦讯技术股份有限公司 一种实现家庭基站网关支持前向切换的方法和系统
US20150296418A1 (en) * 2014-04-15 2015-10-15 Nokia Solutions And Networks Oy Methods and Apparatus for Handover Management of Transfer Control Protocol Proxy Communications
EP3132622B1 (en) * 2014-04-15 2019-09-25 Nokia Solutions and Networks Oy Interworking with bearer-based system
US10219178B2 (en) * 2014-12-02 2019-02-26 Cisco Technology, Inc. Channel aggregation using Wi-Fi
EP4138464A3 (en) * 2015-08-31 2023-03-15 Samsung Electronics Co., Ltd. Method and apparatus for implementing wireless protocol configurable according to services and devices
KR102107327B1 (ko) * 2016-01-08 2020-05-06 닛본 덴끼 가부시끼가이샤 무선국 시스템, 무선 단말, 및 이들을 위한 방법
CN112672343B (zh) * 2016-08-09 2022-04-26 三星电子株式会社 无线通信系统中管理用户平面操作的方法和装置
CN107734573B (zh) * 2016-08-12 2020-08-07 华为技术有限公司 切换方法、基站及通信系统
CN106358238A (zh) * 2016-11-24 2017-01-25 重庆邮电大学 一种lte‑a与wlan基于双连接技术的数据分流方法
MX2019007520A (es) * 2016-12-29 2019-09-02 Ericsson Telefon Ab L M Nodo de red y metodo para configurar pdcp para un dispositivo inalambrico.
US10448386B2 (en) * 2017-01-06 2019-10-15 Kt Corporation Method and apparatus for controlling redundant data transmission
US11202279B2 (en) * 2017-01-16 2021-12-14 Samsung Electronics Co., Ltd Method and apparatus for processing data in wireless communication system
US10499376B2 (en) * 2017-06-16 2019-12-03 Kt Corporation Methods for managing resource based on open interface and apparatuses thereof
JP6994439B2 (ja) * 2017-07-20 2022-01-14 華碩電腦股▲ふん▼有限公司 無線通信システムにおいてQoS(クオリティ・オブ・サービス)フローを提供するための方法及び装置
US10869353B2 (en) * 2017-07-23 2020-12-15 Lg Electronics Inc. Method and apparatus for modifying radio bearer in CU-DU split scenario
CN109661834B (zh) * 2017-07-27 2020-05-12 Oppo广东移动通信有限公司 重配置方法及相关产品
US10708968B2 (en) * 2017-08-25 2020-07-07 Kt Corporation Method of controlling mobility of UE and apparatus therefor
CN111345066B (zh) * 2017-11-16 2022-07-19 瑞典爱立信有限公司 Pdcp版本改变的处理
US10869223B2 (en) * 2018-02-13 2020-12-15 Samsung Electronics Co., Ltd. Method and apparatus for efficient operation upon packet duplication activation and deactivation in next generation wireless communication system

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101682415A (zh) * 2007-06-15 2010-03-24 英特尔公司 移动台从第一到第二类型的无线网络的切换
CN101867982A (zh) * 2009-04-17 2010-10-20 中兴通讯股份有限公司 处理终端业务请求的方法、终端、网络基站、系统
CN103442399A (zh) * 2013-08-26 2013-12-11 东莞宇龙通信科技有限公司 网络切换方法、网络切换系统和终端
US20170034808A1 (en) * 2013-12-27 2017-02-02 Sharp Kabushiki Kaisha Terminal device, base station apparatus, and method
CN104092579A (zh) * 2014-02-12 2014-10-08 腾讯科技(深圳)有限公司 网络类型的模拟方法及装置
CN105636133A (zh) * 2015-12-30 2016-06-01 深圳市金立通信设备有限公司 一种无线接入点的配置方法及基站

Also Published As

Publication number Publication date
EP3499804A1 (en) 2019-06-19
EP3499804A4 (en) 2019-09-04
EP3499804B1 (en) 2020-06-10
US20190268820A1 (en) 2019-08-29
CN109792396A (zh) 2019-05-21
CN109792396B (zh) 2020-04-24

Similar Documents

Publication Publication Date Title
JP7483835B2 (ja) セッション管理の方法、装置、およびシステム
US11528761B2 (en) Communication method and communications apparatus
US10904849B2 (en) User plane for fifth generation cellular architecture
WO2017091960A1 (zh) 切换移动边缘平台的方法、装置和系统
EP4024956A1 (en) Communication method, apparatus, and system
JP7135122B2 (ja) リダイレクション方法、通信システム及び通信装置
WO2019061039A1 (zh) 切换网络的方法、终端设备和网络设备
JP7080832B2 (ja) 情報伝送方法及び装置
EP3745774A1 (en) Policy control method, device and system
WO2023124749A1 (zh) 小区切换方法、装置、网络设备及存储介质
WO2019157712A1 (zh) 通信方法、网络设备和终端设备
EP3841836B1 (en) Communication method and terminal device
CN110913437B (zh) 通信方法和网元
WO2018010127A1 (zh) 无线通信的方法、装置、接入网实体和终端设备
WO2020042026A1 (zh) 无线通信的方法和设备
JP6835229B2 (ja) ハンドオーバ方法、コアネットワークデバイス、アクセスネットワークデバイス、および端末デバイス
CN110784912A (zh) 一种会话对应关系的管理方法和终端设备
WO2023125168A1 (zh) 通信方法和装置
US20210243657A1 (en) Communication method, core network device, access network device, terminal device, and communication system
WO2019024108A1 (zh) 通信方法、网络设备和终端设备
CN109150752B (zh) 缓存控制方法、网元及控制器
WO2024169556A1 (zh) 一种网元选择方法及装置
WO2018201973A1 (zh) 一种消息传输的方法及装置
JP2022033964A (ja) 輻輳処理のための方法及び機器
WO2019019121A1 (zh) 小区切换方法和装置

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2017923980

Country of ref document: EP

Effective date: 20190313

NENP Non-entry into the national phase

Ref country code: DE