WO2023029537A1 - Ue间业务迁移方法、装置和存储介质 - Google Patents

Ue间业务迁移方法、装置和存储介质 Download PDF

Info

Publication number
WO2023029537A1
WO2023029537A1 PCT/CN2022/090060 CN2022090060W WO2023029537A1 WO 2023029537 A1 WO2023029537 A1 WO 2023029537A1 CN 2022090060 W CN2022090060 W CN 2022090060W WO 2023029537 A1 WO2023029537 A1 WO 2023029537A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
source
service
base station
service migration
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2022/090060
Other languages
English (en)
French (fr)
Inventor
沙秀斌
戴博
陆婷
牛丽
谈杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to AU2022337484A priority Critical patent/AU2022337484B2/en
Priority to US18/687,282 priority patent/US20240373335A1/en
Priority to EP22862680.0A priority patent/EP4398640A4/en
Publication of WO2023029537A1 publication Critical patent/WO2023029537A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/148—Migration or transfer of sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/32—Release of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to mobile communication technologies, for example, to a method, device and storage medium for inter-UE service migration.
  • UE User Equipment
  • some terminal users have good visual experience and low energy-saving requirements (such as computers, TVs, tablet computers, etc.), but are not convenient to move; some terminals are convenient to move, but have high energy-saving requirements (such as smart terminals).
  • Users may need to migrate the same service between different UEs during use. For example, users watch videos indoors through a computer connected to a wireless network. When users move from indoors to outdoors, video services need to be migrated to smartphones. However, service switching between different UEs may cause service interruption or discontinuity, affecting user experience.
  • the present application provides a service migration method, device and storage medium between UEs, which realize smooth migration of services between UEs of the same user.
  • the embodiment of the present application provides a service migration method between UEs, including:
  • the target UE sends service migration related information to the base station, and the service migration related information is used to indicate that the first service data of the source UE is migrated to the target UE, and the source UE and the target UE belong to the same PIoT;
  • the target UE receives the first service data sent by the base station, wherein the GTP-U tunnels of the target UE and the source UE are associated with the same PDU session.
  • the embodiment of the present application provides a service migration method between UEs, which includes:
  • the source UE sends service migration indication information to the base station or the core network, and the service migration indication information is used to indicate that the first service data of the source user equipment is migrated to the target UE;
  • the source UE receives a link deletion message or a radio bearer deletion instruction sent by the base station to which the target UE is connected, and the link deletion message includes the NAS identifier or PIoT terminal identifier of the source UE;
  • the source UE deletes the Uu link between the base station connected to the source UE or the radio bearer corresponding to the migrated service.
  • a method for service migration between UEs including:
  • the base station receives service migration related information sent by the target UE, where the service migration related information is used to indicate that the first service data of the source UE is migrated to the target UE, and the source UE and the target UE belong to the same PIoT;
  • the base station sends the first service data to the target UE, wherein the GTP-U of the target UE and the source UE are associated with the same PDU session.
  • a method for service migration between UEs including:
  • the core network device receives service migration related information, and the service migration related information is used to migrate the first service data of the source UE to the target UE;
  • the core network device determines that the source UE and the target UE belong to the same PIoT, associate the GTP-U of the target UE and the source UE with the same PDU session.
  • the embodiment of the present application provides a UE, where the UE is a target UE, including:
  • a sending module configured to send service migration related information to the base station, where the service migration related information is used to indicate that the first service data of the source UE is migrated to the target UE, and the source UE and the target UE belong to the same PIoT;
  • the receiving module is configured to receive the first service data sent by the base station, wherein the GTP-U tunnels of the target UE and the source UE are associated to the same PDU session.
  • the embodiment of the present application provides a UE, where the UE is a source UE, including:
  • a sending module configured to send service migration indication information to a base station or a core network, where the service migration indication information is used to indicate to migrate the first service data of the source UE to the target UE;
  • the receiving module is configured to receive a link deletion message or a radio bearer deletion instruction sent by the base station to which the target UE is connected, where the link deletion message includes the NAS identifier or the PIoT terminal identifier of the source UE;
  • the connection module is used to delete the Uu link between the base station connected to the source UE or the radio bearer corresponding to the migrated service.
  • the embodiment of the present application provides a base station, including:
  • the receiving module is configured to receive service migration related information sent by the target user equipment UE, where the service migration related information is used to indicate that the first service data of the source UE is migrated to the target UE, and the source UE and the target UE belong to the same PIoT;
  • the sending module is used for the base station to send the first service data to the target UE, wherein the GTP-U of the target UE and the source UE are associated to the same PDU session.
  • the embodiment of the present application provides a core network device, including:
  • a receiving module configured to receive service migration related information, where the service migration related information is used to migrate the first service data of the source user equipment UE to the target UE;
  • the processing module is used to associate the GTP-U of the target UE and the source UE with the same PDU session when it is determined that the source UE and the target UE belong to the same network PIoT.
  • the embodiment of the present application provides a storage medium containing computer-executable instructions, and the computer-executable instructions are used to execute any possible implementation manner of the first aspect to the fourth aspect of the UE when executed by a computer processor. Inter-business migration method.
  • the target UE after the target UE sends the service migration-related information indicating to migrate the first service data of the source UE to the target UE to the base station, the target UE receives the information sent by the base station.
  • the first service data wherein, the GTP-U tunnel of the target UE and the source UE are associated with the same PDU session, the source UE and the target UE belong to the same PIoT, and the smooth migration of services between UEs of the same user is realized.
  • Figure 1 is a schematic diagram of service migration between different devices under the same base station
  • FIG. 2 is a flow chart of a method for inter-UE service migration provided by an embodiment of the present application
  • FIG. 3 is a flow chart of another method for inter-UE service migration provided by the embodiment of the present application.
  • FIG. 4 is a flow chart of another method for inter-UE service migration provided by the embodiment of the present application.
  • FIG. 5 is a flow chart of another method for inter-UE service migration provided by the embodiment of the present application.
  • FIG. 6 is a flowchart of a first interaction of a service migration method between UEs provided in an embodiment of the present application
  • FIG. 7 is a second interaction flow chart of the inter-UE service migration method provided by the embodiment of the present application.
  • FIG. 8 is a flowchart of a third interaction of a service migration method between UEs provided in an embodiment of the present application.
  • FIG. 9 is a fourth interaction flowchart of a method for service migration between UEs provided in an embodiment of the present application.
  • FIG. 10 is a fifth interaction flowchart of the inter-UE service migration method provided by the embodiment of the present application.
  • FIG. 1 is a schematic diagram of service migration between different devices under the same base station. As shown in Figure 1, the left side shows that there is a wireless connection between UE1 and the base station (gNB), carrying services, and the user wants to migrate services from UE1 to UE2.
  • gNB base station
  • FIG. 1 shows a schematic diagram of service migration in the same gNB, and the situation of service migration between different gNBs is similar.
  • the inter-UE service migration method proposed in the embodiment of the present application specifies in detail how to realize the specific implementation method of service migration between different UEs shown in FIG. 1 .
  • the source UE refers to the UE before the service migration
  • the target UE refers to the target UE of the service migration
  • the source UE and the target UE may be any kind of UE capable of network connection.
  • the service migration from the source UE to the target UE can be triggered by the source UE or the target UE.
  • the source UE and the target UE are UEs of the same user, to be precise, the source UE and the target UE belong to the same Personal Internet of Things (PIoT), so when performing service migration between the source UE and the target UE, there is no need to Perform re-login, authentication and other processes to ensure the continuity of business migration.
  • PoT Personal Internet of Things
  • Figure 2 is a flow chart of a method for service migration between UEs provided in the embodiment of the present application. As shown in Figure 2, the method for service migration between UEs provided in this embodiment includes:
  • Step S210 the target UE sends service migration related information to the base station, the service migration related information is used to indicate to migrate the first service data of the source UE to the target UE, and the source UE and the target UE belong to the same PIoT.
  • the inter-UE service migration method provided in this embodiment is applied to the target UE.
  • the target UE In order to migrate the first service originally running on the source UE to the target UE, that is, to migrate the first service data sent to the source UE to the target UE, the target UE The service migration related information needs to be sent to the base station first.
  • the target UE sends service relocation related information to the base station accessed by itself.
  • the service migration related information is used to indicate to migrate the first service data of the source UE to the target UE.
  • the service migration-related information includes at least one of the following information: a service switch indication (Service switch indication), a protocol data unit (Protocol Data Unit, PDU) session identifier to be migrated, and a source UE identifier (UE1's NAS ID).
  • a service switch indication Service switch indication
  • PDU Protocol Data Unit
  • UE1's NAS ID source UE identifier
  • the target UE can also receive the information sent by the home subscription server (Home Subscriber Server, HSS) or unified data management function (Unified Data Management, UDM).
  • HSS Home Subscriber Server
  • UDM Unified Data Management
  • the source UE and the target UE may access the same base station or different base stations. If the source UE and the target UE access the same base station, the core network may not be involved in the service handover.
  • the service migration from the source UE to the target UE can be triggered by the target UE or by the source UE. Wherein, if triggered by the target UE, the target UE directly sends service migration related information to the base station. If triggered by the source UE, the source UE directly sends service migration related information to the base station. If triggered by the source UE, the source UE sends service migration indication information to the base station, where the service migration indication information is used to indicate to migrate the first service data of the source user equipment to the target UE.
  • the service migration instruction information includes at least one of the following information: service migration instruction, PDU session identifier to be migrated, target UE identifier (UE2's NAS ID).
  • the base station determines a target UE for service migration according to the service relocation indication information, and sends a paging message to the target UE, where the paging message includes the service relocation indication information.
  • the target UE may carry service migration related information in the paging response sent to the base station.
  • the service migration from the source UE to the target UE can be triggered by the target UE or by the source UE. Wherein, if triggered by the target UE, after the target UE sends the service migration related information to the base station, the base station sends the service migration related information to the core network.
  • the core network equipment completes the migration of services from the source UE to the target UE, that is, after associating the GTP-U tunnels of the target UE and the source UE with the same PDU session, it sends a response to the base station connected to the target UE, so that the base station notifies the source UE and the target UE .
  • the source UE sends the service relocation instruction information to the core network through the base station connected to the source UE or directly sends the service relocation instruction information to the core network.
  • the service migration instruction information is used to indicate to migrate the first service data of the source user equipment to the target UE.
  • the service migration instruction information includes at least one of the following information: service migration instruction, PDU session identifier to be migrated, and target UE identifier.
  • the core network device determines the target UE for service migration according to the service migration indication information, and sends a paging message to the target UE through the base station accessed by the target UE, and the paging message includes the service migration indication information.
  • the target UE may carry service migration related information in the paging response sent to the base station.
  • Step S220 the target UE receives the first service data sent by the base station, wherein the GTP-U tunnels of the target UE and the source UE are associated with the same PDU session.
  • the base station accessed by the target UE may determine that the first service data of the source UE needs to be migrated to the target UE according to the service migration related information. Therefore, the base station can send the first service data to the target UE.
  • the user plane GPRS tunneling protocol GPRS Tunneling Protocol-User Plane, GTP-U
  • GTP-U GPRS Tunneling Protocol-User Plane
  • the GTP-U tunnel of the target UE and the source UE are associated to the same PDU session, which is associated by the core network.
  • the base station can send the received service migration related information to the core network equipment, so that the core network equipment executes GTP-U Tunnel association.
  • the target UE may also receive a radio resource control (Radio Resource Control, RRC) reconfiguration message sent by the base station, and the RRC reconfiguration message includes the cell wireless network temporary identifier (Cell -Radio Network Temporary Identifier C-RNTI), wherein both the source UE and the target UE access the base station and receive the same user plane data. That is, when the source UE and the target UE access the same base station, the base station controls service migration.
  • RRC Radio Resource Control
  • Radio Link Control Radio Link Control
  • HARQ Hybrid Automatic Repeat reQuest
  • Both the source UE and the target UE feed back RLC status information and/or HARQ ACK/NACK, and the base station receives the RLC status information and/or HARQ ACK/NACK fed back by any UE to decide whether to retransmit or the base station receives both The RLC status information and/or HARQ ACK/NACK fed back by the UE decides whether to retransmit.
  • the base station retransmits service data when receiving the RLC status information fed back by the target UE and the source UE and/or the HARQ Negative Acknowledgment (NACK) message at the same time, or receives the RLC status information fed back by the target UE or the source UE and/or The base station retransmits service data when the HARQ non-response NACK message is received.
  • NACK HARQ Negative Acknowledgment
  • Unacknowledged Mode Unacknowledged Mode, UM
  • the target UE does not feed back RLC status information and/or HARQ ACK/NACK.
  • the target UE after the target UE sends service migration-related information indicating to migrate the first service data of the source UE to the target UE to the base station, the target UE receives the first service data sent by the base station, Among them, the GTP-U tunnel of the target UE and the source UE are associated with the same PDU session, and the source UE and the target UE belong to the same PIoT, which realizes the smooth migration of services between UEs of the same user.
  • FIG 3 is a flow chart of another inter-UE service migration method provided in the embodiment of the present application.
  • the inter-UE service migration method provided in this embodiment includes:
  • Step S310 the source UE sends service migration instruction information to the base station or the core network, and the service migration instruction information is used to indicate to migrate the first service data of the source user equipment to the target UE.
  • the inter-UE service migration method provided in this embodiment is applied to the source UE.
  • the source UE In order to migrate the first service originally running on the source UE to the target UE, that is, to migrate the first service data sent to the source UE to the target UE, the source UE The service migration indication information needs to be sent to the base station or the core network first.
  • the source UE sends service migration instruction information to the base station it accesses or directly to the core network.
  • the service migration indication information is used to indicate to migrate the first service data of the source UE to the target UE.
  • the service migration instruction information includes at least one of the following information: service migration instruction, PDU session identifier to be migrated, and target UE identifier.
  • Step S320 the source UE receives a link deletion message or a radio bearer deletion instruction sent by the base station to which the target UE is connected, and the link deletion message includes the NAS identifier or the PIoT terminal identifier of the source UE.
  • Step S330 the source UE deletes the Uu link between the base station connected to the source UE or the radio bearer corresponding to the migrated service.
  • the link or radio bearer of the source UE needs to be deleted.
  • the source UE receives the link deletion message or the radio bearer deletion instruction sent by the base station to which the target UE is connected, it can delete the Uu link between the source UE and the connected base station or the radio bearer corresponding to the migrated service.
  • the source UE and the target UE may be connected to the same base station, or the source UE and the target UE may be connected to different base stations.
  • the Uu link of the source UE or the radio bearer corresponding to the migrated service is decided to be deleted by the base station, or it may be decided to be deleted after the source UE reports a release indication, or it may be released actively by the base station after sensing that the synchronization with the target UE is completed. After allocating the C-RNTI of the source UE to the target UE, it is also necessary to determine how the source UE reports the release indication.
  • the source UE can report a release request to the core network, which carries the NAS identifier of the source UE and/or the PDU session identifier to be migrated, and the core network sends a UE context modification request (UE CONTEXT MODIFICATION REQUEST) to the base station, which carries the NAS identifier of the source UE and PIoT context release indication.
  • UE CONTEXT MODIFICATION REQUEST UE CONTEXT MODIFICATION REQUEST
  • the source UE can report a release request to the base station, which carries the NAS identifier of the source UE and/or the PDU session identifier to be migrated, and the release request is an RRC message or a Media Access Control Control Element (Media Access Control Element, MAC CE) .
  • the base station sends an RRC message or MAC CE carrying the NAS identifier or PIoT terminal identifier of the source UE to the source base station to trigger the source UE to delete the
  • FIG. 4 is a flow chart of another inter-UE service migration method provided in the embodiment of the present application. As shown in FIG. 4 , the inter-UE service migration method provided in this embodiment includes:
  • Step S410 the base station receives service migration related information sent by the target UE, the service migration related information is used to indicate to migrate the first service data of the source to the target UE, and the source UE and the target UE belong to the same PIoT.
  • the inter-UE service migration method provided in this embodiment is applied to a base station, specifically, a base station accessed by a target UE. After receiving the information related to service relocation sent by the target UE, the base station determines that service relocation needs to be performed.
  • the service migration related information is used to indicate to migrate the first service data of the source UE to the target UE.
  • the service migration-related information includes at least one of the following information: service migration indication, PDU session identifier to be migrated, and source UE identifier.
  • the base station After receiving the service migration related information sent by the target UE, the base station sends the service migration related information to the core network (CoreNetwork, CN), so that the CN associates the GTP-U tunnel of the target UE and the source UE with the same PDU session.
  • CoreNetwork CoreNetwork
  • the base station receives the service migration indication information sent by the source UE, and the service migration indication information is used to indicate that the first service data of the source user equipment is migrated to the target UE; then the base station Sending a paging message to the target UE, where the paging message includes service migration indication information; the base station receives a paging response message sent by the target UE, where the paging response message includes information related to service migration.
  • the service migration indication information includes at least one of the following information: a service migration indication, a PDU session identifier to be migrated, and a target UE identifier.
  • Step S420 the base station sends the first service data to the target UE, wherein the GTP-U of the target UE and the source UE are associated with the same voice PDU session.
  • the base station accessed by the target UE may determine that the first service data of the source UE needs to be migrated to the target UE according to the service migration related information. Therefore, the base station can send the first service data to the target UE.
  • the GTP-U tunnels of the target UE and the source UE are associated to the same PDU session.
  • the GTP-U tunnel of the target UE and the source UE are associated to the same PDU session, which is associated by the core network.
  • the base station can send the received service migration related information to the core network equipment, so that the core network equipment executes GTP-U Tunnel association.
  • the base station may also send an RRC reconfiguration message to the target UE.
  • the RRC reconfiguration message includes the C-RNTI of the source UE, wherein both the source UE and the target UE access the base station. That is, when the source UE and the target UE access the same base station, the base station controls service migration.
  • the base station sends the RRC reconfiguration message to the target UE.
  • the base station may determine that the target UE and the source UE belong to the same PIoT when the Uu link of the target UE and the source UE exists at the same time, and send a radio resource control RRC reconfiguration message to the target UE. Or, after the base station sends the RRC reconfiguration message to the target UE, and determines that the Uu links of the target UE and the source UE exist at the same time, it determines that the target UE and the source UE belong to the same PIoT.
  • the base station may also delete the link established with the source UE.
  • the base station deletes the link established with the source UE, after the base station receives the link sent by the source UE or the radio bearer corresponding to the first service, deletes the link established with the source UE or the radio bearer corresponding to the first service; or, After determining that the data of the first service is migrated to the target UE, the base station deletes the link established with the source UE or the radio bearer corresponding to the first service.
  • the base station After the base station receives the link release instruction sent by the source UE, delete the link established with the source UE, including: after the base station receives the UE context modification request and the PIoT context release instruction sent by the core network, send a link deletion message to the source UE, The link deletion message is used to instruct the source UE to delete the Uu link with the base station.
  • the UE context modification request and PIoT context release indication are the link release requests sent by the core network and carrying the source UE's non-access stratum NAS identifier.
  • the UE context modification request includes the NAS identifier of the source UE
  • the link deletion message is an RRC message or MAC CE
  • the link deletion message includes the NAS identifier or PIoT terminal identifier of the source UE
  • send a link delete message to the source UE.
  • the link delete message is used to instruct the source UE to delete the Uu link between the base station and the base station.
  • the link release request is an RRC message or MAC CE.
  • the link delete message includes NAS ID or PIoT terminal ID of the source UE.
  • Deleting the radio bearer corresponding to the first service established by the source UE includes: after receiving the UE context modification request and the PIoT context release indication sent by the core network, the base station sends a bearer release indication to the source UE, and the bearer release indication uses
  • the UE context modification request and the PIoT context release indication are after the core network receives the service release request carrying the non-access stratum NAS identifier of the source UE sent by the source UE Triggered
  • the UE context modification request includes the NAS identifier of the source UE and/or the PDU session identifier to be migrated
  • the bearer release indication is an RRC message or MAC CE
  • FIG. 5 is a flowchart of another inter-UE service migration method provided in the embodiment of the present application. As shown in FIG. 5 , the inter-UE service migration method provided in this embodiment includes:
  • Step S510 the core network device receives service migration related information, and the service migration related information is used to migrate the first service data of the source UE to the target UE.
  • the inter-UE service migration method provided in this embodiment is applied to core network devices, where the core network devices may be any one or more types of core network devices that perform corresponding functions.
  • the core network device may receive service migration related information forwarded by the base station connected to the target UE, or the core network device may also receive service migration instruction information directly sent by the source UE.
  • the service migration related information is used to indicate that the first service data of the source UE is migrated to the target UE, and the service migration instruction information is used to indicate that the first service data of the source UE is migrated to the target UE.
  • Step S520 when the core network device determines that the source UE and the target UE belong to the same PIoT, associate the GTP-U of the target UE and the source UE with the same PDU session.
  • the core network device determines that the service of the source UE needs to be migrated to the target UE according to the service migration information, it first needs to determine that the source UE and the target UE belong to the same PIoT, and then associate the GTP-U of the target UE and the source UE with the same PDU session. In this way, the first service data sent to the source UE can be migrated to the target UE.
  • the access and mobility management function receives information related to service migration.
  • AMF Access and Mobility Management Function
  • the AMF may receive service migration related information sent by the base station accessed by the target UE; or, the AMF may receive service indication related information sent by the base station accessed by the source UE or the AMF may receive service migration indication information directly sent by the source UE.
  • the AMF sends a paging message to the base station accessed by the target UE.
  • the paging message is used to make the base station accessed by the target UE send paging information to the target UE.
  • In the paging message Includes business migration instructions.
  • the HSS or UDM When the service migration is triggered by the target UE, the HSS or UDM sends the target UE the PIoT subscription information to which the target UE belongs, and the PIoT subscription information includes a list of UE identities belonging to the same user.
  • the HSS or UDM sends the PIoT subscription information to which the source UE belongs to the source UE and/or the AMF.
  • the AMF determines that the source UE and the target UE belong to the same PIoT, it sends a session management update request to the session management function (Session Management Function, SMF), and the session management update request includes information about the PDU session related to the source UE;
  • the user plane function (User Plane Function, UPF) sends a session establishment request, which includes the core network channel information of the source UE; UPF sends a session establishment response to the SMF, and the session establishment response includes the PDU session related to the source UE Information;
  • the SMF sends a session management update response to the AFM, and the session management update response includes information about the PDU session related to the source UE.
  • service migration is completed on the core network side.
  • the data flow of the user plane is copied in the UPF.
  • the UPF copies the first service data of the source UE, it sends it to the target UE through the base station accessed by the target UE.
  • UE1 is the source UE
  • UE2 is the target UE
  • gNB is the base station to which the source UE and the target UE are simultaneously connected
  • the second gNB is the base station to which the target UE is connected
  • the first gNB is the base station to which the source UE is connected.
  • the Authentication Server Function is used to authenticate the UE.
  • FIG. 6 is a flowchart of the first interaction of the inter-UE service migration method provided by the embodiment of the present application, and FIG. 6 is a flowchart of user plane continuity migration interaction triggered by the target UE to migrate services under the same base station from the source UE to the target UE.
  • the HSS/UDM sends the PIoT subscription information to UE2, including PIoT related information (UE subscription information (Including Personal IoT related information)).
  • gNB maintains RRC connection state (RRC_CONNRCTED_state) (CM_CONNRCTED_state) with UE1 and SMF, SMF establishes a GTP-U tunnel of PDU session A for UE1, and gNB can send service data (UP Date) to UE1.
  • UE2 triggers service migration to gNB through RRC Msg3/Msg5, including service migration indication, PDU session identifier to be migrated, and source UE identifier (Including Service request, Service switch indication, PDU session indication, UE1's NAS ID).
  • N2 message N2 Message(Including Service request, Service switch indication, PDU session indication, UE1's NAS ID)
  • AMF authenticates UE2 through AUSF (Authentication Security).
  • AMF sends N2 request (N2 Request(Service switch indication, UE 1 GTP-U Tunnel for PDU session A, UE1's NAS ID)) to gNB,
  • N2 request N2 Request(Service switch indication, UE 1 GTP-U Tunnel for PDU session A, UE1's NAS ID)
  • AMF also associates the GTP-U of the target UE and source UE with the same PDU session ( associate UE1 PDU Session A with UE2 GTP-U Tunnel).
  • gNB When gNB judges that UE1 and UE2 are switching between two identical PIoT devices, it sends an RRC reconfiguration message (RRC Reconfiguration) to UE2, including UE1's C-RNTI (C_RNTI of UE1). gNB migrates the service data of UE1 to UE2 (Data duplication and convergence). Finally, gNB instructs UE1 to release the link (RRC or MAC CE for Release Indication (5G-S-TMSI)).
  • RRC Reconfiguration RRC reconfiguration message
  • C_RNTI C-RNTI of UE1
  • gNB migrates the service data of UE1 to UE2 (Data duplication and convergence).
  • gNB instructs UE1 to release the link (RRC or MAC CE for Release Indication (5G-S-TMSI)).
  • FIG. 7 is a second interaction flowchart of the inter-UE service migration method provided by the embodiment of the present application.
  • FIG. 7 is a control plane continuity migration interaction flowchart of service migration from the source UE to the target UE triggered by the target UE under the same base station.
  • the HSS/UDM sends the PIoT subscription information to UE2, including PIoT related information (UE subscription information (Including Personal IoT related information)).
  • gNB maintains RRC connection state (RRC_CONNRCTED_state) (CM_CONNRCTED_state) with UE1 and SMF, SMF establishes a GTP-U tunnel of PDU session A for UE1, and gNB can send service data (UP Date) to UE1.
  • UE2 triggers service migration to gNB through RRC Msg3/Msg5, including service migration indication, PDU session identifier to be migrated, and source UE identifier (Including Service request, Service switch indication, PDU session indication, UE1's NAS ID).
  • N2 message N2 Message(Including Service request, Service switch indication, PDU session indication, UE1's NAS ID)
  • AMF authenticates UE2 through AUSF (Authentication Security).
  • AMF sends N2 request (N2 Request(Service switch indication, UE 1 GTP-U Tunnel for PDU session A, UE1's NAS ID)) to gNB,
  • N2 request N2 Request(Service switch indication, UE 1 GTP-U Tunnel for PDU session A, UE1's NAS ID)
  • AMF also associates the GTP-U of the target UE and source UE with the same PDU session ( associate UE1 PDU Session A with UE2 GTP-U Tunnel).
  • gNB sends an RRC reconfiguration message (RRC Reconfiguration) to UE2, and gNB migrates the service data of UE1 to UE2 (Data duplication and convergence).
  • RRC Reconfiguration RRC reconfiguration
  • gNB judges that UE1 and UE2 are handovers between two identical PIoT devices, gNB instructs UE1 to release the link (RRC ConnectionRelease or MAC CE for Release Indication).
  • the base station determines that the two UEs belong to the same PIoT: transfer the data cache of UE1 to UE2 (the NG port can share a link, and the NG port goes through the modify process); at the same time, it sends an RRCConnectionRelease message to UE1.
  • FIG. 8 is a third interaction flow diagram of the inter-UE service migration method provided by the embodiment of the present application.
  • FIG. 8 is an interaction flow diagram of continuous migration of services under the same base station triggered by the source UE from the source UE to the target UE.
  • the HSS/UDM sends the PIoT subscription information to UE1, including PIoT related information (UE subscription information (Including Personal IoT related information)).
  • gNB maintains RRC connection state (RRC_CONNRCTED_state) (CM_CONNRCTED_state) with UE1 and SMF, SMF establishes a GTP-U tunnel of PDU session A for UE1, and gNB can send service data (UP Date) to UE1.
  • UE1 triggers service migration to gNB through NAS PDU, which includes service migration indication, PDU session identifier to be migrated, and target UE identifier (NAS PDU (Service request, Service switch indication, PDU session indication, UE2's NAS ID)).
  • NAS PDU Service request, Service switch indication, PDU session indication, UE2's NAS ID
  • gNB sends N2 message (N2 Message(Including Service request, Service switch indication, PDU session indication, UE2's NAS ID)) to AMF.
  • AMF sends a paging message (PAGING (Service switch indication, PDU session indication, UE1's NAS ID)) to gNB.
  • PAGING Service switch indication, PDU session indication, UE1's NAS ID
  • PAGING Service switch indication, PDU session indication, UE1's NAS ID
  • FIG. 9 is a fourth interaction flow diagram of the inter-UE service migration method provided by the embodiment of the present application, and FIG. 9 is an interaction flow diagram of a continuous migration interaction triggered by the target UE based on core network perception service migration from the source UE to the target UE.
  • the HSS/UDM sends the PIoT subscription information to UE2, including PIoT related information (UE subscription information (Including Personal IoT related information)).
  • gNB1 maintains the RRC connection state (RRC_CONNRCTED_state) (CM_CONNRCTED_state) with UE1 and SMF, SMF establishes a GTP-U tunnel for PDU session A for UE1, and gNB1 can send service data (UP Date) to UE1.
  • UE2 triggers service migration to gNB2 (Service Request (including UE1 APID or Address, Service Switch Ind), and gNB2 sends N2 message (N2 Message (Including Service Request)) to AMF.
  • AMF authenticates UE2 through AUSF (Authentication Security).
  • AMF When AMF judges that UE1 and UE2 are switching between two identical PIoT devices, AMF sends a session management update request (Nsmf_PDU Session_UpdateSMContext Request) to SMF, which carries UE1 PDUSession A related information, such as PDU SessionID of PDUSession A, CN Tunnel Info, etc.
  • the N4 session establishment request (Session Establishment Request) sent by SMF to UPF carries UE1CN Tunnel Info).
  • the N4 session establishment response (Session Establishment Response) sent by UPF to SMF carries UE1 PDUSession A related information, such as PDU SessionID of PDUSession A, CN Tunnel Info, etc.
  • SMF sends session management update response (Nsmf_PDUSession_UpdateSMContext Response) to AMF, which contains PDU SessionID of PDUSession A, CN Tunnel Info, QFI(s), QoS profile(s), CN N3Tunnel Info, S-NSSAI, User Plane Security Enforcement, UE egrity Protection Maximum Data Rate, RSN, etc.
  • the data flow of the user plane is copied in the UPF and transmitted on the links of the two UEs respectively (association between CN session/tunnel IDs before switching and after switching.).
  • AMF sends N2 request (N2 Request) to gNB2, gNB2 item UE1 sends RRC reconfiguration message (RRCReconfiguration), UE1 sends RRC reconfiguration complete message (RRCReconfigurationComplete) to gNB2, and then gNB2 sends N2 request response (N2 Request Ack) to AMF.
  • UPF migrates the business data of UE1 to UE2 (Data duplication and convergence). When the UPF transmits and receives data, it simultaneously transmits data on the GTP-U tunnels of UE1 and UE2, or performs simultaneous data reception/combination on the GTP-U tunnels of UE1 and UE2.
  • Fig. 10 is a fifth interaction flow diagram of the inter-UE service migration method provided by the embodiment of the present application, and Fig. 10 is an interaction flow diagram of user plane continuity migration triggered by the source UE based on core network perception service migration from the source UE to the target UE .
  • the HSS/UDM sends the PIoT subscription information to UE1 and AMF, including PIoT related information (UE subscription information (Including Personal IoT related information)), and UE1 and/or AMF store the subscription information.
  • gNB1 maintains the RRC connection state (RRC_CONNRCTED_state) (CM_CONNRCTED_state) with UE1 and SMF, carrying PDU Session A, SMF establishes a GTP-U tunnel for PDU session A for UE1, and gNB1 can send service data (UP Date) to UE1.
  • UE1 triggers service migration to AMF (Service Request (including UE2 APID or Address, Service Switch Ind), AMF sends a paging message (Paging (including UE1 APID or Address, Service Switch Ind)) to gNB2, and gNB2 sends a paging message to UE2 (Paging(including UE1 APID or Address,Service Switch Ind)).
  • UE2 then sends a service request (Service Request(including UE1 APID or Address,Service Switch Ind)) to gNB2, and gNB2 sends an N2 message (N2 Message(Including Service Switch Ind)) to AMF Request)).
  • the AMF performs authentication (Authentication Security) on the UE2 through the AUSF.
  • the subsequent process in Figure 10 is the same as the subsequent service migration process in Figure 9, and will not be repeated here.
  • the embodiment of the present application also provides a UE, where the UE is a target UE, including:
  • the sending module is configured to send service migration related information to the base station, the service migration related information is used to indicate that the first service data of the source UE is migrated to the target UE, and the source UE and the target UE belong to the same PIoT; the receiving module is used to receive the information sent by the base station The first service data, wherein the GTP-U tunnels of the target UE and the source UE are associated with the same PDU session.
  • the UE provided in this embodiment is used to implement the inter-UE service migration method in the embodiment shown in FIG. 2 .
  • This embodiment of the present application also provides a UE, where the UE is a source UE, including:
  • the sending module is configured to send service migration instruction information to the base station or the core network, and the service migration instruction information is used to indicate that the first service data of the source UE is migrated to the target UE; the receiving module is used to receive the link sent by the base station connected to the target UE A deletion message, the link deletion message includes the NAS identifier of the source UE or the PIoT terminal identifier; the connection module is used to delete the Uu link between the base stations connected to the source UE.
  • the UE provided in this embodiment is used to implement the inter-UE service migration method in the embodiment shown in FIG. 3 .
  • the embodiment of the present application also provides a base station, including:
  • the receiving module is configured to receive service migration-related information sent by the target user equipment UE, the service migration-related information is used to indicate that the first service data of the source UE is migrated to the target UE, and the source UE and the target UE belong to the same PIoT; the sending module uses Because the base station sends the first service data to the target UE, wherein the GTP-U of the target UE and the source UE are associated with the same PDU session.
  • the UE provided in this embodiment is used to implement the inter-UE service migration method in the embodiment shown in FIG. 4 .
  • the embodiment of the present application also provides a core network device, including:
  • the receiving module is used to receive service migration related information, and the service migration related information is used to migrate the first service data of the source user equipment UE to the target UE; the processing module is used to determine that the source UE and the target UE belong to the same network PIoT, Associate the GTP-U of the target UE and the source UE to the same PDU session.
  • the UE provided in this embodiment is used to implement the inter-UE service migration method in the embodiment shown in FIG. 5 .
  • the embodiment of the present application also provides a storage medium containing computer-executable instructions.
  • the computer-executable instructions When executed by a computer processor, the computer-executable instructions are used to execute a service migration method between UEs.
  • the method includes: the target UE sends the service migration to the base station Related information, service migration related information is used to indicate that the first service data of the source UE is migrated to the target UE, and the source UE and the target UE belong to the same PIoT; the target UE receives the first service data sent by the base station, wherein the target UE and the source UE The GTP-U tunnels are associated to the same PDU session.
  • the embodiment of the present application also provides a storage medium containing computer-executable instructions.
  • the computer-executable instructions When executed by a computer processor, the computer-executable instructions are used to execute a service migration method between UEs.
  • the method includes: sending the source UE to the base station or the core network Sending service migration indication information, the service migration indication information is used to indicate that the first service data of the source UE is migrated to the target UE; the source UE receives a link deletion message or a radio bearer deletion indication sent by the base station connected to the target UE, and the link deletion message includes the source UE's NAS ID or PIoT terminal ID; the source UE deletes the Uu link between the base station connected to the source UE or the radio bearer corresponding to the migrated service.
  • the embodiment of the present application also provides a storage medium containing computer-executable instructions.
  • the computer-executable instructions When executed by a computer processor, the computer-executable instructions are used to implement a service migration method between UEs.
  • the method includes: the base station receives the service sent by the target UE Migration-related information, service migration-related information is used to indicate that the first service data of the source UE is migrated to the target UE, and the source UE and the target UE belong to the same PIoT; the base station sends the first service data to the target UE, wherein the target UE and the source UE The GTP-U is associated to the same PDU session.
  • the embodiment of the present application also provides a storage medium containing computer-executable instructions.
  • the computer-executable instructions When executed by a computer processor, the computer-executable instructions are used to execute a service migration method between UEs.
  • the method includes: a core network device receiving a service migration-related information, service migration related information is used to migrate the first service data of the source UE to the target UE; when the core network device determines that the source UE and the target UE belong to the same PIoT, associate the target UE and the GTP-U of the source UE to The same PDU session.
  • the various embodiments of the present application can be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.
  • Computer program instructions may be assembly instructions, instruction set architecture (Instruction Set Architecture, ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or in any combination of one or more programming languages source code or object code written.
  • instruction set architecture Instruction Set Architecture, ISA
  • machine instructions machine-related instructions
  • microcode firmware instructions
  • state setting data or in any combination of one or more programming languages source code or object code written.
  • Any logic flow block diagrams in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules and functions, or may represent a combination of program steps and logic circuits, modules and functions.
  • Computer programs can be stored on memory.
  • the memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as but not limited to Read-Only Memory (ROM), Random Access Memory (RAM), Optical Memory devices and systems (Digital Video Disc (DVD) or Optical Disc (Compact Disc, CD)), etc.
  • Computer-readable media may include non-transitory storage media.
  • Data processors may be any suitable local technology
  • the type of environment such as but not limited to general purpose computer, special purpose computer, microprocessor, digital signal processor (Digital Signal Processing, DSP), application specific integrated circuit (Application Specific Integrated Circuit, SAIC), programmable logic device (Field-Programmable Gate Array, FGPA) and processors based on multi-core processor architecture.
  • DSP Digital Signal Processing
  • SAIC Application Specific Integrated Circuit
  • FGPA programmable logic device
  • processors based on multi-core processor architecture.

Landscapes

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

Abstract

一种UE间业务迁移方法、装置和存储介质，其中一种UE间业务迁移方法包括：目标UE向基站发送业务迁移相关信息，业务迁移相关信息用于指示将源UE的第一业务数据迁移到目标UE，源UE和目标UE属于同一PIoT(S210)；目标UE接收基站发送的第一业务数据，其中，目标UE和源UE的GTP-U隧道关联到相同的PDU session(S220)。

Description

UE间业务迁移方法、装置和存储介质
相关申请的交叉引用
本申请基于申请号为202111033623.5、申请日为2021年09月03日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及移动通信技术，例如涉及一种UE间业务迁移方法、装置和存储介质。
背景技术
随着无线通讯技术的普及，同一用户拥有多个用户终端(User Equipment，UE)的场景非常普遍。其中，有的终端用户观感体验好、节能需求不强烈(比如电脑、电视、平板电脑等)，但不太方便移动；有的终端方便移动，但节能需求较高(比如智能终端)。
用户在使用中可能需要将同一业务在不同UE间进行业务的迁移，例如用户在室内通过电脑连接无线网络看视频，当用户从室内移动到室外时，视频业务需要迁移到智能手机上。但业务在不同UE间切换，可能导致业务的中断或不连续，影响用户的使用体验。
发明内容
本申请提供一种UE间业务迁移方法、装置和存储介质，实现了同一用户的UE间业务的平滑迁移。
第一方面，本申请实施例提供一种UE间业务迁移方法，包括：
目标UE向基站发送业务迁移相关信息，业务迁移相关信息用于指示将源UE的第一业务数据迁移到目标UE，源UE和目标UE属于同一PIoT；
目标UE接收基站发送的第一业务数据，其中，目标UE和源UE的GTP-U隧道关联到相同的PDU session。
第二方面，本申请实施例提供一种UE间业务迁移方法，其中，包括：
源UE向基站或核心网发送业务迁移指示信息，业务迁移指示信息用于指示将源用户设备的第一业务数据迁移到目标UE；
源UE接收目标UE连接的基站发送的链接删除消息或无线承载删除指示，链接删除消息包括源UE的NAS标识或PIoT终端标识；
源UE删除与源UE连接的基站之间的Uu链路或被迁移业务对应的无线承载。
第三方面，UE间业务迁移方法，其中，包括：
基站接收目标UE发送的业务迁移相关信息，业务迁移相关信息用于指示将源UE的第一业务数据迁移到目标UE，源UE和目标UE属于同一PIoT；
基站向目标UE发送第一业务数据，其中，目标UE和源UE的GTP-U关联到相同的PDU session。
第四方面，UE间业务迁移方法，其中，包括：
核心网设备接收业务迁移相关信息，业务迁移相关信息用于将源UE的第一业务数据迁移到目标UE；
当核心网设备确定源UE和目标UE属于同一PIoT时，将目标UE和源UE的GTP-U关联到相同的PDU session。
第五方面，本申请实施例提供一种UE，UE为目标UE，包括：
发送模块，用于向基站发送业务迁移相关信息，业务迁移相关信息用于指示将源UE的第一业务数据迁移到目标UE，源UE和目标UE属于同一PIoT；
接收模块，用于接收基站发送的第一业务数据，其中，目标UE和源UE的GTP-U隧道关联到相同的PDU session。
第六方面，本申请实施例提供一种UE，UE为源UE，包括：
发送模块，用于向基站或核心网发送业务迁移指示信息，业务迁移指示信息用于指示将源UE的第一业务数据迁移到目标UE；
接收模块，用于接收目标UE连接的基站发送的链接删除消息或无线承载删除指示，链接删除消息包括源UE的NAS标识或PIoT终端标识；
连接模块，用于删除与源UE连接的基站之间的Uu链路或被迁移业务对应的无线承载。
第七方面，本申请实施例提供一种基站，包括：
接收模块，用于接收目标用户设备UE发送的业务迁移相关信息，业务迁移相关信息用于指示将源UE的第一业务数据迁移到目标UE，源UE和目标UE属于同一PIoT；
发送模块，用于基站向目标UE发送第一业务数据，其中，目标UE和源UE的GTP-U关联到相同的PDU session。
第八方面，本申请实施例提供一种核心网设备，包括：
接收模块，用于接收业务迁移相关信息，业务迁移相关信息用于将源用户设备UE的第一业务数据迁移到目标UE；
处理模块，用于当确定源UE和目标UE属于同一网PIoT时，将目标UE和源UE的GTP-U关联到相同的PDU session。
第九方面，本申请实施例提供一种包含计算机可执行指令的存储介质，计算机可执行指令在由计算机处理器执行时用于执行第一方面至第四方面任一种可能的实现方式的UE间业务迁移方法。
本申请实施例提供的UE间业务迁移方法、装置和存储介质，当目标UE向基站发送用于指示将源UE的第一业务数据迁移到目标UE的业务迁移相关信息后，目标UE接收基站发送的第一业务数据，其中，目标UE和源UE的GTP-U隧道关联到相同的PDU session，源UE和目标UE属于同一PIoT，实现了同一用户的UE间业务的平滑迁移。
附图说明
图1为业务在同一基站下不同设备间迁移的示意图；
图2为本申请实施例提供的一种UE间业务迁移方法的流程图；
图3为本申请实施例提供的另一种UE间业务迁移方法的流程图；
图4为本申请实施例提供的另一种UE间业务迁移方法的流程图；
图5为本申请实施例提供的另一种UE间业务迁移方法的流程图；
图6为本申请实施例提供的UE间业务迁移方法的第一交互流程图；
图7为本申请实施例提供的UE间业务迁移方法的第二交互流程图；
图8为本申请实施例提供的UE间业务迁移方法的第三交互流程图；
图9为本申请实施例提供的UE间业务迁移方法的第四交互流程图；
图10为本申请实施例提供的UE间业务迁移方法的第五交互流程图。
具体实施方式
下文中将结合附图对本申请的实施例进行详细说明。
同一用户的多个UE之间需要进行业务迁移时，为了提高业务体验，需要业务在不同终端之间进行平滑迁移，以提高用户的使用体验。要想实现业务在UE间迁移时业务的连续性，就需要在基站与目标UE之间先建立无线链路或无线承载，再删除源UE与基站之间的无线链路或无线承载，以实现业务的平滑迁移。图1为业务在同一基站下不同设备间迁移的示意图，如图1所示，左侧显示UE1与基站(gNB)之间具有无线连接，承载着业务，用户希望将业务从UE1迁移到UE2。则UE2先与gNB建立无线连接(如图1中间所示)，然后待业务在UE2中运行后，再删除UE1与gNB之间的无线链路(如图1中右侧所示)。图1中示出业务在同一gNB迁移的示意图，业务在不同gNB之间迁移的情况类似。本申请实施例提出的UE间业务迁移方法，详细说明了如何实现图1所示的业务在不同UE之间迁移的具体实现方法。
在本申请各实施例中，源UE表示业务迁移前的UE，目标UE表示业务迁移的目标UE，源UE和目标UE可以是任一种具有网络连接能力的UE。业务从源UE迁移到目标UE可以由源UE触发也可以由目标UE触发。且源UE和目标UE是同一用户的UE，确切地说，源UE和目标UE属于同一个人物联网(Personal Internet of Things，PIoT)，这样在源UE和目标UE之间进行业务迁移时，无需进行重新的用户登录、认证等处理，从而能够保证业务迁移的连续性。
图2为本申请实施例提供的一种UE间业务迁移方法的流程图，如图2所示，本实施例提供的UE间业务迁移方法包括：
步骤S210，目标UE向基站发送业务迁移相关信息，业务迁移相关信息用于指示将源UE的第一业务数据迁移到目标UE，源UE和目标UE属于同一PIoT。
本实施例提供的UE间业务迁移方法应用于目标UE，为了使原运行于源UE的第一业务迁移到目标UE，也就是将发送给源UE的第一业务数据迁移到目标UE，目标UE需要先向基站发送业务迁移相关信息。目标UE向自身接入的基站发送业务迁移相关信息。该业务迁移相关信息用于指示将源UE的第一业务数据迁移到目标UE。
其中，业务迁移相关信息包括以下信息中的至少一种：业务迁移指示(Service switch indication)，待迁移的协议数据单元(Protocol Data Unit，PDU)会话标识,源UE标识(UE1's NAS ID)。
为了使目标UE获知源UE的相关信息，目标UE向基站发送业务迁移相关信息之前，目标UE还可以接收归属签约服务器(Home Subscriber Server，HSS)或统一数据管理功能(Unified Data Management，UDM)发送的所属PIoT签约信息，PIoT签约信息包括属于同一用户的UE标识列表。那么目标UE就可以从PIoT签约信息中获取业务迁移相关信息。
源UE和目标UE可以接入相同的基站，也可以接入不同的基站，其中，若源UE和目标UE接入相同的基站，则业务切换可以无需核心网参与。源UE向目标UE的业务迁移可以由目标UE触发也可以由源UE触发。其中，若由目标UE触发，则目标UE直接向基站发送业务迁移相关信息。若由源UE触发，则源UE向基站直接发送业务迁移相关信息。若由源UE触发，则源UE向基站发送业务迁移指示信息，业务迁移指示信息用于指示将源用户设备的第一业务数据迁移到目标UE。业务迁移指示信息包括以下信息中的至少一种：业务迁移指示，待迁移的PDU会话标识,目标UE标识(UE2's NAS ID)。基站根据业务迁移指示信息确定业务迁移的目标UE，向目标UE发送寻呼消息，寻呼消息中包括业务迁移指示信息。目标UE可以在向基站发送的寻呼响应中携带业务迁移相关信息。
若源UE和目标UE接入不同的基站，则业务切换需要核心网参与。源UE向目标UE的业务迁移可以由目标UE触发也可以由源UE触发。其中，若由目标UE触发，则目标UE向基站发送 业务迁移相关信息之后，该基站向核心网发送该业务迁移相关信息。核心网设备完成业务从源UE从目标UE的迁移，即将目标UE和源UE的GTP-U隧道关联到相同的PDU session后，向目标UE连接的基站发送响应，使得基站通知源UE和目标UE。若由源UE触发，则源UE通过源UE连接的基站向核心网发送业务迁移指示信息或直接向核心网发送业务迁移指示信息。业务迁移指示信息用于指示将源用户设备的第一业务数据迁移到目标UE。业务迁移指示信息包括以下信息中的至少一种：业务迁移指示，待迁移的PDU会话标识,目标UE标识。核心网设备根据业务迁移指示信息确定业务迁移的目标UE，通过目标UE接入的基站向目标UE发送寻呼消息，寻呼消息中包括业务迁移指示信息。目标UE可以在向基站发送的寻呼响应中携带业务迁移相关信息。
步骤S220，目标UE接收基站发送的第一业务数据，其中，目标UE和源UE的GTP-U隧道关联到相同的PDU session。
目标UE接入的基站接收到目标基站发送的业务迁移相关信息后，可以根据业务迁移相关信息确定需要将源UE的第一业务数据迁移到目标UE。因此基站可以将第一业务数据发送至目标UE。其中，目标UE和源UE的用户面GPRS隧道协议(GPRS Tunneling Protocol-User Plane，GTP-U)隧道关联到相同的PDU会话(PDU session)。目标UE和源UE的GTP-U隧道关联到相同的PDU session，是由核心网进行关联的，基站可以将接收到的业务迁移相关信息发送至核心网设备，从而使核心网设备执行GTP-U隧道的关联。
目标UE接收基站发送的第一业务数据之前，目标UE还可以接收基站发送的无线资源控制(Radio Resource Control，RRC)重配置消息，RRC重配置消息中包括源UE的小区无线网络临时标识(Cell-Radio Network Temporary Identifier C-RNTI)，其中，源UE和目标UE均接入基站，接收相同的用户面数据。也就是当源UE和目标UE接入同一基站时，才由该基站控制业务迁移。
而若基站为目标UE分配了源UE的C-RNTI，则由于源UE和目标UE的C-RNTI相同，需要确定无线链路控制(Radio Link Control，RLC)状态信息和/或混合自动重传请求消息(Hybrid Automatic Repeat reQuest，HARQ)如何反馈。可以采用如下任一种方式进行RLC状态信息和/或HARQ的反馈。
1、区分主UE和辅UE，只有主UE反馈RLC状态信息和/或HARQ应答/非应答(Acknowledgment/Negative Acknowledgment，ACK/NACK)，那么在目标UE切换为主UE之前，目标UE不反馈RLC状态信息和/或HARQ ACK/NACK，在目标UE切换到主UE之后，目标UE向基站反馈RLC状态信息和/或HARQ ACK/NACK。
2、源UE和目标UE均反馈RLC状态信息和/或HARQ ACK/NACK，基站接收到任一UE反馈的RLC状态信息和/或HARQ ACK/NACK决定是否进行重传或者基站同时接收到两个UE反馈的RLC状态信息和/或HARQ ACK/NACK决定是否进行重传。同时接收到目标UE和源UE反馈的RLC状态信息和/或HARQ的非应答(Negative Acknowledgment，NACK)消息时基站重传业务数据，或者接收到目标UE或源UE反馈的RLC状态信息和/或HARQ的非应答NACK消息时基站重传业务数据。
3、当第一业务数据为非确认模式(Unacknowledged Mode，UM)，目标UE不反馈RLC状态信息和/或HARQ ACK/NACK。
本实施例提供的UE间业务迁移方法，当目标UE向基站发送用于指示将源UE的第一业务数据迁移到目标UE的业务迁移相关信息后，目标UE接收基站发送的第一业务数据，其中，目标UE和源UE的GTP-U隧道关联到相同的PDU session，源UE和目标UE属于同一PIoT，实现了同一用户的UE间业务的平滑迁移。
图3为本申请实施例提供的另一种UE间业务迁移方法的流程图，如图3所示，本实施例提供的UE间业务迁移方法包括：
步骤S310，源UE向基站或核心网发送业务迁移指示信息，业务迁移指示信息用于指示将源用户设备的第一业务数据迁移到目标UE。
本实施例提供的UE间业务迁移方法应用于源UE，为了使原运行于源UE的第一业务迁移到目标UE，也就是将发送给源UE的第一业务数据迁移到目标UE，源UE需要先向基站或核心网发送业务迁移指示信息。源UE向自身接入的基站或直接向核心网发送业务迁移指示信息。该业务迁移指示信息用于指示将源UE的第一业务数据迁移到目标UE。业务迁移指示信息包括以下信息中的至少一种：业务迁移指示，待迁移的PDU会话标识,目标UE标识。
步骤S320，源UE接收目标UE连接的基站发送的链接删除消息或无线承载删除指示，链接删除消息包括源UE的NAS标识或PIoT终端标识。
步骤S330，源UE删除与源UE连接的基站之间的Uu链路或被迁移业务对应的无线承载。
在将第一业务数据从源UE迁移到目标UE之后，还需要将源UE的链接或无线承载删除。当源UE接收到目标UE连接的基站发送的链接删除消息或无线承载删除指示后，可以删除源UE与连接基站之间的Uu链路或被迁移业务对应的无线承载。其中，源UE与目标UE可以连接于同一基站，或者源UE与目标UE可以连接于不同基站。
源UE的Uu链路或被迁移业务对应的无线承载是基站决定删除的，也可以是源UE上报释放指示后决定删除的，或者是基站感知到与目标UE的同步完成后主动释放的。而在为目标UE分配源UE的C-RNTI后，还需要确定源UE如何上报释放指示。
源UE可以向核心网上报释放请求，其中携带源UE的NAS标识和/或被迁移的PDU会话标识，核心网发送UE上下文修改请求(UE CONTEXT MODIFICATION REQUEST)给基站，其中携带源UE的NAS标识和PIoT上下文释放指示。或者源UE可以向基站上报释放请求，其中携带源UE的NAS标识和/或被迁移的PDU会话标识，所述释放请求为RRC消息或介质访问控制控制单元(Media Access Control Control Element，MAC CE)。基站向源基站发送携带源UE的NAS标识或PIoT终端标识的RRC消息或MAC CE，以触发源UE删除Uu链路或无线承载。
图4为本申请实施例提供的另一种UE间业务迁移方法的流程图，如图4所示，本实施例提供的UE间业务迁移方法包括：
步骤S410，基站接收目标UE发送的业务迁移相关信息，业务迁移相关信息用于指示将源的第一业务数据迁移到目标UE，源UE和目标UE属于同一PIoT。
本实施例提供的UE间业务迁移方法应用于基站，确切地说，是目标UE接入的基站。基站在接收到目标UE发送的业务迁移相关信息后，确定需要进行业务迁移。该业务迁移相关信息用于指示将源UE的第一业务数据迁移到目标UE。
其中，业务迁移相关信息包括以下信息中的至少一种：业务迁移指示，待迁移的PDU会话标识,源UE标识。
基站在接收到目标UE发送的业务迁移相关信息后，向核心网(CoreNetwork，CN)发送业务迁移相关信息，以使CN将目标UE和源UE的GTP-U隧道关联到相同的PDU session。
源UE到目标UE的业务迁移若是由源UE触发的，则基站接收源UE发送的业务迁移指示信息，业务迁移指示信息用于指示将源用户设备的第一业务数据迁移到目标UE；然后基站向目标UE发送寻呼消息，寻呼消息中包括业务迁移指示信息；基站接收目标UE发送的寻呼响应消息，寻呼响应消息中包括业务迁移相关信息。其中，业务迁移指示信息包括以下信息中的至少一种： 业务迁移指示，待迁移的PDU会话标识,目标UE标识。
步骤S420，基站向目标UE发送第一业务数据，其中，目标UE和源UE的GTP-U关联到相同的话PDU session。
目标UE接入的基站接收到目标基站发送的业务迁移相关信息后，可以根据业务迁移相关信息确定需要将源UE的第一业务数据迁移到目标UE。因此基站可以将第一业务数据发送至目标UE。其中，目标UE和源UE的GTP-U隧道关联到相同的PDU session。目标UE和源UE的GTP-U隧道关联到相同的PDU session，是由核心网进行关联的，基站可以将接收到的业务迁移相关信息发送至核心网设备，从而使核心网设备执行GTP-U隧道的关联。
目标UE接收基站发送的第一业务数据之前，基站还可以向目标UE发送RRC重配置消息，RRC重配置消息中包括源UE的C-RNTI，其中，源UE和目标UE均接入基站。也就是当源UE和目标UE接入同一基站时，才由该基站控制业务迁移。
基站向目标UE发送RRC重配置消息，可以是基站确定目标UE和源UE的Uu链路同时存在时，确定目标UE和源UE属于同一PIoT，向目标UE发送无线资源控制RRC重配置消息。或者，基站向目标UE发送RRC重配置消息后，确定目标UE和源UE的Uu链路同时存在时，确定目标UE和源UE属于同一PIoT。
另外，基站向目标UE发送第一业务数据之后，还可以删除与源UE建立的链接。基站删除与源UE建立的链接，可以是当基站接收到源UE发送的链接或第一业务对应的无线承载释放指示后，删除与源UE建立的链接或第一业务对应的无线承载；或者，当基站确定第一业务数据迁移到目标UE后，删除与源UE建立的链接或第一业务对应的无线承载。
当基站接收到源UE发送的链接释放指示后，删除与源UE建立的链接，包括：当基站接收到核心网发送的UE上下文修改请求和PIoT上下文释放指示后，向源UE发送链接删除消息，链接删除消息用于指示源UE删除与基站之间的Uu链路，UE上下文修改请求和PIoT上下文释放指示是核心网接收到源UE发送的携带源UE的非接入层NAS标识的链接释放请求后的，UE上下文修改请求包括源UE的NAS标识，链接删除消息为RRC消息或MAC CE，链接删除消息包括源UE的NAS标识或PIoT终端标识；或者，当基站接收到源UE发送的携带源UE的NAS标识的链接释放请求后，向源UE发送链接删除消息，链接删除消息用于指示源UE删除与基站之间的Uu链路，链接释放请求为RRC消息或MAC CE，链接删除消息包括源UE的NAS标识或PIoT终端标识。
或者当源UE承载多个业务，但只迁移第一业务时，可以仅释放第一业务对应的无线承载，当所述基站接收到所述源UE发送的第一业务对应的无线承载释放指示后，删除与所述源UE建立的第一业务对应的无线承载，包括：当基站接收到核心网发送的UE上下文修改请求和PIoT上下文释放指示后，向源UE发送承载释放指示，承载释放指示用于指示源UE删除与基站之间的第一业务的无线承载，UE上下文修改请求和PIoT上下文释放指示是核心网接收到源UE发送的携带源UE的非接入层NAS标识的业务释放请求后触发的，UE上下文修改请求包括源UE的NAS标识和/或被迁移的PDU会话标识，承载释放指示为RRC消息或MAC CE，第一业务对应的无线承载删除消息包括第一业务对应的无线承载标识；或者，当基站接收到源UE发送的携带源UE的NAS标识的链接释放请求后，向源UE发送承载释放指示，承载释放指示用于指示源UE删除与基站之间的第一业务对应的无线承载，承载释放指示为RRC消息或MAC CE，第一业务对应的无线承载删除消息包括第一业务对应的无线承载标识。
图5为本申请实施例提供的另一种UE间业务迁移方法的流程图，如图5所示，本实施例提供的UE间业务迁移方法包括：
步骤S510，核心网设备接收业务迁移相关信息，业务迁移相关信息用于将源UE的第一业务数据迁移到目标UE。
本实施例提供的UE间业务迁移方法应用于核心网设备，其中核心网设备可以是任一种或多种执行相应功能的核心网设备。核心网设备可以接收目标UE连接的基站转发的业务迁移相关信息，或者核心网设备还可以接收源UE直接发送的业务迁移指示信息。该业务迁移相关信息用于指示将源UE的第一业务数据迁移到目标UE，该业务迁移指示信息用于指示将源UE的第一业务数据迁移到目标UE。
步骤S520，当核心网设备确定源UE和目标UE属于同一PIoT时，将目标UE和源UE的GTP-U关联到相同的PDU session。
核心网设备根据业务迁移相关信息确定源UE的业务需要迁移至目标UE时，首先需要确定源UE和目标UE属于同一PIoT，然后将目标UE和源UE的GTP-U关联到相同的PDU session，这样发送至源UE的第一业务数据将能够迁移至目标UE。
具体地，接入和移动管理功能(Access and Mobility Management Function，AMF)接收业务迁移相关信息。当AMF确定源UE和目标UE属于同一PIoT时，目标UE和源UE的GTP-U关联到相同的PDU session。
AMF可以接收目标UE接入的基站发送的业务迁移相关信息；或者，AMF接收源UE接入的基站发送的业务指示相关信息或AMF接收源UE直接发送的业务迁移指示信息。
若MF接收源UE发送的业务迁移相关信息，则AMF向目标UE接入的基站发送寻呼消息，寻呼消息用于使目标UE接入的基站向目标UE发送寻呼信息，寻呼消息中包括业务迁移指示信息。
当由目标UE触发业务迁移时，HSS或UDM向目标UE发送目标UE所属PIoT签约信息，PIoT签约信息包括属于同一用户的UE标识列表。当由源UE触发业务迁移时，HSS或UDM向源UE和/或AMF发送源UE所属PIoT签约信息。
若目标UE和源UE接入的基站不同，那么需要由核心网设备执行业务迁移。那么当AMF确定源UE和目标UE属于同一PIoT时，向会话管理功能(Session Management Function,SMF)发送会话管理更新请求，会话管理更新请求中包括与源UE相关的PDU session的相关信息；SMF向用户面功能(User Plane Function，UPF)发送会话建立请求，会话建立请求中包括源UE的核心网信道信息；UPF向SMF发送会话建立响应，会话建立响应中包括与源UE相关的PDU session的相关信息；SMF向AFM发送会话管理更新响应，会话管理更新响应中包括与源UE相关的PDU session的相关信息。这样就在核心网侧完成了业务的迁移。
在核心网设备进行业务迁移时，用户面的数据流在UPF进行复制，UPF将源UE的第一业务数据复制后，通过目标UE接入的基站向目标UE发送。
下面以几个具体实施例，对本申请提供的UE间业务迁移方法进行进一步详细说明。在图6-图10中，UE1为源UE，UE2为目标UE，gNB为源UE和目标UE同时连接的基站，第二gNB为目标UE连接的基站，第一gNB为源UE连接的基站。鉴权服务功能(Authentication Server Function)用于对UE进行鉴权。
图6为本申请实施例提供的UE间业务迁移方法的第一交互流程图，图6为目标UE触发的同一基站下业务从源UE迁移到目标UE的用户面连续性迁移交互流程图。
在图6中，HSS/UDM向UE2发送所属PIoT签约信息，包括PIoT相关信息(UE subscription information(Including Personal IoT related information))。gNB与UE1以及SMF保持RRC连接状态(RRC_CONNRCTED_state)(CM_CONNRCTED_state)，SMF为UE1建立PDU session A 的GTP-U隧道，gNB即可向UE1发送业务数据(UP Date)。UE2通过RRC Msg3/Msg5向gNB触发业务迁移，其中包括业务迁移指示，待迁移的PDU会话标识,源UE标识(Including Service request,Service switch indication，PDU session indication,UE1's NAS ID)。gNB向AMF发送N2消息(N2 Message(Including Service request,Service switch indication，PDU session indication,UE1's NAS ID))。AMF通过AUSF对UE2进行鉴权(Authentication Security)。AMF向gNB发送N2请求(N2 Request(Service switch indication,UE 1 GTP-U Tunnel for PDU session A,UE1's NAS ID))，AMF还将目标UE和源UE的GTP-U关联到相同的PDU session(associate UE1 PDU Session A with UE2 GTP-U Tunnel)。当gNB判断UE1和UE2为两个相同PIoT设备之间的切换时，向UE2发送RRC重配置消息(RRC Reconfiguration)，包括UE1的C-RNTI(C_RNTI of UE1)。gNB将UE1的业务数据迁移到UE2(Data duplication and convergence)。最后，gNB指示UE1释放链接(RRC or MAC CE for Release Indication(5G-S-TMSI))。
图7为本申请实施例提供的UE间业务迁移方法的第二交互流程图，图7为目标UE触发的同一基站下业务从源UE迁移到目标UE的控制面连续性迁移交互流程图。
在图7中，HSS/UDM向UE2发送所属PIoT签约信息，包括PIoT相关信息(UE subscription information(Including Personal IoT related information))。gNB与UE1以及SMF保持RRC连接状态(RRC_CONNRCTED_state)(CM_CONNRCTED_state)，SMF为UE1建立PDU session A的GTP-U隧道，gNB即可向UE1发送业务数据(UP Date)。UE2通过RRC Msg3/Msg5向gNB触发业务迁移，其中包括业务迁移指示，待迁移的PDU会话标识,源UE标识(Including Service request,Service switch indication，PDU session indication,UE1's NAS ID)。gNB向AMF发送N2消息(N2 Message(Including Service request,Service switch indication，PDU session indication,UE1's NAS ID))。AMF通过AUSF对UE2进行鉴权(Authentication Security)。AMF向gNB发送N2请求(N2 Request(Service switch indication,UE 1 GTP-U Tunnel for PDU session A,UE1's NAS ID))，AMF还将目标UE和源UE的GTP-U关联到相同的PDU session(associate UE1 PDU Session A with UE2 GTP-U Tunnel)。gNB向UE2发送RRC重配置消息(RRC Reconfiguration)，gNB将UE1的业务数据迁移到UE2(Data duplication and convergence)。当gNB判断UE1和UE2为两个相同PIoT设备之间的切换时，gNB指示UE1释放链接(RRC ConnectionRelease or MAC CE for Release Indication)。当UE2链路建立完成，基站判断出两个UE属于同一PIoT:将UE1的数据缓存转给UE2(NG口可共用一条链路，NG口走modify流程)；同时给UE1发送RRCConnectionRelease消息。
图8为本申请实施例提供的UE间业务迁移方法的第三交互流程图，图8为源UE触发的同一基站下业务从源UE迁移到目标UE的连续性迁移交互流程图。
在图8中，HSS/UDM向UE1发送所属PIoT签约信息，包括PIoT相关信息(UE subscription information(Including Personal IoT related information))。gNB与UE1以及SMF保持RRC连接状态(RRC_CONNRCTED_state)(CM_CONNRCTED_state)，SMF为UE1建立PDU session A的GTP-U隧道，gNB即可向UE1发送业务数据(UP Date)。UE1通过NAS PDU向gNB触发业务迁移其中包括业务迁移指示，待迁移的PDU会话标识,目标UE标识(NAS PDU(Service request,Service switch indication，PDU session indication,UE2's NAS ID))。gNB向AMF发送N2消息(N2 Message(Including Service request,Service switch indication，PDU session indication,UE2's NAS ID))。AMF向gNB发送寻呼消息(PAGING(Service switch indication， PDU session indication,UE1's NAS ID))，当gNB判断UE1和UE2为两个相同PIoT设备之间的切换时，gNB向UE2发送寻呼消息(PAGING(Service switch indication，PDU session indication,UE1's NAS ID))。图8的后续流程与图6和图7的后续业务迁移流程相同，此处不再赘述。
图9为本申请实施例提供的UE间业务迁移方法的第四交互流程图，图9为目标UE触发的基于核心网感知的业务从源UE迁移到目标UE的连续性迁移交互流程图。
在图9中，HSS/UDM向UE2发送所属PIoT签约信息，包括PIoT相关信息(UE subscription information(Including Personal IoT related information))。gNB1与UE1以及SMF保持RRC连接状态(RRC_CONNRCTED_state)(CM_CONNRCTED_state)，SMF为UE1建立PDU session A的GTP-U隧道，gNB1即可向UE1发送业务数据(UP Date)。UE2向gNB2触发业务迁移(Service Request(including UE1 APID or Address,Service Switch Ind)，gNB2向AMF发送N2消息(N2 Message(Including Service Request))。AMF通过AUSF对UE2进行鉴权(Authentication Security)。当AMF判断UE1和UE2为两个相同PIoT设备之间的切换时，AMF向SMF发送会话管理更新请求(Nsmf_PDU Session_UpdateSMContext Request)其中携带UE1 PDUSession A相关信息，比如PDUSession A的PDU SessionID,CN Tunnel Info等。SMF向UPF发送的N4会话建立请求(Session Establishment Request)其中携带UE1CN Tunnel Info)。UPF向SMF发送的N4会话建立响应(Session Establishment Response)里携带UE1 PDUSession A相关信息，比如PDUSession A的PDU SessionID,CN Tunnel Info等。SMF向AMF发送会话管理更新响应(Nsmf_PDUSession_UpdateSMContext Response)其中包含PDUSession A的PDU SessionID,CN Tunnel Info、QFI(s),QoS profile(s),CN N3Tunnel Info,S-NSSAI,User Plane Security Enforcement,UE Integrity Protection Maximum Data Rate,RSN等。用户面的数据流在UPF进行复制，并在两个UE的链路上分别进行传输(association between CN session/tunnel IDs before switching and after switching.)。AMF向gNB2发送N2请求(N2 Request)，gNB2项UE1发送RRC重配置消息(RRCReconfiguration)，UE1向gNB2发送RRC重配置完成消息(RRCReconfigurationComplete)，然后gNB2向AMF发送N2请求响应(N2 Request Ack)。UPF将UE1的业务数据迁移到UE2(Data duplication and convergence)。UPF在数据收发时，在UE1和UE2的GTP-U隧道上进行数据同时发送，或者在UE1和UE2的GTP-U隧道上进行数据同时接收/合并。
图10为本申请实施例提供的UE间业务迁移方法的第五交互流程图，图10为源UE触发的基于核心网感知的业务从源UE迁移到目标UE的用户面连续性迁移交互流程图。
在图10中，HSS/UDM向UE1和AMF发送所属PIoT签约信息，包括PIoT相关信息(UE subscription information(Including Personal IoT related information))，UE1和/或AMF存储签约信息。gNB1与UE1以及SMF保持RRC连接状态(RRC_CONNRCTED_state)(CM_CONNRCTED_state)，承载着PDU Session A，SMF为UE1建立PDU session A的GTP-U隧道，gNB1即可向UE1发送业务数据(UP Date)。UE1向AMF触发业务迁移(Service Request(including UE2 APID or Address,Service Switch Ind)，AMF向gNB2发送寻呼消息(Paging(including UE1 APID or Address,Service Switch Ind))，gNB2向UE2发送寻呼消息(Paging(including UE1 APID or Address,Service Switch Ind))。UE2接着向gNB2发送服务请求(Service Request(including UE1 APID or Address,Service Switch Ind))，gNB2向AMF发送N2消息(N2 Message(Including Service Request))。AMF通过AUSF对UE2 进行鉴权(Authentication Security)。图10的后续流程与图9的后续业务迁移流程相同，此处不再赘述。
本申请实施例还提供一种UE，UE为目标UE，包括：
发送模块，用于向基站发送业务迁移相关信息，业务迁移相关信息用于指示将源UE的第一业务数据迁移到目标UE，源UE和目标UE属于同一PIoT；接收模块，用于接收基站发送的第一业务数据，其中，目标UE和源UE的GTP-U隧道关联到相同的PDU session。本实施例提供的UE用于实现图2所示实施例的UE间业务迁移方法。
本申请实施例还提供一种UE，UE为源UE，包括：
发送模块，用于向基站或核心网发送业务迁移指示信息，业务迁移指示信息用于指示将源UE的第一业务数据迁移到目标UE；接收模块，用于接收目标UE连接的基站发送的链接删除消息，链接删除消息包括源UE的NAS标识或PIoT终端标识；连接模块，用于删除与源UE连接的基站之间的Uu链路。本实施例提供的UE用于实现图3所示实施例的UE间业务迁移方法。
本申请实施例还提供一种基站，包括：
接收模块，用于接收目标用户设备UE发送的业务迁移相关信息，业务迁移相关信息用于指示将源UE的第一业务数据迁移到目标UE，源UE和目标UE属于同一PIoT；发送模块，用于基站向目标UE发送第一业务数据，其中，目标UE和源UE的GTP-U关联到相同的PDU session。本实施例提供的UE用于实现图4所示实施例的UE间业务迁移方法。
本申请实施例还提供一种核心网设备，包括：
接收模块，用于接收业务迁移相关信息，业务迁移相关信息用于将源用户设备UE的第一业务数据迁移到目标UE；处理模块，用于当确定源UE和目标UE属于同一网PIoT时，将目标UE和源UE的GTP-U关联到相同的PDU session。本实施例提供的UE用于实现图5所示实施例的UE间业务迁移方法。
本申请实施例还提供一种包含计算机可执行指令的存储介质，计算机可执行指令在由计算机处理器执行时用于执行一种UE间业务迁移方法，该方法包括：目标UE向基站发送业务迁移相关信息，业务迁移相关信息用于指示将源UE的第一业务数据迁移到目标UE，源UE和目标UE属于同一PIoT；目标UE接收基站发送的第一业务数据，其中，目标UE和源UE的GTP-U隧道关联到相同的PDU session。
本申请实施例还提供一种包含计算机可执行指令的存储介质，计算机可执行指令在由计算机处理器执行时用于执行一种UE间业务迁移方法，该方法包括：源UE向基站或核心网发送业务迁移指示信息，业务迁移指示信息用于指示将源UE的第一业务数据迁移到目标UE；源UE接收目标UE连接的基站发送的链接删除消息或无线承载删除指示，链接删除消息包括源UE的NAS标识或PIoT终端标识；源UE删除与源UE连接的基站之间的Uu链路或被迁移业务对应的无线承载。
本申请实施例还提供一种包含计算机可执行指令的存储介质，计算机可执行指令在由计算机处理器执行时用于执行一种UE间业务迁移方法，该方法包括：基站接收目标UE发送的业务迁移相关信息，业务迁移相关信息用于指示将源UE的第一业务数据迁移到目标UE，源UE和目标UE属于同一PIoT；基站向目标UE发送第一业务数据，其中，目标UE和源UE的GTP-U关联到相同的PDU session。
本申请实施例还提供一种包含计算机可执行指令的存储介质，计算机可执行指令在由计算机处理器执行时用于执行一种UE间业务迁移方法，该方法包括：核心网设备接收业务迁移相关 信息，业务迁移相关信息用于将源UE的第一业务数据迁移到目标UE；当核心网设备确定源UE和目标UE属于同一PIoT时，将目标UE和所述源UE的GTP-U关联到相同的PDU session。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构((Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(Read-Only Memory，ROM)、随机访问存储器(Random Access Memory，RAM)、光存储器装置和系统(数码多功能光碟(Digital Video Disc，DVD)或光盘((Compact Disc，CD))等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，SAIC)、可编程逻辑器件(Field-Programmable Gate Array，FGPA)以及基于多核处理器架构的处理器。

Claims (32)

  1. 一种UE间业务迁移方法，包括：
    目标用户设备UE向基站发送业务迁移相关信息，所述业务迁移相关信息用于指示将源UE的第一业务数据迁移到所述目标UE，所述源UE和所述目标UE属于同一个人物联网PIoT；以及
    所述目标UE接收所述基站发送的所述第一业务数据，其中，所述目标UE和所述源UE的用户面GPRS隧道协议GTP-U隧道关联到相同的协议数据单元会话PDU session。
  2. 根据权利要求1所述的方法，其中，所述业务迁移相关信息包括以下信息中的至少一种：业务迁移指示，待迁移的PDU会话标识,源UE标识。
  3. 根据权利要求1所述的方法，所述目标UE向基站发送业务迁移相关信息之前，还包括：
    所述目标UE接收所述基站发送的寻呼消息，所述寻呼消息中包括业务迁移指示信息，所述寻呼消息是所述基站接收到所述源UE发送的业务迁移指示信息后发送的，所述业务迁移指示信息用于指示将源用户设备的第一业务数据迁移到所述目标UE。
  4. 根据权利要求3所述的方法，其中，所述业务迁移指示信息包括以下信息中的至少一种：业务迁移指示，待迁移的PDU会话标识,目标UE标识。
  5. 根据权利要求1～4任一项所述的方法，所述目标UE接收所述基站发送的所述第一业务数据之前，还包括：
    所述目标UE接收所述基站发送的无线资源控制RRC重配置消息，所述RRC重配置消息中包括所述源UE的小区无线网络临时标识C-RNTI，其中，所述源UE和所述目标UE均接入所述基站。
  6. 根据权利要求5所述的方法，所述目标UE接收所述基站发送的RRC重配置消息之后，还包括：
    在所述目标UE切换为主UE之前，所述目标UE不反馈无线链路控制RLC状态信息和/或混合自动重传请求消息HARQ应答/非应答ACK/NACK，在所述目标UE切换到主UE之后，所述目标UE向所述基站反馈RLC状态信息和/或HARQ ACK/NACK；
    或者，所述目标UE反馈RLC状态信息和/或HARQ ACK/NACK，同时接收到所述目标UE和所述源UE反馈的RLC状态信息和/或HARQ的非应答NACK消息的基站重传业务数据，或者接收到所述目标UE或所述源UE反馈的RLC状态信息和/或HARQ的非应答NACK消息的基站重传业务数据；
    或者，当所述第一业务数据为非确认模式UM，所述目标UE不反馈RLC状态信息和/或HARQ ACK/NACK。
  7. 根据权利要求1～4任一项所述的方法，所述目标UE向基站发送业务迁移相关信息之前，还包括：
    所述目标UE接收归属签约服务器HSS或统一数据管理功能UDM发送的所属PIoT签约信息，所述PIoT签约信息包括属于同一用户的UE标识列表。
  8. 一种UE间业务迁移方法，包括：
    源用户设备UE向基站或核心网发送业务迁移指示信息，所述业务迁移指示信息用于指示将源UE的第一业务数据迁移到目标UE；
    所述源UE接收所述目标UE连接的基站发送的链接删除消息或无线承载删除指示，所述链接删除消息包括所述源UE的非接入层NAS标识或个人物联网PIoT终端标识；以及
    所述源UE删除与所述源UE连接的基站之间的Uu链路或被迁移业务对应的无线承载。
  9. 一种UE间业务迁移方法，包括：
    基站接收目标用户设备UE发送的业务迁移相关信息，所述业务迁移相关信息用于指示将源UE的第一业务数据迁移到所述目标UE，所述源UE和所述目标UE属于同一个人物联网PIoT；
    所述基站向所述目标UE发送所述第一业务数据，其中，所述目标UE和所述源UE的用户面GPRS隧道协议GTP-U关联到相同的协议数据单元会话PDU session。
  10. 根据权利要求9所述的方法，其中，所述业务迁移相关信息包括以下信息中的至少一种：业务迁移指示，待迁移的PDU会话标识,源UE标识。
  11. 根据权利要求9所述的方法，所述基站接收目标用户设备UE发送的业务迁移相关信息之后，还包括：
    所述基站向核心网CN发送所述业务迁移相关信息，以使所述CN将所述目标UE和所述源UE的GTP-U隧道关联到相同的PDU session。
  12. 根据权利要求9所述的方法，所述基站接收目标UE发送的业务迁移相关信息之前，还包括：
    所述基站接收所述源UE发送的业务迁移指示信息，所述业务迁移指示信息用于指示将源用户设备的第一业务数据迁移到所述目标UE；
    所述基站向所述目标UE发送寻呼消息，所述寻呼消息中包括所述业务迁移指示信息；
    其中，所述基站接收目标UE发送的业务迁移相关信息，包括：
    所述基站接收所述目标UE发送的寻呼响应消息，所述寻呼响应消息中包括所述业务迁移相关信息。
  13. 根据权利要求12所述的方法，其中，所述业务迁移指示信息包括以下信息中的至少一种：业务迁移指示，待迁移的PDU会话标识,目标UE标识。
  14. 根据权利要求9～13任一项所述的方法，所述基站向所述目标UE发送所述第一业务数据之前，还包括：
    所述基站向所述目标UE发送无线资源控制RRC重配置消息，所述RRC重配置消息中包括所述源UE的小区无线网络临时标识C-RNTI，其中，所述源UE和所述目标UE均接入所述基站。
  15. 根据权利要求14所述的方法，其中，所述基站向所述目标UE发送RRC重配置消息，包括：
    所述基站确定所述目标UE和所述源UE的Uu链路同时存在时，确定所述目标UE和所述源UE属于同一PIoT，向所述目标UE发送RRC重配置消息；
    或者，所述基站向所述目标UE发送RRC重配置消息后，确定所述目标UE和所述源UE的Uu链路同时存在时，确定所述目标UE和所述源UE属于同一PIoT。
  16. 根据权利要求9～13任一项所述的方法，所述基站向所述目标UE发送所述第一业务数据之后，还包括：
    所述基站删除与所述源UE建立的链接。
  17. 根据权利要求16所述的方法，其中，所述基站删除与所述源UE建立的链接，包括：
    当所述基站接收到所述源UE发送的链接或第一业务对应的无线承载释放指示后，删除与所述源UE建立的链接或第一业务对应的无线承载；
    或者，当所述基站确定所述第一业务数据迁移到所述目标UE后，删除与所述源UE建立的链接或第一业务对应的无线承载。
  18. 根据权利要求17所述的方法，其中，当所述基站接收到所述源UE发送的链接或第一 业务对应的无线承载释放指示后，删除与所述源UE建立的链接或第一业务对应的无线承载，包括：
    当所述基站接收到核心网发送的UE上下文修改请求和PIoT上下文释放指示后，向所述源UE发送链接删除消息，所述链接删除消息用于指示所述源UE删除与所述基站之间的Uu链路或无线承载，所述UE上下文修改请求和PIoT上下文释放指示是所述核心网接收到所述源UE发送的携带所述源UE的非接入层NAS标识的链接释放请求后的，所述UE上下文修改请求包括所述源UE的NAS标识，所述链接删除消息为RRC消息或MAC CE，所述链接或第一业务对应的无线承载删除消息包括所述源UE的NAS标识或PIoT终端标识、或第一业务对应的无线承载标识；
    或者，当所述基站接收到所述源UE发送的携带所述源UE的NAS标识的链接释放请求后，向所述源UE发送链接删除消息，所述链接删除消息用于指示所述源UE删除与所述基站之间的Uu链路或无线承载，所述链接释放请求为RRC消息或MAC CE，所述链接或第一业务对应的无线承载删除消息包括所述源UE的NAS标识或PIoT终端标识、或第一业务对应的无线承载标识。
  19. 一种UE间业务迁移方法，包括：
    核心网设备接收业务迁移相关信息，所述业务迁移相关信息用于将源用户设备UE的第一业务数据迁移到目标UE；以及
    当所述核心网设备确定所述源UE和所述目标UE属于同一个人物联网PIoT时，将所述目标UE和所述源UE的用户面GPRS隧道协议GTP-U关联到相同的协议数据单元会话PDU session。
  20. 根据权利要求19所述的方法，其中，所述核心网设备接收业务迁移相关信息，包括：
    接入和移动管理功能AMF接收所述业务迁移相关信息；以及
    所述当所述核心网设备确定所述源UE和所述目标UE属于同一PIoT时，将所述目标UE和所述源UE的GTP-U关联到相同的PDU session，包括：
    当所述AMF确定所述源UE和所述目标UE属于同一PIoT时，所述目标UE和所述源UE的GTP-U关联到相同的PDU session。
  21. 根据权利要求20所述的方法，其中，所述AMF接收所述业务迁移相关信息，包括：
    所述AMF接收所述目标UE接入的基站发送的所述业务迁移相关信息；
    或者，所述AMF接收所述源UE接入的基站发送的业务指示相关信息或所述AMF接收所述源UE直接发送的所述业务迁移指示信息。
  22. 根据权利要求21所述的方法，所述AMF接收所述源UE发送的所述业务迁移相关信息之后，还包括：
    所述AMF向所述目标UE接入的基站发送寻呼消息，所述寻呼消息用于使所述目标UE接入的基站向所述目标UE发送所述寻呼信息，所述寻呼消息中包括所述业务迁移指示信息。
  23. 根据权利要求22所述的方法，其中，所述业务迁移指示信息包括以下信息中的至少一种：业务迁移指示，待迁移的PDU会话标识,目标UE标识。
  24. 根据权利要求19～23任一项所述的方法，所述核心网设备接收业务迁移相关信息之前，还包括：
    归属签约服务器HSS或统一数据管理功能UDM向所述目标UE发送所述目标UE所属PIoT签约信息，所述PIoT签约信息包括属于同一用户的UE标识列表。
  25. 根据权利要求20～23任一项所述的方法，其中，若所述目标UE和所述源UE接入的基站不同，所述当所述AMF确定所述源UE和所述目标UE属于同一PIoT时，所述目标UE和所述源UE的GTP-U关联到相同的PDU session，包括：
    当所述AMF确定所述源UE和所述目标UE属于同一PIoT时，向会话管理功能SMF发送会话管理更新请求，所述会话管理更新请求中包括与所述源UE相关的PDU session的相关信息；
    所述SMF向用户面功能UPF发送会话建立请求，所述会话建立请求中包括所述源UE的核心网信道信息；
    所述UPF向所述SMF发送会话建立响应，所述会话建立响应中包括与所述源UE相关的PDU session的相关信息；以及
    所述SMF向所述AFM发送会话管理更新响应，所述会话管理更新响应中包括与所述源UE相关的PDU session的相关信息。
  26. 根据权利要求25所述的方法，所述将所述目标UE和所述源UE的GTP-U关联到相同的PDU session之后，还包括：
    则UPF将所述源UE的第一业务数据复制后，通过所述目标UE接入的基站向所述目标UE发送。
  27. 根据权利要求25或26所述的方法，还包括：所述HSS或UDM向所述源UE和/或AMF发送所述源UE所属PIoT签约信息。
  28. 一种UE，所述UE为目标UE，包括：
    发送模块，用于向基站发送业务迁移相关信息，所述业务迁移相关信息用于指示将源UE的第一业务数据迁移到所述目标UE，所述源UE和所述目标UE属于同一个人物联网PIoT；以及
    接收模块，用于接收所述基站发送的所述第一业务数据，其中，所述目标UE和所述源UE的用户面GPRS隧道协议GTP-U隧道关联到相同的协议数据单元会话PDU session。
  29. 一种UE，所述UE为源UE，包括：
    发送模块，用于向基站或核心网发送业务迁移指示信息，所述业务迁移指示信息用于指示将源UE的第一业务数据迁移到目标UE；
    接收模块，用于接收所述目标UE连接的基站发送的链接删除消息或无线承载删除指示，所述链接删除消息包括所述源UE的非接入层NAS标识或个人物联网PIoT终端标识；以及
    连接模块，用于删除与所述源UE连接的基站之间的Uu链路或被迁移业务对应的无线承载。
  30. 一种基站，包括：
    接收模块，用于接收目标用户设备UE发送的业务迁移相关信息，所述业务迁移相关信息用于指示将源UE的第一业务数据迁移到所述目标UE，所述源UE和所述目标UE属于同一个人物联网PIoT；以及
    发送模块，用于所述基站向所述目标UE发送所述第一业务数据，其中，所述目标UE和所述源UE的用户面GPRS隧道协议GTP-U关联到相同的协议数据单元会话PDU session。
  31. 一种核心网设备，包括：
    接收模块，用于接收业务迁移相关信息，所述业务迁移相关信息用于将源用户设备UE的第一业务数据迁移到目标UE；以及
    处理模块，用于当确定所述源UE和所述目标UE属于同一个人物联网PIoT时，将所述目标UE和所述源UE的用户面GPRS隧道协议GTP-U关联到相同的协议数据单元会话PDU session。
  32. 一种计算机可读存储介质，存储有计算机可执行指令，其中，所述计算机可执行指令用于执行权利要求1～27任一项的UE间业务迁移方法。
PCT/CN2022/090060 2021-09-03 2022-04-28 Ue间业务迁移方法、装置和存储介质 Ceased WO2023029537A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
AU2022337484A AU2022337484B2 (en) 2021-09-03 2022-04-28 Method and apparatus for service switch between UEs, and storage medium
US18/687,282 US20240373335A1 (en) 2021-09-03 2022-04-28 Method and apparatus for service switch between ues, and storage medium
EP22862680.0A EP4398640A4 (en) 2021-09-03 2022-04-28 METHOD AND APPARATUS FOR MIGRATION OF SERVICE BETWEEN UEs, AND STORAGE MEDIUM

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111033623.5A CN115767659A (zh) 2021-09-03 2021-09-03 Ue间业务迁移方法、装置和存储介质
CN202111033623.5 2021-09-03

Publications (1)

Publication Number Publication Date
WO2023029537A1 true WO2023029537A1 (zh) 2023-03-09

Family

ID=85332629

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/090060 Ceased WO2023029537A1 (zh) 2021-09-03 2022-04-28 Ue间业务迁移方法、装置和存储介质

Country Status (5)

Country Link
US (1) US20240373335A1 (zh)
EP (1) EP4398640A4 (zh)
CN (1) CN115767659A (zh)
AU (1) AU2022337484B2 (zh)
WO (1) WO2023029537A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024207957A1 (zh) * 2023-04-07 2024-10-10 华为技术有限公司 用户下线方法和用户下线装置
WO2025015477A1 (zh) * 2023-07-14 2025-01-23 Oppo广东移动通信有限公司 通信方法和设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103139139A (zh) * 2011-11-22 2013-06-05 华为技术有限公司 用户设备间业务迁移的方法和装置
CN106507267A (zh) * 2015-09-07 2017-03-15 中国移动通信集团公司 业务处理方法、终端及基站
CN111480366A (zh) * 2017-12-15 2020-07-31 华为技术有限公司 共享pdu会话建立和绑定
CN113741762A (zh) * 2021-08-31 2021-12-03 深圳Tcl新技术有限公司 一种多媒体播放方法、装置、电子设备和存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103139139A (zh) * 2011-11-22 2013-06-05 华为技术有限公司 用户设备间业务迁移的方法和装置
CN106507267A (zh) * 2015-09-07 2017-03-15 中国移动通信集团公司 业务处理方法、终端及基站
CN111480366A (zh) * 2017-12-15 2020-07-31 华为技术有限公司 共享pdu会话建立和绑定
CN113741762A (zh) * 2021-08-31 2021-12-03 深圳Tcl新技术有限公司 一种多媒体播放方法、装置、电子设备和存储介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of EP4398640A4 *
SPREADTRUM COMMUNICATIONS: "R18 Personal IoT network considerations", 3GPP DRAFT; RWS-210060, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. TSG RAN, no. Electronic Meeting; 20210628 - 20210702, 7 June 2021 (2021-06-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052025623 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024207957A1 (zh) * 2023-04-07 2024-10-10 华为技术有限公司 用户下线方法和用户下线装置
WO2025015477A1 (zh) * 2023-07-14 2025-01-23 Oppo广东移动通信有限公司 通信方法和设备

Also Published As

Publication number Publication date
EP4398640A4 (en) 2025-09-03
CN115767659A (zh) 2023-03-07
EP4398640A1 (en) 2024-07-10
AU2022337484A1 (en) 2024-04-04
AU2022337484B2 (en) 2025-04-24
US20240373335A1 (en) 2024-11-07

Similar Documents

Publication Publication Date Title
US12501460B2 (en) Data scheduling method, base station, and system
JP7532448B2 (ja) データ伝送方法及び装置
CN109600802B (zh) 数据传输方法、相关设备及系统
US9681339B2 (en) Security processing method and system in network handover process
CN108632915A (zh) 一种终端在4g和5g网络间移动的方法、装置和设备
CN102196394B (zh) 信令跟踪信息的发送方法及装置
CN103428787B (zh) 一种基站切换方法及装置
CN104640165B (zh) 一种数据传输方法、设备和系统
CN108400847B (zh) 数据传输方法及装置
WO2022257975A1 (zh) 由用户设备执行的方法及用户设备
CN101272604B (zh) 信令跟踪方法及设备
KR20240137587A (ko) 멀티캐스트 전송을 지원하기 위한 방법, 기지국, 전자 장치 및 저장 매체
CN114303441A (zh) 5g中的rrc非活动的高效上下文处理
EP4398640A1 (en) Method and apparatus for service migration between ues, and storage medium
WO2023160686A1 (zh) 数据传输的方法、终端及网络侧设备
CN116567864A (zh) 支持组播传输的方法、基站、电子设备及存储介质
WO2018010583A1 (zh) 网络系统
CN104507133B (zh) 语音切换的方法和装置
CN109756619B (zh) 一种终端上下文的配置方法、网络设备及终端
CN108307429A (zh) 一种基站用户数据恢复的方法及装置
WO2020253536A1 (zh) 双连接重建立中数据的处理方法及装置
CN109831810B (zh) 一种建立无线接入承载的方法和装置
WO2019223774A1 (zh) 一种提高寻呼可靠性的方法及装置、计算机存储介质
CN114095874B (zh) 一种组播/广播业务模式处理方法、设备及存储介质
CN106304187A (zh) 一种移动通信系统中程序的处理方法和装置

Legal Events

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

Ref document number: 22862680

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202417018707

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2022337484

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 2022862680

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022337484

Country of ref document: AU

Date of ref document: 20220428

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022862680

Country of ref document: EP

Effective date: 20240403