WO2022222736A1 - 业务处理方法、装置、系统、可读取存储介质和电子设备 - Google Patents

业务处理方法、装置、系统、可读取存储介质和电子设备 Download PDF

Info

Publication number
WO2022222736A1
WO2022222736A1 PCT/CN2022/084831 CN2022084831W WO2022222736A1 WO 2022222736 A1 WO2022222736 A1 WO 2022222736A1 CN 2022084831 W CN2022084831 W CN 2022084831W WO 2022222736 A1 WO2022222736 A1 WO 2022222736A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
terminal device
message
terminal
processing method
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/084831
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.)
Spreadtrum Communications Shanghai Co Ltd
Original Assignee
Spreadtrum Communications Shanghai Co Ltd
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 Spreadtrum Communications Shanghai Co Ltd filed Critical Spreadtrum Communications Shanghai Co Ltd
Publication of WO2022222736A1 publication Critical patent/WO2022222736A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • 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
    • 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/005—Transmission of information for alerting of incoming communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a business processing method, apparatus, system, readable storage medium, and electronic device.
  • the terminal device includes a mobile phone, a tablet, or a smart watch.
  • the user uses one smart electronic device to perform service 1. If he wants another smart electronic device to perform service 1, he must perform a series of manual operations on the other smart electronic device to enable the other smart electronic device to perform service 1.
  • the operation steps are cumbersome. , the user experience is low.
  • the user has a mobile phone and a smart watch, and the user is listening to music through the mobile phone.
  • the user wants to listen to music through the smart watch, the user needs to manually turn off the music on the mobile phone, and then open the audio APP in the smart watch.
  • the audio APP Search for the name of the music and select the music you are listening to play in the search list.
  • the user realizes the sharing of the same service among multiple devices of the same user through manual operation, the operation steps are cumbersome, and the user experience is low.
  • the embodiments of the present application provide a service processing method, apparatus, system, readable storage medium and electronic device, which can automatically realize the sharing of the same service among multiple devices of the same user, with simple operation and high user experience.
  • an embodiment of the present application provides a service processing method, and the method includes:
  • the first message is used to request to share the established first service to the second terminal device.
  • the first message includes service establishment information
  • the service establishment information includes at least one of the following pieces of information: a service identifier of the first service, an identifier of a second terminal device, and an identifier of the second terminal device.
  • the business model includes business migration or business sharing.
  • the method before the sending the first message to the core network device, the method further includes:
  • the confirmation of service establishment with the second terminal device specifically includes:
  • a fourth message is received from the second terminal device, where the fourth message is used to instruct the second terminal device to accept establishment of the requested first service.
  • the third message includes at least one of the following information: a service identifier of the first service, a QoS parameter, a service mode, an identifier of a first terminal device, and an identifier of a cell where the first terminal is located .
  • the fourth message includes: the identity of the cell where the second terminal is located, or the same cell indication information;
  • the same-cell indication information is used to indicate whether the second terminal device is located in the same cell or the same access network device as the first terminal device.
  • the method before the confirmation of service establishment with the second terminal device, the method further includes:
  • the device discovery information sent by the second terminal device is received.
  • the device discovery information includes at least one item of the following information: a second terminal device identifier, a service type that can be established by the second terminal, and a mobility characteristic of the second terminal.
  • the first service is released.
  • the releasing the first service after the second terminal device successfully establishes the first service specifically includes:
  • the releasing the first service after the second terminal device successfully establishes the first service specifically includes:
  • an embodiment of the present application provides a service processing method, the method includes:
  • the first service established in the first terminal device is shared with the second terminal device according to the first message.
  • the first message includes service establishment information
  • the service establishment information includes at least one of the following pieces of information: a service identifier of the first service, an identifier of a second terminal device, and an identifier of the second terminal device.
  • the first terminal device and the second terminal device belong to different access network devices
  • Sharing the first service established in the first terminal device to the second terminal device according to the first message specifically including:
  • the second terminal device If it is determined that the second terminal device is not in the link state, send a second message to the target access network device, and after the second terminal device establishes an RRC connection, establish the first service with the second terminal device;
  • the second message is a paging message, which is used to trigger the second terminal device to establish an RRC connection.
  • the method before the sending the second message to the target access network device, the method further includes:
  • the target access network device where the second terminal device is located is determined according to the identity of the cell where the second terminal device is located in the first message.
  • the second message may carry the cell identifier of the cell where the second terminal device resides.
  • the first terminal device and the second terminal device belong to the same access network device
  • Sharing the first service established in the first terminal device to the second terminal device according to the first message specifically including:
  • a shared data channel is established for the first service of the first terminal device and the second terminal device.
  • a sixth message is sent to the first terminal device, so that the first terminal device releases the first service according to the sixth message, so The sixth message is used to notify the first terminal device to release the first service.
  • the method before sending the sixth message to the first terminal device, the method further includes:
  • An eighth message is received from the first terminal device, the eighth message being used to initiate the release of the first service shown.
  • the first terminal device and the second terminal device are located in the same access network device;
  • the method further includes:
  • the ninth message is sent after the access network device starts to schedule the first service of the second terminal device.
  • an embodiment of the present application provides a service processing apparatus, and the apparatus includes:
  • a first transceiver module configured to send a first message to the core network device, so that the core network device shares the established first service with the second terminal device;
  • the first message is used to request to share the established first service to the second terminal device.
  • an embodiment of the present application provides a service processing apparatus, and the apparatus includes:
  • a second transceiver module configured to receive a first message sent by a first terminal device, where the first message is used to request to share the first service established in the first terminal device to the second terminal device ;
  • a service processing module configured to share the first service established in the first terminal device to the second terminal device according to the first message.
  • an embodiment of the present application provides a service processing system, where the system includes: a first terminal device, a second terminal device, and a core network device;
  • the first terminal device configured to send a first message to the core network device, where the first message is used to request to share the established first service to the second terminal device;
  • the core network device is configured to share the first service established in the first terminal device to the second terminal device according to the first message; and after the second terminal device successfully establishes all the services After the first service is performed, send a sixth message to the first terminal device, where the sixth message is used to notify the first terminal device to release the first service;
  • the first terminal device is further configured to release the first service according to the sixth message.
  • an embodiment of the present application provides a readable storage medium, where the readable storage medium includes a stored program, wherein when the program runs, the device where the readable storage medium is located is controlled to execute the above The service processing method described in the first aspect or the second aspect.
  • an embodiment of the present application provides an electronic device, including a memory and a processor, where the memory is used to store information including program instructions, and the processor is used to control the execution of the program instructions, wherein the When the program instructions are loaded and executed by the processor, the steps of the service processing method described in the first aspect or the second aspect are implemented.
  • the first terminal device sends a first message to the core network device, and the first message is used to request the first terminal
  • the first service established in the device is shared to the second terminal device; the core network device shares the first service established in the first terminal device to the second terminal device according to the first message; and the second terminal device successfully establishes the first service.
  • a sixth message is sent to the first terminal device, where the sixth message is used to notify the first terminal device to release the first service; the first terminal device releases the first service according to the sixth message.
  • the embodiments of the present application can automatically realize the sharing of the same service among multiple devices of the same user, with simple operation and high user experience.
  • FIG. 1 is a flowchart of a service processing method provided by an embodiment of the present application
  • FIG. 2 is a flowchart of a service processing method provided by another embodiment of the present application.
  • FIG. 3 is a specific flow chart of confirming service establishment with the second terminal device according to the device discovery information of the second terminal device in FIG. 2;
  • FIG. 4 is a schematic diagram of configuration information interaction between a first terminal device and a second terminal device
  • FIG. 5 is a system architecture diagram of a service processing system provided by an embodiment of the present application.
  • FIG. 6 is a specific flowchart of releasing the first service after the second terminal device successfully establishes the first service in FIG. 2;
  • Fig. 7 is another specific flow chart of releasing the first service after the second terminal device successfully establishes the first service in Fig. 2;
  • Fig. 8 is another specific flow chart of releasing the first service after the second terminal device successfully establishes the first service in Fig. 2;
  • FIG. 9 is a flowchart of a service processing method provided by another embodiment of the present application.
  • FIG. 10 is a flowchart of a service processing method provided by another embodiment of the present application.
  • FIG. 11 is a specific flowchart of sharing the first service established in the first terminal device to the second terminal device according to the first message in FIG. 10;
  • FIG. 12 is a schematic structural diagram of a service processing apparatus according to an embodiment of the application.
  • Fig. 13 is the concrete structure schematic diagram of the confirmation module in Fig. 12;
  • Fig. 14 is the concrete structure schematic diagram of the release module in Fig. 12;
  • FIG. 15 is a schematic structural diagram of a service processing apparatus according to another embodiment of the present application.
  • Fig. 16 is the concrete structural schematic diagram of the service processing module in Fig. 15;
  • FIG. 17 is a schematic structural diagram of a service processing system according to an embodiment of the application.
  • FIG. 18 is a schematic diagram of an electronic device according to an embodiment of the present application.
  • transmission can include sending and/or receiving, and can be a noun or a verb.
  • the equals involved in the embodiments of this application can be used in conjunction with greater than, and are applicable to the technical solutions adopted when greater than, and can also be used in conjunction with less than, and are applicable to the technical solutions adopted when and less than. It should be noted that when equals and greater than are connected When used, it is not used with less than; when equal to and less than, it is not used with greater than.
  • the terminal device in this embodiment of the present application is a device with a wireless communication function, which may be referred to as a terminal (terminal), user equipment (UE), mobile station (mobile station, MS), mobile terminal (mobile terminal, MT) ), access terminal equipment, vehicle terminal equipment, industrial control terminal equipment, UE unit, UE station, mobile station, remote station, remote terminal equipment, mobile equipment, UE terminal equipment, wireless communication equipment, UE proxy or UE device, etc.
  • Terminal devices can be fixed or mobile.
  • the terminal device may support at least one wireless communication technology, such as LTE, new radio interface (new radio, NR), and the like.
  • the terminal device may be a mobile phone (mobile phone), a tablet computer (pad), a desktop computer, a notebook computer, an all-in-one computer, a vehicle terminal, a virtual reality (virtual reality, VR) terminal device, an augmented reality (augmented reality, AR) terminal Equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, wireless terminals in smart grid, transportation safety Wireless terminals in (transportation safety), wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless Wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, wearable devices, future mobile communications
  • the terminal device may also be a device with a transceiving function, such as a chip system
  • the access network device is a device that provides a wireless communication function for terminal devices, and may also be referred to as a radio access network (radio access network, RAN) device, or an access network element, or the like.
  • the access network device may support at least one wireless communication technology, such as LTE, NR, and the like.
  • the access network equipment includes, but is not limited to: a next-generation base station (generation nodeB, gNB), an evolved node B (evolved node B, eNB), wireless Network controller (radio network controller, RNC), node B (node B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved node B, or home node B, HNB), baseband unit (BBU), transmitting and receiving point (TRP), transmitting point (TP), mobile switching center, etc.
  • generation nodeB, gNB next-generation base station
  • evolved node B, eNB evolved node B
  • wireless Network controller radio network controller
  • node B node B
  • base station controller base station controller
  • BTS base transceiver station
  • home base station for example, home evolved node B, or home node B, HNB
  • BBU baseband unit
  • TRP transmitting and receiving point
  • the network device may also be a wireless controller, centralized unit (centralized unit, CU), and/or distributed unit (distributed unit, DU) in a cloud radio access network (cloud radio access network, CRAN) scenario, or an access network
  • the device may be a relay station, an access point, a vehicle-mounted device, a terminal device, a wearable device, and an access network device in future mobile communications or an access network device in a future evolved PLMN, and the like.
  • the access network device may also be an apparatus having a wireless communication function for the terminal device, such as a chip system.
  • the system-on-chip may include chips, and may also include other discrete devices.
  • the access network device may also communicate with an Internet Protocol (Internet Protocol, IP) network, such as the Internet (internet), a private IP network, or other data networks.
  • IP Internet Protocol
  • the core network in the embodiment of the present application is composed of core network network elements.
  • the core network element may also be referred to as a core network device, and is a network element deployed in the core network, such as a core network control plane network element or a core network user plane network element.
  • the core network in this embodiment of the present application may be an evolved packet core network (Evolved Packet Core, EPC), a 5G core network (5G Core Network), or may be a new type of core network in a future communication system.
  • EPC evolved Packet Core
  • 5G Core Network 5G core network
  • the 5G core network consists of a set of network elements, and implements access and mobility management functions (Access and Mobility Management Function, AMF) for functions such as mobility management, provides packet routing and forwarding and QoS (Quality of Service) management User Plane Function (UPF), which provides functions such as session management, IP address allocation and management, and Session Management Function (SMF), etc.
  • AMF Access and Mobility Management Function
  • UPF Quality of Service management User Plane Function
  • SMF Serving Gateway
  • PDN Gateway PDN Gateway that provides functions such as terminal address allocation and rate control.
  • the core network may include several new network elements to implement packet forwarding, MBS conference management, QoS management, and transmission mode switching (unicast and multicast/broadcast transmission). switch between modes). Another way is that the functions can be implemented by existing core network elements.
  • uplink communication may also be referred to as uplink transmission, which refers to unidirectional communication from a terminal device to an access network device, where a communication link used for uplink communication is an uplink.
  • Data transmitted on the uplink is uplink data.
  • the transmission direction of upstream data is the upstream direction.
  • downlink communication may also be referred to as downlink transmission, which refers to unidirectional communication from an access network device to a terminal device, where a communication link used for downlink communication is an uplink. Data transmitted on the downlink is downlink data. The transmission direction of downlink data is the downlink direction.
  • FIG. 1 is a flowchart of a service processing method provided by an embodiment of the present application, which is applied to a first terminal device. As shown in FIG. 1 , the method includes:
  • Step 101 Send a first message to the core network device, so that the core network device shares the established first service with the second terminal device.
  • the first message is used to request to share the established first service to the second terminal device.
  • a first message is sent to the core network device, so that the core network device shares the established first service with the second terminal device; wherein, the first message uses upon requesting to share the established first service with the second terminal device.
  • FIG. 2 is a flowchart of a service processing method provided by another embodiment of the present application, which is applied to a first terminal device. As shown in FIG. 2 , the method includes:
  • Step 201 Receive device discovery information sent by a second terminal device.
  • User's terminal devices such as the first terminal device and the second terminal device can send device discovery information of the terminal device, and the device discovery information is used by other terminal devices to discover the terminal device.
  • the terminal device can periodically send device discovery information.
  • the device discovery information may include at least one of the following: an identifier of the terminal device, a service type that the terminal device can establish, and mobility characteristics of the terminal device.
  • the service types that the terminal equipment can establish refers to the service types that the terminal equipment supports to establish; the mobility characteristics refer to one or more of fixed, high-speed mobile, low-speed mobile, and medium-speed mobile.
  • the first terminal device may receive device discovery information from multiple terminal devices, and select one terminal device from the multiple terminal devices to send a message requesting service establishment.
  • the device discovery information includes at least one of the following information: a device identifier of the second terminal, a service type that can be established by the second terminal, and a mobility characteristic of the second terminal.
  • Step 202 confirming service establishment with the second terminal device.
  • step 202 specifically includes:
  • Step 2021 Send a third message to the second terminal device, where the third message is used to request the second terminal to establish the first service.
  • the first terminal device sends a third message to the second terminal device to request establishment of the first service according to the device discovery information of the second terminal device.
  • the third message includes configuration information
  • the configuration information includes at least one of the following information: a service identifier of the first service, a quality of service (Quality of Service, QoS) parameter, a service mode, and a first terminal device ID, ID of the cell where the first terminal is located.
  • QoS Quality of Service
  • the QoS parameters include one or more of: service type, delay, packet loss rate, priority, and rate.
  • An index identifier may be used to represent one or more of the above-mentioned QoS parameters.
  • the service types include: video services or voice services.
  • the third message includes the service identifier 1 and the service type is a video service
  • the third message includes the service identifier 1
  • the QoS parameter of the first service includes that the service type is a video service.
  • Step 2022 Receive a fourth message from the second terminal device, where the fourth message is used to confirm that the second terminal device accepts the establishment of the requested first service
  • the second terminal device can accept the establishment of the first service requested by the first terminal device, it sends a fourth message to the first terminal device, and the fourth message is used to indicate the second terminal device.
  • the terminal device can accept the establishment of the first service.
  • the fourth message includes: the identity of the cell where the second terminal is located, or the same cell indication information; the same cell indication information is used to indicate whether the second terminal device is located in the same cell as the first terminal device or the same cell indication information. the same access network device.
  • the second terminal device if the second terminal device cannot accept the establishment of the first service requested by the first terminal device, the second terminal device sends a fifth message to the first terminal device, and the fifth message is used to indicate that the second terminal device cannot Initiate the first business.
  • third message, fourth message and fifth message are all sent through the direct communication interface between terminal devices.
  • the discovery and selection of the terminal device can be realized for service sharing, and the service establishment process can be initiated, thereby triggering the core network device in the second terminal device. Do business establishment.
  • Step 203 Send a first message to the core network device, so that the core network device shares the established first service with the second terminal device.
  • the user owns the first terminal device and the second terminal device, and when the user needs to share the first service established in the first terminal device with the second terminal device, the first terminal device sends a message to the core network device.
  • First news the first news.
  • the first message is used to request to share the established first service to the second terminal device.
  • the first message may be a non-intrusive layer NAS message or other type of message.
  • the first message includes service establishment information
  • the service establishment information includes at least one of the following information: a service identifier of the first service, an identifier of a second terminal device, an identifier of a cell where the second terminal device is located, Describe the business model of the first business.
  • the service identifier is used to identify the service requested to be established, and the service identifier includes but is not limited to QoS flow identifier (QoS Flow ID, QFI), session identifier (session id), temporary user group identifier (Temporary Mobile Group Identity, TMGI), One or more of the Internet Protocol (IP) addresses.
  • QoS flow ID QoS Flow ID, QFI
  • session id session identifier
  • TMGI Temporary Mobile Group Identity
  • IP Internet Protocol
  • the second terminal device identifier is used to indicate the device identifier of the second terminal device, and refers to the device identifiers of multiple terminal devices of the same user, and the device identifiers may be allocated by the core network device. For example, the core network device assigns device identifiers a, b, c, d, and e to five terminal devices of the same user. If the device identifier of the second terminal device is a, the core network device receives the device identifier a and can identify the out the second terminal device. The device identification may also be set by the user.
  • the cell identifier where the second terminal device is located refers to the cell identifier of the cell where the second terminal device resides, and may be a Cell Global Identifier (CGI).
  • CGI Cell Global Identifier
  • the business model includes business migration or business sharing.
  • Service migration refers to migrating a service from one terminal device to another terminal device; service sharing means that the same service is performed in multiple terminal devices.
  • the core network device after receiving the first message, decides to establish the requested first service for the second terminal device according to the content of the first message.
  • the core network device first needs to determine whether the second terminal device is in the link state. As shown in FIG. 5 , if the second terminal device is in the link state, the core network device and the second terminal device establish the first service. If the second terminal device is not in the link state, the core network device sends a second message to the target access network device, where the second message is a paging message; the core network device can The cell identifier of the cell where the device is located obtains the identifier of the target access network device, thereby determining to send paging messages to the target access network device, which can reduce the number of paging messages sent and the load of message sending between network elements.
  • the paging message may carry the cell identifier of the cell where the second terminal equipment resides.
  • the target access network device that receives the paging message can only send the paging message in the cell, thereby reducing the transmission load of the air interface paging message.
  • the second terminal device After receiving the paging message, the second terminal device performs a radio resource control protocol (Radio Resource Control, RRC) connection establishment, and then the core network device establishes the first service on the second terminal device.
  • RRC Radio Resource Control
  • the user plane data channel between the core network equipment and the access network equipment such as GPRS Tunnelling Protocol for the user plane, GTPU) tunnel, which can be multiplexed among multiple terminal devices, that is, the same data channel can be used for uplink or downlink data transmission of the first terminal device and the second terminal device.
  • the core network device may indicate that the data channel of the first service of the first terminal device of the access network device can be used to transmit data of the first service of the second terminal device.
  • the core network device establishes a separate user plane data channel between the access network device and the first service of the second terminal device.
  • the network side can establish the same service among multiple terminal devices for the user, thereby realizing service migration or service sharing.
  • Step 204 After the second terminal device successfully establishes the first service, the first service is released.
  • step 204 is executed; if the service mode of the first service is service sharing, after step 203, step 204 does not need to be executed.
  • step 204 specifically includes:
  • Step 2041 Receive a sixth message from the core network device, where the sixth message is used to notify the first terminal device to release the first service.
  • the core network device decides to release the first service in the first terminal device.
  • the core network device initiates a process of releasing the first service in the first terminal device. Specifically, the core network device sends a sixth message to the first terminal device, where the sixth message is used to notify the first terminal device to release the first service.
  • the sixth message includes but is not limited to a PDU session release command (PDU session release command) message and a PDU session modification command (PDU session modification request) message, wherein the sixth message carries the identifier of the first service.
  • PDU session release command PDU session release command
  • PDU session modification request PDU session modification request
  • Step 2042 Release the first service according to the sixth message.
  • step 204 specifically includes:
  • Step 2041 Receive a seventh message from the second terminal device, where the seventh message is used to notify that the first service is successfully established on the second terminal device.
  • the seventh message sent from the second terminal device is received through the direct interface between the terminal devices.
  • Step 2042 Send an eighth message to the core network device, where the eighth message is used to initiate release of the first service.
  • the first terminal device receives the seventh message, and sends the eighth message to the core network device, where the eighth message is used to initiate release of the first service.
  • the eighth message includes but is not limited to a PDU session modification request message and a PDU session release request message, wherein the eighth message carries the identifier of the first service.
  • step 204 specifically includes:
  • Step 2041 After the access network device sends the ninth message to the core network device, receive a sixth message from the core network device, where the ninth message is used to request the release of the first service, and the ninth message carries the identifier of the first service.
  • the access network device After the access network device starts to schedule the first service of the second terminal device, it sends a ninth message to the core network device, and receives a sixth message sent by the core network device according to the ninth message.
  • the access network device decides to release the first service of the first terminal device after starting to schedule the first service of the second terminal device. Specifically, the access network device sends the ninth message to the core network device, requesting to release the first service of the first terminal device, and the core network device receiving the ninth message initiates a process of releasing the first service of the first terminal device. Specifically, the core network device sends the sixth message to the first terminal device. The ninth message is used to request to release the first service of the first terminal device; the sixth message is used to notify the first terminal device to release the first service.
  • Step 2042 Release the first service according to the sixth message.
  • the technical solution of the service processing method provided in this application can be applied to a 5G (5 Generation) communication system, can also be applied to a 4G communication system, and can also be applied to various new communication systems in the future, such as 6G, 7G, etc.
  • the technical solution of the service processing method provided in this application is also applicable to different network architectures, including but not limited to terrestrial communication network architecture, non-terrestrial communication network architecture, relay network architecture, dual link architecture, vehicle-to-any object communication (Vehicle to any object) -to-Everything) architecture and other architectures.
  • network architectures including but not limited to terrestrial communication network architecture, non-terrestrial communication network architecture, relay network architecture, dual link architecture, vehicle-to-any object communication (Vehicle to any object) -to-Everything) architecture and other architectures.
  • the device discovery information sent by the second terminal device is received, and according to the device discovery information of the second terminal device, the service establishment confirmation is performed with the second terminal device;
  • the network device sends the first message, so that the core network device shares the established first service with the second terminal device; after the second terminal device successfully establishes the first service, the first service is released; wherein, the first message is used for Request to share the established first service to the second terminal device.
  • FIG. 9 is a flowchart of a service processing method provided by another embodiment of the present application, which is applied to core network equipment. As shown in FIG. 9 , the method includes:
  • Step 301 Receive a first message sent by a first terminal device, where the first message is used to request to share a first service established in the first terminal device to a second terminal device.
  • Step 302 Share the first service established in the first terminal device to the second terminal device according to the first message.
  • a first message sent by a first terminal device is received, and the first message is used to request to share the first service established in the first terminal device to the second terminal equipment; sharing the first service established in the first terminal equipment with the second terminal equipment according to the first message.
  • the embodiments of the present application can automatically realize the sharing of the same service among multiple devices of the same user, with simple operation and high user experience.
  • FIG. 10 is a flowchart of a service processing method provided by another embodiment of the present application, which is applied to core network equipment. As shown in FIG. 10 , the method includes:
  • Step 401 Receive a first message sent by a first terminal device, where the first message is used to request to share the first service established in the first terminal device to the second terminal device.
  • the user owns the first terminal device and the second terminal device, and when the user needs to share the first service established in the first terminal device with the second terminal device, the first terminal device sends a message to the core network device.
  • First news the first news.
  • the first message is used to request to share the established first service to the second terminal device.
  • the first message may be a non-intrusive layer NAS message or other type of message.
  • the first message includes service establishment information
  • the service establishment information includes at least one of the following information: a service identifier of the first service, an identifier of a second terminal device, and an identifier of the second terminal device.
  • the service identifier is used to identify the service requested to be established, and the service identifier includes but is not limited to one or more of QoS flow id, session id, TMGI, and IP address.
  • the second terminal device identifier is used to indicate the device identifier of the second terminal device, and refers to the device identifiers of multiple terminal devices of the same user, and the device identifiers may be allocated by the core network device. For example, the core network device assigns device identifiers a, b, c, d, and e to five terminal devices of the same user. If the device identifier of the second terminal device is a, the core network device receives the device identifier a and can identify the out the second terminal device. The device identification may also be set by the user.
  • the cell identifier where the second terminal device is located refers to the cell identifier of the cell where the second terminal device resides, and may be a global cell identifier.
  • the business model refers to business migration or business sharing.
  • Service migration refers to migrating a service from one terminal device to another terminal device; service sharing means that the same service is performed in multiple terminal devices.
  • Step 402 Share the first service established in the first terminal device to the second terminal device according to the first message.
  • the core network device after receiving the first message, decides to establish the requested first service for the second terminal device according to the content of the first message.
  • step 402 specifically includes:
  • Step 4021 determine whether the second terminal device is in the link state; if yes, go to step 4022 ; if not, go to step 4023 .
  • the core network device first needs to determine whether the second terminal device is in the link state.
  • Step 4022 establish a first service with the second terminal device; and continue to perform step 403 .
  • the core network device and the second terminal device establish the first service.
  • Step 4023 Determine the target access network device where the second terminal device is located according to the cell identifier where the second terminal device is located in the first message.
  • the core network device obtains the identifier of the target access network device according to the cell identifier of the cell where the second terminal device is located in the first message, so as to determine the target access network where the second terminal device is located. equipment.
  • Step 4024 Send a second message to the target access network device, so that the target access network device sends a second message to the second terminal device according to the second message, where the second message is a paging message and is used to trigger the second terminal device Perform RRC connection establishment.
  • the core network device sends a second message to the target access network device, where the second message is a paging message, which is used to trigger the second terminal device to establish an RRC connection; sending the paging message to the target access network device may The number of paging messages sent is reduced, and the load of message sending between network elements is reduced.
  • the paging message may carry the cell identifier of the cell where the second terminal equipment resides.
  • the target access network device that receives the paging message can only send the paging message in the cell, thereby reducing the transmission load of the air interface paging message.
  • Step 4025 After the second terminal device establishes the RRC connection according to the paging message, establish the first service with the second terminal device.
  • the second terminal device After receiving the paging message, the second terminal device performs RRC connection establishment, and then the core network device establishes the first service on the second terminal device.
  • step 402 specifically includes: establishing a shared data channel for the first service of the first terminal device and the second terminal device.
  • the user plane data channel between the core network device and the access network device can be multiplexed among multiple terminal devices, that is, the same data channel It can be used for uplink or downlink data transmission of the first terminal device and the second terminal device.
  • the core network device may indicate that the data channel of the first service of the first terminal device of the access network device can be used to transmit data of the first service of the second terminal device.
  • Step 403 After the second terminal device successfully establishes the first service, send a sixth message to the first terminal device, so that the first terminal device releases the first service according to the sixth message, and the sixth message is used to notify the first terminal device Release the first business.
  • step 403 if the service mode of the first service is service migration, after step 402, step 403 is executed; if the service mode of the first service is service sharing, after step 402, step 403 does not need to be executed.
  • the method before sending the sixth message to the first terminal device, the method further includes:
  • Step 402' Receive an eighth message from the first terminal device, where the eighth message is used to initiate the release of the first service shown.
  • the first terminal device and the second terminal device are located in the same access network device; before sending the sixth message to the first terminal device, the method further includes:
  • Step 402' Receive a ninth message from the access network device, where the ninth message is used to request to release the first service of the first terminal device.
  • the ninth message is sent after the access network device starts to schedule the first service of the second terminal device.
  • the access network device decides to release the first service of the first terminal device after starting to schedule the first service of the second terminal device. Specifically, the access network device sends the ninth message to the core network device, requesting to release the first service of the first terminal device, and the core network device receiving the ninth message initiates a process of releasing the first service of the first terminal device. Specifically, the core network device sends the sixth message to the first terminal device. The ninth message is used to request to release the first service of the first terminal device; the sixth message is used to notify the first terminal device to release the first service.
  • the technical solution of the service processing method provided in this application can be applied to 5G communication system, 4G communication system, and various new communication systems in the future, such as 6G, 7G, etc.
  • the technical solution of the service processing method provided in this application is also applicable to different network architectures, including but not limited to terrestrial communication network architecture, non-terrestrial communication network architecture, relay network architecture, dual link architecture, vehicle-to-any object communication architecture, etc. Architecture.
  • a first message sent by a first terminal device is received, and the first message is used to request to share the first service established in the first terminal device to the second terminal device; share the first service established in the first terminal device to the second terminal device according to the first message; after the second terminal device successfully establishes the first service, send a sixth message to the first terminal device, so that the first A terminal device releases the first service according to the sixth message, and the sixth message is used to notify the first terminal device to release the first service.
  • the embodiments of the present application can automatically realize the sharing of the same service among multiple devices of the same user, with simple operation and high user experience.
  • FIG. 12 is a schematic structural diagram of a service processing apparatus according to an embodiment of the application. As shown in FIG. 12 , the apparatus includes: a first transceiver module 51 , a confirmation module 52 and a release module 53 .
  • the first transceiver module 51 is configured to receive device discovery information sent by the second terminal device.
  • the device discovery information includes at least one of the following information: a device identifier of the second terminal, a service type that can be established by the second terminal, and a mobility characteristic of the second terminal.
  • the confirmation module 52 is used for confirming service establishment with the second terminal device.
  • the confirmation module 52 specifically includes: a creation request sub-module 521 and a confirmation sub-module 522 .
  • the establishment request sub-module 521 is configured to send a third message to the second terminal device, where the third message is used to request the second terminal to establish the first service.
  • the third message includes at least one of the following information: a service identifier of the first service, a QoS parameter, a service mode, an identifier of the first terminal device, and an identifier of a cell where the first terminal is located.
  • the confirmation sub-module 522 is configured to receive a fourth message from the second terminal device, where the fourth message is used to confirm that the second terminal device accepts the establishment of the requested first service.
  • the fourth message includes: the identity of the cell where the second terminal is located, or the same cell indication information; the same cell indication information is used to indicate whether the second terminal device is located in the same cell or connected to the first terminal device. access equipment.
  • the first transceiver module 51 is further configured to send a first message to the core network device, so that the core network device shares the established first service with the second terminal device.
  • the first message is used to request to share the established first service to the second terminal device.
  • the first message includes service establishment information
  • the service establishment information includes at least one of the following information: a service identifier of the first service, an identifier of the second terminal device, the identifier of the cell where the second terminal device is located, the Describe the business model of the first business.
  • the business model includes business migration or business sharing.
  • the releasing module 53 is configured to release the first service after the second terminal device successfully establishes the first service.
  • the release module 53 specifically includes: a notification sub-module 531 and a release sub-module 532 .
  • the notification submodule 531 is used to receive the sixth message from the core network device, and the sixth message is used to notify the first terminal device to release the first service; the release submodule 532 is used to release the first service according to the sixth message Release the first business.
  • the notification sub-module 531 is configured to receive a seventh message sent by the second terminal device, where the seventh message is used to notify the first terminal device that the first service is successfully established in the second terminal device; release the sub-module 532, for sending an eighth message to the core network device, where the eighth message is used for initiating release of the first service.
  • the first terminal device and the second terminal device are located in the same access network device; the notification sub-module 531 is configured to receive the core network device after the access network device sends the ninth message to the core network device.
  • the ninth message is used to request to release the first service of the first terminal device; the sixth message is used to notify the first terminal device to release the first service.
  • the service processing apparatus provided by the embodiments of the present application can be used to implement the service processing methods in the foregoing FIG. 1 to FIG. 8 .
  • the service processing apparatus can be used to implement the service processing methods in the foregoing FIG. 1 to FIG. 8 .
  • FIG. 8 For a specific description, refer to the embodiments of the foregoing service processing methods, which will not be repeated here.
  • the service processing device may be, for example, a chip, a chip module, or a part of a chip module.
  • the device discovery information sent by the second terminal device is received, and according to the device discovery information of the second terminal device, the service establishment confirmation is performed with the second terminal device;
  • the network device sends the first message, so that the core network device shares the established first service with the second terminal device; after the second terminal device successfully establishes the first service, the first service is released; wherein, the first message is used for Request to share the established first service to the second terminal device.
  • FIG. 15 is a schematic structural diagram of a service processing apparatus provided by an embodiment of the application. As shown in FIG. 15 , the apparatus includes: a second transceiver module 61 and a service processing module 62 .
  • the second transceiver module 61 is configured to receive a first message sent by the first terminal device, where the first message is used to request to share the first service established in the first terminal device to the second terminal device.
  • the first message includes service establishment information
  • the service establishment information includes at least one of the following information: a service identifier of the first service, an identifier of a second terminal device, and an identifier of the second terminal device.
  • the service processing module 62 is configured to share the first service established in the first terminal device to the second terminal device according to the first message.
  • the service processing module 62 specifically includes: a judgment submodule 621 , a first establishment submodule 622 , a determination submodule 623 and a second establishment submodule 624 .
  • the judging submodule 621 is used for judging whether the second terminal device is in the link state according to the first message.
  • the first establishment sub-module 622 is configured to establish the first service with the second terminal device if the judgment sub-module 621 judges that the second terminal device is in the link state; and continue to execute after the second terminal device successfully establishes the first service. An operation of sending the sixth message by the first terminal device.
  • the determining submodule 623 is configured to determine the target access network device where the second terminal device is located according to the cell identifier where the second terminal device is located in the first message if the determining submodule 621 determines that the second terminal device is not in the link state.
  • the second transceiver module 61 is further configured to send a second message to the target access network device, so that the target access network device sends a second message to the second terminal device according to the second message.
  • the second message is a paging message and is used for in triggering the second terminal device to establish an RRC connection.
  • the second establishment submodule 624 is configured to establish the first service with the second terminal device after the second terminal device establishes the RRC connection according to the paging message.
  • the first terminal device and the second terminal device belong to the same access network device; the service processing module 62 is specifically configured to: establish a shared data channel for the first service of the first terminal device and the second terminal device .
  • the second transceiver module 61 is further configured to send a sixth message to the first terminal device after the second terminal device successfully establishes the first service, so that the first terminal device releases the first service according to the sixth message; the sixth message uses the to notify the first terminal device to release the first service.
  • the second transceiving module 61 is further configured to receive an eighth message from the first terminal device, where the eighth message is used to initiate a communication to the first terminal device. A business release.
  • the first terminal device and the second terminal device are located in the same access network device; before sending the sixth message to the first terminal device, the second transceiver module 61 is further configured to receive data from the access network
  • the ninth message sent by the device where the ninth message is used to request to release the first service of the first terminal device.
  • the ninth message is sent after the access network device starts to schedule the first service of the second terminal device.
  • the service processing apparatus provided by the embodiments of the present application can be used to implement the service processing methods in the foregoing FIG. 9 to FIG. 11 .
  • the service processing apparatus can be used to implement the service processing methods in the foregoing FIG. 9 to FIG. 11 .
  • the description is not repeated here.
  • the service processing device may be, for example, a chip, a chip module, or a part of a chip module.
  • a first message sent by a first terminal device is received, and the first message is used to request to share the first service established in the first terminal device to the second terminal device; share the first service established in the first terminal device to the second terminal device according to the first message; after the second terminal device successfully establishes the first service, send a sixth message to the first terminal device, so that the first A terminal device releases the first service according to the sixth message, and the sixth message is used to notify the first terminal device to release the first service.
  • the embodiments of the present application can automatically realize the sharing of the same service among multiple devices of the same user, with simple operation and high user experience.
  • modules/units which may be software modules/units, hardware modules/units, or may be partly software modules/units, partly Hardware modules/units.
  • each module/unit included in the product may be implemented by hardware such as circuits, or at least some modules/units may be implemented by software programs, which run on the integrated processing inside the chip.
  • the remaining (if any) part of the modules/units can be implemented by hardware such as circuits; for each device and product corresponding to or integrated with the chip module, the modules/units contained therein can be implemented by hardware such as circuits.
  • modules/units can be located in the same part of the chip module (such as chips, circuit modules, etc.) or in different components, and at least some/units can be implemented in the form of software programs that run on the integrated processor inside the chip module
  • the remaining (if any) modules/units can be implemented by hardware such as circuits; for each device or product that corresponds to or integrated with the terminal, the modules/units contained therein can be implemented by hardware such as circuits, and different modules/units can be implemented by hardware such as circuits.
  • modules/units can be implemented in the form of software programs, which run on the processor integrated inside the terminal, and the remaining (if any) components Modules/units can be implemented in hardware such as circuits.
  • FIG. 17 is a schematic structural diagram of a service processing system provided by an embodiment of the application. As shown in FIG. 17 , the system includes: a first terminal device 71 , a second terminal device 72 , and a core network device 73 .
  • the first terminal device 71 is configured to send a first message to the core network device 73 , where the first message is used to request to share the established first service to the second terminal device 72 .
  • the core network device 73 is used to share the first service established in the first terminal device 71 to the second terminal device 72 according to the first message; and after the second terminal device 72 successfully establishes the first service, to the first terminal
  • the device 71 sends a sixth message, and the sixth message is used to notify the first terminal device 71 to release the first service;
  • the first terminal device 72 is further configured to release the first service according to the sixth message.
  • the system further includes: a target access network device 74 .
  • the target access network device 74 is the access network device where the second terminal device 72 is located.
  • the target access network device 74 is configured to receive a second message sent by the core cloud device 73 when the second terminal device is not in the link state, and send a second message to the second terminal device 72 according to the second message, where the second message is a search request. call message.
  • the first terminal device 71 and the second terminal device 72 are located in the same access network device; before the core cloud device 73 sends the sixth message to the first terminal device 71,
  • the target access network device 74 is further configured to schedule the first service of the second terminal device 72 and send a ninth message to the core cloud device 73 , where the ninth message is used to request to release the first service of the first terminal device 71 .
  • the service processing system provided by the embodiments of the present application can be used to implement the service processing methods in FIG. 1 to FIG. 11 .
  • the service processing system can be used to implement the service processing methods in FIG. 1 to FIG. 11 .
  • the first terminal device sends a first message to the core network device, and the first message is used to request to share the first service established in the first terminal device to the first terminal device.
  • the core network device shares the first service established in the first terminal device to the second terminal device according to the first message; and after the second terminal device successfully establishes the first service, sends the first service to the first terminal device.
  • the sixth message is used to notify the first terminal device to release the first service; the first terminal device releases the first service according to the sixth message.
  • FIG. 18 is a schematic structural diagram of an embodiment of an electronic device in this specification.
  • the electronic device may include at least one processor; and at least one memory communicatively connected to the processor, wherein: the memory stores data that can be processed
  • the above-mentioned processor can call the above-mentioned program instructions to execute the service processing methods provided by the embodiments shown in FIG. 1 to FIG. 8 or FIG. 9 to FIG. 11 of this specification.
  • Figure 18 shows a block diagram of an exemplary electronic device suitable for use in implementing embodiments of the present specification.
  • the electronic device shown in FIG. 1 is only an example, and should not impose any limitation on the function and scope of use of the embodiments of the present specification.
  • the electronic device takes the form of a general-purpose computing device.
  • Components of the electronic device may include, but are not limited to, one or more processors 21 , a memory 23 , and a communication bus 24 connecting different system components (including the memory 23 and the processing unit 21 ).
  • Communication bus 24 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of a variety of bus structures.
  • these architectures include, but are not limited to, Industry Standard Architecture (hereinafter referred to as: ISA) bus, Micro Channel Architecture (hereinafter referred to as: MAC) bus, enhanced ISA bus, video electronics Standards Association (Video Electronics Standards Association; hereinafter referred to as: VESA) local bus and Peripheral Component Interconnection (Peripheral Component Interconnection; hereinafter referred to as: PCI) bus.
  • ISA Industry Standard Architecture
  • MAC Micro Channel Architecture
  • VESA Video Electronics Standards Association
  • PCI Peripheral Component Interconnection
  • Electronic devices typically include various computer system readable media. These media can be any available media that can be accessed by the electronic device, including both volatile and nonvolatile media, removable and non-removable media.
  • the memory 23 may include a computer system readable medium in the form of volatile memory, such as random access memory (Random Access Memory; hereinafter referred to as: RAM) and/or cache memory.
  • RAM random access memory
  • the electronic device may further include other removable/non-removable, volatile/non-volatile computer system storage media.
  • the memory 23 may include at least one program product having a set (eg, at least one) of program modules configured to perform the functions of the various embodiments of this specification.
  • Program modules typically perform the functions and/or methods of the embodiments described in this specification.
  • the processor 21 executes various functional applications and data processing by running the programs stored in the memory 23 , for example, implementing the service processing methods provided by the embodiments shown in FIGS. 1 to 8 or 9 to 11 of this specification.
  • each step of the above-mentioned method can be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the steps of the method disclosed in combination with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software units in the processor.
  • the software unit may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor executes the instructions in the memory, and completes the steps of the above method in combination with its hardware. To avoid repetition, detailed description is omitted here.
  • the processor of the above device may be a central processing unit (Central Processing Unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs) , Field Programmable Gate Array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • CPU Central Processing Unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • Embodiments of the present application further provide a computer storage medium, wherein the computer storage medium stores a computer program for electronic data exchange, and the computer program causes the computer to execute part or all of the steps of any method described in the above method embodiments .
  • Embodiments of the present application further provide a computer program product, where the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute any one of the method embodiments described above. some or all of the steps of the method.
  • the computer program product may be a software installation package.
  • the disclosed apparatus may be implemented in other manners.
  • the device embodiments described above are only illustrative.
  • the division of the above units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical or other forms.
  • the units described above as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solutions of the embodiments of the present application.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the above-mentioned integrated units if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable memory.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art, or all or part of the technical solution, and the computer software product is stored in a memory.
  • a computer device which may be a personal computer, a server, or a TRP, etc.
  • the aforementioned memory includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

Landscapes

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

Abstract

本申请实施例提供了一种业务处理方法、装置、系统、可读取存储介质和电子设备。本申请实施例提供的技术方案中，第一终端设备向核心网设备发送第一消息，第一消息用于请求将第一终端设备中已建立的第一业务共享至第二终端设备；核心网设备根据第一消息将第一终端设备中已建立的第一业务共享至第二终端设备；并在第二终端设备成功建立第一业务后，向第一终端设备发送第六消息，第六消息用于通知第一终端设备释放第一业务；第一终端设备根据第六消息释放所述第一业务。本申请实施例能够自动实现同一用户的多个设备间共享同一业务，操作简单且用户体验高。

Description

业务处理方法、装置、系统、可读取存储介质和电子设备 技术领域
本申请涉及通信技术领域，尤其涉及一种业务处理方法、装置、系统、可读取存储介质和电子设备。
背景技术
随着智能终端设备的快速发展，用户往往拥有多个智能终端设备。例如，终端设备包括手机、平板或者智能手表等。
用户使用一个智能电子设备执行业务一，若想要另一个智能电子设备执行业务一，必须重新在另一个智能电子设备中进行一系列人工操作才能使得另一个智能电子设备执行业务一，操作步骤繁琐，用户体验低。例如，用户拥有手机和智能手表，用户正在通过手机听音乐，当用户想通过智能手表来听音乐时，用户需要人工关闭手机上的音乐，然后打开智能手表中音频类APP，在音频类APP中搜索音乐的名称，并在搜索列表中选择正在听的音乐播放。
因此，目前用户通过人工操作实现同一用户的多个设备间共享同一业务，操作步骤繁琐，且用户体验低。
发明内容
有鉴于此，本申请实施例提供了一种业务处理方法、装置、系统、可读取存储介质和电子设备，能够自动实现同一用户的多个设备间共享同一业务，操作简单且用户体验高。
第一方面，本申请实施例提供了一种业务处理方法，所述方法包括：
向核心网设备发送第一消息，以使所述核心网设备将已建立的第一业务共享至第二终端设备；
在所述第二终端设备成功建立所述第一业务后，释放所述第一业务；
其中，所述第一消息用于请求将已建立的所述第一业务共享至所述第二终端设备。
可选地，所述第一消息包括业务建立信息，所述业务建立信息包括以下信息中的至少一项：所述第一业务的业务标识、第二终端设备标识、所述第二终端设备所处的小区标识、所述第一业务的业务模式。
可选地，所述业务模式包括业务迁移或者业务共享。
可选地，所述向核心网设备发送第一消息之前，还包括：
与所述第二终端设备进行业务建立的确认。
可选地，所述与所述第二终端设备进行业务建立的确认，具体包括：
向所述第二终端设备发送第三消息，所述第三消息用于请求所述第二终端进行所述第一业务的建立；
接收来自所述第二终端设备的第四消息，所述第四消息用于指示所述第二终端设备接受所请求第一业务的建立。
可选地，所述第三消息包括以下信息中的至少一项：所述第一业务的业务标识、QoS参数、业务模式，以及第一终端设备标识、所述第一终端所处的小区标识。
可选地，所述第四消息包括：所述第二终端所处的小区标识，或者同小区指示信息；
所述同小区指示信息用于指示所述第二终端设备是否和所述第一终端设备所处同一小区或同一接入网设备。
可选地，在所述与所述第二终端设备进行业务建立的确认之前，还包括：
接收所述第二终端设备发送的设备发现信息。
可选地，所述设备发现信息包括以下信息中的至少一项：第二终端设备标识、所述第二终端能够建立的业务类型、所述第二终端的移动性特性。
可选地，还包括：
在所述第二终端设备成功建立所述第一业务后，释放所述第一业务。
可选地，所述在所述第二终端设备成功建立所述第一业务后，释放所述第一业务，具体包括：
接收来自所述核心网设备的第六消息，所述第六消息用于通知所述第一终端设备释放所述第一业务；
根据所述第六消息释放所述第一业务。
可选地，所述在所述第二终端设备成功建立所述第一业务后，释放所述第一业务，具体包括：
接收来自所述第二终端设备的第七消息，所述第七消息用于通知所述第一终端设备所述第一业务在所述第二终端设备建立成功；
根据所述第七消息向所述核心网设备发送第八消息，所述第八消息用于发起对所述第一业务的释放。
第二方面，本申请实施例提供了一种业务处理方法，所述方法包括：
接收第一终端设备发送的第一消息，所述第一消息用于请求将所述第一终端设备中已建立的所述第一业务共享至所述第二终端设备；
根据所述第一消息将所述第一终端设备中已建立的第一业务共享至第二终端设备。
可选地，所述第一消息包括业务建立信息，所述业务建立信息包括以下信息中的至少一项：所述第一业务的业务标识、第二终端设备标识、所述第二终端设备所处的小区标识、所述第一业务的业务模式。
可选地，所述第一终端设备和所述第二终端设备归属不同的接入网设备；
根据所述第一消息将所述第一终端设备中已建立的第一业务共享至第二终端设备，具体包括：
根据所述第一消息，判断所述第二终端设备是否在链接态；
若判断出所述第二终端设备在链接态，与所述第二终端设备建立所述第一业务；
若判断出所述第二终端设备不在链接态，向目标接入网设备发送第二消息，在第二终端设备进行RRC连接建立后，与所述第二终端设备建立所述第一业务；
其中，所述第二消息是寻呼消息，用于触发所述第二终端设备进行RRC连接建立。
可选地，所述向所述目标接入网设备发送第二消息之前，还包括：
根据所述第一消息中所述第二终端设备所处的小区标识确定所述第二终端设备所处的所述目标接入网设备。
可选地，所述第二消息可携带所述第二终端设备所驻留小区的小区标识。
可选地，所述第一终端设备和所述第二终端设备归属同一接入网设备；
根据所述第一消息将所述第一终端设备中已建立的第一业务共享至第二终端设备，具体包括：
为所述第一终端设备和所述第二终端设备的所述第一业务建立共享数据通道。
可选地，还包括：
在所述第二终端设备成功建立所述第一业务后，向所述第一终端设备发送第六消息，以使所述第一终端设备根据所述第六消息释放所述第一业务，所述第六消息用于通知所述第一终端设备释放所述第一业务。
可选地，向所述第一终端设备发送第六消息之前，还包括：
接收来自第一终端设备的第八消息，所述第八消息用于发起对所示第一业务的释放。
可选地，所述第一终端设备和所述第二终端设备所处同一接入网设备；
向所述第一终端设备发送第六消息之前，还包括：
接收来自所述接入网设备的第九消息，所述第九消息用于请求释放所述第一终端设备的所述第一业务；
其中，所述第九消息是所述接入网设备开始调度所述第二终端设备的所述第一业务后发送的。
第三方面，本申请实施例提供了一种业务处理装置，所述装置包括：
第一收发模块，用于向核心网设备发送第一消息，以使所述核心网设备将已建立的第一业务共享至第二终端设备；
其中，所述第一消息用于请求将已建立的所述第一业务共享至所述第二终端设备。
第四方面，本申请实施例提供了一种业务处理装置，所述装置包括：
第二收发模块，用于接收第一终端设备发送的第一消息，所述第一消息用于请求将所述第一终端设备中已建立的所述第一业务共享至所述第二终端设备；
业务处理模块，用于根据所述第一消息将所述第一终端设备中已建立的第一业务共享至第二终端设备。
第五方面，本申请实施例提供了一种业务处理系统，所述系统包括：第一终端设备、第二终端设备、核心网设备；
所述第一终端设备，用于向核心网设备发送第一消息，所述第一消息用于请求将已建立的所述第一业务共享至所述第二终端设备；
所述核心网设备，用于根据所述第一消息将所述第一终端设备中已建立的所述第一业务共享至所述第二终端设备；并在所述第二终端设备成功建立所述第一业务后， 向所述第一终端设备发送第六消息，所述第六消息用于通知所述第一终端设备释放所述第一业务；
所述第一终端设备，还用于根据所述第六消息释放所述第一业务。
第六方面，本申请实施例提供了一种可读取存储介质，所述可读取存储介质包括存储的程序，其中，在所述程序运行时控制所述可读取存储介质所在设备执行上述第一方面或者第二方面所述的业务处理方法。
第七方面，本申请实施例提供了一种电子设备，包括存储器和处理器，所述存储器用于存储包括程序指令的信息，所述处理器用于控制程序指令的执行，其特征在于，所述程序指令被处理器加载并执行时实现上述第一方面或者第二方面所述业务处理方法的步骤。
本申请实施例提供的业务处理方法、装置、系统、可读取存储介质和电子设备的技术方案中，第一终端设备向核心网设备发送第一消息，第一消息用于请求将第一终端设备中已建立的第一业务共享至第二终端设备；核心网设备根据第一消息将第一终端设备中已建立的第一业务共享至第二终端设备；并在第二终端设备成功建立第一业务后，向第一终端设备发送第六消息，第六消息用于通知第一终端设备释放第一业务；第一终端设备根据第六消息释放所述第一业务。本申请实施例能够自动实现同一用户的多个设备间共享同一业务，操作简单且用户体验高。
附图说明
图1为本申请一实施例提供的一种业务处理方法的流程图；
图2为本申请又一实施例提供的一种业务处理方法的流程图；
图3为图2中根据第二终端设备的设备发现信息，与第二终端设备进行业务建立的确认的具体流程图；
图4为第一终端设备和第二终端设备之间配置信息交互的示意图；
图5为本申请实施例提供的一种业务处理系统的系统架构图；
图6为图2中在第二终端设备成功建立第一业务后，释放第一业务的一种具体流程图；
图7为图2中在第二终端设备成功建立第一业务后，释放第一业务的另一种具体流程图；
图8为图2中在第二终端设备成功建立第一业务后，释放第一业务的又一种具体流程图；
图9为本申请又一实施例提供的一种业务处理方法的流程图；
图10为本申请又一实施例提供的一种业务处理方法的流程图；
图11为图10中根据第一消息将第一终端设备中已建立的第一业务共享至第二终端设备的具体流程图；
图12为本申请一实施例提供的一种业务处理装置的结构示意图；
图13为图12中确认模块的具体结构示意图；
图14为图12中释放模块的具体结构示意图；
图15为本申请又一实施例提供的一种业务处理装置的结构示意图；
图16为图15中业务处理模块的具体结构示意图；
图17为本申请一实施例提供的一种业务处理系统的结构示意图；
图18为本申请实施例提供的一种电子设备的示意图。
具体实施方式
为了更好的理解本申请的技术方案，下面结合附图对本申请实施例进行详细描述。
应当明确，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其它实施例，都属于本申请保护的范围。
在本申请实施例中使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本申请。在本申请实施例和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。
应当理解，本文中使用的术语“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，甲和/或乙，可以表示：单独存在甲，同时存在甲和乙，单独存在乙这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。本申请实施例中“至少一个”是指一个或者多个，“多个”是指两个或两个以上。
在本申请实施例中，“示例的”“在一些实施例中”“在另一实施例中”等用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
本申请实施例中“的(of)”，“相应的(corresponding，relevant)”和“对应的(corresponding)”有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是一致的。本申请实施例中通信、传输有时可以混用，应当指出的是，在不强调区别是，其所表达的含义是一致的。例如传输可以包括发送和/或接收，可以为名词，也可以是动词。本申请实施例中涉及的等于可以与大于连用，适用于大于时所采用的技术方案，也可以与小于连用，适用于与小于时所采用的技术方案，需要说明的是，当等于与大于连用时，不与小于连用；当等于与小于连用时，不与大于连用。
首先，对本申请实施例涉及的部分名词进行解释，以便于本领域技术人员理解。
1、终端设备。本申请实施例的终端设备是一种具有无线通信功能的设备，可以称为终端(terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)、接入终端设备、车载终端设备、工业控制终端设备、UE单元、UE站、移动站、远方站、远程终端设备、移动设备、UE终端设备、无线通信设备、UE代理或UE装置等。终端设备可以是固定的或者移动的。需要说明的是，终端设备可以支持至少一种无线通信技术，例如LTE、新空口(new radio，NR)等。例如，终端设备可以是手机(mobile phone)、平板电脑(pad)、台式机、笔记本电脑、一体机、车载终端、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线 终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、可穿戴设备、未来移动通信网络中的终端设备或者未来演进的公共移动陆地网络(public land mobile network，PLMN)中的终端设备等。在本申请的一些实施例中，终端设备还可以是具有收发功能的装置，例如芯片系统。其中，芯片系统可以包括芯片，还可以包括其它分立器件。
2、接入网设备。本申请实施例中接入网设备是一种为终端设备提供无线通信功能的设备，也可称之为无线接入网(radio access network，RAN)设备、或接入网网元等。其中，接入网设备可以支持至少一种无线通信技术，例如LTE、NR等。示例的，接入网设备包括但不限于：第五代移动通信系统(5th-generation，5G)中的下一代基站(generation nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved node B、或home node B，HNB)、基带单元(baseband unit，BBU)、收发点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。网络设备还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器、集中单元(centralized unit，CU)、和/或分布单元(distributed unit，DU)，或者接入网设备可以为中继站、接入点、车载设备、终端设备、可穿戴设备以及未来移动通信中的接入网设备或者未来演进的PLMN中的接入网设备等。在一些实施例中，接入网设备还可以为具有为终端设备提供无线通信功能的装置，例如芯片系统。示例的，芯片系统可以包括芯片，还可以包括其它分立器件。
在一些实施例中，接入网设备还可以与互联网协议(Internet Protocol，IP)网络进行通信，例如因特网(internet)，私有的IP网，或其他数据网等。
3、核心网。本申请实施例核心网是由核心网网元组成的。其中，核心网网元又可以称之为核心网设备，为核心网中部署的网元，例如核心网控制面网元或核心网用户面网元。本申请实施例的核心网可以是演进型分组核心网(Evolved Packet Core，EPC)、5G核心网(5G Core Network)，还可以是未来通信系统中的新型核心网。例如，5G核心网由一组网元组成，并实现移动性管理等功能的接入和移动性管理功能(Access and Mobility Management Function，AMF)、提供数据包路由转发和QoS(Quality of Service)管理等功能的用户面功能(User Plane Function,UPF)、提供会话管理、IP地址分配和管理等功能的会话管理功能(Session Management Function，SMF)等。EPC可由提供移动性管理、网关选择等功能的移动管理实体(Mobility Management Entity，MME)、提供数据包转发等功能的Serving Gateway(S-GW)、提供终端地址分配、速率控制等功能的PDN Gateway(P-GW)组成。对于多播广播业务(Multicast Broadcast Service，MBS)，核心网中可包含若干新的网元，来实现数据包的转发、MBS会议管理、QoS管理、传输模式切换(单播和组播/广播传输模式之间的切换)等功能。另一 种方式是所述功能可以由现有的核心网网元来实现。
4、上行通信。本申请实施例中上行通信又可以称之为上行传输，指的是终端设备到接入网设备的单向通信，其中，用于上行通信的通信链路为上行链路。在上行链路上传输的数据为上行数据。上行数据的传输方向为上行方向。
5、下行通信。本申请实施例中下行通信又可以称之为下行传输，指的是接入网设备到终端设备的单向通信，其中，用于下行通信的通信链路为上行链路。在下行链路上传输的数据为下行数据。下行数据的传输方向为下行方向。
图1为本申请一实施例提供的一种业务处理方法的流程图，应用于第一终端设备，如图1所示，该方法包括：
步骤101、向核心网设备发送第一消息，以使核心网设备将已建立的第一业务共享至第二终端设备。
其中，第一消息用于请求将已建立的第一业务共享至第二终端设备。
本申请实施例提供的一种业务处理方法的技术方案中，向核心网设备发送第一消息，以使核心网设备将已建立的第一业务共享至第二终端设备；其中，第一消息用于请求将已建立的第一业务共享至第二终端设备。本申请实施例能够自动实现同一用户的多个设备间共享同一业务，操作简单且用户体验高。
图2为本申请又一实施例提供的一种业务处理方法的流程图，应用于第一终端设备，如图2所示，该方法包括：
步骤201、接收第二终端设备发送的设备发现信息。
第一终端设备、第二终端设备等用户的终端设备可以发送本终端设备的设备发现信息，设备发现信息用于其它终端设备来发现本终端设备。终端设备可以周期性的发送设备发现信息。设备发现信息可以包含以下至少一项：终端设备的标识、终端设备能够建立的业务类型、终端设备的移动性特性等。其中，终端设备能够建立的业务类型是指终端设备支持建立的业务类型；移动性特性是指固定、高速移动、低速移动、中速移动等其中一项或多项。
进一步的，第一终端设备可接收来自多个终端设备的设备发现信息，从多个终端设备中选择一个终端设备发送请求业务建立的消息。
本申请实施例中，设备发现信息包括以下信息中的至少一项：第二终端设备标识、第二终端能够建立的业务类型、第二终端的移动性特性。
步骤202、与第二终端设备进行业务建立的确认。
本申请实施例中，如图3所示，步骤202具体包括：
步骤2021、向第二终端设备发送第三消息，第三消息用于请求第二终端进行第一业务的建立。
本申请实施例中，如图4所示，第一终端设备根据第二终端设备的设备发现信息，向第二终端设备发送第三消息请求第一业务的建立。
本申请实施例中，第三消息包括配置信息，配置信息包括以下信息中的至少一项：第一业务的业务标识、服务质量(Quality of Service，QoS)参数、业务模式，以及第一终端设备标识、第一终端所处的小区标识。
其中，QoS参数包括：业务类型、时延、丢包率、优先级、速率等其中的一项或 多项。其中可以采用一个索引标识来表示上述QoS参数中的一项或多项。
例如，业务类型包括：视频类业务或者语音类业务等。
例如，第一业务的业务标识为1，业务类型为视频类业务，则第三消息中包括业务标识1，第一业务的QoS参数包括业务类型为视频类业务。
步骤2022、接收来自第二终端设备的第四消息，第四消息用于确认第二终端设备接受所请求的第一业务的建立
本申请实施例中，如图4所示，若第二终端设备可接受第一终端设备请求的第一业务的建立，则向第一终端设备发送第四消息，第四消息用于指示第二终端设备可以接受第一业务的建立。
本申请实施例中，第四消息包括：第二终端所处的小区标识，或者同小区指示信息；所述同小区指示信息用于指示第二终端设备是否和第一终端设备所处同一小区或同一接入网设备。
如图4所示，若第二终端设备不可接受第一终端设备请求的第一业务的建立，第二终端设备向第一终端设备发送第五消息，第五消息用于指示第二终端设备不能发起第一业务。
需要说明的是，上述第三消息、第四消息和第五消息均是通过终端设备间的直接通信接口发送的。
本申请实施例中，通过第一终端设备和第二终端设备之间的信息交互，可以为业务共享实现终端设备的发现和选择，以及发起业务建立过程，从而触发核心网设备在第二终端设备进行业务建立。
步骤203、向核心网设备发送第一消息，以使核心网设备将已建立的第一业务共享至第二终端设备。
本申请实施例中，用户拥有第一终端设备和第二终端设备，当用户需要将第一终端设备中已建立的第一业务共享至第二终端设备时，第一终端设备向核心网设备发送第一消息。
其中，第一消息用于请求将已建立的第一业务共享至第二终端设备。第一消息可以是非介入层NAS消息或其他类型消息。
本申请实施例中，第一消息包括业务建立信息，业务建立信息包括以下信息中的至少一项：第一业务的业务标识、第二终端设备标识、第二终端设备所处的小区标识、所述第一业务的业务模式。
其中，业务标识用于标识请求建立的业务，业务标识包括但不限于QoS流标识(QoS Flow ID,QFI)，会话标识(session id)，临时用户组标识(Temporary Mobile Group Identity，TMGI)，，互联网协议(Internet Protocol，IP)地址中的一项或多项。
其中，第二终端设备标识用于指示第二终端设备的设备标识，是指同一用户的多个终端设备的设备标识，所述设备标识可以由核心网设备分配。例如，核心网设备为同一用户的5个终端设备分配设备标识a,b,c,d,e，若第二终端设备的设备标识为a，则核心网设备接收到设备标识a，则可识别出第二终端设备。所述设备标识也可以是用户设置的。
其中，第二终端设备所处的小区标识，是指第二终端设备所驻留小区的小区标识， 可以是全球小区标识(Cell Global Identifier，CGI)。
其中，业务模式包括业务迁移或者业务共享。业务迁移，是指将业务从一个终端设备迁移到另一个终端设备；业务共享，是指同一业务在多个终端设备中进行。
本申请实施例中，核心网设备接收到第一消息后，根据第一消息中的内容，决定为第二终端设备建立所请求的第一业务。
具体的，核心网设备首先需要判断第二终端设备是否在链接态。如图5所示，若第二终端设备在链接态，则核心网设备和第二终端设备建立第一业务。若第二终端设备不在链接态，则核心网设备发送第二消息到目标接入网设备，其中，第二消息为寻呼消息(paging)；核心网设备可以根据第一消息中的第二终端设备所在小区的小区标识得到目标接入网设备的标识，从而确定发送寻呼消息到目标接入网设备，可以减少寻呼消息的发送数量，减少网元间的消息发送的负荷。
进一步的，寻呼消息中可携带第二终端设备所驻留小区的小区标识。接收到所述寻呼消息的目标接入网设备，可只在所述小区中发送寻呼消息，从而减少了空口寻呼消息的发送负荷。
第二终端设备接收到寻呼消息后，进行无线资源控制协议(Radio Resource Control，RRC)连接建立，然后由核心网设备在第二终端设备建立第一业务。
进一步的，若第一终端设备和第二终端设备归属同一接入网设备，核心网设备和接入网设备间的用户面数据通道，例如GPRS用户面隧道协议(GPRS Tunnelling Protocol for the user plane，GTPU)隧道，可以在多个终端设备间复用，即同一数据通道可用于第一终端设备和第二终端设备的上行或下行的数据传输。具体的，核心网设备可指示接入网设备第一终端设备的第一业务的数据通道可用于传输第二终端设备的第一业务的数据。
若第一终端设备和第二终端设备归属不同的接入网设备，核心网设备为第二终端设备的第一业务建立和接入网设备间的单独的用户面数据通道。
本申请实施例中，通过终端设备主动请求，网络侧可为用户在多个终端设备间建立同一业务，从而可以实现业务迁移或业务共享。
步骤204、在第二终端设备成功建立第一业务后，释放第一业务。
需要说明的是，若第一业务的业务模式是业务迁移，则在步骤203之后，执行步骤204；若第一业务的业务模式是业务共享，则在步骤203之后，无需执行步骤204。
作为一种可选方案，如图6所示，步骤204，具体包括：
步骤2041、接收来自核心网设备的第六消息，第六消息用于通知第一终端设备释放第一业务。
本申请实施例中，若第一业务的业务模式是业务迁移，在第二终端设备中的第一业务建立成功后，由核心网设备决定对第一终端设备中的第一业务进行释放。核心网设备发起对第一终端设备中的第一业务的释放流程。具体的，核心网设备向第一终端设备发送第六消息，第六消息用于通知第一终端设备释放第一业务。
其中，第六消息包括但不限于PDU会话释放命令(PDU session release command)消息和PDU会话修改命令(PDU session modification request)消息，其中，第六消息携带第一业务的标识。
步骤2042、根据第六消息释放第一业务。
作为另一种可选方案，如图7所示，步骤204，具体包括：
步骤2041、接收来自第二终端设备的第七消息，第七消息用于通知第一业务在第二终端设备建立成功。
本申请实施例中，在第二终端设备成功建立第一业务后，通过终端设备间的直接接口接收来自第二终端设备发送的第七消息。
步骤2042、向核心网设备发送第八消息，第八消息用于发起对第一业务的释放。
本申请实施例中，若第一业务的业务模式是业务迁移，第一终端设备接收第七消息，向核心网设备发送第八消息，第八消息用于发起对第一业务的释放。第八消息包括但不限于PDU session modification request消息、PDU session release request消息，其中，第八消息携带第一业务的标识。
作为又一种可选方案，第一终端设备和第二终端设备所处同一接入网设备；如图8所示，步骤204，具体包括：
步骤2041、在接入网设备向核心网设备发送第九消息后，接收来自核心网设备的第六消息，第九消息用于请求释放第一业务，第九消息中携带第一业务的标识。
具体的，接入网设备开始调度第二终端设备的第一业务后，向核心网设备发送第九消息，接收核心网设备根据第九消息发送的第六消息。
本申请实施例中，若第一业务的业务模式是业务迁移，则接入网设备在开始调度第二终端设备的第一业务后，决定进行第一终端设备的第一业务的释放。具体的，接入网设备发送第九消息到核心网设备，请求释放第一终端设备的第一业务，接收到第九消息的核心网设备发起对第一终端设备的第一业务的释放流程。具体的，核心网设备向第一终端设备发送第六消息。其中，第九消息用于请求释放第一终端设备的第一业务；第六消息用于通知第一终端设备释放第一业务。
步骤2042、根据第六消息释放第一业务。
本申请提供的业务处理方法的技术方案可适用于5G(5 Generation)通信系统，还可适用于4G通信系统，还可适用于未来新的各种通信系统，例如6G、7G等。
本申请提供的业务处理方法的技术方案也适用于不同的网络架构，包括但不限于陆地通信网络架构、非陆地通信网络架构、中继网络架构、双链接架构、车辆到任何物体的通信(Vehicle-to-Everything)架构等架构。
本申请实施例提供的一种业务处理方法的技术方案中，接收第二终端设备发送的设备发现信息，根据第二终端设备的设备发现信息，与第二终端设备进行业务建立的确认；向核心网设备发送第一消息，以使核心网设备将已建立的第一业务共享至第二终端设备；在第二终端设备成功建立第一业务后，释放第一业务；其中，第一消息用于请求将已建立的第一业务共享至第二终端设备。本申请实施例能够自动实现同一用户的多个设备间共享同一业务，操作简单且用户体验高。
图9为本申请又一实施例提供的一种业务处理方法的流程图，应用于核心网设备，如图9所示，该方法包括：
步骤301、接收第一终端设备发送的第一消息，第一消息用于请求将第一终端设备中已建立的第一业务共享至第二终端设备。
步骤302、根据第一消息将第一终端设备中已建立的第一业务共享至第二终端设备。
本申请实施例提供的一种业务处理方法的技术方案中，接收第一终端设备发送的第一消息，第一消息用于请求将第一终端设备中已建立的第一业务共享至第二终端设备；根据第一消息将第一终端设备中已建立的第一业务共享至第二终端设备。本申请实施例能够自动实现同一用户的多个设备间共享同一业务，操作简单且用户体验高。
图10为本申请又一实施例提供的一种业务处理方法的流程图，应用于核心网设备，如图10所示，该方法包括：
步骤401、接收第一终端设备发送的第一消息，所述第一消息用于请求将所述第一终端设备中已建立的所述第一业务共享至所述第二终端设备。
本申请实施例中，用户拥有第一终端设备和第二终端设备，当用户需要将第一终端设备中已建立的第一业务共享至第二终端设备时，第一终端设备向核心网设备发送第一消息。
其中，第一消息用于请求将已建立的第一业务共享至第二终端设备。第一消息可以是非介入层NAS消息或其他类型消息。
本申请实施例中，第一消息包括业务建立信息，所述业务建立信息包括以下信息中的至少一项：所述第一业务的业务标识、第二终端设备标识、所述第二终端设备所处的小区标识、所述第一业务的业务模式。
其中，业务标识用于标识请求建立的业务，业务标识包括但不限于QoS flow id，session id，TMGI，IP地址中的一项或多项。
其中，第二终端设备标识用于指示第二终端设备的设备标识，是指同一用户的多个终端设备的设备标识，所述设备标识可以由核心网设备分配。例如，核心网设备为同一用户的5个终端设备分配设备标识a,b,c,d,e，若第二终端设备的设备标识为a，则核心网设备接收到设备标识a，则可识别出第二终端设备。所述设备标识也可以是用户设置的。
其中，第二终端设备所处的小区标识，是指第二终端设备所驻留小区的小区标识，可以是全球小区标识。
其中，业务模式，是指业务迁移还是业务共享。业务迁移，是指将业务从一个终端设备迁移到另一个终端设备；业务共享，是指同一业务在多个终端设备中进行。
步骤402、根据所述第一消息将所述第一终端设备中已建立的第一业务共享至第二终端设备。
本申请实施例中，核心网设备接收到第一消息后，根据第一消息中的内容，决定为第二终端设备建立所请求的第一业务。
作为一种可选方案，如图11所示，步骤402，具体包括：
步骤4021、根据第一消息，判断第二终端设备是否在链接态；若是，执行步骤4022；若否，执行步骤4023。
具体的，核心网设备首先需要判断第二终端设备是否在链接态。
步骤4022、与第二终端设备建立第一业务；并继续执行步骤403。
若第二终端设备在链接态，则核心网设备和第二终端设备建立第一业务。
步骤4023、根据第一消息中第二终端设备所处的小区标识确定第二终端设备所处的目标接入网设备。
若第二终端设备不在链接态，则核心网设备根据第一消息中的第二终端设备所在小区的小区标识得到目标接入网设备的标识，从而确定第二终端设备所处的目标接入网设备。
步骤4024、向目标接入网设备发送第二消息，以使目标接入网设备根据第二消息向第二终端设备发送第二消息，第二消息为寻呼消息，用于触发第二终端设备进行RRC连接建立。
核心网设备发送第二消息到目标接入网设备，其中，第二消息为寻呼消息，用于触发所述第二终端设备进行RRC连接建立；发送寻呼消息到目标接入网设备，可以减少寻呼消息的发送数量，减少网元间的消息发送的负荷。
进一步的，寻呼消息中可携带第二终端设备所驻留小区的小区标识。接收到所述寻呼消息的目标接入网设备，可只在所述小区中发送寻呼消息，从而减少了空口寻呼消息的发送负荷。
步骤4025、在第二终端设备根据寻呼消息进行RRC连接建立后，与第二终端设备建立第一业务。
第二终端设备接收到寻呼消息后，进行RRC连接建立，然后由核心网设备在第二终端设备建立第一业务。
作为另一种可选方案，第一终端设备和第二终端设备归属同一接入网设备；步骤402，具体包括：为第一终端设备和第二终端设备的第一业务建立共享数据通道。
若第一终端设备和第二终端设备归属同一接入网设备，核心网设备和接入网设备间的用户面数据通道，例如GTPU隧道，可以在多个终端设备间复用，即同一数据通道可用于第一终端设备和第二终端设备的上行或下行的数据传输。具体的，核心网设备可指示接入网设备第一终端设备的第一业务的数据通道可用于传输第二终端设备的第一业务的数据。
步骤403、在第二终端设备成功建立第一业务后，向第一终端设备发送第六消息，以使第一终端设备根据第六消息释放第一业务，第六消息用于通知第一终端设备释放第一业务。
需要说明的是，若第一业务的业务模式是业务迁移，则在步骤402之后，执行步骤403；若第一业务的业务模式是业务共享，则在步骤402之后，无需执行步骤403。
作为一种可选方案，向第一终端设备发送第六消息之前，还包括：
步骤402’、接收来自第一终端设备的第八消息，所述第八消息用于发起对所示第一业务的释放。
作为另一种可选方案，，第一终端设备和第二终端设备所处同一接入网设备；向第一终端设备发送第六消息之前，还包括：
步骤402’、接收来自接入网设备的第九消息，第九消息用于请求释放第一终端设备的第一业务。
其中，所述第九消息是所述接入网设备开始调度所述第二终端设备的所述第一业务后发送的。
本申请实施例中，若第一业务的业务模式是业务迁移，则接入网设备在开始调度第二终端设备的第一业务后，决定进行第一终端设备的第一业务的释放。具体的，接入网设备发送第九消息到核心网设备，请求释放第一终端设备的第一业务，接收到第九消息的核心网设备发起对第一终端设备的第一业务的释放流程。具体的，核心网设备向第一终端设备发送第六消息。其中，第九消息用于请求释放第一终端设备的第一业务；第六消息用于通知第一终端设备释放第一业务。
本申请提供的业务处理方法的技术方案可适用于5G通信系统，还可适用于4G通信系统，还可适用于未来新的各种通信系统，例如6G、7G等。
本申请提供的业务处理方法的技术方案也适用于不同的网络架构，包括但不限于陆地通信网络架构、非陆地通信网络架构、中继网络架构、双链接架构、车辆到任何物体的通信架构等架构。
本申请实施例提供的一种业务处理方法的技术方案中，接收第一终端设备发送的第一消息，第一消息用于请求将第一终端设备中已建立的第一业务共享至第二终端设备；根据第一消息将第一终端设备中已建立的第一业务共享至第二终端设备；在第二终端设备成功建立第一业务后，向第一终端设备发送第六消息，以使第一终端设备根据第六消息释放第一业务，第六消息用于通知第一终端设备释放第一业务。本申请实施例能够自动实现同一用户的多个设备间共享同一业务，操作简单且用户体验高。
图12为本申请一实施例提供的一种业务处理装置的结构示意图，如图12所示，所述装置包括：第一收发模块51、确认模块52和释放模块53。
第一收发模块51，用于接收第二终端设备发送的设备发现信息。
本申请实施例中，设备发现信息包括以下信息中的至少一项：第二终端设备标识、第二终端能够建立的业务类型、第二终端的移动性特性。
确认模块52，用于与第二终端设备进行业务建立的确认。
本申请实施例中，如图13所示，确认模块52具体包括：建立请求子模块521和确认子模块522。
建立请求子模块521，用于向第二终端设备发送第三消息，第三消息用于请求第二终端进行第一业务的建立。
本申请实施例中，第三消息包括以下信息中的至少一项：第一业务的业务标识、QoS参数、业务模式，以及第一终端设备标识、第一终端所处的小区标识。
确认子模块522，用于接收来自第二终端设备的第四消息，第四消息用于确认第二终端设备接受所请求的第一业务的建立。
本申请实施例中，第四消息包括：第二终端所处的小区标识，或者同小区指示信息；同小区指示信息用于指示第二终端设备是否和第一终端设备所处同一小区或同一接入网设备。
第一收发模块51，还用于向核心网设备发送第一消息，以使核心网设备将已建立的第一业务共享至第二终端设备。
其中，第一消息用于请求将已建立的第一业务共享至第二终端设备。
本申请实施例中，第一消息包括业务建立信息，业务建立信息包括以下信息中的至少一项：第一业务的业务标识、第二终端设备标识、第二终端设备所处的小区标识、 所述第一业务的业务模式。其中，业务模式包括业务迁移或者业务共享。
释放模块53，用于在第二终端设备成功建立第一业务后，释放第一业务。
本申请实施例中，如图14所示，释放模块53具体包括：通知子模块531和释放子模块532。
作为一种可选方案，通知子模块531，用于接收来自核心网设备的第六消息，第六消息用于通知第一终端设备释放第一业务；释放子模块532，用于根据第六消息释放第一业务。
作为另一种可选方案，通知子模块531，用于接收第二终端设备发送的第七消息，第七消息用于通知第一终端设备第一业务在第二终端设备建立成功；释放子模块532，用于向核心网设备发送第八消息，第八消息用于发起对第一业务的释放。
作为又一种可选方案，第一终端设备和第二终端设备所处同一接入网设备；通知子模块531，用于在接入网设备向核心网设备发送第九消息后，接收核心网设备根据第九消息发送的第六消息；释放子模块532，用于根据第六消息释放第一业务。
其中，第九消息用于请求释放第一终端设备的第一业务；第六消息用于通知第一终端设备释放第一业务。
本申请实施例提供的业务处理装置可用于实现上述图1至图8中的业务处理方法，具体描述可参见上述业务处理方法的实施例，此处不再重复描述。
所述业务处理装置，例如可以是：芯片、芯片模组或者芯片模组的一部分。
本申请实施例提供的一种业务处理装置的技术方案中，接收第二终端设备发送的设备发现信息，根据第二终端设备的设备发现信息，与第二终端设备进行业务建立的确认；向核心网设备发送第一消息，以使核心网设备将已建立的第一业务共享至第二终端设备；在第二终端设备成功建立第一业务后，释放第一业务；其中，第一消息用于请求将已建立的第一业务共享至第二终端设备。本申请实施例能够自动实现同一用户的多个设备间共享同一业务，操作简单且用户体验高。
图15为本申请一实施例提供的一种业务处理装置的结构示意图，如图15所示，所述装置包括：第二收发模块61、业务处理模块62。
第二收发模块61，用于接收第一终端设备发送的第一消息，第一消息用于请求将第一终端设备中已建立的第一业务共享至第二终端设备。
本申请实施例中，第一消息包括业务建立信息，所述业务建立信息包括以下信息中的至少一项：所述第一业务的业务标识、第二终端设备标识、所述第二终端设备所处的小区标识、所述第一业务的业务模式。
业务处理模块62，用于根据第一消息将第一终端设备中已建立的第一业务共享至第二终端设备。
作为一种可选方案，如图16所示，业务处理模块62，具体包括：判断子模块621、第一建立子模块622、确定子模块623和第二建立子模块624。
判断子模块621，用于根据第一消息，判断第二终端设备是否在链接态。
第一建立子模块622，用于若判断子模块621判断出第二终端设备在链接态，与第二终端设备建立第一业务；并继续执行在第二终端设备成功建立第一业务后，向第一终端设备发送第六消息的操作。
确定子模块623，用于若判断子模块621判断出第二终端设备不在链接态，根据第一消息中第二终端设备所处的小区标识确定第二终端设备所处的目标接入网设备。
第二收发模块61，还用于向目标接入网设备发送第二消息，以使目标接入网设备根据第二消息向第二终端设备发送第二消息，第二消息为寻呼消息，用于触发所述第二终端设备进行RRC连接建立。
第二建立子模块624，用于在所述第二终端设备根据所述寻呼消息进行RRC连接建立后，与所述第二终端设备建立所述第一业务。
作为另一种可选方案，第一终端设备和第二终端设备归属同一接入网设备；业务处理模块62具体用于：为第一终端设备和第二终端设备的第一业务建立共享数据通道。
第二收发模块61，还用于在第二终端设备成功建立第一业务后，向第一终端设备发送第六消息，以使第一终端设备根据第六消息释放第一业务；第六消息用于通知第一终端设备释放第一业务。
作为一种可选方案，向第一终端设备发送第六消息之前，第二收发模块61，还用于接收来自第一终端设备的第八消息，所述第八消息用于发起对所示第一业务的释放。
作为另一种可选方案，第一终端设备和第二终端设备所处同一接入网设备；向第一终端设备发送第六消息之前，第二收发模块61，还用于接收来自接入网设备发送的第九消息，第九消息用于请求释放第一终端设备的第一业务。其中，第九消息是所述接入网设备开始调度所述第二终端设备的所述第一业务后发送的。
本申请实施例提供的业务处理装置可用于实现上述图9至图11中的业务处理方法，具体描述可参见上述业务处理方法的实施例，此处不再重复描述。
所述业务处理装置，例如可以是：芯片、芯片模组或者芯片模组的一部分。
本申请实施例提供的一种业务处理装置的技术方案中，接收第一终端设备发送的第一消息，第一消息用于请求将第一终端设备中已建立的第一业务共享至第二终端设备；根据第一消息将第一终端设备中已建立的第一业务共享至第二终端设备；在第二终端设备成功建立第一业务后，向第一终端设备发送第六消息，以使第一终端设备根据第六消息释放第一业务，第六消息用于通知第一终端设备释放第一业务。本申请实施例能够自动实现同一用户的多个设备间共享同一业务，操作简单且用户体验高。
关于上述如图12至图16实施例中描述的各个装置、产品包含模块/单元，其可以是软件模块/单元，也可以是硬件模块/单元，或者也可以部分是软件模块/单元，部分是硬件模块/单元。例如，对于应用或集成芯片的各个装置、产品其包含的各个模块/单元可以都采用电路等硬件的方式实现，或者至少部分模块/单元可以采用软件程序的方式实现，该运行于芯片内部集成处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现；对于应于或集成芯片模组的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，不同模块/单元可以位于芯片模组的同一件(例如芯片、电路模块等)或者不同组件中，至少部分/单元可以采用软件程序的方式实现，该软件程运行于芯片模组内部集成处理器剩余(如果有)部分模块/单元可以采用电路等硬件方式实现；对于应或集成终端的各个装置、产品，其包含的模块/单元可以都采用电路等硬件的方式实现，不同的模块/单元可以位于终端内同一组件(例如，芯片、电路模块等)或者不同组件中，或者至少部分模块/单元可以采用软件程序的方 式实现，该程序运行于终端内部集成的处理器，剩余(如果有)分模块/单元可以采用电路等硬件方式实现。
图17为本申请一实施例提供的一种业务处理系统的结构示意图，如图17所示，所述系统包括：第一终端设备71、第二终端设备72、核心网设备73。
第一终端设备71，用于向核心网设备73发送第一消息，第一消息用于请求将已建立的第一业务共享至第二终端设备72。
核心网设备73，用于根据第一消息将第一终端设备71中已建立的第一业务共享至第二终端设备72；并在第二终端设备72成功建立第一业务后，向第一终端设备71发送第六消息，第六消息用于通知第一终端设备71释放第一业务；
第一终端设备72，还用于根据第六消息释放第一业务。
本申请实施例中，所述系统还包括：目标接入网设备74。该目标接入网设备74为第二终端设备72所处的接入网设备。
目标接入网设备74，用于当第二终端设备不在链接态时，接收核心云设备73发送的第二消息，根据第二消息向第二终端设备72发送第二消息，第二消息为寻呼消息。
本申请实施例中，第一终端设备71和所述第二终端设备72所处同一接入网设备；在核心云设备73向第一终端设备71发送第六消息之前，
目标接入网设备74，还用于调度第二终端设备72的第一业务，并向核心云设备73发送第九消息，第九消息用于请求释放第一终端设备71的第一业务。
本申请实施例提供的业务处理系统可用于实现上述图1至图11中的业务处理方法，具体描述可参见上述业务处理方法的实施例，此处不再重复描述。
本申请实施例提供的一种业务处理系统的技术方案中，第一终端设备向核心网设备发送第一消息，第一消息用于请求将第一终端设备中已建立的第一业务共享至第二终端设备；核心网设备根据第一消息将第一终端设备中已建立的第一业务共享至第二终端设备；并在第二终端设备成功建立第一业务后，向第一终端设备发送第六消息，第六消息用于通知第一终端设备释放第一业务；第一终端设备根据第六消息释放所述第一业务。本申请实施例能够自动实现同一用户的多个设备间共享同一业务，操作简单且用户体验高。
图18为本说明书电子设备一个实施例的结构示意图，如图18所示，上述电子设备可以包括至少一个处理器；以及与上述处理器通信连接的至少一个存储器，其中：存储器存储有可被处理器执行的程序指令，上述处理器调用上述程序指令能够执行本说明书图1～图8或者图9～图11所示实施例提供的业务处理方法。
图18示出了适于用来实现本说明书实施方式的示例性电子设备的框图。图1显示的电子设备仅仅是一个示例，不应对本说明书实施例的功能和使用范围带来任何限制。
如图18所示，电子设备以通用计算设备的形式表现。电子设备的组件可以包括但不限于：一个或者多个处理器21，存储器23，连接不同系统组件(包括存储器23和处理单元21)的通信总线24。
通信总线24表示几类总线结构中的一种或多种，包括存储器总线或者存储器控制器，外围总线，图形加速端口，处理器或者使用多种总线结构中的任意总线结构的局域总线。举例来说，这些体系结构包括但不限于工业标准体系结构(Industry Standard  Architecture；以下简称：ISA)总线，微通道体系结构(Micro Channel Architecture；以下简称：MAC)总线，增强型ISA总线、视频电子标准协会(Video Electronics Standards Association；以下简称：VESA)局域总线以及外围组件互连(Peripheral Component Interconnection；以下简称：PCI)总线。
电子设备典型地包括多种计算机系统可读介质。这些介质可以是任何能够被电子设备访问的可用介质，包括易失性和非易失性介质，可移动的和不可移动的介质。
存储器23可以包括易失性存储器形式的计算机系统可读介质，例如随机存取存储器(Random Access Memory；以下简称：RAM)和/或高速缓存存储器。电子设备可以进一步包括其它可移动/不可移动的、易失性/非易失性计算机系统存储介质。存储器23可以包括至少一个程序产品，该程序产品具有一组(例如至少一个)程序模块，这些程序模块被配置以执行本说明书各实施例的功能。
具有一组(至少一个)程序模块的程序/实用工具，可以存储在存储器23中，这样的程序模块包括——但不限于——操作系统、一个或者多个应用程序、其它程序模块以及程序数据，这些示例中的每一个或某种组合中可能包括网络环境的实现。程序模块通常执行本说明书所描述的实施例中的功能和/或方法。
处理器21通过运行存储在存储器23中的程序，从而执行各种功能应用以及数据处理，例如实现本说明书图1～图8或者图9～图11所示实施例提供的业务处理方法。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本申请并不受所描述的动作顺序的限制，因为依据本申请，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本申请所必须的。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件单元组合执行完成。软件单元可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器执行存储器中的指令，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
在本申请实施例中，上述装置的处理器可以是中央处理单元(Central Processing Unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
本申请实施例还提供一种计算机存储介质，其中，该计算机存储介质存储用于电子数据交换的计算机程序，该计算机程序使得计算机执行如上述方法实施例中记载的任一方法的部分或全部步骤。
本申请实施例还提供一种计算机程序产品，上述计算机程序产品包括存储了计算 机程序的非瞬时性计算机可读存储介质，上述计算机程序可操作来使计算机执行如上述方法实施例中记载的任一方法的部分或全部步骤。该计算机程序产品可以为一个软件安装包。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置，可通过其它的方式实现。例如，以上所描述的装置实施例仅是示意性的，例如上述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性或其它的形式。
上述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
上述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储器中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储器中，包括若干指令用以使得一台计算机设备(可为个人计算机、服务器或者TRP等)执行本申请各个实施例方法的全部或部分步骤。而前述的存储器包括：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
以上对本申请实施例进行了详细介绍，本文中应用了具体个例对本申请的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本申请的方法及其核心思想；同时，对于本领域的一般技术人员，依据本申请的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本申请的限制。

Claims (26)

  1. 一种业务处理方法，其特征在于，所述方法包括：
    向核心网设备发送第一消息，以使所述核心网设备将已建立的第一业务共享至第二终端设备；
    其中，所述第一消息用于请求将已建立的所述第一业务共享至所述第二终端设备。
  2. 根据权利要求1所述的业务处理方法，其特征在于，所述第一消息包括业务建立信息，所述业务建立信息包括以下信息中的至少一项：所述第一业务的业务标识、第二终端设备标识、所述第二终端设备所处的小区标识、所述第一业务的业务模式。
  3. 根据权利要求2所述的业务处理方法，其特征在于，所述业务模式包括业务迁移或者业务共享。
  4. 根据权利要求1所述的业务处理方法，其特征在于，所述向核心网设备发送第一消息之前，还包括：
    与所述第二终端设备进行所述第一业务建立的确认。
  5. 根据权利要求4所述的业务处理方法，其特征在于，所述与所述第二终端设备进行业务建立的确认，具体包括：
    向所述第二终端设备发送第三消息，所述第三消息用于请求所述第二终端进行所述第一业务的建立；
    接收来自所述第二终端设备的第四消息，所述第四消息用于指示所述第二终端设备接受所请求第一业务的建立。
  6. 根据权利要求5所述的业务处理方法，其特征在于，所述第三消息包括以下信息中的至少一项：所述第一业务的业务标识、QoS参数、业务模式，以及第一终端设备标识、所述第一终端所处的小区标识。
  7. 根据权利要求5所述的业务处理方法，其特征在于，所述第四消息包括：所述第二终端所处的小区标识，或者同小区指示信息；
    所述同小区指示信息用于指示所述第二终端设备是否和所述第一终端设备所处同一小区或同一接入网设备。
  8. 根据权利要求4所述的业务处理方法，其特征在于，在所述与所述第二终端设备进行业务建立的确认之前，还包括：
    接收所述第二终端设备发送的设备发现信息。
  9. 根据权利要求8所述的业务处理方法，其特征在于，所述设备发现信息包括以下信息中的至少一项：第二终端设备标识、所述第二终端能够建立的业务类型、所述第二终端的移动性特性。
  10. 根据权利要求1所述的业务处理方法，其特征在于，还包括：
    在所述第二终端设备成功建立所述第一业务后，释放所述第一业务。
  11. 根据权利要求10所述的业务处理方法，其特征在于，所述在所述第二终端设备成功建立所述第一业务后，释放所述第一业务，具体包括：
    接收来自所述核心网设备的第六消息，所述第六消息用于通知所述第一终端设备释放所述第一业务；
    根据所述第六消息释放所述第一业务。
  12. 根据权利要求10所述的业务处理方法，其特征在于，所述在所述第二终端设备成功建立所述第一业务后，释放所述第一业务，具体包括：
    接收来自所述第二终端设备的第七消息，所述第七消息用于通知所述第一终端设备所述第一业务在所述第二终端设备建立成功；
    向所述核心网设备发送第八消息，所述第八消息用于发起对所述第一业务的释放。
  13. 一种业务处理方法，其特征在于，所述方法包括：
    接收第一终端设备发送的第一消息，所述第一消息用于请求将所述第一终端设备中已建立的所述第一业务共享至所述第二终端设备；
    根据所述第一消息将所述第一终端设备中已建立的第一业务共享至第二终端设备。
  14. 根据权利要求13所述的业务处理方法，其特征在于，所述第一消息包括业务建立信息，所述业务建立信息包括以下信息中的至少一项：所述第一业务的业务标识、第二终端设备标识、所述第二终端设备所处的小区标识、所述第一业务的业务模式。
  15. 根据权利要求13所述的业务处理方法，其特征在于，根据所述第一消息将所述第一终端设备中已建立的第一业务共享至第二终端设备，具体包括：
    根据所述第一消息，判断所述第二终端设备是否在链接态；
    若判断出所述第二终端设备在链接态，与所述第二终端设备建立所述第一业务；
    若判断出所述第二终端设备不在链接态，向目标接入网设备发送第二消息，在第二终端设备进行RRC连接建立后，与所述第二终端设备建立所述第一业务；
    其中，所述第二消息是寻呼消息，用于触发所述第二终端设备进行RRC连接建立。
  16. 根据权利要求15所述的业务处理方法，其特征在于，所述向所述目标接入网设备发送第二消息之前，还包括：
    根据所述第一消息中所述第二终端设备所处的小区标识确定所述第二终端设备所处的所述目标接入网设备。
  17. 根据权利要求15所述的业务处理方法，其特征在于，所述第二消息携带所述第二终端设备所驻留小区的小区标识。
  18. 根据权利要求15所述的业务处理方法，其特征在于，所述第一终端设备和所述第二终端设备归属同一接入网设备；
    根据所述第一消息将所述第一终端设备中已建立的第一业务共享至第二终端设备，具体包括：
    为所述第一终端设备和所述第二终端设备的所述第一业务建立共享数据通道。
  19. 根据权利要求13所述的业务处理方法，其特征在于，还包括：
    在所述第二终端设备成功建立所述第一业务后，向所述第一终端设备发送第六消息，以使所述第一终端设备根据所述第六消息释放所述第一业务，所述第六消息用于通知所述第一终端设备释放所述第一业务。
  20. 根据权利要求19所述的业务处理方法，其特征在于，
    向所述第一终端设备发送第六消息之前，还包括：
    接收来自第一终端设备的第八消息，所述第八消息用于发起对所述第一业务的释放。
  21. 根据权利要求19所述的业务处理方法，其特征在于，所述第一终端设备和所 述第二终端设备所处同一接入网设备；
    向所述第一终端设备发送第六消息之前，还包括：
    接收来自所述接入网设备的第九消息，所述第九消息用于请求释放所述第一终端设备的所述第一业务。
    其中，所述第九消息是所述接入网设备开始为所述第二终端设备调度所述第一业务后发送的。
  22. 一种业务处理装置，其特征在于，所述装置包括：
    第一收发模块，用于向核心网设备发送第一消息，以使所述核心网设备将已建立的第一业务共享至第二终端设备；
    其中，所述第一消息用于请求将已建立的所述第一业务共享至所述第二终端设备。
  23. 一种业务处理装置，其特征在于，所述装置包括：
    第二收发模块，用于接收第一终端设备发送的第一消息，所述第一消息用于请求将所述第一终端设备中已建立的所述第一业务共享至所述第二终端设备；
    业务处理模块，用于根据所述第一消息将所述第一终端设备中已建立的第一业务共享至第二终端设备。
  24. 一种业务处理系统，其特征在于，所述系统包括：第一终端设备、第二终端设备、核心网设备；
    所述第一终端设备，用于向核心网设备发送第一消息，所述第一消息用于请求将已建立的所述第一业务共享至所述第二终端设备；
    所述核心网设备，用于根据所述第一消息将所述第一终端设备中已建立的所述第一业务共享至所述第二终端设备；并在所述第二终端设备成功建立所述第一业务后，向所述第一终端设备发送第六消息，所述第六消息用于通知所述第一终端设备释放所述第一业务；
    所述第一终端设备，还用于根据所述第六消息释放所述第一业务。
  25. 一种可读取存储介质，其特征在于，所述可读取存储介质包括存储的程序，其中，在所述程序运行时控制所述可读取存储介质所在设备执行权利要求1-12任一项或13-21任一项所述的业务处理方法。
  26. 一种电子设备，包括存储器和处理器，所述存储器用于存储包括程序指令的信息，所述处理器用于控制程序指令的执行，其特征在于，所述程序指令被处理器加载并执行时实现权利要求1-12任一项或13-21任一项所述的业务处理方法的步骤。
PCT/CN2022/084831 2021-04-22 2022-04-01 业务处理方法、装置、系统、可读取存储介质和电子设备 Ceased WO2022222736A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110436766.4 2021-04-22
CN202110436766.4A CN115243401B (zh) 2021-04-22 2021-04-22 业务处理方法、装置、系统、可读取存储介质和电子设备

Publications (1)

Publication Number Publication Date
WO2022222736A1 true WO2022222736A1 (zh) 2022-10-27

Family

ID=83666247

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/084831 Ceased WO2022222736A1 (zh) 2021-04-22 2022-04-01 业务处理方法、装置、系统、可读取存储介质和电子设备

Country Status (2)

Country Link
CN (1) CN115243401B (zh)
WO (1) WO2022222736A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101394605A (zh) * 2008-10-30 2009-03-25 深圳华为通信技术有限公司 一种终端设备间媒体转移方法、装置和网络设备
CN101631388A (zh) * 2009-07-28 2010-01-20 青岛海信移动通信技术股份有限公司 一种基于无线网络的多方视频共享方法及系统
CN102695234A (zh) * 2011-03-25 2012-09-26 中兴通讯股份有限公司 业务承载迁移方法及装置
WO2012149954A1 (en) * 2011-05-03 2012-11-08 Nokia Siemens Networks Oy Traffic offload in communication networks
CN106507267A (zh) * 2015-09-07 2017-03-15 中国移动通信集团公司 业务处理方法、终端及基站
CN108206993A (zh) * 2018-01-29 2018-06-26 中兴通讯股份有限公司 业务共享方法、装置、存储介质及电子装置

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104125221B (zh) * 2014-07-17 2017-05-24 东北大学 Ims终端设备多软终端资源共享和应用协同装置及方法
CN108141784B (zh) * 2015-09-16 2021-07-27 Lg 电子株式会社 在无线通信系统中发送/接收数据的承载设置方法和支持该方法的设备
KR102458489B1 (ko) * 2016-06-07 2022-10-25 삼성전자 주식회사 무선 통신 시스템에서 단말에 서비스를 제공하는 방법 및 장치
WO2018045533A1 (zh) * 2016-09-08 2018-03-15 华为技术有限公司 一种业务切换方法及相关设备
CN107949036A (zh) * 2016-10-12 2018-04-20 中国移动通信有限公司研究院 一种共享方法、网络设备、终端设备及系统
WO2020156488A1 (zh) * 2019-01-31 2020-08-06 华为技术有限公司 一种通信方法、装置及系统
CN111586643B (zh) * 2019-02-15 2022-07-22 华为技术有限公司 单播传输的方法和通信装置
CN111294741A (zh) * 2019-06-18 2020-06-16 展讯通信（上海）有限公司 业务信息的提取、发送方法及装置、终端、基站
CN112203354B (zh) * 2020-10-13 2023-08-11 中国联合网络通信集团有限公司 一种业务处理方法及装置
CN112511989A (zh) * 2020-10-23 2021-03-16 中兴通讯股份有限公司 一种切换处理方法、通信设备及计算机可读存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101394605A (zh) * 2008-10-30 2009-03-25 深圳华为通信技术有限公司 一种终端设备间媒体转移方法、装置和网络设备
CN101631388A (zh) * 2009-07-28 2010-01-20 青岛海信移动通信技术股份有限公司 一种基于无线网络的多方视频共享方法及系统
CN102695234A (zh) * 2011-03-25 2012-09-26 中兴通讯股份有限公司 业务承载迁移方法及装置
WO2012149954A1 (en) * 2011-05-03 2012-11-08 Nokia Siemens Networks Oy Traffic offload in communication networks
CN106507267A (zh) * 2015-09-07 2017-03-15 中国移动通信集团公司 业务处理方法、终端及基站
CN108206993A (zh) * 2018-01-29 2018-06-26 中兴通讯股份有限公司 业务共享方法、装置、存储介质及电子装置

Also Published As

Publication number Publication date
CN115243401A (zh) 2022-10-25
CN115243401B (zh) 2025-04-11

Similar Documents

Publication Publication Date Title
US11700509B2 (en) Communication system, communication method, and apparatus thereof
CN113411857B (zh) 通信方法及装置
US20230180349A1 (en) Bearer configuration method and apparatus, context information management method and apparatus, releasing method and apparatus, and device
US12294916B2 (en) Communication method and communications apparatus
WO2022171028A1 (zh) 传输方法及装置
CN107231623B (zh) 一种数据调度方法、基站及系统
WO2022227587A1 (zh) 共享业务的建立方法及相关产品
WO2021190278A1 (zh) 业务的请求方法及装置
WO2021097858A1 (zh) 一种通信方法及装置
WO2021189260A1 (zh) 多播通信方法及通信装置
CN103841616B (zh) 一种应用数据包处理方法、装置及系统
WO2022028479A1 (zh) 车联网发现过程的计算任务增强方法及相关产品
CN116939505A (zh) 一种通信方法及装置
WO2017091936A1 (zh) 一种上行数据传输的控制方法、用户终端及网络服务器
WO2023125730A1 (zh) 状态转换方法、装置及设备
WO2023071847A1 (zh) 一种业务转移方法及通信装置
WO2022063186A1 (zh) 传输链路的切换方法及相关产品
EP3691302B1 (en) Data flow transmission method, device, and system
US20230020573A1 (en) Transmission tunnel changing method, access network device, and core network device
WO2022222736A1 (zh) 业务处理方法、装置、系统、可读取存储介质和电子设备
CN108464034B (zh) 语音业务处理方法和装置
CN112291848B (zh) 一种终端能力配置的方法及通信装置
WO2022165813A1 (zh) 一种通信方法及装置
US20250203713A1 (en) Broadcast message transmission method and device, network function and storage medium
CN113973268B (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: 22790845

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

Country of ref document: EP

Kind code of ref document: A1