WO2019148654A1 - Procédé et appareil de retour de réseau, et support de stockage informatique - Google Patents

Procédé et appareil de retour de réseau, et support de stockage informatique Download PDF

Info

Publication number
WO2019148654A1
WO2019148654A1 PCT/CN2018/082849 CN2018082849W WO2019148654A1 WO 2019148654 A1 WO2019148654 A1 WO 2019148654A1 CN 2018082849 W CN2018082849 W CN 2018082849W WO 2019148654 A1 WO2019148654 A1 WO 2019148654A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
message
terminal
target service
network element
Prior art date
Application number
PCT/CN2018/082849
Other languages
English (en)
Chinese (zh)
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 CN201880037301.8A priority Critical patent/CN110710247B/zh
Publication of WO2019148654A1 publication Critical patent/WO2019148654A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H04W36/1443—Reselecting a network or an air interface over a different radio air interface technology between licensed networks

Definitions

  • the present invention relates to the field of wireless communication technologies, and in particular, to a network return method and apparatus, and a computer storage medium.
  • Fifth generation (5G, 5 th Generation) mobile communication system is also called a new radio (NR, New Radio) system, the initial deployment network 5G 5G or in the case of network congestion, the network may not support voice 5G on NR ( VoNR, voice over New Radio), 5G 5G network needs to trigger from the network to the fourth generation (4G, 4 th Generation) network switch or redirect the flow process, the voice network 4G long term evolution (VoLTE, voice over long Term Evolution) Completes the voice service of the terminal.
  • NR New Radio
  • an embodiment of the present invention provides a network return method and apparatus, and a computer storage medium.
  • the terminal switches or redirects from the first network to the second network, and performs target service under the second network, where the terminal switches or redirects from the first network to the second network, Determining that the reason value of the handover or redirection is a fallback corresponding to the target service, where the cause value is used to indicate that the handover or redirection is caused by a fallback corresponding to the target service, and is sent to the second network.
  • the terminal After completing the target service in the second network, the terminal receives a handover or redirection message sent by the second network, and switches or redirects from the second network to the device according to the handover or redirection message.
  • the first network is configured; or, after the terminal completes the target service in the second network, the terminal receives the redirect or release connection message sent by the second network.
  • Determining, by the terminal, that the reason value of the handover is a fallback corresponding to the target service, where the cause value is used to indicate that the handover is caused by a fallback corresponding to the target service including:
  • the terminal determines, according to the handover command, that the cause value of the handover is a fallback corresponding to the target service, and the cause value is used to indicate that the handover is caused by a fallback corresponding to the target service.
  • a handover process is completed between the first network and the second network; or, the first network and the first The switching process is completed between the two networks through the third network.
  • the terminal switching from the first network to the second network includes:
  • the terminal switches from the first access network to the second access network, and maintains the connection with the first core network unchanged.
  • the terminal switching from the first network to the second network includes:
  • the terminal switches from the first access network to the second access network, and switches from the first core network to the second core network.
  • Determining, by the terminal, that the reason value of the redirection is a fallback corresponding to the target service, where the cause value is used to indicate that the redirection is caused by a fallback corresponding to the target service including:
  • the terminal determines, according to the redirection message, that the reason value of the redirection is a fallback corresponding to the target service, and the reason value is used to indicate that the redirection is caused by a fallback corresponding to the target service.
  • the redirect message is an N2 request message or a radio resource control (RRC, Radio Resource Control) connection release message.
  • RRC Radio Resource Control
  • the terminal determines, according to the RRC connection release message, that the reason value of the redirection is a fallback corresponding to the target service, where the cause value is used to indicate that the redirection is caused by a fallback corresponding to the target service.
  • the terminal determines that the reason value of the handover or redirection is a fallback corresponding to the target service, and the cause value is used to indicate that the handover or redirection is caused by a fallback corresponding to the target service.
  • the terminal After the terminal sends a Session Initiation Protocol (SIP) message, if the handover command or the RRC connection release message sent by the first network is received within the first time period, the terminal determines the handover or redirection.
  • the cause value is a fallback corresponding to the target service, and the cause value is used to indicate that the handover or redirection is caused by a fallback corresponding to the target service.
  • the terminal sends the fallback indication information corresponding to the target service and/or the last used PLMN ID to the second network, including:
  • an AS layer (AS, Access Stratum) message and/or an AS parameter in a non-access stratum (NAS, Non-Access Stratum) message to the second network, the AS message and/or the NAS message
  • the AS parameter in the carrying carries the fallback indication information corresponding to the target service and/or the last used PLMN ID.
  • the AS message includes at least one of the following: an RRC connection request message, a handover complete message, and an RRC connection setup complete message.
  • the AS parameter in the NAS message includes at least one of the following: an AS parameter in an attach request message, and an AS parameter in a tracking area update request message.
  • the access network element of the second network obtains the fallback indication information corresponding to the target service and/or the last used PLMN ID from the AS parameters in the AS message and/or the NAS message. .
  • the terminal sends the fallback indication information corresponding to the target service and/or the last used PLMN ID to the second network, including:
  • the terminal sends a NAS message to the second network, where the NAS message carries the fallback indication information corresponding to the target service and/or the last used PLMN ID.
  • the NAS message includes at least one of the following: an NAS message in an attach request message, and a NAS message in a tracking area update request message.
  • the core network element of the second network obtains the fallback indication information corresponding to the target service and/or the last used PLMN ID from the NAS message, and the corresponding target service falls back.
  • the indication information and/or the last used PLMN ID are sent to the access network element of the second network.
  • the core network element of the second network sends the fallback indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network, including:
  • the core network element of the second network sends the drop indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network by using a bearer setup or release message; or,
  • the core network element of the second network sends the drop indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network by using an initial context setup request message.
  • the core network element of the second network receives the fallback indication information corresponding to the target service and/or the last used PLMN ID sent by the core network element of the first network, where The core network element of the second network sends the fallback indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network.
  • the core network element of the first network sends a voice QoS flow setup request message to the access network network element of the first network, and receives the access network element of the first network to send a reject message, the reject message carrying a cause value, the cause value being used to indicate that the reject message is caused by a fallback corresponding to the target service; if the core network element of the first network is at a first time Receiving the handover request message sent by the access network element of the first network, the reason that the core network element of the first network determines the handover request message is caused by the fallback of the target service .
  • the access network element of the second network completes the release of the bearer, and the terminal receives the handover or the heavy transmission sent by the second network. Directed message.
  • the core network element of the second network completes the bearer release, and the terminal receives the core network element of the second network to send Switch or redirect message.
  • the first network is selected as the target network of the terminal.
  • the method further includes: determining cell information and/or frequency information of the target network.
  • the first network is selected as the target network of the terminal based on the last used PLMN ID.
  • the terminal after the terminal completes the target service in the second network, after completing the bearer release, the terminal receives the RRC release message sent by the access network element of the second network, and releases the RRC connection. Entering the idle state, performing cell reselection through the radio resource management RFSP policy, and returning to the first network.
  • the terminal after the terminal completes the target service in the second network, after completing the bearer release, the terminal receives the RRC release message sent by the core network element of the second network, and releases the RRC connection.
  • the terminal In the idle state, cell reselection is performed through the radio resource management RFSP policy, and the process returns to the first network.
  • the terminal receives the redirect or release connection message sent by the second network, including:
  • the terminal After the access network element of the second network receives the fallback indication information corresponding to the target service and/or the last used PLMN ID from the core network element of the second network, the terminal receives the second A redirect or release connection message sent by the network.
  • the terminal receives the redirect message sent by the second network, including:
  • the access network element of the second network detects that there is a base station of the first network in the target area around the terminal, and the signal strength of the base station of the first network is higher than the first threshold, Receiving, by the terminal, a redirection message corresponding to the access network of the first network sent by the access network element of the second network, where the redirection message corresponding to the access network of the first network carries the Frequency information and/or cell information of the access network of the first network;
  • the terminal receives a redirect message corresponding to the access network of the third network sent by the access network element of the second network, where the access network of the third network corresponds to The redirect message carries frequency information and/or cell information of the access network of the third network.
  • the terminal receives the release connection message sent by the second network, including:
  • the terminal receives the NAS connection release message sent by the core network element of the second network, enters an idle state, and selects to access the first network or the third network by using the configured frequency and/or cell selection priority information. .
  • the terminal receives the release connection message sent by the second network, including:
  • the terminal in the process of the terminal registering or attaching to the network side, the terminal receives the frequency and/or cell selection priority information sent by the network side.
  • the second network receives the fallback indication information corresponding to the target service sent by the terminal and/or the last used PLMN ID;
  • the second network After the terminal completes the target service in the second network, the second network sends a handover or redirection message to the terminal based on the fallback indication information corresponding to the target service and/or the last used PLMN ID. To trigger the terminal to switch or redirect from the second network to the first network; or the second network sends a redirect or release connection message to the terminal.
  • the receiving, by the second network, the fallback indication information corresponding to the target service sent by the terminal, and/or the last used PLMN ID includes:
  • the second network receives the AS parameter in the AS message and/or the NAS message sent by the terminal, and the AS parameter in the AS message and/or the NAS message carries the fallback indication information corresponding to the target service and/or the last use.
  • PLMN ID PLMN ID
  • the access network element of the second network obtains the fallback indication information corresponding to the target service and/or the last used PLMN ID from the AS parameters in the AS message and/or the NAS message.
  • the AS message includes at least one of the following: an RRC connection request message, a handover complete message, and an RRC connection setup complete message.
  • the AS parameter in the NAS message includes at least one of the following: an AS parameter in an attach request message, and an AS parameter in a tracking area update request message.
  • the access network element of the second network obtains the fallback indication information corresponding to the target service and/or the last used PLMN ID from the AS parameters in the AS message and/or the NAS message. .
  • the receiving, by the second network, the fallback indication information corresponding to the target service sent by the terminal, and/or the last used PLMN ID includes:
  • the second network receives the NAS message sent by the terminal, where the NAS message carries the fallback indication information corresponding to the target service and/or the last used PLMN ID;
  • the core network element of the second network obtains the fallback indication information corresponding to the target service and/or the last used PLMN ID from the NAS message, and the fallback indication information corresponding to the target service and / or the last used PLMN ID is sent to the access network element of the second network.
  • the NAS message includes at least one of the following: an NAS message in an attach request message, and a NAS message in a tracking area update request message.
  • the core network element of the second network obtains the fallback indication information corresponding to the target service and/or the last used PLMN ID from the NAS message, and the corresponding target service falls back.
  • the indication information and/or the last used PLMN ID are sent to the access network element of the second network.
  • the core network element of the second network sends the fallback indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network, including:
  • the core network element of the second network sends the drop indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network by using a bearer setup or release message; or,
  • the core network element of the second network sends the drop indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network by using an initial context setup request message.
  • the core network element of the second network receives the fallback indication information corresponding to the target service and/or the last used PLMN ID sent by the core network element of the first network, where The core network element of the second network sends the fallback indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network.
  • the core network element of the first network sends a voice QoS flow setup request message to the access network network element of the first network, and receives the access network element of the first network to send a reject message, the reject message carrying a cause value, the cause value being used to indicate that the reject message is caused by a fallback corresponding to the target service; if the core network element of the first network is at a first time Receiving the handover request message sent by the access network element of the first network, the reason that the core network element of the first network determines the handover request message is caused by the fallback of the target service .
  • the access network element of the second network completes the release of the bearer, and sends a handover or redirection message to the terminal.
  • the core network element of the second network completes the release of the bearer, and sends a handover or redirection message to the terminal.
  • the first network is selected as the target network of the terminal.
  • the method further includes: determining cell information and/or frequency information of the target network.
  • the first network is selected as the target network of the terminal based on the last used PLMN ID.
  • the access network element of the second network sends an RRC release message to the terminal, so that the The terminal releases the RRC connection to enter an idle state, and performs cell reselection through the RFSP policy, and returns to the first network.
  • the core network element of the second network sends an RRC release message to the terminal, so that the terminal Release the RRC connection to the idle state, and perform cell reselection through the RFSP policy, and return to the first network.
  • the second network sends a redirect or release connection message to the terminal, including:
  • the access network element of the second network After receiving the fallback indication information corresponding to the target service and/or the last used PLMN ID, the access network element of the second network sends a redirect or a redirect to the terminal from the core network element of the second network. Release the connection message.
  • the access network element of the second network sends a redirect message to the terminal, including:
  • the access network element of the second network detects that there is a base station of the first network in the target area around the terminal, and the signal strength of the base station of the first network is higher than the first threshold, The access network element of the second network sends the redirection message corresponding to the access network of the first network to the terminal, where the redirection message corresponding to the access network of the first network carries the Frequency information and/or cell information of a network access network;
  • the access network element of the second network detects that there is no base station of the first network or a base station of the first network in the target area around the terminal, but the signal strength of the base station of the first network is lower than a first threshold, where the access network element of the second network sends a redirect message corresponding to the access network of the third network to the terminal, where the access network of the third network corresponds to the weight
  • the orientation message carries frequency information and/or cell information of the access network of the third network.
  • the access network element of the second network sends a release connection message to the terminal, including:
  • the core network element of the second network sends a NAS connection release message to the terminal, to trigger the terminal to enter an idle state, and select to access the first network by using the configured frequency and/or cell selection priority information. Or the third network.
  • the access network element of the second network sends a release connection message to the terminal, including:
  • the access network element of the second network sends an RRC connection release message to the terminal, to trigger the terminal to enter an idle state, and select to access the first by using the configured frequency and/or cell selection priority information.
  • Network or third network
  • the network side in a process in which the terminal registers or attaches to the network side, the network side sends the frequency and/or cell selection priority information to the terminal.
  • the network returning device provided by the embodiment of the present invention is applied to a terminal, and the device includes:
  • a first network change unit configured to switch or redirect from the first network to the second network, and perform target service under the second network
  • a determining unit configured to determine, in a process of the terminal switching or redirecting from the first network to the second network, that the reason value of the handover or redirection is a fallback corresponding to a target service, where the cause value is Used to indicate that the handover or redirection is caused by a fallback corresponding to the target service;
  • a first sending unit configured to send, by the second network, fallback indication information corresponding to the target service and/or a last used PLMN ID;
  • a first receiving unit configured to receive a handover or redirection message sent by the second network after completing the target service in the second network; or receive a redirect or release connection message sent by the second network;
  • a second network changing unit configured to switch or redirect from the second network to the first network based on the switching or redirecting message.
  • the device further includes: a second receiving unit, configured to receive a handover command sent by the first network, where the handover command carries fallback indication information corresponding to the target service;
  • the determining unit is configured to determine, according to the handover command, that the reason value of the handover is a fallback corresponding to the target service, where the cause value is used to indicate that the handover is caused by a fallback corresponding to the target service.
  • a handover process is completed between the first network and the second network; or, the first network and the first The switching process is completed between the two networks through the third network.
  • the first network changing unit is configured to switch from the first access network to the second access network, and maintain the connection with the first core network unchanged.
  • the first network changing unit switches from the first access network to the second access network, and switches from the first core network to the second core network.
  • the device further includes: a third receiving unit, configured to receive a redirection message sent by the first network, where the redirection message carries the fallback indication information corresponding to the target service;
  • the determining unit is configured to determine, according to the redirect message, that the reason value of the redirection is a fallback corresponding to the target service, where the cause value is used to indicate that the redirection is caused by a fallback corresponding to the target service of.
  • the redirect message is an N2 request message or an RRC connection release message.
  • the device further includes: a second sending unit, configured to send a SIP invite message;
  • the determining unit is configured to: after receiving the SIP invite message, if the handover command or the RRC connection release message sent by the first network is received within the first duration, determining that the cause value of the handover or redirection is a target The traffic corresponding to the fallback, the reason value is used to indicate that the handover or redirection is caused by the fallback corresponding to the target service.
  • the first sending unit is configured to send an AS parameter in an AS message and/or a NAS message to the second network, where an AS parameter in the AS message and/or the NAS message carries a target.
  • the AS message includes at least one of the following: an RRC connection request message, a handover complete message, and an RRC connection setup complete message.
  • the AS parameter in the NAS message includes at least one of the following: an AS parameter in an attach request message, and an AS parameter in a tracking area update request message.
  • the access network element of the second network obtains the fallback indication information corresponding to the target service and/or the last used PLMN ID from the AS parameters in the AS message and/or the NAS message. .
  • the first sending unit is configured to send a NAS message to the second network, where the NAS message carries the fallback indication information corresponding to the target service and/or the last used PLMN ID.
  • the NAS message includes at least one of the following: an NAS message in an attach request message, and a NAS message in a tracking area update request message.
  • the core network element of the second network obtains the fallback indication information corresponding to the target service and/or the last used PLMN ID from the NAS message, and the corresponding target service falls back.
  • the indication information and/or the last used PLMN ID are sent to the access network element of the second network.
  • the core network element of the second network sends the fallback indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network, including:
  • the core network element of the second network sends the drop indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network by using a bearer setup or release message; or,
  • the core network element of the second network sends the drop indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network by using an initial context setup request message.
  • the core network element of the second network receives the fallback indication information corresponding to the target service and/or the last used PLMN ID sent by the core network element of the first network, where The core network element of the second network sends the fallback indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network.
  • the core network element of the first network sends a voice QoS flow setup request message to the access network network element of the first network, and receives the access network element of the first network to send a reject message, the reject message carrying a cause value, the cause value being used to indicate that the reject message is caused by a fallback corresponding to the target service; if the core network element of the first network is at a first time Receiving the handover request message sent by the access network element of the first network, the reason that the core network element of the first network determines the handover request message is caused by the fallback of the target service .
  • the access network element of the second network completes the release of the bearer, and the first receiving unit receives the connection of the second network.
  • the switch or redirect message sent by the network element is
  • the core network element of the second network completes the release of the bearer, and the first receiving unit receives the core network of the second network.
  • the switch or redirect message sent by the NE is not limited to the embodiment of the present invention.
  • the first network is selected as the target network of the terminal.
  • the terminal after selecting the first network as the target network of the terminal, determining cell information and/or frequency information of the target network.
  • the first network is selected as the target network of the terminal based on the last used PLMN ID.
  • the first receiving unit receives the RRC release message sent by the access network element of the second network, Release the RRC connection to enter the idle state, perform cell reselection through the radio resource management RFSP policy, and return to the first network.
  • the first receiving unit receives the RRC release message sent by the core network element of the second network, and releases the The RRC connection enters an idle state, performs cell reselection through the radio resource management RFSP policy, and returns to the first network.
  • the The first receiving unit receives the redirect or release connection message sent by the second network.
  • the access network element of the second network detects that the base station of the first network is in the target area around the terminal, and the signal strength of the base station of the first network is higher than the first door
  • the first receiving unit receives a redirect message corresponding to the access network of the first network sent by the access network element of the second network, where the access network of the first network Transmitting, by the corresponding redirection message, frequency information and/or cell information of the access network of the first network;
  • the first receiving unit receives a redirect message corresponding to the access network of the third network sent by the access network element of the second network, where the third network accesses
  • the redirect message corresponding to the network carries frequency information and/or cell information of the access network of the third network.
  • the first receiving unit receives the NAS connection release message sent by the core network element of the second network, to enter an idle state, and selects the selected frequency and/or the cell selection priority information. Into the first network or the third network.
  • the first receiving unit receives an RRC connection release message sent by the access network element of the second network, to enter an idle state, and uses the configured frequency and/or cell selection priority information to select Accessing the first network or the third network.
  • the first receiving unit in the process of the terminal registering or attaching to the network side, is further configured to receive the frequency and/or cell selection priority information sent by the network side.
  • the network returning device provided by the embodiment of the present invention is applied to a network, and the device includes:
  • a receiving unit configured to receive, in a process of the terminal switching or redirecting from the first network to the second network, the drop indication information corresponding to the target service sent by the terminal and/or the last used PLMN ID;
  • a sending unit configured to send, after the terminal completes the target service in the second network, a handover or redirect message to the terminal, according to the fallback indication information corresponding to the target service and/or the last used PLMN ID And triggering the terminal to switch or redirect from the second network to the first network; or sending a redirect or release connection message to the terminal.
  • the receiving unit is configured to receive an AS parameter in the AS message and/or the NAS message sent by the terminal, where the AS parameter in the AS message and/or the NAS message carries the target service.
  • the fallback indication information and/or the last used PLMN ID are obtained; the fallback indication information corresponding to the target service and/or the last used PLMN ID are obtained from the AS parameters in the AS message and/or the NAS message.
  • the AS message includes at least one of the following: an RRC connection request message, a handover complete message, and an RRC connection setup complete message.
  • the AS parameter in the NAS message includes at least one of the following: an AS parameter in an attach request message, and an AS parameter in a tracking area update request message.
  • the access network element of the second network obtains the fallback indication information corresponding to the target service and/or the last used PLMN ID from the AS parameters in the AS message and/or the NAS message. .
  • the receiving unit is configured to receive a NAS message sent by the terminal, where the NAS message carries the fallback indication information corresponding to the target service and/or the last used PLMN ID; from the NAS message Obtaining the fallback indication information corresponding to the target service and/or the last used PLMN ID, and sending the fallback indication information corresponding to the target service and/or the last used PLMN ID to the second network Network access network.
  • the NAS message includes at least one of the following: an NAS message in an attach request message, and a NAS message in a tracking area update request message.
  • the core network element of the second network obtains the fallback indication information corresponding to the target service and/or the last used PLMN ID from the NAS message, and the corresponding target service falls back.
  • the indication information and/or the last used PLMN ID are sent to the access network element of the second network.
  • the core network element of the second network sends the fallback indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network, including:
  • the core network element of the second network sends the drop indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network by using a bearer setup or release message; or,
  • the core network element of the second network sends the drop indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network by using an initial context setup request message.
  • the core network element of the second network receives the fallback indication information corresponding to the target service and/or the last used PLMN ID sent by the core network element of the first network, where The core network element of the second network sends the fallback indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network.
  • the core network element of the first network sends a voice QoS flow setup request message to the access network network element of the first network, and receives the access network element of the first network to send a reject message, the reject message carrying a cause value, the cause value being used to indicate that the reject message is caused by a fallback corresponding to the target service; if the core network element of the first network is at a first time Receiving the handover request message sent by the access network element of the first network, the reason that the core network element of the first network determines the handover request message is caused by the fallback of the target service .
  • the access network element of the second network completes the release of the bearer, and sends a handover or redirection message to the terminal.
  • the core network element of the second network completes the release of the bearer, and sends a handover or redirection message to the terminal.
  • the device further includes:
  • a selecting unit configured to select the first network as a target network of the terminal.
  • the apparatus further includes: a determining unit, configured to determine cell information and/or frequency information of the target network.
  • the selecting unit is configured to select the first network as the target network of the terminal based on the last used PLMN ID.
  • the access network element of the second network sends an RRC release message to the terminal, so that the The terminal releases the RRC connection to enter an idle state, and performs cell reselection through the RFSP policy, and returns to the first network.
  • the core network element of the second network sends an RRC release message to the terminal, so that the terminal Release the RRC connection to the idle state, and perform cell reselection through the RFSP policy, and return to the first network.
  • the The sending unit sends a redirect or release connection message to the terminal.
  • the sending unit sends, to the terminal, a redirect message corresponding to the access network of the first network, where the redirect message corresponding to the access network of the first network carries the first Frequency information and/or cell information of the access network of the network;
  • the sending unit sends a redirect message corresponding to the access network of the third network to the terminal, where the redirect message corresponding to the access network of the third network carries the Frequency information and/or cell information of the access network of the three networks.
  • the sending unit sends a NAS connection release message to the terminal, to trigger the terminal to enter an idle state, and select to access the first network by using the configured frequency and/or cell selection priority information. Or the third network.
  • the sending unit sends an RRC connection release message to the terminal, to trigger the terminal to enter an idle state, and select to access the first network by using the configured frequency and/or cell selection priority information. Or the third network.
  • the sending unit in the process of the terminal registering or attaching to the network side, is further configured to send the frequency and/or cell selection priority information to the terminal.
  • the computer storage medium provided by the embodiment of the present invention has stored thereon computer executable instructions, and the computer executable instructions are implemented by the processor to implement the network return method.
  • the terminal switches or redirects from the first network to the second network, and performs target service under the second network, where the terminal switches or redirects from the first network to In the process of the second network, determining that the cause value of the handover or redirection is a fallback corresponding to the target service, where the cause value is used to indicate that the handover or redirection is caused by a fallback corresponding to the target service. And sending the fallback indication information corresponding to the target service and/or the last used PLMN ID to the second network; after the terminal completes the target service in the second network, receiving the handover sent by the second network or A redirect message is switched or redirected from the second network to the first network based on the handover or redirect message.
  • the technical solution of the embodiment of the present invention provides a judgment and trigger mechanism to quickly return to the 5G network after the terminal ends the voice on the 4G network, thereby ensuring the experience of the terminal in the 5G network.
  • FIG. 1 is a system architecture diagram of a 5G network according to an embodiment of the present invention.
  • FIG. 2 is a system architecture diagram of a 4G network according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a handover (HO, Handover) process according to an embodiment of the present invention
  • FIG. 4(a) is a schematic flowchart 1 of a network fallback according to an embodiment of the present invention.
  • 4(b) is a second schematic flowchart of a network fallback according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart 1 of a network returning method according to an embodiment of the present invention.
  • FIG. 6 is a schematic flowchart 2 of a network returning method according to an embodiment of the present invention.
  • FIG. 7 is a first schematic structural diagram of a network return device according to an embodiment of the present invention.
  • FIG. 8 is a second schematic structural diagram of a network return device according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a computer device according to an embodiment of the present invention.
  • FIG. 10 is a schematic flowchart of an indirect fallback according to an embodiment of the present invention.
  • FIG. 11 is a schematic flowchart of redirecting or releasing a connection according to an embodiment of the present invention.
  • FIG. 1 is a system architecture diagram of a 5G network according to an embodiment of the present invention. As shown in FIG. 1 , the devices involved in the 5G network system include:
  • UE User Equipment
  • RAN Radio Access Network
  • UPF User Plane Function
  • DN Data Network
  • AMF Receive Core Access
  • Mobility Manager AMF
  • Session Management Function SMF
  • PCF Policy Control Function
  • AF Application Function
  • AUSF Authentication Server Function
  • UDM Unified Data Management
  • FIG. 2 is a system architecture diagram of a 4G network according to an embodiment of the present invention. As shown in FIG. 2, the devices involved in the 4G network system include:
  • UE User Equipment
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • MME Mobility Management Entity
  • SGSN Serving GPRS Support Node
  • HSS Home Subscriber Server
  • PDN Packet Data Network Gateway
  • PCRF Policy and Charging Rules Function Unit
  • FIG. 1 and FIG. 2 are only examples of a network architecture that implements the embodiments of the present invention.
  • the embodiments of the present invention are not limited to the network structures described in FIG. 1 and FIG.
  • FIG. 3 is a schematic diagram of a handover (HO, Handover) process according to an embodiment of the present invention.
  • the example of FIG. 3 describes a process of handover from a 5G network to a 4G network.
  • the 5G network may not support VoNR.
  • the 5G network needs to trigger the 5G ⁇ 4G Handover process or the Redirection process (see Figures 4(a) and 4(b). Shown), let the 4G network perform VoLTE, thereby completing the UE's request for voice establishment.
  • the 5G->4G Handover process or the Redirection process the following three types are included:
  • the 5G core network is unchanged, and the RAT is triggered to fall back when the UE needs to perform voice, and the RAT access is changed from NR to LTE, and then the VoLTE operation is performed.
  • the 5G core network switches to the 4G core network, and the RAT will also change from NR to LTE, and then perform VoLTE operation.
  • the base station of the 5G network directly sends an RRC Connection Release message to the UE, and carries cell information (Cell ID) and frequency (Frequency Band) information of the target network (such as a 4G network).
  • Cell ID cell ID
  • Frequency Band frequency
  • the above 1), 2), and 3) are all triggered by the RAN (ie, NG-RAN) on the 5G network side.
  • the RAN ie, NG-RAN
  • the 5G core network (5GC) is unchanged, and the AMF does not change during the RAT fallback process.
  • the NG-RAN sends a reject indication to the AMF in step 5b shown in Fig. 4(a), indicating that the reject is due to the HO being performed.
  • the NG-RAN sends a reject indication to the AMF in step 5b shown in FIG. 4(a), indicating that the reject is due to the HO being performed.
  • the technical solution of the embodiment of the present invention provides a judgment and trigger mechanism to quickly return to the 5G network after the terminal ends the voice on the 4G network.
  • the registration process and the session establishment process are mobility management (MM) and The session management (SM) is the most basic and most important process.
  • MM mobility management
  • SM session management
  • the voice support identifier is added to the UE in the registration process, and the NAS is sent to the SMF through the NAS-SM message, and the voice support is added to the UDM.
  • the identifier is sent to the SMF through a subscription data response message in the session establishment process for the SMF to determine when the 5G falls back to the 4G.
  • FIG. 5 is a schematic flowchart 1 of a network returning method according to an embodiment of the present invention. As shown in FIG. 5, the network returning method includes the following steps:
  • Step 501 The terminal switches or redirects from the first network to the second network, and performs target service under the second network, where the terminal switches or redirects from the first network to the second network.
  • determining that the cause value of the handover or redirection is a fallback corresponding to the target service where the cause value is used to indicate that the handover or redirection is caused by a fallback corresponding to the target service, and to the The second network sends the fallback indication information corresponding to the target service and/or the last used PLMN ID.
  • the first network is a 5G network
  • the second network is a 4G network
  • how does the terminal know that the performed handover or redirection is based on the fallback trigger corresponding to the target service is implemented by:
  • Manner 1 In the case that the terminal is switched from the first network to the second network, the terminal receives the handover command sent by the first network, where the handover command carries a fallback indication corresponding to the target service.
  • the information is determined by the terminal, based on the handover command, that the cause value of the handover is a fallback corresponding to the target service, and the cause value is used to indicate that the handover is caused by a fallback corresponding to the target service.
  • the UE adds a “target traffic corresponding fallback” indication to the Handover Command message on the 5G network, and the indication causes the UE to know that the triggered Handover is caused by the fallback corresponding to the target service.
  • the terminal switches from the first network to the second network, and has the following two switching modes:
  • RAT handover that is, the terminal switches from the first access network to the second access network, and maintains the connection with the first core network unchanged.
  • EPS switching that is, the terminal switches from the first access network to the second access network, and switches from the first core network to the second core network.
  • Manner 2 In the case that the terminal is redirected from the first network to the second network, the terminal receives a redirect message sent by the first network, where the redirect message carries a target service Corresponding fallback indication information; the terminal determines, according to the redirect message, that the reason value of the redirection is a fallback corresponding to the target service, where the cause value is used to indicate that the redirection is due to the target service Fallback caused.
  • a handover process is completed between the first network and the second network; or, the first network and the first The switching process is completed between the two networks through the third network.
  • FIG. 10 is a flow chart of indirect fallback.
  • the mechanism of indirect fallback is the same as the mechanism of direct fallback, but only requires the transition of the third system network element (generally 5G to 3G for SRVCC). This is the case).
  • the fallback in this case can be specifically for SRVCC to fall back.
  • the redirect message is an N2 request message or an RRC connection release message.
  • the UE adds a “target traffic corresponding fallback” indication to the RRC Connection Release message on the 5G network, and the indication causes the UE to know that the triggered redirection is caused by the fallback corresponding to the target service.
  • Manner 3 After the terminal sends the SIP invite message, if the handover command or the RRC connection release message sent by the first network is received in the first time period, it is determined that the reason value of the handover or redirection is the target service corresponding The reason value is used to indicate that the switching or redirection is caused by a fallback corresponding to the target service.
  • the UE may introduce a timer in a certain time. If the network side triggers the Handover or RRC Connection Release message, the UE considers that the handover or redirection is caused by the fallback of the target service.
  • how the second network knows that the UE is the UE that falls back to the target service is implemented in the following manner:
  • Manner 1 The terminal sends an AS parameter in the AS message and/or the NAS message to the second network, where the AS parameter in the AS message and/or the NAS message carries the fallback indication information corresponding to the target service and/or The last used PLMN ID.
  • the AS message includes at least one of the following: an RRC connection request message, a handover complete message, and an RRC connection setup complete message.
  • the AS parameter in the NAS message includes at least one of the following: an AS parameter in an attach request message, and an AS parameter in a tracking area update request message.
  • the access network element of the second network acquires the fallback indication information corresponding to the target service and/or the last used PLMN ID from the AS parameters in the AS message and/or the NAS message.
  • the UE carries the fallback indication information corresponding to the target service and/or the last used PLMN ID in the AS parameter in the AS message and/or the NAS message of the 4G network, and the connection establishment of the identifier with the 4G network is due to the fallback of the target service.
  • the implementation of the AS message is, for example, an RRC Connection Request, a Handover Complete, an RRC Connection setup complete, and an implementation of an AS parameter in the NAS message, for example, an attach request (Attach)
  • the AS parameter in the request), the AS parameter in the tracking area update request (TAU Request), and the 4G base station (eNodeB) knows that the UE is the "fallback corresponding to the target service" through the AS parameter in the AS message and/or the NAS message. And know the last used PLMN ID.
  • Manner 2 The terminal sends a NAS message to the second network, where the NAS message carries the fallback indication information corresponding to the target service and/or the last used PLMN ID.
  • the NAS message includes at least one of the following: an NAS message in an attach request message, and a NAS message in a tracking area update request message.
  • the core network element of the second network obtains the fallback indication information corresponding to the target service and/or the last used PLMN ID from the NAS message, and the fallback indication information corresponding to the target service and / or the last used PLMN ID is sent to the access network element of the second network.
  • the core network element of the second network sends the drop indication information corresponding to the target service and/or the last used PLMN ID to the access network of the second network by using a bearer setup or release message.
  • the core network element of the second network sends the drop indication information corresponding to the target service and/or the last used PLMN ID to the access of the second network by using an initial context setup request message. Network element.
  • the NAS carries the fallback indication information corresponding to the target service and/or the last used PLMN ID in the NAS message of the 4G network, and the connection establishment of the identifier with the 4G network is caused by the fallback of the target service
  • the implementation of the NAS message is as follows: Adding the fallback indication information corresponding to the target service and/or the last used PLMN ID in the NAS message in the Attach request message, carrying the fallback indication information corresponding to the target service and/or the last used PLMN ID in the NAS message of the TAU Request message .
  • the MME of the 4G network After receiving the indication, the MME of the 4G network transmits the indication to the eNodeB through the S1 interface in subsequent messages.
  • the fallback indication information and/or the last used PLMN ID is given to the eNodeB.
  • Manner 3 The core network element of the second network receives the fallback indication information corresponding to the target service and/or the last used PLMN ID sent by the core network element of the first network, where the second network The core network element sends the fallback indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network.
  • the core network element of the second network is the MME
  • the core network element of the first network is AMF
  • the access network element eNodeB of the second network for example: AMF through the N26 interface (AMF and
  • the interface between the MMEs is configured to inform the MME of the fallback indication information corresponding to the target service and/or the last used PLMN ID.
  • the MME of the 4G network passes the indication through the S1 interface in subsequent messages. Passed to the eNodeB.
  • the fallback indication information and/or the last used PLMN ID is given to the eNodeB.
  • the core network element of the first network sends a voice QoS flow setup request message to the access network network element of the first network, and receives the access network element of the first network to send a reject message, the reject message carrying a cause value, the cause value being used to indicate that the reject message is caused by a fallback corresponding to the target service; if the core network element of the first network is at a first time Receiving the handover request message sent by the access network element of the first network, the reason that the core network element of the first network determines the handover request message is caused by the fallback of the target service .
  • the core network element of the first network is an AMF, and the access network element gNodeB of the first network.
  • Step 502 After completing the target service in the second network, the terminal receives a handover or redirection message sent by the second network, and switches or re-chops from the second network based on the handover or redirection message. Oriented to the first network; or, after completing the target service in the second network, the terminal receives a redirect or release connection message sent by the second network.
  • how to trigger the network side to quickly return to the 5G network after the completion of the target service of the UE is implemented by:
  • Manner 1 1) After the terminal completes the target service in the second network, the access network element of the second network completes the release of the bearer, and the terminal receives the handover or redirection sent by the second network. Message. Or, after the terminal completes the target service in the second network, the core network element of the second network completes the release of the bearer, and the terminal receives the handover sent by the core network element of the second network. Or redirect the message.
  • the first network is selected as the target network of the terminal.
  • cell information and/or frequency information of the target network is determined.
  • the first network is selected as the target network of the terminal based on the last used PLMN ID.
  • Manner 2 1) After the terminal completes the target service in the second network, after completing the bearer release, the terminal receives the RRC release message sent by the access network element of the second network, and releases the RRC connection. In the idle state, cell reselection is performed through the radio resource management RFSP policy, and the process returns to the first network. Or, after the terminal completes the target service in the second network, after completing the bearer release, the terminal receives the RRC release message sent by the core network element of the second network, and releases the RRC connection to enter the idle state. Performing cell reselection through the radio resource management RFSP policy, and returning to the first network.
  • the UE sends an RRC Connection Release message to the UE after the call is released.
  • the eNodeB or the MME sends the RRC Connection Release message to the UE to release the RRC connection, so that the UE can quickly return to the idle (Idle) state, and the UE manages through radio resources.
  • the (RFSP) policy performs cell reselection and returns to the 5G network.
  • the foregoing target service of the embodiment of the present invention is not limited to the voice service, and may also be used for other services, and may be implemented by the present invention as long as the certain service needs to fall back and the network needs to return to the original network after the network is executed.
  • the fallback mechanism of the example For example, other services that are not supported by 5G can also be completed by falling back to EPC or even 3G, such as V2X (vehicle networking) services, public security services, and so on.
  • the RAN side must only send a redirect or release connection to the UE (the handover return cannot be triggered). That is, after the access network element of the second network receives the fallback indication information corresponding to the target service and/or the last used PLMN ID from the core network element of the second network, the terminal receives the A redirect or release connection message sent by the second network.
  • the access network element of the second network receives the fallback indication information corresponding to the target service and/or the last used PLMN ID from the core network element of the second network.
  • the receiving, by the terminal, the redirect message sent by the second network includes:
  • the access network element of the second network detects that there is a base station of the first network in the target area around the terminal, and the signal strength of the base station of the first network is higher than the first threshold, Receiving, by the terminal, a redirection message corresponding to the access network of the first network sent by the access network element of the second network, where the redirection message corresponding to the access network of the first network carries the Frequency information and/or cell information of the access network of the first network;
  • the terminal receives a redirect message corresponding to the access network of the third network sent by the access network element of the second network, where the access network of the third network corresponds to The redirect message carries frequency information and/or cell information of the access network of the third network.
  • the receiving, by the terminal, the release connection message sent by the second network includes:
  • the terminal receives the NAS connection release message sent by the core network element of the second network, enters an idle state, and selects to access the first network or the third network by using the configured frequency and/or cell selection priority information. .
  • the receiving, by the terminal, the release connection message sent by the second network includes:
  • the terminal in the process of registering or attaching the terminal to the network side, receives the frequency and/or cell selection priority information sent by the network side.
  • the network side performs one of the following actions:
  • the 3G RAN detects that there is a 5G base station around the UE, it preferentially sends a redirection to the 5G RAN to the UE, that is, the frequency and/or cell information of the target 5G RAN is included in the RRC Connection Release message. If there is no 5G base station or 5G base station signal below the UE below a certain strength, the 3G-RAN sends a redirect to the 4G RAN to the UE.
  • the UE reports the 4G GUTI and/or the original 5G GUTI mapped by the original 5G GUTI, and the MME queries the 5GC AMF for the saved session management context information.
  • the MSC sends the NAS connection release to the UE or the RRC connection is immediately released on the 3G RAN side, so that the UE returns to the idle state, and the UE uses the previously configured frequency/cell selection priority information to select the access 5G or 4G. Network cell access.
  • FIG. 6 is a schematic flowchart 2 of a network returning method according to an embodiment of the present invention. As shown in FIG. 6, the network returning method includes the following steps:
  • Step 601 In the process of the terminal switching or redirecting from the first network to the second network, the second network receives the fallback indication information corresponding to the target service sent by the terminal and/or the last used PLMN ID.
  • the first network is a 5G network
  • the second network is a 4G network
  • the second network receives the fallback indication information corresponding to the target service sent by the terminal and/or the last used PLMN ID, and is implemented by:
  • the second network receives the AS parameter in the AS message and/or the NAS message sent by the terminal, and the AS parameter in the AS message and/or the NAS message carries the fallback indication information corresponding to the target service and/or Or the last used PLMN ID; the access network element of the second network acquires the fallback indication information corresponding to the target service and/or the last used PLMN from the AS parameters in the AS message and/or the NAS message. ID.
  • the AS message includes at least one of the following: an RRC connection request message, a handover complete message, and an RRC connection setup complete message.
  • the AS parameter in the NAS message includes at least one of the following: an AS parameter in an attach request message, and an AS parameter in a tracking area update request message.
  • the access network element of the second network acquires the fallback indication information corresponding to the target service and/or the last used PLMN ID from the AS parameters in the AS message and/or the NAS message. .
  • the second network receives the NAS message sent by the terminal, where the NAS message carries the fallback indication information corresponding to the target service and/or the last used PLMN ID; the core network element of the second network is from Obtaining, in the NAS message, the fallback indication information corresponding to the target service and/or the last used PLMN ID, and sending the fallback indication information corresponding to the target service and/or the last used PLMN ID to the The access network element of the second network.
  • the NAS message includes at least one of the following: an NAS message in an attach request message, and a NAS message in a tracking area update request message.
  • the core network element of the second network obtains the fallback indication information corresponding to the target service and/or the last used PLMN ID from the NAS message, and the corresponding target service falls back.
  • the indication information and/or the last used PLMN ID are sent to the access network element of the second network.
  • the core network element of the second network sends the drop indication information corresponding to the target service and/or the last used PLMN ID to the second network by using a bearer setup or release message.
  • the access network element; or the core network element of the second network sends the drop indication information corresponding to the target service and/or the last used PLMN ID to the second by using an initial context setup request message Network access network element.
  • the core network element of the second network receives the fallback indication information corresponding to the target service and/or the last used PLMN ID sent by the core network element of the first network, where The core network element of the second network sends the fallback indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network.
  • the core network element of the first network sends a voice QoS flow setup request message to the access network network element of the first network, and receives the access network element of the first network to send a reject message, the reject message carrying a cause value, the cause value being used to indicate that the reject message is caused by a fallback corresponding to the target service; if the core network element of the first network is at a first time Receiving the handover request message sent by the access network element of the first network, the reason that the core network element of the first network determines the handover request message is caused by the fallback of the target service .
  • Step 602 After the terminal completes the target service in the second network, the second network sends a handover or a heavy to the terminal based on the fallback indication information corresponding to the target service and/or the last used PLMN ID. Orienting a message to trigger the terminal to switch or redirect from the second network to the first network; or the second network sends a redirect or release connection message to the terminal.
  • the access network element of the second network completes the release of the bearer, and sends a handover or redirection message to the terminal.
  • the core network element of the second network completes the release of the bearer, and sends a handover or redirection message to the terminal.
  • the first network is selected as the target network of the terminal.
  • the method further comprises determining cell information and/or frequency information of the target network.
  • the first network is selected as the target network of the terminal based on the last used PLMN ID.
  • the access network element of the second network after the terminal completes the target service in the second network, after completing the bearer release, the access network element of the second network sends an RRC release message to the terminal, so that the terminal The terminal releases the RRC connection to enter an idle state, and performs cell reselection through the RFSP policy, and returns to the first network.
  • the core network element of the second network sends an RRC release message to the terminal, so that the terminal Release the RRC connection to the idle state, and perform cell reselection through the RFSP policy, and return to the first network.
  • the second network sends a redirect or release connection message to the terminal, including:
  • the access network element of the second network After receiving the fallback indication information corresponding to the target service and/or the last used PLMN ID, the access network element of the second network sends a redirect or a redirect to the terminal from the core network element of the second network. Release the connection message.
  • the access network element of the second network sends a redirect message to the terminal, including:
  • the access network element of the second network detects that there is a base station of the first network in the target area around the terminal, and the signal strength of the base station of the first network is higher than the first threshold, The access network element of the second network sends the redirection message corresponding to the access network of the first network to the terminal, where the redirection message corresponding to the access network of the first network carries the Frequency information and/or cell information of a network access network;
  • the access network element of the second network detects that there is no base station of the first network or a base station of the first network in the target area around the terminal, but the signal strength of the base station of the first network is lower than a first threshold, where the access network element of the second network sends a redirect message corresponding to the access network of the third network to the terminal, where the access network of the third network corresponds to the weight
  • the orientation message carries frequency information and/or cell information of the access network of the third network.
  • the access network element of the second network sends a release connection message to the terminal, including:
  • the core network element of the second network sends a NAS connection release message to the terminal, to trigger the terminal to enter an idle state, and select to access the first network by using the configured frequency and/or cell selection priority information. Or the third network.
  • the access network element of the second network sends a release connection message to the terminal, including:
  • the access network element of the second network sends an RRC connection release message to the terminal, to trigger the terminal to enter an idle state, and select to access the first by using the configured frequency and/or cell selection priority information.
  • Network or third network
  • the network side in a process in which the terminal registers or attaches to the network side, the network side sends the frequency and/or cell selection priority information to the terminal.
  • FIG. 7 is a schematic structural diagram of a network return device according to an embodiment of the present invention.
  • the device in this embodiment is applied to a terminal.
  • the network return device includes:
  • the first network changing unit 701 is configured to switch or redirect from the first network to the second network, and perform target service under the second network;
  • the determining unit 702 is configured to determine, in the process of the terminal switching or redirecting from the first network to the second network, that the reason value of the handover or redirection is a fallback corresponding to the target service, where the reason The value is used to indicate that the handover or redirection is caused by a fallback corresponding to the target service;
  • a first sending unit 703 configured to send, by the second network, fallback indication information corresponding to the target service and/or a last used PLMN ID;
  • the first receiving unit 704 is configured to: after completing the target service in the second network, receive a handover or redirection message sent by the second network; or receive a redirect or release connection message sent by the second network ;
  • the second network changing unit 705 is configured to switch or redirect from the second network to the first network based on the handover or redirect message.
  • the device further includes: a second receiving unit 706, configured to receive a handover command sent by the first network, where the handover command carries the fallback indication information corresponding to the target service;
  • the determining unit 702 is configured to determine, according to the handover command, that the reason value of the handover is a fallback corresponding to the target service, where the cause value is used to indicate that the handover is caused by a fallback corresponding to the target service.
  • a handover process is completed between the first network and the second network; or, the first network and the first The switching process is completed between the two networks through the third network.
  • the first network changing unit 701 is configured to switch from the first access network to the second access network, and maintain the connection with the first core network unchanged.
  • the first network changing unit 701 switches from the first access network to the second access network, and switches from the first core network to the second core network.
  • the terminal in the case that the terminal is redirected from the first network to the second network:
  • the device further includes: a third receiving unit 707, configured to receive the redirection message sent by the first network, where the redirection message carries the fallback indication information corresponding to the target service;
  • the determining unit 702 is configured to determine, according to the redirect message, that the reason value of the redirection is a fallback corresponding to the target service, where the cause value is used to indicate that the redirection is due to a fallback of the target service Caused.
  • the redirect message is an N2 request message or an RRC connection release message.
  • the apparatus further includes: a second sending unit 708, configured to send a SIP invite message;
  • the determining unit 702 is configured to: after receiving the SIP invite message, if the handover command or the RRC connection release message sent by the first network is received within the first duration, determining that the cause value of the handover or redirection is A fallback corresponding to the target service, where the cause value is used to indicate that the handover or redirection is caused by a fallback corresponding to the target service.
  • the first sending unit 703 is configured to send an AS parameter in an AS message and/or a NAS message to the second network, where the AS parameter in the AS message and/or the NAS message is carried in an AS parameter.
  • the fallback indication information corresponding to the target service and/or the last used PLMN ID.
  • the AS message includes at least one of the following: an RRC connection request message, a handover complete message, and an RRC connection setup complete message.
  • the AS parameter in the NAS message includes at least one of the following: an AS parameter in an attach request message, and an AS parameter in a tracking area update request message.
  • the access network element of the second network acquires the fallback indication information corresponding to the target service and/or the last used PLMN ID from the AS parameters in the AS message and/or the NAS message. .
  • the first sending unit 703 is configured to send a NAS message to the second network, where the NAS message carries the fallback indication information corresponding to the target service and/or the last used PLMN ID.
  • the NAS message includes at least one of the following: an NAS message in an attach request message, and a NAS message in a tracking area update request message.
  • the core network element of the second network obtains the fallback indication information corresponding to the target service and/or the last used PLMN ID from the NAS message, and the corresponding target service falls back.
  • the indication information and/or the last used PLMN ID are sent to the access network element of the second network.
  • the core network element of the second network sends the fallback indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network, including:
  • the core network element of the second network sends the drop indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network by using a bearer setup or release message; or,
  • the core network element of the second network sends the drop indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network by using an initial context setup request message.
  • the core network element of the second network receives the fallback indication information corresponding to the target service and/or the last used PLMN ID sent by the core network element of the first network, where The core network element of the second network sends the fallback indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network.
  • the core network element of the first network sends a voice QoS flow setup request message to the access network network element of the first network, and receives the access network element of the first network.
  • a reject message carrying a cause value, the cause value being used to indicate that the reject message is caused by a fallback corresponding to the target service; if the core network element of the first network is at a first time Receiving the handover request message sent by the access network element of the first network, the reason that the core network element of the first network determines the handover request message is caused by the fallback of the target service .
  • the access network element of the second network completes the release of the bearer, and the first receiving unit 704 receives the second network.
  • the core network element of the second network completes the release of the bearer, and the first receiving unit 704 receives the core of the second network.
  • the first network is selected as the target network of the terminal.
  • the selecting the first network as the target network of the terminal determining cell information and/or frequency information of the target network.
  • the first network is selected as the target network of the terminal based on the last used PLMN ID.
  • the first receiving unit 704 receives the RRC release message sent by the access network element of the second network. And releasing the RRC connection to enter an idle state, performing cell reselection through the radio resource management RFSP policy, and returning to the first network.
  • the first receiving unit 704 receives the RRC release message sent by the core network element of the second network, Release the RRC connection to enter the idle state, perform cell reselection through the radio resource management RFSP policy, and return to the first network.
  • the The first receiving unit receives the redirect or release connection message sent by the second network.
  • the access network element of the second network detects a base station of the first network in the target area around the terminal, and the signal strength of the base station of the first network is higher than the first door
  • the first receiving unit receives a redirect message corresponding to the access network of the first network sent by the access network element of the second network, where the access network of the first network Transmitting, by the corresponding redirection message, frequency information and/or cell information of the access network of the first network;
  • the first receiving unit receives a redirect message corresponding to the access network of the third network sent by the access network element of the second network, where the third network accesses
  • the redirect message corresponding to the network carries frequency information and/or cell information of the access network of the third network.
  • the first receiving unit receives the NAS connection release message sent by the core network element of the second network to enter an idle state, and selects the selected frequency and/or the cell selection priority information. Into the first network or the third network.
  • the first receiving unit receives an RRC connection release message sent by an access network element of the second network, to enter an idle state, and uses the configured frequency and/or cell selection priority information to select Accessing the first network or the third network.
  • the first receiving unit in the process of registering or attaching the terminal to the network side, is further configured to receive the frequency and/or cell selection priority information sent by the network side.
  • the implementation functions of the units in the network return device shown in FIG. 7 can be understood by referring to the related description of the foregoing network return method.
  • the functions of the units in the network returning device shown in FIG. 7 can be implemented by a program running on the processor, or can be realized by a specific logic circuit.
  • FIG. 8 is a schematic structural diagram of a network return device according to an embodiment of the present invention.
  • the device in this embodiment is applied to a network.
  • the network return device includes:
  • the receiving unit 801 is configured to: when the terminal switches or redirects to the second network from the first network, receive the fallback indication information corresponding to the target service sent by the terminal, and/or the last used PLMN ID;
  • the sending unit 802 is configured to send, after the terminal completes the target service in the second network, a handover or redirection to the terminal, according to the fallback indication information corresponding to the target service and/or the last used PLMN ID. a message to trigger the terminal to switch or redirect from the second network to the first network; or send a redirect or release connection message to the terminal.
  • the receiving unit 801 is configured to receive an AS parameter in the AS message and/or the NAS message sent by the terminal, where the AS parameter in the AS message and/or the NAS message carries the target service corresponding And the last used PLMN ID is obtained from the AS parameters in the AS message and/or the NAS message.
  • the AS message includes at least one of the following: an RRC connection request message, a handover complete message, and an RRC connection setup complete message.
  • the AS parameter in the NAS message includes at least one of the following: an AS parameter in an attach request message, and an AS parameter in a tracking area update request message.
  • the access network element of the second network acquires the fallback indication information corresponding to the target service and/or the last used PLMN ID from the AS parameters in the AS message and/or the NAS message. .
  • the receiving unit 801 is configured to receive a NAS message sent by the terminal, where the NAS message carries the fallback indication information corresponding to the target service and/or the last used PLMN ID; from the NAS message. Obtaining the fallback indication information corresponding to the target service and/or the last used PLMN ID, and sending the fallback indication information corresponding to the target service and/or the last used PLMN ID to the second network. Access network element.
  • the NAS message includes at least one of the following: an NAS message in an attach request message, and a NAS message in a tracking area update request message.
  • the core network element of the second network obtains the fallback indication information corresponding to the target service and/or the last used PLMN ID from the NAS message, and the corresponding target service falls back.
  • the indication information and/or the last used PLMN ID are sent to the access network element of the second network.
  • the core network element of the second network sends the fallback indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network, including:
  • the core network element of the second network sends the drop indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network by using a bearer setup or release message; or,
  • the core network element of the second network sends the drop indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network by using an initial context setup request message.
  • the core network element of the second network receives the fallback indication information corresponding to the target service and/or the last used PLMN ID sent by the core network element of the first network, where The core network element of the second network sends the fallback indication information corresponding to the target service and/or the last used PLMN ID to the access network element of the second network.
  • the core network element of the first network sends a voice QoS flow setup request message to the access network network element of the first network, and receives the access network element of the first network.
  • a reject message carrying a cause value, the cause value being used to indicate that the reject message is caused by a fallback corresponding to the target service; if the core network element of the first network is at a first time Receiving the handover request message sent by the access network element of the first network, the reason that the core network element of the first network determines the handover request message is caused by the fallback of the target service .
  • the access network element of the second network completes the release of the bearer, and sends a handover or redirection message to the terminal.
  • the core network element of the second network completes the release of the bearer, and sends a handover or redirection message to the terminal.
  • the device further includes:
  • the selecting unit 803 is configured to select the first network as a target network of the terminal.
  • the apparatus further includes: a determining unit 804, configured to determine cell information and/or frequency information of the target network.
  • the selecting unit 803 is configured to select the first network as the target network of the terminal based on the last used PLMN ID.
  • the access network element of the second network after the terminal completes the target service in the second network, after completing the bearer release, the access network element of the second network sends an RRC release message to the terminal, so that the terminal The terminal releases the RRC connection to enter an idle state, and performs cell reselection through the RFSP policy, and returns to the first network.
  • the core network element of the second network sends an RRC release message to the terminal, so that the terminal Release the RRC connection to the idle state, and perform cell reselection through the RFSP policy, and return to the first network.
  • the handover or redirection message sent by the sending unit 802 to the terminal carries cell information and/or frequency information of the first network.
  • the The sending unit sends a redirect or release connection message to the terminal.
  • the sending unit sends, to the terminal, a redirect message corresponding to the access network of the first network, where the redirect message corresponding to the access network of the first network carries the first Frequency information and/or cell information of the access network of the network;
  • the sending unit sends a redirect message corresponding to the access network of the third network to the terminal, where the redirect message corresponding to the access network of the third network carries the Frequency information and/or cell information of the access network of the three networks.
  • the sending unit sends a NAS connection release message to the terminal to trigger the terminal to enter an idle state, and select to access the first network by using the configured frequency and/or cell selection priority information. Or the third network.
  • the sending unit sends an RRC connection release message to the terminal, to trigger the terminal to enter an idle state, and select to access the first network by using the configured frequency and/or cell selection priority information. Or the third network.
  • the sending unit in the process of registering or attaching the terminal to the network side, is further configured to send the frequency and/or cell selection priority information to the terminal.
  • the implementation functions of the units in the network returning apparatus shown in FIG. 8 can be understood by referring to the related description of the foregoing network returning method.
  • the functions of the units in the network return device shown in FIG. 8 can be implemented by a program running on the processor, or can be realized by a specific logic circuit.
  • the network return device described above may also be stored in a computer readable storage medium if it is implemented in the form of a software function module and sold or used as a standalone product. Based on such understanding, the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions.
  • a computer device (which may be a personal computer, server, or network device, etc.) is caused to perform all or part of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read only memory (ROM), a magnetic disk, or an optical disk.
  • program codes such as a USB flash drive, a mobile hard disk, a read only memory (ROM), a magnetic disk, or an optical disk.
  • the embodiment of the present invention further provides a computer storage medium, wherein the computer executable instructions are stored, and the computer executable instructions are executed by the processor to implement the network return method of the embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a computer device according to an embodiment of the present invention.
  • the computer device may be a terminal or a network device.
  • computer device 100 may include one or more (only one shown) processor 1002 (processor 1002 may include, but is not limited to, a Micro Controller Unit (MCU) or a programmable logic device.
  • a processing device such as an FPGA (Field Programmable Gate Array), a memory 1004 for storing data, and a transmission device 1006 for a communication function.
  • FPGA Field Programmable Gate Array
  • FIG. 9 is merely illustrative and does not limit the structure of the above electronic device.
  • computer device 100 may also include more or fewer components than shown in FIG. 9, or have a different configuration than that shown in FIG.
  • the memory 1004 can be used to store software programs and modules of application software, such as program instructions/modules corresponding to the method in the embodiment of the present invention, and the processor 1002 executes various functional applications by running software programs and modules stored in the memory 1004. And data processing, that is, to achieve the above method.
  • Memory 1004 can include high speed random access memory, and can also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory.
  • memory 1004 can further include memory remotely located relative to processor 1002, which can be connected to computer device 100 over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • Transmission device 1006 is for receiving or transmitting data via a network.
  • the network specific examples described above may include a wireless network provided by a communication provider of computer device 100.
  • the transmission device 1006 includes a Network Interface Controller (NIC) that can be connected to other network devices through a base station to communicate with the Internet.
  • the transmission device 1006 can be a radio frequency (RF) module for communicating with the Internet wirelessly.
  • NIC Network Interface Controller
  • RF radio frequency
  • the disclosed method and smart device 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 such as: multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored or not executed.
  • the coupling, or direct coupling, or communication connection of the components shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical, mechanical or other forms. of.
  • the units described above as separate components may or may not be physically separated, and the components displayed as the unit may or may not be physical units, that is, may be located in one place or 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 invention may be integrated into one second processing unit, or each unit may be separately used as one unit, or two or more units may be integrated into one unit;
  • the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

Landscapes

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

Abstract

La présente invention concerne un procédé et un appareil de retour de réseau, et un support de stockage informatique. Le procédé comprend les étapes suivantes : un terminal commute ou est redirigé d'un premier réseau vers un second réseau et effectue un service cible dans le second réseau, dans lequel dans le processus du terminal commutant ou étant redirigé du premier réseau vers le second réseau, il est déterminé qu'une valeur de cause de commutation ou de redirection est un repli correspondant au service cible, et la valeur de cause est utilisée pour indiquer que la commutation ou la redirection est provoquée par le repli correspondant au service cible, et des informations d'indication de repli correspondant au service cible et/ou à un identifiant de PLMN utilisé en dernier est/sont envoyés au second réseau; et après achèvement du service cible dans le second réseau, le terminal reçoit un message de commutation ou de redirection envoyé par le second réseau, et la commutation ou la redirection, sur la base du message de commutation ou de redirection, du second réseau au premier réseau, ou, après achèvement du service cible dans le second réseau, le terminal reçoit un message de redirection ou de libération de connexion envoyé par le second réseau.
PCT/CN2018/082849 2018-02-05 2018-04-12 Procédé et appareil de retour de réseau, et support de stockage informatique WO2019148654A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201880037301.8A CN110710247B (zh) 2018-02-05 2018-04-12 一种网络返回方法及装置、计算机存储介质

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
CNPCT/CN2018/075332 2018-02-05
CN2018075332 2018-02-05
CNPCT/CN2018/075872 2018-02-08
CN2018075872 2018-02-08
CNPCT/CN2018/076879 2018-02-14
PCT/CN2018/076879 WO2019148552A1 (fr) 2018-02-05 2018-02-14 Procédé et appareil de retour à un réseau, et support de stockage informatique

Publications (1)

Publication Number Publication Date
WO2019148654A1 true WO2019148654A1 (fr) 2019-08-08

Family

ID=67477821

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2018/076879 WO2019148552A1 (fr) 2018-02-05 2018-02-14 Procédé et appareil de retour à un réseau, et support de stockage informatique
PCT/CN2018/082849 WO2019148654A1 (fr) 2018-02-05 2018-04-12 Procédé et appareil de retour de réseau, et support de stockage informatique

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/076879 WO2019148552A1 (fr) 2018-02-05 2018-02-14 Procédé et appareil de retour à un réseau, et support de stockage informatique

Country Status (2)

Country Link
CN (2) CN110710265B (fr)
WO (2) WO2019148552A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111356195A (zh) * 2020-03-03 2020-06-30 深圳前海达闼云端智能科技有限公司 网络选择的方法、装置、存储介质及网络设备
TWI775266B (zh) * 2020-01-07 2022-08-21 聯發科技股份有限公司 用於多種無線電存取技術協調之使用者設備和方法

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113498123B (zh) * 2020-03-20 2023-06-02 华为技术有限公司 一种网络接入系统、方法及终端
CN113747517B (zh) * 2020-05-28 2023-02-03 中国电信股份有限公司 EPS Fallback后从LTE重定向到NR的方法和设备
CN114071620B (zh) * 2020-08-05 2024-03-26 华为技术有限公司 通信方法、装置及系统
CN112243280B (zh) * 2020-10-20 2023-05-09 Oppo广东移动通信有限公司 业务发起方法、装置、终端及存储介质
CN112399517B (zh) * 2020-12-02 2022-08-26 中国联合网络通信集团有限公司 一种终端切换方法及系统
CN112996066B (zh) * 2021-02-10 2023-04-07 展讯通信（上海）有限公司 驻网方法及相关设备
CN112804720B (zh) * 2021-02-25 2023-03-14 北京小米移动软件有限公司 网络切换方法及装置
CN115398969A (zh) * 2021-03-23 2022-11-25 北京小米移动软件有限公司 网络切换方法及装置、存储介质
CN115209491B (zh) * 2021-04-12 2024-04-19 维沃移动通信有限公司 信息处理方法、装置、终端及网络侧设备
CN113260088B (zh) * 2021-04-21 2023-05-30 RealMe重庆移动通信有限公司 保持通话业务的方法、装置、终端和存储介质
CN115767483A (zh) * 2021-09-02 2023-03-07 维沃移动通信有限公司 无线网络服务的配置方法、终端及网络侧设备
CN115314960B (zh) * 2021-11-29 2023-04-07 北京广厦网络技术股份公司 获取性能指标的方法、存储介质及电子设备
CN116456403A (zh) * 2022-01-07 2023-07-18 维沃移动通信有限公司 重定向的方法、终端及网络侧设备

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103906158A (zh) * 2012-12-28 2014-07-02 展讯通信（上海）有限公司 一种从2g/3g网络返回lte网络的方法

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014094260A1 (fr) * 2012-12-19 2014-06-26 华为技术有限公司 Procédé, dispositif et système pour un retour dans un réseau de type évolution à long terme après un appel
WO2014200408A1 (fr) * 2013-06-14 2014-12-18 Telefonaktiebolaget L M Ericsson (Publ) Premier nœud de réseau, second nœud de réseau, et procédés correspondants, pour la fourniture d'un dernier identifiant de réseau mobile terrestre public utilisé
CN104284380A (zh) * 2013-07-09 2015-01-14 中国移动通信集团公司 多模终端的网络返回方法及多模终端
CN104904265B (zh) * 2013-12-31 2019-04-16 华为技术有限公司 一种选择长期演进lte网络的方法及设备
US10117145B2 (en) * 2015-01-28 2018-10-30 At&T Mobility Ii Llc User equipment based fast return to LTE
EP3324702A4 (fr) * 2015-08-17 2018-08-08 Huawei Technologies Co., Ltd. Procédé et appareil de redémarrage après défaillance à commutation de circuits
CN105338584B (zh) * 2015-09-29 2019-04-02 中国联合网络通信集团有限公司 一种返回lte网络的方法及装置
WO2017101118A1 (fr) * 2015-12-18 2017-06-22 华为技术有限公司 Procédé et dispositif pour traiter un appel vocal
CN107548108A (zh) * 2016-06-28 2018-01-05 中兴通讯股份有限公司 一种基于重定向的频点确定方法及装置

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103906158A (zh) * 2012-12-28 2014-07-02 展讯通信（上海）有限公司 一种从2g/3g网络返回lte网络的方法

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CHINA UNICOM: "Discussion for returning back to NR in case of handover for voice", SA WG2 MEETING #122BIS, S2-175487, 15 August 2017 (2017-08-15), XP051325340 *
OPPO ET AL.: "Discussion for returning back to NR in case of handover for voice", SA WG2 MEETING #122BIS, S 2-176976, 17 October 2017 (2017-10-17), XP051346932 *
OPPO ET AL.: "Returning back to NR in case of handover for voice", SA WG2 MEETING #122BIS, S2-176977, 17 October 2017 (2017-10-17), XP051346933 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI775266B (zh) * 2020-01-07 2022-08-21 聯發科技股份有限公司 用於多種無線電存取技術協調之使用者設備和方法
US11751279B2 (en) 2020-01-07 2023-09-05 Mediatek Inc. Apparatuses and methods for multi-radio access technology (RAT) coordination
CN111356195A (zh) * 2020-03-03 2020-06-30 深圳前海达闼云端智能科技有限公司 网络选择的方法、装置、存储介质及网络设备

Also Published As

Publication number Publication date
CN110710265A (zh) 2020-01-17
CN110710265B (zh) 2021-03-05
CN110710247B (zh) 2021-06-29
WO2019148552A1 (fr) 2019-08-08
CN110710247A (zh) 2020-01-17

Similar Documents

Publication Publication Date Title
WO2019148654A1 (fr) Procédé et appareil de retour de réseau, et support de stockage informatique
JP7351395B2 (ja) Ｕｅ及びｕｅの方法
US10694571B2 (en) Service processing method and service processing apparatus
KR102205907B1 (ko) 이동 통신 시스템에서 서비스 제공 장치 및 방법
WO2019096077A1 (fr) Procédé de transfert intercellulaire de réseau et élément de réseau de gestion de session
KR101339044B1 (ko) 서빙 코어 네트워크 노드가 변경될 때의 모바일 장치의 접근성의 처리
US10827394B2 (en) Triggering selective fallback based on user subscription information
JP7188462B2 (ja) Ｕｅの方法及びｕｅ
JP2020529167A (ja) ネットワークハンドオーバ方法、装置、およびシステム
WO2011153702A1 (fr) Procédé, appareil et système pour la sélection d'un réseau mobile terrestre public
CA3045177A1 (fr) Methode et appareil d'utilisation de ladn dans un systeme de communication sans fil
US20180007720A1 (en) Service processing method, related apparatus, and system
JP2021509546A (ja) ネットワーク切替方法、ネットワークデバイス及び端末デバイス
WO2014005444A1 (fr) Procédé d'accès, système, entité de gestion de mobilité et équipement utilisateur pour mise en dérivation de réseau local sans fil
CN110505662B (zh) 一种策略控制方法、装置及系统
CN105706518A (zh) Csfb呼叫建立方法及装置
WO2010099741A1 (fr) Procédé de sélection de réseau, dispositif et terminal
WO2013152546A1 (fr) Procédé de resélection de cellule et équipement utilisateur
US11051268B2 (en) Service activation and deactivation method, device and computer storage medium
CN113163349B (zh) 用于语音业务的通信方法、装置和系统
WO2014146500A1 (fr) Procédé de changement de réseau d'accès radio, et procédé et dispositif de traitement du changement
WO2021098389A1 (fr) Procédé de redirection et appareil électronique pour terminal inactif, et support lisible par ordinateur
WO2012040918A1 (fr) Procédé, appareil, et système pour la sélection de technologie cible d'accès radio
WO2019090788A1 (fr) Procédé et appareil de déclenchement de transfert de réseau, et support de stockage informatique
US11974355B2 (en) Indication information sending method, apparatus and system, and storage medium

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: 18903546

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18903546

Country of ref document: EP

Kind code of ref document: A1