Wireless communication method, terminal device and network device

Abstract

Provided are a wireless communication method, a terminal device and a network device. The method comprises: a target terminal device sending a first request to a network device, wherein the first request is used to request the migration of a target service from a first terminal device to a second terminal device; and the target terminal device is the first terminal device or the second terminal device. In the embodiments of the present application, the target terminal device can send the first request to the network device to request the migration of the target service from the first terminal device to the second terminal device. That is, the introduction of the first request helps the network device to perceive the requirement for the cross-terminal-device migration of the target service so as to optimize subsequent processes on the basis of the requirement. Compared with that during conventional cross-terminal-device migration of a target service, the network device is unable to perceive the requirement for the cross-terminal-device migration of the target service, and is thus unable to optimize the subsequent processes on the basis of the requirement, an improvement in the user experience is facilitated.

Description

Wireless communication method, terminal equipment and network equipment Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a wireless communication method, terminal equipment, and network equipment. Background Art

[0002] With the advancement of technology and the improvement of living standards, a user usually owns multiple terminal devices. In some scenarios, users often switch between multiple terminal devices. For example, a user runs a certain service (also known as the "target service") on a first terminal device, and then the user needs to switch to a second terminal device to run the service. In this case, the user needs to first terminate the target service on the first terminal device and then start the target service on the second terminal device. This way of switching terminal devices will increase the sense of stagnation of the target service and reduce the user experience.

[0003] Summary of the Invention

[0004] The present application provides a wireless communication method, terminal device, and network device. The following introduces various aspects of the present application.

[0005] In a first aspect, a method for wireless communication is provided, comprising: a target terminal device sends a first request to a network device, wherein the first request is used to request migration of a target service from a first terminal device to a second terminal device; wherein the target terminal device is the first terminal device or the second terminal device.

[0006] In a second aspect, a method for wireless communication is provided, including: a network device receives a first request sent by a target terminal device, the first request being used to request migration of a target service from a first terminal device to a second terminal device; wherein the target terminal device is a first terminal device or a second terminal device.

[0007] According to a third aspect, a method for wireless communication is provided, comprising: a fifth core network device sends target information to a sixth core network device, wherein the target information is used to indicate QoS parameters associated with a user, and the user is associated with one or more terminal devices.

[0008] In a fourth aspect, a method for wireless communication is provided, comprising: a sixth core network device receives target information sent by a fifth core network device, wherein the target information is used to indicate QoS parameters associated with a user, and the user is associated with one or more terminal devices.

[0009] In the fifth aspect, a terminal device is provided, which is a target terminal device, and the target terminal device includes: a sending unit, used to send a first request to a network device, and the first request is used to request to migrate the target service from the first terminal device to the second terminal device; wherein the target terminal device is the first terminal device or the second terminal device.

[0010] In the sixth aspect, a network device is provided, including: a receiving unit for receiving a first request sent by a target terminal device, wherein the first request is used to request to migrate the target service from the first terminal device to the second terminal device; wherein the target terminal device is the first terminal device or the second terminal device.

[0011] In the seventh aspect, a network device is provided, which is a fifth core network device, including: a sending unit, used to send target information to the sixth core network device, the target information is used to indicate the QoS parameters associated with the user, and the user is associated with one or more terminal devices.

[0012] In the eighth aspect, a network device is provided, which is a sixth core network device, including: a receiving unit for receiving target information sent by a fifth core network device, wherein the target information is used to indicate QoS parameters associated with a user, and the user is associated with one or more terminal devices.

[0013] In the ninth aspect, a terminal device is provided, comprising a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the terminal device executes part or all of the steps in the method of the above aspect.

[0014] In the tenth aspect, a network device is provided, comprising a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the network device executes part or all of the steps in the method of the above aspect.

[0015] In an eleventh aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned terminal device and / or network device. In another possible design, the system may also include other devices that interact with the terminal device or network device in the solution provided in the embodiment of the present application.

[0016] In the twelfth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program enables a communication device (for example, a terminal device or a network device) to perform some or all of the steps in the methods of the above aspects.

[0017] In a thirteenth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a communication device (e.g., a terminal device or a network device) to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.

[0018] In the fourteenth aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0019] In an embodiment of the present application, a target terminal device may send a first request to a network device to request that a target service be migrated from a first terminal device to a second terminal device. In other words, the introduction of the first request helps the network device perceive the cross-terminal device migration requirement of the target service, so that subsequent processes can be optimized based on this requirement. This is compared to traditional cross-terminal device migration of a target service, in which the network device is unable to perceive the cross-terminal device migration requirement of the target service and, consequently, is unable to optimize subsequent processes based on this requirement, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] FIG1 is a wireless communication system used in an embodiment of the present application.

[0021] FIG2 is a schematic diagram of the QoS flow applied in the embodiment of the present application.

[0022] FIG3 is a schematic flowchart of a wireless communication method according to an embodiment of the present application.

[0023] FIG4 is a schematic diagram of a PDU session involved in the target service migration process of an embodiment of the present application.

[0024] FIG5 is a schematic flowchart for migrating a target service in an embodiment of the present application.

[0025] FIG6 is a schematic flowchart for migrating a target service in another embodiment of the present application.

[0026] FIG7 is a schematic flowchart for migrating a target service in another embodiment of the present application.

[0027] FIG8 is a schematic flowchart of QoS parameter reporting in an embodiment of the present application.

[0028] FIG9 is a schematic diagram of a terminal device according to an embodiment of the present application.

[0029] FIG10 is a schematic diagram of a network device according to an embodiment of the present application.

[0030] FIG11 is a schematic diagram of a network device according to an embodiment of the present application.

[0031] FIG12 is a schematic diagram of a network device according to an embodiment of the present application.

[0032] FIG13 is a schematic structural diagram of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION

[0033] The technical solutions in this application will be described below in conjunction with the accompanying drawings. For ease of understanding, the following first introduces a schematic diagram of the communication system architecture of an embodiment of this application in conjunction with Figure 1. Figure 1 is a schematic diagram of a communication system architecture applicable to an embodiment of this application. The network architecture may include terminal devices, access network (AN) network elements, and core network network elements.

[0034] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0035] The terminal device in the embodiments of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless core network element, user agent or user device. The terminal device in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in vehicle-to-everything (V2X) or device-to-device (D2D). For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through a base station.

[0036] An access network element can be an access network device. This device is used by terminals to wirelessly access the network architecture and is primarily responsible for radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. An access network device can also be referred to as a radio access network (RAN) device. For example, an access network device can be a base station. A base station may broadly cover various names as follows, or replace the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master eNB (MeNB), secondary eNB (SeNB), multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. A base station may also refer to a communication module, modem, or chip used to be set in the aforementioned device or apparatus. A base station may also be a mobile switching center and a device that performs base station functions in D2D, V2X, and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. A base station may support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form used by the access network device.

[0037] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0038] In some deployments, the access network device in the embodiments of the present application may refer to a CU or a DU, or the access network device may include a CU and a DU. The gNB may also include an AAU.

[0039] The types of core network elements may include user plane function (UPF) network element, access and mobility management function (AMF) network element, session management function (SMF) network element, policy control function (PCF) network element, application function (AF), data network (DN), network slice selection function (NSSF), authentication server function (AUSF), unified data management function (UDM), network exposure function (NEF), network repository function (NRF), and network slice-specific authentication and authorization function (NSSAAF). Among them, the UPF network element is mainly responsible for the transmission of user data, and the other network elements can be called control plane function network elements, which are mainly responsible for authentication, authorization, registration management, session management, mobility management, and policy control, etc., to ensure the reliable and stable transmission of user data.

[0040] The UPF network element can be used to forward and receive data from the terminal. For example, the UPF network element can receive service data from the data network and transmit it to the terminal through the access network device; the UPF network element can also receive user data from the terminal through the access network device and forward it to the data network. Among them, the transmission resources allocated and scheduled by the UPF network element for the terminal are managed and controlled by the SMF network element. The bearer between the terminal and the UPF network element may include: the user plane connection between the UPF network element and the access network device, and the establishment of a channel between the access network device and the terminal. Among them, the user plane connection is a QoS flow that can be established between the UPF network element and the access network device to transmit data.

[0041] The AMF network element can be used to manage the terminal's access to the core network, such as terminal location update, network registration, access control, terminal mobility management, terminal attachment and detachment, etc. The AMF network element can also provide control plane storage resources for the session while providing services for the terminal's session, to store the session identifier, the SMF network element identifier associated with the session identifier, etc.

[0042] The SMF network element can be used to select a user plane network element for the terminal, redirect the user plane network element for the terminal, allocate an Internet Protocol (IP) address to the terminal, establish a bearer (also called a session) between the terminal and the UPF network element, modify and release the session, and control QoS.

[0043] The PCF network element is used to provide policies to the AMF network element and the SMF network element, such as QoS policy and slice selection policy.

[0044] The AF network element is used to interact with the 3GPP core network elements to support application-affected data routing, access network exposure functions, and interact with the PCF network elements for policy control.

[0045] A DN can provide data services to users on networks such as IP Multimedia Service (IMS) and the Internet. A DN can contain multiple application servers (ASs) that provide different application services, such as carrier services, Internet access, or third-party services. The ASs can implement AF functions.

[0046] NSSF is used for network slice selection and supports the following functions: selecting the set of network slice instances serving the UE; determining the allowed Network Slice Selection Assistance Information (NSSAI) and, when necessary, determining the mapping to the contracted single-Network Slice Selection Assistance Information (S-NSSAI); determining the configured NSSAI and, when necessary, determining the mapping to the contracted S-NSSAI; determining the set of AMFs that may be used to query the UE, or determining a list of candidate AMFs based on the configuration.

[0047] AUSF is used to receive the request from AMF to authenticate the terminal, request the key from UDM, and then forward the issued key to AMF for authentication processing.

[0048] UDM includes functions such as the generation and storage of user contract data, management of authentication data, and supports interaction with external third-party servers.

[0049] NEF is used for capability exposure. That is, based on NEF, network capabilities can be exported to external networks. External, untrusted applications can access core network data through NEF to ensure network security. NEF can also provide external application QoS capability exposure, event subscription, and AF request distribution.

[0050] The NRF is used to register, manage, and monitor the status of core network elements, enabling automated management of these elements. Upon startup, a core network element must register with the NRF before it can provide services. Registration information may include the core network element's type, address, and service list.

[0051] In addition, some networks (such as 5G networks) have added a network data analytics function (NWDAF) to the core network. Based on NWDAF, data can be collected from various core network elements and network management systems, and big data statistics, analysis, or intelligent data analysis can be performed to obtain network-side analysis or prediction data, thereby assisting various network elements to more effectively control terminal device access based on the data analysis results.

[0052] In some communication systems (such as 5G systems), core network elements may also be referred to as network functions (NFs).

[0053] The network elements in Figure 1 can be network components in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). It should be noted that the network architecture shown in the above figure is only an example of the network elements included in the entire network architecture. In the embodiments of the present application, the network elements included in the entire network architecture are not limited.

[0054] Those skilled in the art will appreciate that the network architecture shown in Figure 1 does not limit the network architecture. In a specific implementation, the network architecture may include more or fewer network elements than shown, or may combine certain network elements. It should be understood that in Figure 1, the AN or RAN is represented by (R)AN.

[0055] Quality of Service (QoS) flow

[0056] As shown in Figure 2, the concept of QoS flows is introduced in 5G networks. After a terminal accesses the 5G network through the Uu port, it establishes a QoS flow for data transmission under the control of the SMF. The SMF provides the base station with QoS flow configuration information for each QoS flow, including specific bit rate requirements, latency requirements, and bit error rate requirements. For each QoS flow, the base station schedules radio resources based on the QoS flow configuration information received from the SMF to ensure the QoS requirements of the QoS flow. In a 5G network, a QoS flow can carry both uplink data flows (i.e., data flows sent by the terminal to a peer device via the 5G network) and downlink data flows (i.e., data flows sent by a peer device to the terminal via the 5G network). The peer device here refers to the peer application server or the peer terminal. The latency requirements for the uplink and downlink data flows in a QoS flow are the same. If the latency requirements for the uplink and downlink data flows of a service differ, they will be transmitted through different QoS flows. Latency here refers to the data transmission delay between the terminal and the UPF.

[0057] In a mobile communication network, one or more QoS flows need to be established to transmit user-plane data. Different QoS flows correspond to different QoS parameters. As an important measure of communication quality, QoS parameters are often used to indicate the characteristics of a QoS flow. QoS parameters may include, but are not limited to, 5G QoS Identifier (5QI), Address Resolution Protocol (ARP), Guaranteed Flow Bit Rate (GFBR), Maximum Flow Bit Rate (MFBR), Maximum Packet Loss Rate (UL / DL), End-to-End Packet Delay Budget (PDB), AN-PDB, Packet Error Rate (PER), Priority Level, Averaging Window, Resource Type, Maximum Data Burst Volume, User Equipment Aggregate Maximum Bit Rate (UE-AMBR), Session-AMBR, etc.

[0058] Filters, or service data flow (SDF) templates, contain parameters that describe the characteristics of data packets and are used to filter out specific data packets bound to specific QoS flows. The most commonly used filter is the IP quintuple: source IP address, destination IP address, source port number, destination port number, and protocol type.

[0059] The user-side network elements and terminals on the network side will form filters based on the combination of data packet characteristic parameters (see the trapezoid in the terminal and the parallelogram in the UPF in Figure 2) to filter the uplink or downlink data packets that meet the data packet characteristics transmitted on the user plane and bind them to a certain data flow.

[0060] Scenario of cross-terminal migration of target business

[0061] Currently, user terminal types are becoming increasingly diverse, and the same user may own multiple terminal devices. For example, a person may simultaneously own a mobile phone, PAD, laptop, TV, smart car, and other devices. Users tend to use different terminal devices to continuously carry the same services in different living spaces. For example, a user may participate in an online meeting on a computer in the office. After get off work, they may continue the online meeting on their mobile phone on the way to the parking lot. After starting the car, they can continue the meeting using the in-car intelligent system. When they return home, they can switch the meeting service to the TV or computer. Another example is a user watching a TV program on the TV in the living room and then continue watching the program on a PAD or mobile phone in the bedroom.

[0062] Traditional target business migration solution

[0063] In conventional technology, after executing the cross-terminal device migration of the target service, the user views the service in the following manner.

[0064] First, the user closes the target service on the terminal device 1. In response, the core network device releases the protocol data unit (PDU) session of the target service, and the RAN releases the radio resources allocated to the target service flow.

[0065] Afterwards, terminal device 2 uses an existing PDU session or establishes a new PDU session to transmit the target service. At this point, terminal device 2 or the network device needs to initiate a PDU session modification process to adjust the QoS configuration of the target service. Accordingly, the RAN also needs to reallocate new radio resources for it.

[0066] Obviously, the migration of the target service between different terminals makes it difficult to ensure service continuity and stable service quality. During the period between the shutdown of terminal device 1 and the startup of terminal device 2, when the target service is activated and logged into an account, the user is unable to access the service information, resulting in a significant degradation in user experience. Ensuring service continuity is particularly crucial for services such as electronic conferencing and live broadcasts of sports.

[0067] Of course, users can also transmit the target service of terminal device 1 to terminal device 2 through wireless screen projection technology. However, during this period, the communication system needs to spend double resources to transmit the same service, and at the same time consume the power of multiple devices and generate additional traffic billing.

[0068] The user can also wait for terminal device 2 to receive the business data and display it before turning off terminal device 1 to ensure business continuity. However, this also requires the user to reserve time or consume additional waiting time, which to a certain extent increases the inconvenience of the user and affects the user experience. In addition, when the user urgently needs to change the workspace, or when the user needs to switch terminal devices due to some unexpected events, it is difficult for the user to reserve enough time to wait for the switch to be completed. Users often need to complete seamless business migration between multiple devices in a short period of time.

[0069] Support for UE session and service continuity in traditional solutions

[0070] The support for session and service continuity in the 5G system architecture can address the various continuity requirements of different applications / services on terminal devices. The 5G system supports the following three different session and service continuity (SSC) modes. The SSC mode associated with a PDU session does not change during the life cycle of the PDU session.

[0071] For SSC Mode 1, the network retains the connection service provided to the terminal device. Regardless of the access technology (such as access type and cell) that the terminal device uses to access the network, the UPF that acts as the PDU session anchor when the PDU session is established remains unchanged. For PDU sessions of IPv4, IPv6, or IPv4v6 type, the IP address remains unchanged.

[0072] For SSC Mode 2, the network may release the connection service delivered to the terminal device and release the corresponding PDU session. For IPv4 or IPv6 or IPv4v6 types, the release of the PDU session results in the release of the IP address allocated to the terminal device.

[0073] For SSC mode 3, PDU sessions can provide business continuity services for terminal devices, but cannot provide session continuity. Unlike SSC mode 1, the anchor point UPF of the service flow can change. The network instructs the terminal device to establish a new PDU session and selects a local anchor point UPF with a more optimized route during the session establishment process; after a certain period of time after the new PDU session is established, the old PDU session is released. During this process, the IP address of the terminal device will change, but since the terminal device always has at least one PDU session connected to the DN at any time, service continuity is guaranteed.

[0074] The above-mentioned session and business continuity support is for a single terminal device and cannot be used to ensure business continuity when the same user migrates business between multiple terminals. In traditional solutions, the design is often centered on the terminal device, and one user is bound to one terminal device by default. However, with the advancement of technology and the improvement of living standards, a user often has multiple terminal devices, and in some scenarios, users often switch between multiple terminal devices. For example, a user runs a certain service (also called "target service") on a first terminal device, and then the user needs to switch to a second terminal device to run the service. In this case, the user needs to first terminate the target service on the first terminal device, and then start the target service on the second terminal device. This way of switching terminal devices will increase the sense of stagnation of the target service and reduce the user experience.

[0075] Taking web browsing as the target service, web browsing includes services such as video on demand with caching capabilities. If the target service is to be migrated from the first terminal device to the second terminal device (i.e., service migration across terminal devices), the second terminal device usually does not have a cache of the target service. Therefore, the user needs to wait for a long time for the progress of the newly running target service on the second terminal device to be consistent with the progress of the target service running on the first terminal device, resulting in a lower user experience.

[0076] Taking the target business including live broadcast business as an example, live broadcast business usually has strong real-time requirements. If the user follows the solution introduced above, first terminates the target business on the first terminal device, and then runs the target business on the second terminal device, then during the above-mentioned cross-terminal device migration process, the user will lose a lot of key information of the live broadcast business, resulting in a low user experience.

[0077] Of course, in order to improve the user experience, avoid users waiting for a long time or avoid users losing a lot of key business-related information, when the user needs to switch the target business from the first terminal device to the second terminal device, the user can first start the target business on the second terminal device, and wait until the second terminal device is ready (for example, until the second terminal device starts playing live content, or until the progress of the target business in the second terminal device is consistent with the progress of the target business in the first terminal device), and then the user can close the target business running on the first terminal device. However, this solution for cross-terminal device business migration may lead to a significant increase in network resources used to transmit the target business.

[0078] The applicant believes that the above problems arise because the communication system does not take into account the user's need to migrate the target service across terminal devices, resulting in various problems in the process of migrating the target service from the first terminal device to the second terminal device. Therefore, in response to the above problems, an embodiment of the present application provides a method for wireless communication. For ease of understanding, the wireless communication method of the embodiment of the present application is described below in conjunction with Figure 3. Figure 4 is a schematic flow chart of the wireless communication method of the embodiment of the present application. The method shown in Figure 3 includes step S310.

[0079] In step S310, the target terminal device sends a first request to the network device.

[0080] In some implementations, the first request is used to request migration of the target service from the first terminal device to the second terminal device. Therefore, in the example of this application, the first request is also called a "migration request."

[0081] In the embodiment of the present application, the manner in which the first request indicates the target service is not limited. In some implementations, the first request may carry indication information of the target service, where the indication information of the target service may include one or more of the following: an identifier of the first terminal device, an identifier of the second terminal device, a DNN, a PDU session ID, and an S-NSSAI indicating the target service. The PDU session indicated by the PDU session ID may be a PDU session used to transmit the target service.

[0082] In some scenarios, the communication system does not perceive the granularity of the service, or in other words, the minimum granularity perceived by the communication system is the QoS flow. Therefore, in the example of this application, the migration of the target service can be understood as the migration of the QoS flow that transmits the target service. Accordingly, the above-mentioned first request is used to request the migration of the first QoS flow from the first terminal device to the second terminal device, wherein the first QoS flow can be a QoS flow in the first terminal device, or the first QoS flow can be used to transmit the target service.

[0083] In some implementations, the QoS flow used to transmit the target service is part or all of the QoS flows in the associated PDU session. In other words, the QoS flows of the PDU session can be migrated as a whole, or part of the QoS flows of the PDU session can be migrated as a whole.

[0084] For example, assuming that all QoS flows included in the PDU session are used to transmit audio and video services, accordingly, all QoS flows included in the PDU session can be migrated to the second terminal device.

[0085] For another example, assuming that the multiple QoS flows contained in the PDU session are used for audio services and video services, the QoS flow for transmitting the video service can be migrated from the first terminal device to the second terminal device, and accordingly, the QoS flow for transmitting the audio service can be retained in the first terminal device (for example, headphones).

[0086] As mentioned above, the target service is carried in a PDU session. If the target service is migrated from the first terminal device to the second terminal device, a PDU session (e.g., a second PDU session) that can be used to transmit the target service is required on the second terminal device. In some implementations, the second PDU session may be different from the PDU session (e.g., the first PDU session) used by the first terminal device to transmit the target service. For example, the second PDU session may be re-established by the second terminal device. For another example, the second PDU session may be a modification of an existing PDU session of the second terminal device.

[0087] As shown in Figure 4(a), after the target service is migrated from the first terminal device to the second terminal device, the second PDU session used to transmit the target service on the second terminal device is different from the first PDU session. This will be described in detail below in conjunction with Figures 5 and 6, and for the sake of brevity, it will not be repeated here.

[0088] In other implementations, the second PDU session can be the same as the first PDU session used by the first terminal device to transmit the target service. As shown in Figure 4(b), after the target service is migrated from the first terminal device to the second terminal device, the second PDU session used by the second terminal device to transmit the target service is the same as the first PDU session. This will be described in detail below in conjunction with Figure 7 and will not be repeated here for the sake of brevity.

[0089] It should be noted that, in the embodiment of the present application, the second PDU session may be the PDU session for carrying the target service described above, or in other words, the PDU session for carrying the target service in the second terminal device. Of course, in the embodiment of the present application, the second PDU session may also be a PDU session of the second terminal device, for example, the second PDU session may be a specific PDU session of the second terminal device.

[0090] In addition, in the embodiment of the present application, the first PDU session may be the PDU session for carrying the target service described above, or in other words, the PDU session for carrying the target service in the first terminal device. Of course, in the embodiment of the present application, the first PDU session may also be the PDU session of the first terminal device, for example, the first PDU session may be a specific PDU session of the first terminal device.

[0091] In some implementations, the first terminal device and the second terminal device may have an association relationship. For example, if the association relationship is through user association, the first terminal device and the second terminal device may belong to the same user. For example, if the association relationship is through terminal group association, the first terminal device and the second terminal device may belong to the same terminal group. Of course, in the embodiments of the present application, the first terminal device and the second terminal device may simply be two terminal devices involved in the migration process of the target service, and this embodiment of the present application is not limited to this.

[0092] Taking the association relationship through user association as an example, the association relationship between the terminal device (including the first terminal device and / or the second terminal device) and the user can be dynamic, static or semi-static.

[0093] Taking the dynamic association relationship as an example, for some public terminal devices, the users associated with them may be different in different time periods. Therefore, in this scenario, the association relationship between the terminal device and the user can be dynamic. Taking the static association relationship as an example, for some private terminal devices, the users associated with them may be the same in different time periods. Therefore, in this scenario, the association relationship between the terminal device and the user can be static. Taking the semi-static association relationship as an example, for some terminal devices shared within the home (inflow, smart TVs, smart cars, etc.), the users associated with them change within a set of multiple users in different time periods. Therefore, in this scenario, the association relationship between the terminal device and the user can be semi-static.

[0094] In some implementations, the target terminal device is the first terminal device and / or the second terminal device. That is, the first request may be triggered by the first terminal device and / or the second terminal device, but this is not limited in this embodiment of the present application. For ease of understanding, the following description will combine Examples 1 and 2, using the example of the first terminal device or the second terminal device sending the first migration request, respectively.

[0095] In embodiment 1, the target terminal device is a first terminal device.

[0096] In some implementations, the first request may include one or more of the following information: information indicating the first terminal device; information indicating the second terminal device; information for determining the second PDU session; information indicating the association relationship between the first terminal device and the second terminal device; information indicating the first PDU session; information indicating the first QoS flow; and QoS parameters of the QoS flow transmitting the target service.

[0097] Taking the example of the first request including information indicating the first terminal device, the information indicating the first terminal device includes an identifier of the first terminal device and / or address information of the first terminal device. The address information of the first terminal device may be, for example, an IP address of the first terminal device. Of course, in the embodiment of the present application, the address information of the first terminal device may be, for example, a MAC address of the first terminal device.

[0098] Taking the example of the first request including information indicating the second terminal device, the information indicating the second terminal device includes an identifier of the second terminal device and / or address information of the second terminal device. The address information of the second terminal device may be, for example, an IP address of the second terminal device. Of course, in the embodiment of the present application, the address information of the second terminal device may be, for example, a MAC address of the second terminal device.

[0099] Taking the example of the first request including information for indicating the association relationship, based on the above introduction, it can be seen that in some implementations, the above-mentioned association relationship can be associated through the user of the terminal device. At this time, the information for indicating the association relationship can include indication information of the common user to which the first terminal device and the second terminal device belong (for example, the indication information can be a user identifier).

[0100] In other implementations, the above-mentioned association relationship can be associated through a terminal group of the terminal device. In this case, the information used to indicate the association relationship may include indication information of the terminal group to which the first terminal device and the second terminal device belong (for example, the indication information may be an identifier of the terminal group).

[0101] In other implementations, the above-mentioned association relationship may directly include the association relationship between terminal devices. In this case, the information used to indicate the association relationship may include identification information of the association relationship between the first terminal device and the second terminal device.

[0102] Take the example of the first request including information for indicating the first PDU session, wherein the first PDU session is a PDU session for the first terminal device to carry the target service, or the first PDU session is a PDU session for the first terminal device. Accordingly, the information for indicating the first PDU session may include, for example, an identifier of the first PDU session. In an embodiment of the present application, information for indicating the first PDU session may be carried in the first request, which helps the network device determine the PDU session where the target service that needs to be migrated is located.

[0103] Take the example of the first request including information for indicating the second PDU session, wherein the second PDU session is a PDU session for the second terminal device to carry the target service, or the second PDU session is a PDU session for the second terminal device. Accordingly, the information for indicating the second PDU session may include, for example, an identifier of the second PDU session. Of course, in an embodiment of the present application, the above-mentioned information for indicating the second PDU session may also include other information. For example, the information for indicating the second PDU session may also include information of the second terminal device and application service description information associated with the target service, so as to assist the network device (such as SMF) in determining the second PDU. The information of the second terminal device may include identification information of the second terminal device and / or address information of the second terminal device. The application service description information may include one or more of application identification, DNN, and S-NSSAI.

[0104] In an embodiment of the present application, by including information indicating the second PDU session in the first request, it helps the network device to determine the second PDU session.

[0105] Take the example of the first request including information for indicating the first QoS flow, wherein the first QoS flow is used for the first terminal device to transmit the target service, or the first QoS flow is the QoS flow of the first terminal device. The embodiment of the present application does not limit the information used to indicate the first QoS flow. In some implementations, the information used to indicate the first QoS flow may include an identifier of the first QoS flow. In other implementations, the information used to indicate the first QoS flow may include flow description information of the first QoS flow, wherein the flow description information may, for example, include one or more of the following: the source address of the first QoS flow, the destination address of the first QoS flow, the source port number of the first QoS flow, the destination port number of the first QoS flow, and the protocol identifier associated with the first QoS flow.

[0106] It should be noted that the first QoS flow can be one QoS flow or multiple QoS flows. Accordingly, the information indicating the first QoS flow can include information indicating one QoS flow or information indicating multiple QoS flows. This embodiment of the present application is not limited to this. For example, the information indicating the first QoS flow can include identifiers of one or more QoS flows.

[0107] In the embodiment of the present application, the information indicating the first QoS flow helps the network device determine the QoS flow of the target service to be migrated. Of course, in some cases, the first request may not carry this information, for example, when the first terminal device has only one QoS flow. For another example, all QoS flows in the PDU session containing the QoS flow can be migrated to the second terminal device.

[0108] Taking the example of a first request including QoS parameters for a QoS flow transmitting a target service, in some implementations, the QoS parameters may be associated with the second terminal device. For example, the QoS parameters may be obtained via a subscription message from the second terminal device. In other implementations, the QoS parameters may be associated with the user to whom the first terminal device and the second terminal device belong. For example, the QoS parameters may be obtained via a subscription message from the user. This will be described in detail below in conjunction with Example X and will not be repeated here for the sake of brevity.

[0109] In an embodiment of the present application, the first request may not include the QoS parameters of the QoS flow for the target service. In this case, after the QoS flow corresponding to the target service is migrated to the second PDU session, the QoS parameters of the QoS flow may be the QoS parameters of other QoS flows in the second PDU session. Of course, if the first request includes the first QoS parameters, the QoS parameters of the QoS flow may be determined based on the QoS of the first QoS flow, which is not limited in this embodiment of the present application.

[0110] In this embodiment of the present application, since the first request may be sent by the first terminal device, the information carried in the first request may be related to information of the first terminal device. For example, the first request may carry QoS parameters of the first QoS flow. For another example, the first request may carry information related to the first PDU session.

[0111] In embodiment 2, the target terminal device is the second terminal device.

[0112] In some implementations, the first request may include one or more of the following information: information indicating the first terminal device; information indicating the second terminal device; information indicating the association relationship between the first terminal device and the second terminal device; information for determining the second PDU session; information for determining the first PDU session; information for determining the first QoS flow and resolution information of the second terminal device.

[0113] Taking the example of the first request including information indicating the first terminal device, the information indicating the first terminal device includes an identifier of the first terminal device and / or address information of the first terminal device. The address information of the first terminal device may be, for example, an IP address of the first terminal device. Of course, in the embodiment of the present application, the address information of the first terminal device may be, for example, a MAC address of the first terminal device.

[0114] Taking the example of the first request including information indicating the second terminal device, the information indicating the second terminal device includes an identifier of the second terminal device and / or address information of the second terminal device. The address information of the second terminal device may be, for example, an IP address of the second terminal device. Of course, in the embodiment of the present application, the address information of the second terminal device may be, for example, a MAC address of the second terminal device.

[0115] Taking the example of the first request including information for indicating the association relationship, based on the above introduction, it can be seen that in some implementations, the above-mentioned association relationship can be associated through the user of the terminal device. At this time, the information for indicating the association relationship can include indication information of the common user to which the first terminal device and the second terminal device belong (for example, the indication information can be a user identifier).

[0116] In other implementations, the above-mentioned association relationship can be associated through a terminal group of the terminal device. In this case, the information used to indicate the association relationship may include indication information of the terminal group to which the first terminal device and the second terminal device belong (for example, the indication information may be an identifier of the terminal group).

[0117] In other implementations, the above-mentioned association relationship may directly include the association relationship between terminal devices. In this case, the information used to indicate the association relationship may include identification information of the association relationship between the first terminal device and the second terminal device.

[0118] Take the example of the first request including information for indicating the second PDU session, wherein the second PDU session is a PDU session for the second terminal device to carry the target service, or the second PDU session may be a PDU session for the second terminal device. Accordingly, the information for indicating the second PDU session may include, for example, an identifier of the second PDU session. In an embodiment of the present application, information for indicating the second PDU session may be carried in the first request, which helps the network device determine the PDU session where the target service to be migrated is located.

[0119] Taking the example of the first request including information for determining the first PDU session, wherein the first PDU session is a PDU session for the first terminal device to carry the target service, or the first PDU session can be a PDU session for the first terminal device. Accordingly, the information used to determine the first PDU session may, for example, include application service description information associated with the target service to assist the network device (such as SMF) in determining the first PDU. The application service description information may include one or more of an application identifier, a DNN, and an S-NSSAI.

[0120] In an embodiment of the present application, by including information for determining the first PDU session in the first request, it helps the network device to determine the first PDU session.

[0121] Taking the example of the first request including information for determining the first QoS flow, wherein the first QoS flow is used for the first terminal device to transmit the target service, or the first QoS flow is the QoS flow of the first terminal device. In some implementations, the information for determining the first QoS flow may include packet filters. In an embodiment of the present application, the first request can assist the network device in determining the first QoS flow by carrying information for determining the first QoS flow, thereby helping the network device to determine the QoS flow to be migrated.

[0122] Take the example of the first request including the resolution information of the second terminal device, where the resolution information of the second terminal device can also be referred to as the resolution size information of the second terminal device. In some implementations, the resolution of the second terminal device can be used to determine the QoS parameters of the second QoS flow of the target service transmitted by the second terminal device. For example, the network device can store the association relationship between multiple resolutions and QoS parameters. Accordingly, after receiving the first request, the network device can determine the QoS parameters associated with the resolution information of the second terminal device based on the resolution information of the second terminal device and the association relationship between the multiple resolutions and QoS parameters.

[0123] As introduced above, in the example of this application, the target service needs to be migrated from the first terminal device to the second terminal device. However, in the process of migrating the target service, the QoS parameters of the QoS flow used to transmit the target service may change, resulting in the QoS parameters of the corresponding QoS flow of the target service before and after the migration do not match, affecting the transmission performance of the target service and reducing the user experience.

[0124] Therefore, in order to avoid the above problem, the QoS parameters of the first QoS flow are the same as the QoS parameters of the second QoS flow, or the QoS configuration of the first QoS flow is the same as the QoS configuration of the second QoS flow.

[0125] The above describes the relationship between the QoS parameters of the first QoS flow and the QoS parameters of the second QoS flow in the embodiment of the present application. The following describes the configuration method of the QoS parameters of the second QoS flow in the example of the present application.

[0126] In some implementations, a network device (e.g., a second core network device) may configure appropriate QoS parameters for the second QoS flow to transmit the target service. Specifically, if the network device is a second core network device, the method further includes: the second core network device configuring QoS parameters for the second QoS flow of the second terminal device. The following describes the method for configuring QoS parameters in this application example in conjunction with Methods 1 to 6.

[0127] In method 1, the QoS parameters of the QoS flow used to transmit the target service can be obtained through the contract information, that is, the above method also includes: the second core network device obtains the contract information, and the contract information records the QoS parameters of the QoS flow used to transmit the target service; the above second core network device configures QoS parameters for the second QoS flow of the second terminal device, including: the second core network device configures QoS parameters for the second QoS flow based on the contract information.

[0128] In some implementations, the above-mentioned subscription information may be the subscription information of the second terminal device. Accordingly, the QoS parameters in the subscription information are related to the second terminal device. At this time, the second core network device can configure QoS parameters for the second QoS flow based on the QoS parameters associated with the second terminal device.

[0129] It should be noted that the above-mentioned subscription message can be provided by the second terminal device or by the AF, and this embodiment of the present application is not limited to this. Among them, the AF can, for example, provide QoS parameters through the AF session request establishment process. The following will be described in conjunction with Figure 8 and will not be repeated here for the sake of brevity.

[0130] In the embodiment of the present application, configuring QoS parameters for the second QoS flow based on the QoS parameters associated with the second terminal device can be understood as directly using the QoS parameters associated with the second terminal device as the QoS parameters of the second QoS flow. Of course, in the embodiment of the present application, configuring QoS parameters for the second QoS flow based on the QoS parameters associated with the second terminal device can be understood as adjusting the QoS parameters associated with the second terminal device to obtain the adjusted QoS parameters, and configuring the second QoS flow based on the adjusted QoS parameters.

[0131] In other implementations, the above-mentioned contract information may be the contract information of the user, wherein the user may be the user to which the first terminal device and the second terminal device belong, or in other words, the user may be the common user (also referred to as the target user) to which the first terminal device and the second terminal device belong. Accordingly, the QoS parameters in the contract information are related to the user. In this case, the second core network device may configure QoS parameters for the second QoS flow based on the QoS parameters associated with the user.

[0132] It should be noted that, in the embodiment of the present application, configuring QoS parameters for the second QoS flow based on the user-associated QoS parameters can be understood as directly using the user-associated QoS parameters as the QoS parameters of the second QoS flow. Of course, in the embodiment of the present application, configuring QoS parameters for the second QoS flow based on the user-associated QoS parameters can be understood as adjusting the user-associated QoS parameters to obtain the adjusted QoS parameters, and configuring the second QoS flow based on the adjusted QoS parameters.

[0133] In mode 2, if the first request carries QoS parameters for the QoS flow transmitting the target service, the second core network device configures the QoS parameters for the second QoS flow of the second terminal device, including: the second core network device configures the QoS parameters for the second QoS flow based on the first request. In other words, the second core network device configures the QoS parameters for the second QoS flow based on the QoS parameters carried in the first request.

[0134] It should be noted that, in the embodiment of the present application, configuring QoS parameters for the second QoS flow based on the QoS parameters carried in the first request can be understood as directly using the QoS parameters carried in the first request as the QoS parameters for the second QoS flow. In other words, the QoS parameters specified in the first request are configured for the second QoS flow. Of course, in the embodiment of the present application, configuring QoS parameters for the second QoS flow based on the QoS parameters associated with the QoS parameters carried in the first request can be understood as adjusting the QoS parameters carried in the first request to obtain the adjusted QoS parameters, and configuring the second QoS flow based on the adjusted QoS parameters.

[0135] In mode 3, the second core network device may configure the same QoS parameters for the second QoS flow as for the migrated QoS flow (the first QoS flow). That is, the second core network device configures the QoS parameters for the second QoS flow of the second terminal device, including: the second core network device obtains the first QoS parameters, which are the QoS parameters of the first QoS flow used by the first terminal device to transmit the target service; and the second core network device configures the QoS parameters for the second QoS flow of the second terminal device based on the first QoS parameters.

[0136] It should be noted that, in the embodiment of the present application, configuring QoS parameters for the second QoS flow based on the first QoS parameters can be understood as directly using the first QoS parameters as the QoS parameters for the second QoS flow. In other words, the first QoS parameters are configured for the second QoS flow. Of course, in the embodiment of the present application, configuring QoS parameters for the second QoS flow based on the first QoS parameters can be understood as adjusting the first QoS parameters to obtain the adjusted QoS parameters, and then configuring the second QoS flow based on the adjusted QoS parameters.

[0137] In method 4, if the first request includes information for indicating the first terminal device and information for indicating the second terminal device, or in other words, the first request only includes information for indicating the first terminal device and information for indicating the second terminal device, then the above method also includes: the second core network device determines the first QoS flow of the first terminal device based on the information for indicating the first terminal device; the second core network device determines the QoS parameters of the first QoS flow; the above second core network device configures QoS parameters for the second QoS flow of the second terminal device, including: the second core network device configures QoS parameters for the second QoS flow based on the QoS parameters of the first QoS flow.

[0138] In some implementations, the above-mentioned information used to indicate the first terminal device may include the user identifier of the user to which the first terminal device belongs. Accordingly, the second core network device may determine the first QoS flow for transmitting the target service in the first terminal device based on the user identifier and QFI.

[0139] Of course, in the embodiment of the present application, there is no limitation on the method for determining the first QoS flow. For example, the first QoS flow can also be determined based on other information. In some implementations, the second core network device can determine the first QoS flow based on the IP five-tuple information of the first QoS flow; thereafter, the second core network device determines the QoS parameters of the first QoS flow; the above-mentioned second core network device configures QoS parameters for the second QoS flow of the second terminal device, including: the second core network device configures QoS parameters for the second QoS flow based on the QoS parameters of the first QoS flow. Among them, the IP five-tuple information includes the source address, destination address, source port, destination port and protocol identifier of the target service flow.

[0140] It should be noted that, in the embodiments of the present application, configuring QoS parameters for the second QoS flow based on the QoS parameters of the first QoS flow can be understood as directly using the QoS parameters of the first QoS flow as the QoS parameters of the second QoS flow. In other words, the QoS parameters of the first QoS flow are configured for the second QoS flow. Of course, in the embodiments of the present application, configuring QoS parameters for the second QoS flow based on the QoS parameters of the first QoS flow can be understood as adjusting the QoS parameters of the first QoS flow to obtain the adjusted QoS parameters, and then configuring the second QoS flow based on the adjusted QoS parameters.

[0141] In method 5, if the first request includes information for indicating the association relationship between the first terminal device and the second terminal device, the above method also includes: the second core network device determines the QoS parameters corresponding to the association relationship based on the association relationship; the above second core network device configures QoS parameters for the second QoS flow of the second terminal device, including: the second core network device configures QoS parameters for the second QoS flow of the second terminal device based on the QoS parameters corresponding to the association relationship.

[0142] In some implementations, the above-mentioned association relationship may include that the first terminal device and the second terminal device belong to the same user. In this case, the QoS parameters corresponding to the above-mentioned association relationship can be understood as user-associated QoS parameters. In other implementations, the above-mentioned association relationship may include that the first terminal device and the second terminal device belong to the same terminal group. In this case, the QoS parameters corresponding to the above-mentioned association relationship can be understood as terminal group-associated QoS parameters. In other implementations, the above-mentioned association relationship may be the association relationship between the first terminal device and the second terminal device. In this case, the QoS parameters corresponding to the above-mentioned association relationship can be understood as QoS parameters associated with the association relationship.

[0143] In method 6, if the first request includes the resolution information of the second terminal device, the second core network device can determine the QoS parameters corresponding to the resolution information of the second terminal device based on the resolution information of the second terminal device and the correspondence between the pre-stored resolution information and the QoS parameters; accordingly, the above-mentioned second core network device configures QoS parameters for the second QoS flow of the second terminal device, including: the second core network device configures QoS parameters for the second QoS flow of the second terminal device based on the QoS parameters corresponding to the resolution information of the second terminal device.

[0144] In the embodiment of the present application, the second core network device may be, for example, an SMF. Of course, in the embodiment of the present application, the second core network device may also be another network element with a QoS parameter configuration function. Taking the second core network device as an SMF as an example, based on the known communication system architecture, the first request may be forwarded to the second core network device via other network devices. For example, the target terminal device may send the first request to the access network device, which may forward the request to the AMF, which may then forward the request to the SMF.

[0145] It should be noted that in the process of transmitting the first request, each intermediate node (access network equipment, AMF, etc.) can process the first request, or each intermediate node can directly forward the first request. This embodiment of the present application does not limit this.

[0146] In some scenarios, the second core network device also needs to configure packet detection rules for the third core network device (e.g., UPF) to map the target service's packets to the QoS flow between the second terminal device and the third core network device. In some implementations, the above method further includes: the second core network device configuring the third core network device with an N4 rule corresponding to the second QoS flow and / or a QoS rule corresponding to the second QoS flow.

[0147] In some implementations, the third core network device and the second core network device may communicate via an N4 interface. Accordingly, N4 rules may be understood as rules related to communication on the N4 interface. For example, N4 rules may include one or more of packet detection rules (PDRs), forwarding action rules (FARs), QoS enforcement rules (QERs), and usage reporting rules (URRs).

[0148] In the embodiment of the present application, the information sent by the second core network device to the third core network device is not limited. For example, the second core network device may also send an N4 session identifier (N4 session ID) and / or an identifier of a QoS flow (e.g., a second QoS flow) for transmitting the target service to the third core network device.

[0149] In an embodiment of the present application, the N4 rule corresponding to the above-mentioned second QoS flow and / or the QoS rule corresponding to the second QoS flow can be carried in a PDU session modification request, which is used to request modification of the PDU session used to transmit the target service.

[0150] In some scenarios, the second core network device also needs to configure data packet detection rules for the third core network device (e.g., UPF) so as to map the data packets of the target service to the QoS flow between the second terminal device and the third core network device. In some implementations, the above method also includes: the second core network device configures the N4 rule corresponding to the second QoS flow and / or the QoS rule corresponding to the second QoS flow for the third core network device. Of course, in an embodiment of the present application, the above information transmitted between the second core network device and the third core network device can also be information transmitted separately.

[0151] In order to facilitate the transmission of data packets corresponding to the migrated target service between the second terminal device and the access network device of the second terminal device, in some implementations, the second core network device can send the QoS configuration of the second QoS flow and / or the alternative QoS configuration of the second QoS flow to the access network device.

[0152] The embodiments of the present application do not limit the content of the QoS configuration. For example, the QoS configuration may include 5QI, ARP, RQA, GFBR, MFBR and other QoS parameters.

[0153] It should be noted that, in addition to sending the above information to the access network device, the second core network device may also send information indicating the second QoS flow to the access network device. For example, the second core network device may send identification information of the second QoS flow to the access network device.

[0154] In addition, in an embodiment of the present application, the QoS configuration of the above-mentioned second QoS flow and / or the alternative QoS configuration of the second QoS flow can be carried in a PDU session modification request, which is used to request modification of the PDU session used to transmit the target service.

[0155] In other implementations, in order to facilitate the transmission of data corresponding to the migrated target service between the second terminal device and the access network device, the above method also includes: the second core network device configures the QoS rules of the second QoS flow and / or QoS parameters of the QoS flow level for the second terminal device.

[0156] It should be noted that, in addition to sending the above information to the second terminal device, the second core network device may also send an identifier of the second QoS flow to the second terminal device.

[0157] In addition, in an embodiment of the present application, the QoS configuration of the above-mentioned second QoS flow and / or the alternative QoS configuration of the second QoS flow can be carried in a PDU session modification request, which is used to request modification of the PDU session used to transmit the target service. Accordingly, in some implementations, if the second terminal device can return a PDU session modification confirmation message to the second core network device. Taking the second core network device as SMF as an example, the second terminal device can send the above-mentioned PDU session modification confirmation message to AMF through RAN, and accordingly, AMF can send the received PDU session modification confirmation message to SMF.

[0158] As previously introduced, in some scenarios, the above information can be carried in a PDU session modification request, or in other words, the above information can be transmitted during the PDU session modification process. Therefore, it can be understood that the above solution can be applicable to the scenario where the second terminal device has established a PDU session (also called the second PDU session). At this time, the second PDU session can be modified based on the PDU session modification process so that the second PDU session can be used to transmit the target service. Accordingly, in the above case, the above first request can be carried in a PDU session modification request, which is used to request modification of the PDU session of the second terminal device to transmit the target service.

[0159] Of course, in this embodiment of the present application, a new PDU session (also referred to as a "second PDU session") may be established for transmitting the target service to the second terminal device. In this case, the first request may be carried in the PDU session establishment request. In this case, the first request may also be transmitted independently.

[0160] In some implementations, the second core network device may allocate address information for the newly established second PDU session. That is, in some implementations, the method further includes: the second core network device allocates address information for the second PDU session. The address information may be, for example, IP address information or MAC address information.

[0161] In some implementations, if the first terminal device and the second terminal device belong to the same user, the address information of the second PDU session may be one of the address sets corresponding to the user. Of course, in the embodiment of the present application, the address information of the second PDU session may also be unrelated to the user.

[0162] In the embodiments of the present application, the above-mentioned address set is not limited. Taking the address information as an IP address as an example, the address set can include one or more of the following address sets: an address segment in the form of an IPv4 address and a subnet mask, an address segment in the form of an IPv6 address and a prefix, and multiple discrete IP addresses.

[0163] In addition, in an embodiment of the present application, the above-mentioned address set can be pre-configured in a core network device (e.g., a second core network device and / or a third core network device). Taking the address set stored in the second core network device as an example, the second core network device can configure address information for the second PDU session based on the pre-stored address set. Of course, in an embodiment of the present application, the above-mentioned address set can also be stored in the UDM as a user subscription message, and accordingly, the second core network device can obtain it from the UDM through the user subscription message.

[0164] In some implementations, the above method also includes: the second core network device sends a second request to the fourth core network device, the second request is used to request the PCC rules for transmitting the target service; the second core network device receives a response message sent by the fourth core network device to the second request, and the response message carries the PCC rules.

[0165] In some implementations, the second request carries information indicating the second terminal device and / or address information of the second PDU session.

[0166] In the embodiment of the present application, the fourth core network device may be a PCF. Of course, the fourth core network device may also be other devices with similar functions, which is not limited in the embodiment of the present application.

[0167] In addition, in the embodiment of the present application, the second core network device may obtain the PCC rule information in an SMF initiated SM Policy Association Modification procedure. Of course, in the embodiment of the present application, the process of obtaining the PCC rule may also be an independent process.

[0168] In some scenarios, the first PDU session can be the same as the second PDU session, or in other words, the second terminal device can reuse the first PDU session to transmit the target service. For example, when the access network device of the first terminal device is the same as the access network device of the second terminal device, the second terminal device can reuse the first PDU session to transmit the target service.

[0169] It should be noted that if the second terminal device reuses the PDU session of the first terminal device, then all QoS flows in the PDU session of the first terminal device can be migrated to the second terminal device.

[0170] In some implementations, the access network device may configure QoS parameters for the QoS flow used to transmit the target service in the second PDU session based on the QoS parameters of the target service. That is, if the network device is an access network device, the method further includes: the access network device obtaining information indicating an association relationship between the first terminal device and the second terminal device; the access network device determining, based on the information indicating the association relationship, a QoS configuration associated with the information indicating the association relationship; and the access network device configuring a second QoS flow for the second terminal device based on the QoS configuration associated with the information indicating the association relationship.

[0171] In some implementations, the second core network device may allocate address information for the second PDU session. That is, if the network device is the second core network device, the method includes: in response to receiving the first request, the second core network device allocates address information to the second terminal device.

[0172] In some implementations, the address information of the second terminal device satisfies one of the following: the address information of the second terminal device is the same as the address information of the first terminal device; the address information of the second terminal device is different from the address information of the first terminal device; the address information of the second terminal device belongs to a target address information segment, the target address information segment is associated with a target user, and the target user is a common user of the first terminal device and the second terminal device.

[0173] In some scenarios, if the address information of the second terminal device is different from the address information of the first terminal device, the second core network device can update the source address information and / or destination address information in the original N4 rule corresponding to the first terminal device to the address information of the second terminal device when configuring the N4 rule.

[0174] In other scenarios, if the address information of the second terminal device is the same as that of the first terminal device, the second core network device does not update the original N4 rule corresponding to the first terminal device when configuring the N4 rule to simplify the configuration process of the N4 rule.

[0175] In some scenarios, the second core network device needs to determine the second terminal device based on the first request. Specifically, if the target terminal device is the first terminal device and the network device is the second core network device, the method further includes: in response to receiving the first request, the second core network device determining the second terminal device. Depending on the information carried in the first request, the second core network device determines the second terminal device in different ways.

[0176] In some implementations, if the first request carries information indicating the association relationship between the first terminal device and the second terminal device, the above-mentioned second core network device determines the second terminal device, including: the second core network device determines, based on the association relationship, that the terminal device that has an association relationship with the first terminal device is the second terminal device.

[0177] In some implementations, if the first request carries information for indicating the second terminal device, the second core network device determines the second terminal device, including: the second core network device determines the second terminal device based on the information for indicating the second terminal device.

[0178] In some implementations, if the first request includes information for determining the second PDU session, the method further includes: the second core network device determining the second PDU session based on the first request.

[0179] The above describes several implementation methods of the first request in the embodiment of the present application, several configuration methods of QoS parameters, configuration methods of the second terminal device, configuration methods of the second PDU session, etc. These methods can be arbitrarily combined with each other, and the embodiment of the present application does not limit this. For ease of understanding, the following describes the method for migrating target services in the embodiment of the present application in combination with Examples 1 to 3. Among them, Example 1 introduces the process of the first terminal device triggering the first request in combination with modifying the second PDU session as an example. Example 2 introduces the process of the second terminal device triggering the first request in combination with establishing the second PDU session as an example. Example 3 introduces the process of the second terminal device triggering the first request in combination with multiplexing the first PDU session as an example.

[0180] Example 1, FIG5 shows a schematic flowchart of migrating a target service in an embodiment of the present application. The method shown in FIG5 includes steps S510 to S580. Assume that a user needs to migrate a target service from a first terminal device (also referred to as a "source UE", S-UE) to a second terminal device (also referred to as a "target UE", T-UE).

[0181] In step S510, the first terminal device sends a first request to the access network device, where the first request is used to request the migration of a first QoS flow, the first QoS flow is used to carry the target service, or the first QoS flow is the QoS flow of the first terminal device.

[0182] Generally, the service content is not perceived within the 5G system (5GS). Therefore, for 5GS, the only way to optimize the target service migration is to adjust the scheduling QoS flow. That is to say, for 5GS, the migration of the target service is equivalent to the migration of the QoS flow.

[0183] In some implementations, the first request is used to inform the network device (including the core network device and the access network device) of the second terminal device and the first QoS flow that needs to be migrated. Therefore, the first request includes at least one or more of the following information.

[0184] Information 1: identification information of the first terminal device, wherein the identification information of the first terminal device may be, for example, one or more of the ID of the first terminal device, the IP address of the first terminal device, and the MAC address of the first terminal device.

[0185] Information 2: ID of the first PDU session.

[0186] Information 3: Identification information of the first QoS flow in the first terminal device. The identification information may include, for example, a QFI and / or flow description information. The flow description information may include the source address, destination address, source port number, destination port number, and protocol identifier.

[0187] It should be noted that the first QoS flow may include identifiers of one QoS flow or multiple QoS flows, that is, the QoS flow to be migrated may include one QoS flow or multiple QoS flows.

[0188] Information 4: identification information of the second terminal device, where the identification information of the second terminal device may be, for example, one or more of the ID of the second terminal device, the IP address of the second terminal device, and the MAC address of the second terminal device.

[0189] It should be understood that this information applies to scenarios where a first terminal device can obtain the identification of a second terminal device. For example, the first terminal device is a mobile phone and the second terminal device is a television. Accordingly, the above scenario may include the user pre-binding the television's IP address identification information to the mobile phone. In another example, the first terminal device connects to the second terminal device via Bluetooth, D2D, or other means and obtains the identification information of the second terminal device.

[0190] Information 5 is used to indicate the association relationship between the second terminal device and the first terminal device.

[0191] It should be noted that, assuming that the information used to indicate the association relationship between the second terminal device and the first terminal device has been registered in the contract message stored in the UDM / UDR, one or more of the user identifier (User ID) indicating the association relationship, the group identifier (group ID) indicating the association relationship, and the correlation relationship identifier (correlation ID) indicating the association relationship can also be used to assist the network device (core network device and access network device) in configuring QoS parameters for the second QoS flow used to transmit the target service in the second terminal device. The QoS parameters can be, for example, the same as the QoS parameters of the first QoS flow in the first terminal device, or QoS parameters pre-configured by the QoS parameters.

[0192] Information 6 is used to transmit the QoS parameters corresponding to the QoS flow of the target service.

[0193] Information 7: Application service description information of the target service. The service description information may include application identifier, DNN, S-NSSAI, packet filter, etc.

[0194] Information 8, the second PDU session ID used to transmit the target service in the second terminal device.

[0195] It should be noted that, in the information carried in the above-mentioned first request, information 1 may be a parameter that needs to be included. The combination of information 1 and information 4 or information 5 are two implementation methods of indicating that the two first terminal devices and the second terminal device of the network device have an associated relationship. Information 2 may be a mandatory parameter, used to inform the network device of the first PDU session. Information 3 may be an optional parameter. If this information is not included in the first request, it is considered that all QoS flows in the first PDU session need to be migrated to the second terminal device. Information 6 may be an optional parameter. If this parameter is not included in the first request, after the first QoS flow is migrated to the second PDU session, the QoS parameters may continue to use the QoS parameters of the second QoS flow in the second PDU session. Information 7 or information 8 is used to assist the SMF in determining the second PDU session.

[0196] In step S520, the access network device forwards the received first request to the AMF.

[0197] In step S530, the AMF forwards the received first request to the SMF.

[0198] In step S540, in response to receiving the first request, the SMF determines a second terminal device based on the first request.

[0199] In one implementation, if the first request carries identification information of the second terminal device, the SMF may determine the second terminal device based on the identification information of the second terminal device.

[0200] In one implementation, if the first request carries information indicating an association relationship (for example, a user ID, a group ID, or an association relationship ID), the SMF can determine the second terminal device by querying the signing message, wherein the signing message records the second terminal device associated with the information indicating the association relationship.

[0201] In step S550, the SMF determines the second PDU session.

[0202] For example, if the first request carries the ID of the second PDU session, the SMF can determine the second PDU session by the ID of the second PDU session. For another example, if the first request carries the service description information of the target service (for example, application identifier, DNN, S-NSSAI, IP quintuple), the SMF can determine the second PDU session based on the service description information of the target service.

[0203] In step S560, the SMF configures QoS parameters for the second QoS flow of the second terminal device.

[0204] In some implementations, the SMF configures QoS parameters for the second QoS flow by querying a subscription message, wherein the subscription message includes the QoS parameters associated with the association relationship, or the subscription message includes the QoS parameters associated with the second terminal device.

[0205] In some implementations, if the first request carries QoS parameters for a QoS flow used to transmit the target service, the SMF configures the QoS parameters carried in the first request for the second QoS flow.

[0206] In some implementations, the SMF configures the same QoS parameters for the second QoS flow as the migrated first QoS flow.

[0207] In step S570, the SMF configures N4 rules for the UPF, configures QoS rules and QoS flow-level QoS parameters for the second terminal device, and configures QoS configuration for the access network device so as to map the data packets of the target service to the second QoS flow.

[0208] For example, the SMF sends the N4 rules related to the first QoS flow (e.g., PDRs, URRs, QERs, FARs, etc.) to the UPF. In addition to the above N4 rules, the SMF may also send the identifier QFI and N4 session ID of the second QoS flow to the UPF.

[0209] Afterwards, the SMF sends QoS profiles and / or alternative QoS profiles to the access network device to which the second terminal device is connected. The QoS profiles may include QoS parameters such as 5QI, ARP, RQA, GFBR, and MFBR. In addition, the SMF sends the QFI corresponding to each QoS profile to the access network device.

[0210] Afterwards, the SMF sends the QFI and the QoS rules corresponding to each QFI, and the QoS parameters of the QoS flow level to the second terminal device through the access network device.

[0211] It should be noted that the above step S570 can be implemented by initiating a PDU session modification process through the SMF. In the PDU session modification process, the second terminal device returns a PDU session modification confirmation message to the SMF through the RAN and AMF.

[0212] In addition, one or more of the above-mentioned PDR, QoS rules, and QoS configuration information may be QoS flow configuration parameters with terminal device granularity. Of course, one or more of the above-mentioned PDR, QoS rules, and QoS configuration information may be QoS flow configuration parameters with user granularity, which is not limited in the embodiments of the present application.

[0213] In step S580, in response to receiving the PDU session modification confirmation message, the SMF may initiate a PDU session release process to release the first PDU session. For example, the SMF may release the IP address and UPF resources allocated to the first terminal device. Accordingly, the access network device may release the radio resources allocated to the first terminal device.

[0214] In an embodiment of the present application, on the one hand, a first request is initiated by a first terminal device. At this time, the first request can carry the QoS parameters of the first QoS flow, which helps the second terminal device to obtain the QoS parameters of the first QoS flow to avoid the problem of inconsistent QoS of the target service after cross-terminal migration.

[0215] On the other hand, in an embodiment of the present application, the second terminal device can be determined through pre-configured association information, which helps to avoid the problem of the first terminal device being unable to determine the second terminal device and thus being unable to determine the migration object.

[0216] On the other hand, the first request is initiated by the first terminal device, and the first terminal device can determine the first QoS flow that needs to be migrated. At this time, the first terminal device can directly inform the core network device of the first QoS flow, thereby facilitating the SMF to determine the QoS parameters of the QoS flow that needs to be configured for the second terminal device.

[0217] On the other hand, when a service migration request is initiated through the first terminal device, the first PDU session can be released after the migration process is completed, thereby ensuring the continuity of the target service migrated across terminals.

[0218] Example 2, FIG6 shows a schematic flowchart of migrating a target service in another embodiment of the present application. The method shown in FIG6 includes steps S610 to S690. Assume that a user needs to migrate a target service from a first terminal device (also referred to as a "source UE", S-UE) to a second terminal device (also referred to as a "target UE", T-UE).

[0219] In step S610, the second terminal device sends a first request to the access network device, where the first request is used to request migration of a first QoS flow, the first QoS flow is used to carry the target service, or the first QoS is the QoS flow of the first terminal device.

[0220] Generally, the service content is not perceived within the 5G system (5GS). Therefore, for 5GS, the only way to optimize the target service migration is to adjust the scheduling QoS flow. That is to say, for 5GS, the migration of the target service is equivalent to the migration of the QoS flow.

[0221] In some implementations, the first request may be carried via a PDU session establishment request or a PDU session modification request.

[0222] In some implementations, the first request includes at least one or more of the following information.

[0223] Information 1: identification information of the second terminal device, where the identification information of the second terminal device may be, for example, one or more of the ID of the second terminal device, the IP address of the second terminal device, and the MAC address of the second terminal device.

[0224] Information 2, information used to indicate the association relationship between the second terminal device and the first terminal device.

[0225] Information 3, identification information of the first terminal device, wherein the identification information of the first terminal device may be, for example, one or more of the ID of the first terminal device, the IP address of the first terminal device, and the MAC address of the first terminal device.

[0226] Information 4, second PDU session ID.

[0227] Information 5: Application service description information of the target service. The service description information may include application identifier, DNN, S-NSSAI, packet filter, etc.

[0228] Information 6, device resolution and size of the second terminal device and other information.

[0229] It should be noted that, in the information carried in the above-mentioned first request, information 1 may be a parameter that needs to be included. Information 1 combined with information 3 or information 2 are two implementation methods for indicating that the two first terminal devices and the second terminal device of the network device have an associated relationship. Information 4 may be a parameter that must be included. Information 5 may be an optional parameter, wherein the packet filter can be used to assist in identifying the first QoS flow of the first terminal device, while application identification, DNN, S-NSSAI and other information can be used to identify the first PDU session. Information 6 may be an optional parameter used to assist the SMF in selecting appropriate QoS parameters for the second QoS flow of the second terminal device.

[0230] In step S615, the access network device forwards the received first request to the AMF.

[0231] In step S620, the AMF finds the target SMF based on one or more information of DNN, S-NSSAI, and User ID.

[0232] In step S625, the AMF forwards the first request to the target SMF.

[0233] In step S630, the SMF determines the QoS parameters of the second QoS flow of the second terminal device.

[0234] For example, if the first request only carries the first terminal device identifier and the second terminal device identifier, the SMF determines the first PDU session and the first QoS flow, thereby determining the first QoS flow and its corresponding QoS parameters.

[0235] For another example, if the first request carries identification information for indicating the association relationship, and the correspondence between the identification information for indicating the association relationship and the QoS parameters of the target service is registered in the core network network element (such as SMF, UDM, UDR), then the SMF can obtain the N4 rules corresponding to the association relationship locally, or the SMF can obtain the QoS parameters corresponding to the target service from the core network network elements such as UDM and PCF.

[0236] For example, if the first request includes the resolution size information of the second terminal device, and the mapping relationship between the device resolution size information and the QoS parameters is configured in the SMF local or the second terminal device's contract message, the SMF can also derive the QoS parameters of the second QoS flow of the second terminal device based on this.

[0237] It should be noted that if the SMF does not have the corresponding session management contract information locally, the SMF can obtain it from the UDM.

[0238] In step S635, the SMF returns a response message to the AMF for the first request, where the response message indicates whether the SMF is capable of processing the first request. If the first request is rejected, the SMF may include the reason for rejecting the first request in the response message.

[0239] In step S640, the SMF may perform security authentication and authorization by triggering a secondary authentication process to confirm that the first terminal device and the second terminal device belong to the same user.

[0240] For example, when the first request contains the ID of the first terminal device and the ID of the second terminal device, the SMF can trigger a secondary authentication process to perform security authentication and authorization, and confirm that the first terminal device and the second terminal device belong to the same user. For another example, when the first request contains the identifier and user ID of the second terminal device, the SMF can trigger a secondary authentication process to perform security authentication and authorization, and confirm that the first terminal device belongs to the user.

[0241] In step S645, the SMF allocates an IP address for the second PDU session. The IP address can be one of a set of IP addresses corresponding to the User ID. The address set can be pre-configured on a core network element such as the SMF, or stored in the UDM as a user subscription message.

[0242] In some scenarios, if the first request carries information such as DNN / S-NSSAI and User ID, SMF can determine PCF and PSA UPF based on the first request.

[0243] In step S650, the SMF sends a second request to the PCF to request policy information associated with the target service.

[0244] In some implementations, the second request carries the user ID, the ID of the second terminal device, and the second PDU session allocated IP address.

[0245] In step S655, the PCF sends a response message to the second request to the SMF, where the response message to the second request carries the PCC rule corresponding to the target service.

[0246] It should be noted that the above steps S650 and S655 can be performed in an SMF initiated SM Policy Association Modification procedure.

[0247] In step S660, the SMF sends an N4 session establishment or modification request for the second PDU session to the UPF.

[0248] In some implementations, the SMF provides the UPF with the N4 rules for the second PDU session. In addition, if the SMF is configured to request the UPF to allocate an address, the SMF instructs the UPF to perform the address allocation. The UPF also provides the SMF with the CN Tunnel Info.

[0249] In step S665, the SMF sends an N1N2 message (Namf_Communication_N1N2MessageTransfer) to the AMF. This N1N2 message carries the QoS configuration, QoS rules, QoS flow-level QoS parameters, QFIs associated with the QoS flow-level QoS parameters, and the user identity. In addition, the SMF also provides the CN Tunnel Info to the RAN.

[0250] In step S670, the AMF sends an N2 PDU session request to the access network device, which carries the information in step S665.

[0251] In step S675, the access network device exchanges signaling with the second terminal device and performs an AN-specific resource setup procedure. During this procedure, radio resources are allocated for the second PDU session, and QoS rules and flow-level QoS parameters, along with their associated QFIs and User ID, are sent to the UE. AN tunnel information is also allocated for the PDU session.

[0252] In step S680, the RAN sends an N2 PDU session response to the AMF, where the N2 PDU session response carries the AN tunnel information.

[0253] In step S685, the AMF provides the AN tunnel information (Tunnel Info) to the SMF. The AN tunnel information may be carried in the Nsmf_PDUSession_CreateSMContext Request.

[0254] In step S690, the SMF provides the AN tunnel information to the UPF. The AN Tunnel Info may be carried in the N4 session establishment or modification request (N4 Session Establishment / Modification).

[0255] In an embodiment of the present application, the first request is triggered by the second terminal device and the second PDU session is established. The configuration of the QoS parameters can be completed directly during the first PDU session establishment and modification process initiated by the second terminal device, thereby eliminating the need to wait for the target service to be migrated and then for the network device to initiate the PDU session modification process for the second time to adjust the QoS parameters of the second QoS flow. This reduces the signaling interaction process for configuring the QoS parameters while ensuring the stability of the QoS of the target service to be migrated.

[0256] Example 3, FIG7 shows a schematic flowchart of migrating a target service in another embodiment of the present application. The method shown in FIG7 includes steps S710 to S790. Assume that a user needs to migrate a target service from a first terminal device (also referred to as a "source UE", S-UE) to a second terminal device (also referred to as a "target UE", T-UE), and the first terminal device and the second terminal device are connected to the same access network device.

[0257] In step S710, the second terminal device sends a first request to the access network device, where the first request is used to request migration of a first QoS flow, where the first QoS flow is used to carry a target service, or the first QoS flow is a QoS flow of the first terminal device.

[0258] Generally, the service content is not perceived within the 5G system (5GS). Therefore, for 5GS, the only way to optimize the target service migration is to adjust the scheduling QoS flow. That is to say, for 5GS, the migration of the target service is equivalent to the migration of the QoS flow.

[0259] In some implementations, the first request may be carried via a PDU session establishment request or a PDU session modification request.

[0260] In some implementations, the first request includes at least one or more of the following information.

[0261] Information 1: identification information of the second terminal device, where the identification information of the second terminal device may be, for example, one or more of the ID of the second terminal device, the IP address of the second terminal device, and the MAC address of the second terminal device.

[0262] Information 2, information used to indicate the association relationship between the second terminal device and the first terminal device.

[0263] Information 3, identification information of the first terminal device, wherein the identification information of the first terminal device may be, for example, one or more of the ID of the first terminal device, the IP address of the first terminal device, and the MAC address of the first terminal device.

[0264] Information 4, the second PDU session ID used to transmit the target service in the second terminal device.

[0265] Information 5: Application service description information of the target service. The service description information may include application identifier, DNN, S-NSSAI, packet filter, etc.

[0266] Information 6, device resolution and size of the second terminal device and other information.

[0267] It should be noted that, in the information carried in the above-mentioned first request, information 1 may be a parameter that needs to be included. Information 1 combined with information 3 or information 2 are two implementation methods for indicating that the two first terminal devices and the second terminal device of the network device have an associated relationship. Information 4 may be a parameter that must be included. Information 5 may be an optional parameter, wherein the packet filter can be used to assist in identifying the first QoS flow of the first terminal device, while application identification, DNN, S-NSSAI and other information can be used to identify the first PDU session. Information 6 may be an optional parameter used to assist the SMF in selecting appropriate QoS parameters for the second QoS flow of the second terminal device.

[0268] In step S720, the access network device configures QoS parameters for the second QoS flow of the second terminal device. For example, the access network device may directly assign QoS configuration information associated with the association relationship to the second QoS flow of the second terminal device.

[0269] In step S730, the access network device sends the identification information of the second terminal device carried in the first request and the information indicating the association relationship (user identification information) to the AMF.

[0270] In step S740, AMF sends the identification information of the second terminal device and information indicating the association relationship (user identification information) to SMF.

[0271] In step S750, the SMF allocates an IP address to the second terminal device.

[0272] In some implementations, the IP address of the second terminal device may be the same as the IP address of the first terminal device. Alternatively, the IP address of the second terminal device may be different from the IP address of the first terminal device. Alternatively, the IP address of the second terminal device may be part of an address segment allocated by the SMF to the user to which the second terminal device belongs.

[0273] In addition, the SMF configures the N4 rule for the PSA UPF corresponding to the second PDU session ID or DNN, S-NSSAI. Specifically, the SMF can update the source IP address information and destination IP address information in the N4 rule associated with the first terminal device to the IP address information of the second terminal device.

[0274] It should be noted that if the IP address of the second terminal device is the same as the IP address of the first terminal device, or the IP address of the second terminal device can be part of the address segment allocated by the SMF to the user to which the second terminal device belongs, the above-mentioned process of updating the source IP address information and destination IP address information in the N4 rule to the IP address information of the second terminal device can be omitted.

[0275] In step S760, SMF sends QoS rules, QoS parameters, and the IP address of the second terminal device to the access network device through AMF.

[0276] In step S770, the access network device sends QoS rules, QoS parameters, and the IP address of the second terminal device to the second terminal device.

[0277] In step S780, the second terminal device and the access network device establish air interface resources for carrying the target service through signaling interaction.

[0278] In step S790, the access network device releases the air interface resources allocated to the first terminal device for migrating the target service.

[0279] In this application example, when the first terminal device and the second terminal device are served by the same access network, the same PDU session can be used. In this case, there is no need to re-establish a new GTP-U tunnel for the second terminal device, that is, the user plane path between the PSA UPF and the access network device, nor is there any need to re-bind the QoS parameters for the QoS flow in the PDU session. Instead, only the wireless bearer of the air interface needs to be updated to quickly establish a user plane data transmission channel for the second terminal device, thereby reducing the time required for cross-terminal migration of the target service.

[0280] As described above, in some scenarios, the QoS parameters of the QoS flow used to transmit the target service can be provided by the AF. For example, the AF can provide the QoS parameters during the process of establishing the AF session. The following, in conjunction with Figure 8, takes the QoS parameters associated with the user as an example to introduce the process of establishing the AF session in an embodiment of the present application. Figure 8 is a schematic diagram of the process of establishing the AF session in an embodiment of the present application. The method shown in Figure 8 includes steps S810 to S811.

[0281] In step S810 , the AF sends a request 1 to the NEF to request to reserve resources for the AF session.

[0282] In some implementations, request 1 may include the user identifier of the target user, the address information of the terminal device that the target user is using or has used (including IP address and / or MAC address), AF identifier, flow description information, QoS reference or separate QoS parameters, or PDU set QoS parameters, protocol description information, alternative target service requirements and other information.

[0283] In some implementations, the request 1 may be a request to create an AF session with QoS parameters (also referred to as “Nnef_AFsessionWithQoS_Create request”) or a request to update an AF session with QoS parameters (“Nnef_AFsessionWithQoS_Update”).

[0284] In step S820, the NEF authorizes request 1, generates a transaction reference ID for the AF session, and associates (or binds) the transaction reference ID with the target user's user ID and the address of the target user's associated terminal device. If authorization fails, step S850 is executed.

[0285] In step S830, if the authorization is successful, the NEF can use the user ID of the target user or the address information of the terminal device to discover the PCF through the BSF, and forward the user ID of the target user, QoS parameters and other information carried in the request 1 to the PCF.

[0286] In some implementations, the above information interaction between the PCF and the NEF may be carried through a policy authorization creation request (Npcf_PolicyAuthorization_Create request).

[0287] It should be noted that if the AF is a trusted AF, the request 1 may be directly sent to the PCF without being forwarded through the NEF.

[0288] In step S840, the PCF confirms whether to authorize the request and notifies the NEF or AF if not. If the request is authorized, the PCF derives the QoS parameters required by the PCC rules based on the information provided by the NEF or AF, determines whether to allow this QoS (based on PCF configuration), and notifies the NEF or directly to the trusted AF of the result.

[0289] In some implementations, the above information interaction between the PCF and the NEF or AF may be carried in a policy authorization creation response (Npcf_PolicyAuthorization_Create response).

[0290] In step S850, the NEF returns a request response message to the AF, where the response message includes the Transaction Reference ID, the User ID, and the authorization result. In some implementations, the request response message may be Nnef_AFsessionWithQoS_Create response.

[0291] In step S860, the NEF sends a subscription request to the PCF to subscribe to the resource allocation status and specific events of the terminal device associated with the target user. In some implementations, the subscription request can be Npcf_PolicyAuthorization_Subscribe. In some implementations, the subscription request can carry the user ID of the target user.

[0292] In step S870, when the preset conditions are met, the PCF sends a notification message 1 to the NEF, which carries the event subscribed by the NEF. The notification message is also called "Npcf_PolicyAuthorization_Notify".

[0293] In some implementations, the preset condition may include when the establishment of the transmission resource corresponding to the QoS update is successful or failed. In addition, the notification message 1 may carry a user identifier of the target user.

[0294] In step S880, the NEF sends a notification message 2 to the AF, which carries the event to which the NEF subscribes. The notification message is also called "Nnef_AFsessionWithQoS_Notify." In addition, the notification message 2 may carry the user ID of the target user.

[0295] In an embodiment of the present application, a method is provided for the AF to configure QoS parameters based on the target user for the network, so as to configure the QoS parameters of the second QoS flow based on the QoS parameters associated with the target user.

[0296] In addition, in this embodiment of the present application, when executing the binding mechanism (see step S820), the AF session of this embodiment can be bound to the second PDU session of the second terminal device (which can be a newly established PDU session or the first PDU session of the triple-multiplexed example). Subsequently, the QoS parameters based on the target user are configured for the QoS flow carrying the target service through the PCC rule authorization and QoS flow binding mechanism.

[0297] It should be noted that the above-mentioned AF session can be understood as an AF session based on the target user. The AF session can be bound to the PDU session established with the target user, thereby avoiding the large amount of signaling overhead and delay caused by the need for multiple terminal devices associated with the same user to bind multiple PDU sessions established for the same target service to multiple AF sessions.

[0298] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 8 . The device embodiment of the present application is described in detail below in conjunction with Figures 9 to 13 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for portions not described in detail, reference can be made to the above method embodiment.

[0299] FIG9 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device shown in FIG9 is a target terminal device, and the terminal device 900 includes a sending unit 910 .

[0300] The sending unit 910 is used to send a first request to the network device, where the first request is used to request to migrate the target service from the first terminal device to the second terminal device; wherein the target terminal device is the first terminal device or the second terminal device.

[0301] In some implementations, the first request includes one or more of the following information: information indicating the first terminal device; information indicating the second terminal device; information determining a second PDU session; and information indicating an association relationship between the first terminal device and the second terminal device.

[0302] In some implementations, if the first request includes information indicating the first terminal device, the information indicating the first terminal device includes an identifier of the first terminal device and / or address information of the first terminal device.

[0303] In some implementations, if the first request includes information indicating the second terminal device, the information indicating the second terminal device includes an identifier of the second terminal device and / or address information of the second terminal device.

[0304] In some implementations, if the first request includes information indicating the association relationship, the information indicating the association relationship includes one or more of the following: identification information of a terminal group to which the first terminal device and the second terminal device belong;

[0305] Identification information of users to whom the first terminal device and the second terminal device belong; identification information of the association relationship between the first terminal device and the second terminal device.

[0306] In some implementations, if the first request includes information for indicating the second PDU session, the information for indicating the second PDU session includes: application service description information of the target service, and / or, an identifier of the second PDU session.

[0307] In some implementations, if the target device is the first terminal device, the first request includes one or more of the following information: information indicating a first PDU session; information indicating a first QoS flow; and QoS parameters of the QoS flow transmitting the target service.

[0308] In some implementations, the first request includes the information indicating the first QoS flow, and the information indicating the first QoS flow includes: an identifier QFI of the first QoS flow, and / or flow description information of the first QoS flow.

[0309] In some implementations, if the first request includes information indicating the first PDU session, the information indicating the first PDU session includes: an identifier of the first PDU session.

[0310] In some implementations, if the target terminal device is the first terminal device, the first request is used to request migration of the first QoS flow from the first terminal device to the second terminal device.

[0311] In some implementations, if the target device is the second terminal device, the first request includes resolution information of the second terminal device.

[0312] In some implementations, the resolution information of the second terminal device is used to determine QoS parameters of a second QoS flow of the second terminal device.

[0313] In some implementations, if the target terminal device is the second terminal device, the first request is carried in a PDU session establishment request, and the PDU session request is used to request to establish a PDU session for the target service; or the first request is carried in a PDU session modification request, and the PDU session request is used to request to modify the PDU session used to transmit the target service.

[0314] In some implementations, the PDU session used by the first terminal device to transmit the target service is the same as the PDU session used by the second terminal device to transmit the target service, or the QoS parameters of the first QoS flow used by the first terminal device to transmit the target service are the same as the QoS parameters of the second QoS flow, or the QoS configuration of the first QoS flow of the first terminal device is the same as the QoS configuration of the second QoS flow of the second terminal device.

[0315] In some implementations, if the first PDU session is the same as the second PDU session, the network device accessed by the first terminal device is the same as the network device accessed by the second terminal device.

[0316] In some implementations, the address information of the first terminal device is the same as the address information of the second terminal device; or the address information of the first terminal device is different from the address information of the second terminal device.

[0317] In some implementations, the first terminal device and the second terminal device have the same user, and the QoS parameters of the target service are associated with the user.

[0318] In some implementations, the QoS flow used to transmit the target service is part or all of the QoS flows in the associated PDU session.

[0319] FIG10 is a schematic diagram of a network device according to an embodiment of the present application. The network device 1000 shown in FIG10 includes a receiving unit 1010 .

[0320] The receiving unit 1010 is configured to receive a first request sent by a target terminal device, where the first request is used to request migration of a target service from the first terminal device to the second terminal device; wherein the target terminal device is the first terminal device or the second terminal device.

[0321] In some implementations, the first request includes one or more of the following information: information indicating the first terminal device; information indicating the second terminal device; information determining a second PDU session; and information indicating an association relationship between the first terminal device and the second terminal device.

[0322] In some implementations, if the first request includes information indicating the first terminal device, the information indicating the first terminal device includes an identifier of the first terminal device and / or address information of the first terminal device.

[0323] In some implementations, if the first request includes information indicating the second terminal device, the information indicating the second terminal device includes an identifier of the second terminal device and / or address information of the second terminal device.

[0324] In some implementations, if the first request includes information for indicating the association relationship, the information for indicating the association relationship includes one or more of the following: indication information of the terminal group to which the first terminal device and the second terminal device belong; indication information of the users to which the first terminal device and the second terminal device belong; and identification information of the association relationship between the first terminal device and the second terminal device.

[0325] In some implementations, if the first request includes information for indicating the second PDU session, the information for indicating the second PDU session includes: application service description information of the target service, and / or, an identifier of the second PDU session.

[0326] In some implementations, if the target device is the first terminal device, the first request includes one or more of the following information: information indicating a first PDU session; information indicating a first QoS flow; and QoS parameters of the QoS flow transmitting the target service.

[0327] In some implementations, the first request includes the information indicating the first QoS flow, and the information indicating the first QoS flow includes: an identifier QFI of the first QoS flow, and / or flow description information of the first QoS flow.

[0328] In some implementations, if the first request includes information indicating the first PDU session, the information indicating the first PDU session includes: an identifier of the first PDU session.

[0329] In some implementations, if the target terminal device is the first terminal device, the first request is used to request migration of the first QoS flow from the first terminal device to the second terminal device.

[0330] In some implementations, if the target device is the second terminal device, the first request includes resolution information of the second terminal device.

[0331] In some implementations, the resolution information of the second terminal device is used to determine QoS parameters of a second QoS flow for transmitting the target service by the second terminal device.

[0332] In some implementations, if the network device is a second core network device, the network device further includes: a first processing unit, configured to configure QoS parameters for a second QoS flow of the second terminal device.

[0333] In some implementations, the network device further includes: a first acquisition unit, configured to acquire contract information, wherein the contract information records QoS parameters of the QoS flow used to transmit the target service; and the first processing unit, configured to configure QoS parameters for the second QoS flow based on the contract information.

[0334] In some implementations, the contract information is contract information associated with a target user, the QoS parameters carried by the contract information are associated with the target user, and the target user is a common user of the first terminal device and the second terminal device; or the contract information is contract information of the second terminal device, and the QoS parameters carried by the contract information are associated with the second terminal device.

[0335] In some implementations, if the first request carries QoS parameters of a QoS flow transmitting the target service, the first processing unit is configured to configure QoS parameters for the second QoS flow based on the first request.

[0336] In some implementations, the first processing unit is used to: obtain a first QoS parameter, which is a QoS parameter of a first QoS flow used by the first terminal device to transmit the target service; and configure QoS parameters for a second QoS flow of the second terminal device based on the first QoS parameter.

[0337] In some implementations, if the first request includes information for indicating the first terminal device and information for indicating the second terminal device, the network device further includes: a second processing unit for determining the first QoS flow of the first terminal device based on the information for indicating the first terminal device; and determining the QoS parameters of the first QoS flow; the first processing unit is used for the second core network device to configure QoS parameters for the second QoS flow based on the QoS parameters of the first QoS flow.

[0338] In some implementations, if the first request includes information indicating an association relationship between the first terminal device and the second terminal device, the network device further includes: a third processing unit, configured to determine QoS parameters corresponding to the association relationship based on the association relationship; and the first processing unit, configured to configure QoS parameters for the second QoS flow of the second terminal device based on the QoS parameters corresponding to the association relationship.

[0339] In some implementations, if the first request includes resolution information of the second terminal device, the network device also includes: a fourth processing unit, used to determine the QoS parameters corresponding to the resolution information of the second terminal device based on the resolution information of the second terminal device and the correspondence between the pre-stored resolution information and the QoS parameters; the first processing unit, used to configure QoS parameters for the second QoS flow of the second terminal device based on the QoS parameters corresponding to the resolution information of the second terminal device.

[0340] In some implementations, the network device further includes: a fifth processing unit, configured to allocate address information for the second PDU session.

[0341] In some implementations, the network device further includes: a first sending unit, configured to send a second request to a fourth core network device, wherein the second request is used to request the PCC rule for transmitting the target service; and a receiving unit, configured to receive a response message sent by the fourth core network device to the second request, wherein the response message carries the PCC rule.

[0342] In some implementations, the second request carries information indicating the second terminal device and / or address information of the second PDU session.

[0343] In some implementations, the network device further includes: a sixth processing unit, configured to configure the N4 rule corresponding to the second QoS flow and / or the QoS rule corresponding to the second QoS flow for the third core network device.

[0344] In some implementations, the N4 rule corresponding to the second QoS flow and / or the QoS rule corresponding to the second QoS flow are carried in a PDU session modification request, and the PDU session modification request is used to request modification of the PDU session used to transmit the target service.

[0345] In some implementations, the N4 rules corresponding to the second QoS flow include one or more of the following: packet monitoring rules, forwarding operation rules, QoS enforcement rules, and usage reporting rules.

[0346] In some implementations, the network device further includes: a second sending unit, configured to send the QoS configuration of the second QoS flow and / or the alternative QoS configuration of the second QoS flow to an access network device serving the second terminal device.

[0347] In some implementations, the network device further includes: a seventh processing unit, configured to configure QoS rules of the second QoS flow for the second terminal device.

[0348] In some implementations, the first PDU session is the same as the second PDU session, or the QoS parameters of the first QoS flow of the first terminal device are the same as the QoS parameters of the second QoS flow of the second terminal device, or the QoS configuration of the first QoS flow of the first terminal device is the same as the QoS configuration of the second QoS flow of the second terminal device.

[0349] In some implementations, if the first PDU session is the same as the second PDU session, the access network device of the first terminal device is the same as the access network device of the second terminal device.

[0350] In some implementations, the network device is the access network device, and the network device further includes: a second acquisition unit, used to acquire information indicating the association relationship between the first terminal device and the second terminal device; an eighth processing unit, used to determine the QoS configuration associated with the information indicating the association relationship based on the information indicating the association relationship; and configure a second QoS flow for the second terminal device based on the QoS configuration associated with the information indicating the association relationship.

[0351] In some implementations, if the network device is a second core network device, the network device includes: in response to receiving the first request, a ninth processing unit, for allocating address information to the second terminal device, wherein the address information of the second terminal device satisfies one of the following: the address information of the second terminal device is the same as the address information of the first terminal device; the address information of the second terminal device is different from the address information of the first terminal device; the address information of the second terminal device belongs to a target address information segment, the target address information segment is associated with a target user, and the target user is a common user of the first terminal device and the second terminal device.

[0352] In some implementations, if the target terminal device is the second terminal device, the first request is carried in a PDU session establishment request, and the PDU session request is used to request to establish a PDU session for the target service; or the first request is carried in a PDU session modification request, and the PDU session request is used to request to modify the PDU session used to transmit the target service.

[0353] In some implementations, if the network device is a first core network device, the network device further includes: a second sending unit, configured to receive the first request sent by the target terminal device through an access network device.

[0354] In some implementations, the network device further includes: a third sending unit, configured to send the first request to the second core network device.

[0355] In some implementations, the target terminal device is the first terminal device, and the network device is a second core network device, and the network device further includes: in response to receiving the first request, a tenth processing unit is used to determine the second terminal device.

[0356] In some implementations, if the first request carries information indicating an association relationship between the first terminal device and the second terminal device, the tenth processing unit is used to determine, based on the association relationship, that the terminal device having the association relationship with the first terminal device is the second terminal device.

[0357] In some implementations, if the first request carries information indicating the second terminal device, the tenth processing unit is configured to determine the second terminal device based on the information indicating the second terminal device.

[0358] In some implementations, if the first request includes information for determining a second PDU session, the network device further includes: an eleventh processing unit, configured to determine the second PDU session based on the first request.

[0359] In some implementations, the QoS flow used to transmit the target service is part or all of the QoS flows in the associated PDU session.

[0360] FIG11 is a schematic diagram of a network device according to another embodiment of the present application. The network device shown in FIG11 is a fifth core network device, and the network device 1100 includes a sending unit 1110 .

[0361] The sending unit 1110 is used to send target information to the sixth core network device, where the target information is used to indicate the QoS parameters associated with the user, and the user is associated with one or more terminal devices.

[0362] In some implementations, the third information is carried in a third request, wherein the third request is used to request the creation of an AF session with QoS; or the third request is used to request the update of an AF session with QoS.

[0363] In some implementations, the user-associated QoS parameters are used when the user's target service is migrated between multiple terminal devices associated with the user.

[0364] Figure 12 is a schematic diagram of a network device according to another embodiment of the present application. The network device shown in Figure 12 is a sixth core network device. The network device 1200 includes: a receiving unit 1210.

[0365] The receiving unit 1210 is used to receive target information sent by the fifth core network device, where the target information is used to indicate QoS parameters associated with a user, and the user is associated with one or more terminal devices.

[0366] In some implementations, the third information is carried in a third request, wherein the third request is used to request the creation of an AF session with QoS; or the third request is used to request the update of an AF session to be provided with QoS.

[0367] In some implementations, the network device further includes: in response to receiving the third request, a first processing unit, used to associate the transaction reference identifier of the AF session with the user identifier of the user; and a first sending unit, used to send a response message to the third request to the fifth core network device, the response message carrying the transaction reference identifier of the AF session and the user identifier of the user.

[0368] In some implementations, the method further includes: a second sending unit, configured to send a fourth request for requesting PCC rules to a fourth core network device, wherein the fourth request carries a user identifier of the user and the QoS parameter.

[0369] Figure 13 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 13 indicate that the unit or module is optional. Apparatus 1300 may be used to implement the method described in the above method embodiment. Apparatus 1300 may be a chip, a terminal device, or a network device.

[0370] The device 1300 may include one or more processors 1310. The processor 1310 may support the device 1300 to implement the method described in the above method embodiment. The processor 1310 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0371] The apparatus 1300 may further include one or more memories 1320. The memories 1320 store programs that can be executed by the processor 1310, causing the processor 1310 to perform the methods described in the above method embodiments. The memories 1320 may be independent of the processor 1310 or integrated into the processor 1310.

[0372] The apparatus 1300 may further include a transceiver 1330. The processor 1310 may communicate with other devices or chips via the transceiver 1330. For example, the processor 1310 may transmit and receive data with other devices or chips via the transceiver 1330.

[0373] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0374] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0375] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or network device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0376] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0377] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0378] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0379] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0380] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0381] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0382] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0383] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0384] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0385] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0386] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0387] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0388] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A wireless communication method, characterized in that: include: The target terminal device sends a first request to the network device, where the first request is used to request to migrate the target service from the first terminal device to the second terminal device; The target terminal device is a first terminal device or a second terminal device.

2. The method according to claim 1, characterized in that The first request includes one or more of the following information: Information used to indicate the first terminal device; Information used to indicate the second terminal device; Information for determining a second PDU session; Information used to indicate the association relationship between the first terminal device and the second terminal device.

3. The method according to claim 2, characterized in that If the first request includes information for indicating the first terminal device, the information for indicating the first terminal device includes an identifier of the first terminal device and / or address information of the first terminal device.

4. The method according to claim 2 or 3, characterized in that If the first request includes information for indicating the second terminal device, the information for indicating the second terminal device includes an identifier of the second terminal device and / or address information of the second terminal device.

5. The method according to any one of claims 2 to 4, characterized in that: If the first request includes information for indicating the association relationship, the information for indicating the association relationship includes one or more of the following: identification information of the terminal group to which the first terminal device and the second terminal device belong; Identification information of users to which the first terminal device and the second terminal device belong; Identification information of the association relationship between the first terminal device and the second terminal device.

6. The method according to any one of claims 2 to 5, characterized in that: If the first request includes information for indicating the second PDU session, the information for indicating the second PDU session includes: application service description information of the target service, and / or an identifier of the second PDU session.

7. The method according to any one of claims 1 to 6, characterized in that If the target device is the first terminal device, the first request includes one or more of the following information: Information used to indicate the first PDU session; Information used to indicate the transmission of the first QoS flow; as well as The QoS parameters of the QoS flow transmitting the target service.

8. The method according to claim 7, characterized in that The first request includes the information indicating the first QoS flow, and the information indicating the first QoS flow includes: an identifier QFI of the first QoS flow, and / or flow description information of the first QoS flow.

9. The method according to claim 7 or 8, characterized in that If the first request includes information for indicating the first PDU session, the information for indicating the first PDU session includes: an identifier of the first PDU session.

10. The method according to any one of claims 1 to 9, characterized in that If the target terminal device is the first terminal device, the first request is used to request migration of the first QoS flow from the first terminal device to the second terminal device.

11. The method according to any one of claims 1 to 6, characterized in that If the target device is the second terminal device, the first request includes resolution information of the second terminal device.

12. The method according to claim 11, characterized in that The resolution information of the second terminal device is used to determine the QoS parameters of the second QoS flow.

13. The method according to any one of claims 1 to 6 and 11, characterized in that: If the target terminal device is the second terminal device, the first request is carried in a PDU session establishment request, and the PDU session request is used to request to establish a PDU session for the target service; or The first request is carried in a PDU session modification request, and the PDU session request is used to request modification of a PDU session used to transmit the target service.

14. The method according to any one of claims 1 to 13, characterized in that The first PDU session of the first terminal device is the same as the second PDU session of the second terminal device, or The QoS parameters of the first QoS flow of the first terminal device are the same as the QoS parameters of the second QoS flow of the second terminal device, or The QoS configuration of the first QoS flow of the first terminal device is the same as the QoS configuration of the second QoS flow of the second terminal device.

15. The method according to claim 14, characterized in that If the first PDU session is the same as the second PDU session, the network device accessed by the first terminal device is the same as the network device accessed by the second terminal device.

16. The method according to claim 15, characterized in that The address information of the first terminal device is the same as the address information of the second terminal device; or The address information of the first terminal device is different from the address information of the second terminal device.

17. The method according to any one of claims 1 to 16, characterized in that The user of the first terminal device and the second terminal device is the same, and the QoS parameter of the target service is associated with the user.

18. The method according to any one of claims 1 to 17, characterized in that The QoS flow used to transmit the target service is part or all of the QoS flows in the associated PDU session.

19. A wireless communication method, characterized in that: include: The network device receives a first request sent by a target terminal device, where the first request is used to request migration of a target service from the first terminal device to a second terminal device; The target terminal device is a first terminal device or a second terminal device.

20. The method of claim 19, wherein: The first request includes one or more of the following information: Information used to indicate the first terminal device; Information used to indicate the second terminal device; Information for determining a second PDU session; Information used to indicate the association relationship between the first terminal device and the second terminal device.

21. The method of claim 20, wherein: If the first request includes information for indicating the first terminal device, the information for indicating the first terminal device includes an identifier of the first terminal device and / or address information of the first terminal device.

22. The method according to claim 20 or 21, characterized in that If the first request includes information for indicating the second terminal device, the information for indicating the second terminal device includes an identifier of the second terminal device and / or address information of the second terminal device.

23. The method according to any one of claims 20 to 22, characterized in that If the first request includes information for indicating the association relationship, the information for indicating the association relationship includes one or more of the following: Indicative information of the terminal group to which the first terminal device and the second terminal device belong; Indicative information of users to which the first terminal device and the second terminal device belong; Identification information of the association relationship between the first terminal device and the second terminal device.

24. The method according to any one of claims 20 to 23, characterized in that If the first request includes information for indicating the second PDU session, the information for indicating the second PDU session includes: application service description information of the target service, and / or an identifier of the second PDU session.

25. The method according to any one of claims 19 to 24, characterized in that If the target device is the first terminal device, the first request includes one or more of the following information: Information used to indicate the first PDU session; Information of the first QoS flow; as well as The QoS parameters of the QoS flow transmitting the target service.

26. The method of claim 25, wherein: The first request includes the information indicating the first QoS flow, and the information indicating the first QoS flow includes: an identifier QFI of the first QoS flow, and / or flow description information of the first QoS flow.

27. The method according to claim 25 or 26, characterized in that If the first request includes information for indicating the first PDU session, the information for indicating the first PDU session includes: an identifier of the first PDU session.

28. The method according to any one of claims 19 to 27, characterized in that If the target terminal device is the first terminal device, the first request is used to request migration of the first QoS flow from the first terminal device to the second terminal device.

29. The method according to any one of claims 19 to 24, characterized in that If the target device is the second terminal device, the first request includes resolution information of the second terminal device.

30. The method of claim 29, wherein: The resolution information of the second terminal device is used to determine the QoS parameters of the second QoS flow of the target service transmitted by the second terminal device.

31. The method according to any one of claims 19 to 30, characterized in that If the network device is a second core network device, the method further includes: The second core network device configures QoS parameters for the second QoS flow of the second terminal device.

32. The method of claim 31, wherein: The method further comprises: The second core network device obtains the subscription information, wherein the subscription information records the QoS of the QoS flow used to transmit the target service. parameter; The second core network device configures QoS parameters for the second QoS flow of the second terminal device, including: The second core network device configures QoS parameters for the second QoS flow based on the subscription information.

33. The method of claim 32, wherein: The contract information is contract information associated with a target user, the QoS parameter carried in the contract information is associated with the target user, and the target user is a common user of the first terminal device and the second terminal device; or The subscription information is the subscription information of the second terminal device, and the QoS parameters carried by the subscription information are associated with the second terminal device.

34. The method of claim 31, wherein: If the first request carries the QoS parameters of the QoS flow for transmitting the target service, the second core network device configures the QoS parameters for the second QoS flow of the second terminal device, including: The second core network device configures QoS parameters for the second QoS flow based on the first request.

35. The method of claim 31, wherein: The second core network device configures QoS parameters for the second QoS flow of the second terminal device, including: The second core network device obtains a first QoS parameter, where the first QoS parameter is a QoS parameter used by the first terminal device to transmit the target service; The second core network device configures QoS parameters for the second QoS flow of the second terminal device based on the first QoS parameters.

36. The method of claim 31, wherein: If the first request includes information for indicating the first terminal device and information for indicating the second terminal device, the method further includes: The second core network device determines, based on the information indicating the first terminal device, a first QoS flow in the first terminal device for transmitting the target service; The second core network device determines a QoS parameter of the first QoS flow; The second core network device configures QoS parameters for the second QoS flow of the second terminal device, including: The second core network device configures QoS parameters for the second QoS flow based on the QoS parameters of the first QoS flow.

37. The method of claim 31, wherein: If the first request includes information indicating an association relationship between the first terminal device and the second terminal device, the method further includes: The second core network device determines, based on the association relationship, a QoS parameter corresponding to the association relationship; The second core network device configures QoS parameters for the second QoS flow of the second terminal device, including: The second core network device configures QoS parameters for the second QoS flow of the second terminal device based on the QoS parameters corresponding to the association relationship.

38. The method of claim 31, wherein: If the first request includes resolution information of the second terminal device, the method further includes: The second core network device determines the QoS parameter corresponding to the resolution information of the second terminal device based on the resolution information of the second terminal device and the pre-stored correspondence between the resolution information and the QoS parameter; The second core network device configures QoS parameters for the second QoS flow of the second terminal device, including: The second core network device configures QoS parameters for the second QoS flow of the second terminal device based on the QoS parameters corresponding to the resolution information of the second terminal device.

39. The method according to any one of claims 19 to 38, characterized in that The method further comprises: The second core network device allocates address information to the second PDU session.

40. The method according to any one of claims 19 to 38, wherein: The method further comprises: The second core network device sends a second request to a fourth core network device, where the second request is used to request a PCC rule for transmitting the target service; The second core network device receives a response message sent by the fourth core network device to the second request, where the response message carries the PCC rule.

41. The method of claim 40, wherein: The second request carries information indicating the second terminal device and / or address information of the second PDU session.

42. The method according to any one of claims 19 to 41, characterized in that The method further comprises: The second core network device configures the N4 rule corresponding to the second QoS flow and / or the QoS rule corresponding to the second QoS flow for the third core network device.

43. The method of claim 42, wherein: The N4 rule corresponding to the second QoS flow and / or the QoS rule corresponding to the second QoS flow are carried in a PDU session modification request, and the PDU session modification request is used to request modification of the PDU session used to transmit the target service.

44. The method of claim 43, wherein: The N4 rules corresponding to the second QoS flow include one or more of the following: data packet monitoring rules, forwarding operation rules, QoS enforcement rules, and usage reporting rules.

45. The method according to any one of claims 19 to 44, characterized in that The method further comprises: The second core network device sends the QoS configuration of the second QoS flow and / or the alternative QoS configuration of the second QoS flow to the access network device, and the access network device serves the second terminal device.

46. ​​The method according to any one of claims 19 to 45, characterized in that The method further comprises: The second core network device configures QoS rules of the second QoS flow for the second terminal device.

47. The method according to any one of claims 19 to 30, characterized in that The first PDU session of the first terminal device is the same as the second PDU session of the second terminal device, or The QoS parameters of the first QoS flow of the first terminal device are the same as the QoS parameters of the second QoS flow of the second terminal device, or The QoS configuration of the first QoS flow of the first terminal device is the same as the QoS configuration of the second QoS flow of the second terminal device.

48. The method of claim 47, wherein: If the first PDU session is the same as the second PDU session, the access network device of the first terminal device is the same as the access network device of the second terminal device.

49. The method of claim 48, wherein: The network device is the access network device, and the method further includes: The access network device acquires information indicating an association relationship between the first terminal device and the second terminal device; The access network device determines, based on the information used to indicate the association relationship, a QoS configuration associated with the information used to indicate the association relationship; The access network device configures a second QoS flow for the second terminal device based on the QoS configuration associated with the information indicating the association relationship.

50. The method of claim 48, wherein: If the network device is a second core network device, the method includes: In response to receiving the first request, the second core network device allocates address information to the second terminal device, wherein the address information of the second terminal device satisfies one of the following: The address information of the second terminal device is the same as the address information of the first terminal device; The address information of the second terminal device is different from the address information of the first terminal device; The address information of the second terminal device belongs to a target address information segment, and the target address information segment is associated with a target user, and the target user is a common user of the first terminal device and the second terminal device.

51. The method according to any one of claims 19 to 24 and 29, characterized in that If the target terminal device is the second terminal device, the first request is carried in a PDU session establishment request, and the PDU session request is used to request to establish a PDU session for the target service; or The first request is carried in a PDU session modification request, and the PDU session request is used to request modification of a PDU session used to transmit the target service.

52. The method according to any one of claims 19 to 30, characterized in that If the network device is a first core network device, the method further includes: The first core network device receives the first request sent by the target terminal device through the access network device.

53. The method of claim 52, wherein: The method further comprises: The first core network device sends the first request to the second core network device.

54. The method according to any one of claims 19 to 48, wherein: The target terminal device is the first terminal device, and the network device is a second core network device, and the method further includes: In response to receiving the first request, the second core network device determines the second terminal device.

55. The method of claim 54, wherein: If the first request carries information indicating an association relationship between the first terminal device and the second terminal device, the second core network device determines the second terminal device, including: Based on the association relationship, the second core network device determines that the terminal device having the association relationship with the first terminal device is the second terminal device.

56. The method of claim 54, wherein: If the first request carries information for indicating the second terminal device, the second core network device determines the second terminal device, including: The second core network device determines the second terminal device based on the information used to indicate the second terminal device.

57. The method according to any one of claims 19 to 48, wherein: If the first request includes information for determining the second PDU session, the method further includes: The second core network device determines the second PDU session based on the first request.

58. The method according to any one of claims 19 to 57, wherein: The QoS flow used to transmit the target service is part or all of the QoS flows in the associated PDU session.

59. A method of wireless communication, characterized in that: include: The fifth core network device sends target information to the sixth core network device, where the target information is used to indicate QoS parameters associated with a user, where the user is associated with one or more terminal devices.

60. The method according to any one of claims 1 to 59, wherein: The third information is carried in a third request, wherein the third request is used to request the creation of an AF session with QoS; or the third request is used to request the update of an AF session with QoS.

61. The method according to any one of claims 19 to 60, characterized in that The user-associated QoS parameters are used when the user's target service is migrated between multiple terminal devices associated with the user.

62. A method of wireless communication, characterized in that: include: The sixth core network device receives target information sent by the fifth core network device, where the target information is used to indicate QoS parameters associated with a user, and the user is associated with one or more terminal devices.

63. The method of claim 62, wherein: The third information is carried in a third request, wherein the third request is used to request the creation of an AF session with QoS; or the third request is used to request the update of an AF session to be provided with QoS.

64. The method of claim 63, wherein: The method further comprises: In response to receiving the third request, the sixth core network device associates the transaction reference identifier of the AF session with the user identifier of the user; The sixth core network device sends a response message to the third request to the fifth core network device, where the response message carries the transaction reference identifier of the AF session and the user identifier of the user.

65. The method of claim 63 or 64, wherein: The method further comprises: The sixth core network device sends a fourth request for requesting PCC rules to the fourth core network device, where the fourth request carries the user identifier of the user and the QoS parameter.

66. A terminal device, characterized in that: The terminal device is a target terminal device, and the target terminal device includes: A sending unit, configured to send a first request to a network device, wherein the first request is used to request migration of a target service from a first terminal device to a second terminal device; The target terminal device is a first terminal device or a second terminal device.

67. The terminal device according to claim 66, characterized in that: The first request includes one or more of the following information: Information used to indicate the first terminal device; Information used to indicate the second terminal device; Information for determining a second PDU session; Information used to indicate the association relationship between the first terminal device and the second terminal device.

68. The terminal device according to claim 67, characterized in that: If the first request includes information for indicating the first terminal device, the information for indicating the first terminal device includes an identifier of the first terminal device and / or address information of the first terminal device.

69. The terminal device according to claim 67 or 68, characterized in that: If the first request includes information for indicating the second terminal device, the information for indicating the second terminal device includes an identifier of the second terminal device and / or address information of the second terminal device.

70. The terminal device according to any one of claims 67 to 69, characterized in that: If the first request includes information for indicating the association relationship, the information for indicating the association relationship includes one or more of the following: identification information of the terminal group to which the first terminal device and the second terminal device belong; Identification information of users to which the first terminal device and the second terminal device belong; Identification information of the association relationship between the first terminal device and the second terminal device.

71. The terminal device according to any one of claims 67 to 70, characterized in that: If the first request includes information for indicating the second PDU session, the information for indicating the second PDU session includes: application service description information of the target service, and / or an identifier of the second PDU session.

72. The terminal device according to any one of claims 66 to 71, characterized in that: If the target device is the first terminal device, the first request includes one or more of the following information: Information used to indicate the first PDU session; Information used to indicate a first QoS flow; as well as The QoS parameters of the QoS flow transmitting the target service.

73. The terminal device according to claim 72, characterized in that: The first request includes the information indicating the first QoS flow, and the information indicating the first QoS flow includes: an identifier QFI of the first QoS flow, and / or flow description information of the first QoS flow.

74. The terminal device according to claim 72 or 73, characterized in that: If the first request includes information for indicating the first PDU session, the information for indicating the first PDU session includes: an identifier of the first PDU session.

75. The terminal device according to any one of claims 66 to 74, characterized in that: If the target terminal device is the first terminal device, the first request is used to request migration of the first QoS flow from the first terminal device to the second terminal device.

76. The terminal device according to any one of claims 66 to 71, characterized in that: If the target device is the second terminal device, the first request includes resolution information of the second terminal device.

77. The terminal device according to claim 76, characterized in that: The resolution information of the second terminal device is used to determine the QoS parameters of the second QoS flow of the second terminal device.

78. The terminal device according to any one of claims 66 to 71 and 76, characterized in that: If the target terminal device is the second terminal device, the first request is carried in a PDU session establishment request, and the PDU session request is used to request to establish a PDU session for the target service; or The first request is carried in a PDU session modification request, and the PDU session request is used to request modification of a PDU session used to transmit the target service.

79. The terminal device according to any one of claims 66 to 78, characterized in that: The PDU session used by the first terminal device to transmit the target service is the same as the PDU session used by the second terminal device to transmit the target service, or The QoS parameters of the first QoS flow of the first terminal device are the same as the QoS parameters of the second QoS flow of the second terminal device, or The QoS configuration of the first QoS flow of the first terminal device is the same as the QoS configuration of the second QoS flow of the second terminal device.

80. The terminal device according to claim 79, characterized in that: If the first PDU session is the same as the second PDU session, the network device accessed by the first terminal device is the same as the network device accessed by the second terminal device.

81. The terminal device as claimed in claim 80, characterized in that: The address information of the first terminal device is the same as the address information of the second terminal device; or The address information of the first terminal device is different from the address information of the second terminal device.

82. The terminal device according to any one of claims 66 to 81, characterized in that: The user of the first terminal device and the second terminal device is the same, and the QoS parameter of the target service is associated with the user.

83. The terminal device according to any one of claims 66 to 82, characterized in that: The QoS flow used to transmit the target service is part or all of the QoS flows in the associated PDU session.

84. A network device, characterized in that: include: A receiving unit, configured to receive a first request sent by a target terminal device, wherein the first request is used to request migration of a target service from the first terminal device to a second terminal device; The target terminal device is a first terminal device or a second terminal device.

85. The network device according to claim 84, characterized in that The first request includes one or more of the following information: Information used to indicate the first terminal device; Information used to indicate the second terminal device; Information for determining a second PDU session; Information used to indicate the association relationship between the first terminal device and the second terminal device.

86. The network device according to claim 85, characterized in that If the first request includes information for indicating the first terminal device, the information for indicating the first terminal device includes an identifier of the first terminal device and / or address information of the first terminal device.

87. The network device according to claim 85 or 86, characterized in that: If the first request includes information for indicating the second terminal device, the information for indicating the second terminal device includes an identifier of the second terminal device and / or address information of the second terminal device.

88. The network device according to any one of claims 85 to 87, characterized in that: If the first request includes information for indicating the association relationship, the information for indicating the association relationship includes one or more of the following: Indicative information of the terminal group to which the first terminal device and the second terminal device belong; Indicative information of users to which the first terminal device and the second terminal device belong; Identification information of the association relationship between the first terminal device and the second terminal device.

89. The network device according to any one of claims 85 to 88, characterized in that: If the first request includes information for indicating the second PDU session, the information for indicating the second PDU session includes: application service description information of the target service, and / or an identifier of the second PDU session.

90. The network device according to any one of claims 84 to 89, characterized in that: If the target device is the first terminal device, the first request includes one or more of the following information: Information used to indicate the first PDU session; Information used to indicate a first QoS flow; as well as The QoS parameters of the QoS flow transmitting the target service.

91. The network device according to claim 90, characterized in that The first request includes the information indicating the first QoS flow, and the information indicating the first QoS flow includes: an identifier QFI of the first QoS flow, and / or flow description information of the first QoS flow.

92. The network device according to claim 90 or 91, characterized in that: If the first request includes information for indicating the first PDU session, the information for indicating the first PDU session includes: an identifier of the first PDU session.

93. The network device according to any one of claims 84 to 92, characterized in that: If the target terminal device is the first terminal device, the first request is used to request migration of the first QoS flow from the first terminal device to the second terminal device.

94. The network device according to any one of claims 84 to 89, characterized in that: If the target device is the second terminal device, the first request includes resolution information of the second terminal device.

95. The network device according to claim 94, characterized in that The resolution information of the second terminal device is used to determine the QoS parameters of the second QoS flow.

96. The network device according to any one of claims 84 to 95, characterized in that: If the network device is a second core network device, the network device further includes: The first processing unit is used to configure QoS parameters for the second QoS flow of the second terminal device.

97. The network device according to claim 96, characterized in that The network device also includes: A first acquisition unit, configured to acquire contract information, wherein the contract information records QoS parameters of a QoS flow for transmitting the target service; The first processing unit is used to configure QoS parameters for the second QoS flow based on the subscription information.

98. The network device according to claim 97, characterized in that The contract information is contract information associated with a target user, the QoS parameter carried in the contract information is associated with the target user, and the target user is a common user of the first terminal device and the second terminal device; or The subscription information is the subscription information of the second terminal device, and the QoS parameters carried by the subscription information are associated with the second terminal device.

99. The network device according to claim 96, characterized in that If the first request carries the QoS parameters of the QoS flow transmitting the target service, the first processing unit is used to configure the QoS parameters for the second QoS flow based on the first request.

100. The network device according to claim 96, characterized in that: The first processing unit is configured to: Acquire a first QoS parameter, where the first QoS parameter is a QoS parameter of a first QoS flow used by the first terminal device to transmit the target service; Based on the first QoS parameters, QoS parameters are configured for the second QoS flow of the second terminal device.

101. The network device according to claim 96, characterized in that: If the first request includes information for indicating the first terminal device and information for indicating the second terminal device, the network device further includes: A second processing unit, configured to determine, based on the information indicating the first terminal device, a first QoS flow for transmitting the target service in the first terminal device; and determine a QoS parameter of the first QoS flow; The first processing unit is used for the second core network device to configure QoS parameters for the second QoS flow based on the QoS parameters of the first QoS flow.

102. The network device according to claim 96, characterized in that: If the first request includes information indicating an association relationship between the first terminal device and the second terminal device, the network device further includes: A third processing unit, configured to determine a QoS parameter corresponding to the association relationship based on the association relationship; The first processing unit is used to configure QoS parameters for the second QoS flow of the second terminal device based on the QoS parameters corresponding to the association relationship.

103. The network device according to claim 96, characterized in that: If the first request includes the resolution information of the second terminal device, the network device further includes: a fourth processing unit, configured to determine, based on the resolution information of the second terminal device and a pre-stored correspondence between the resolution information and the QoS parameter, a QoS parameter corresponding to the resolution information of the second terminal device; The first processing unit is used to configure QoS parameters for the second QoS flow of the second terminal device based on the QoS parameters corresponding to the resolution information of the second terminal device.

104. The network device according to any one of claims 84 to 103, characterized in that: The network device also includes: The fifth processing unit is used to allocate address information for the second PDU session.

105. The network device according to any one of claims 84 to 103, characterized in that: The network device also includes: A first sending unit, configured to send a second request to a fourth core network device, where the second request is used to request a PCC rule for transmitting the target service; The receiving unit is used to receive a response message sent by the fourth core network device to the second request, where the response message carries the PCC rule.

106. The network device according to claim 105, characterized in that The second request carries information indicating the second terminal device and / or address information of the second PDU session.

107. The network device according to any one of claims 84 to 106, characterized in that: The network device also includes: The sixth processing unit is used to configure the N4 rule corresponding to the second QoS flow and / or the QoS rule corresponding to the second QoS flow for the third core network device, and the second QoS flow is used for the second terminal device to transmit the target service.

108. The network device according to claim 107, characterized in that The N4 rule corresponding to the second QoS flow and / or the QoS rule corresponding to the second QoS flow are carried in a PDU session modification request, and the PDU session modification request is used to request modification of the PDU session used to transmit the target service.

109. The network device according to claim 108, characterized in that The N4 rules corresponding to the second QoS flow include one or more of the following: data packet monitoring rules, forwarding operation rules, QoS enforcement rules, and usage reporting rules.

110. The network device according to any one of claims 84 to 109, characterized in that: The network device also includes: The second sending unit is used to send the QoS configuration of the second QoS flow and / or the alternative QoS configuration of the second QoS flow to the access network device, and the access network device serves the second terminal device.

111. The network device according to any one of claims 84 to 110, characterized in that: The network device also includes: The seventh processing unit is used to configure the QoS rules of the second QoS flow for the second terminal device.

112. The network device according to any one of claims 84 to 104, characterized in that: The first PDU session of the first terminal device is the same as the second PDU session of the second terminal device, or The QoS parameters of the first QoS flow of the first terminal device are the same as the QoS parameters of the second QoS flow of the second terminal device, or The QoS configuration of the first QoS flow of the first terminal device is the same as the QoS configuration of the second QoS flow of the second terminal device.

113. The network device according to claim 112, characterized in that: If the first PDU session is the same as the second PDU session, the access network device of the first terminal device is the same as the access network device of the second terminal device.

114. The network device according to claim 113, characterized in that The network device is the access network device, and the network device further includes: A second acquiring unit, used to acquire information indicating an association relationship between the first terminal device and the second terminal device; an eighth processing unit, configured to determine, based on the information indicating the association relationship, a QoS configuration associated with the information indicating the association relationship; and Based on the QoS configuration associated with the information indicating the association relationship, a second QoS flow of the second terminal device is configured.

115. The network device according to claim 113, characterized in that: If the network device is a second core network device, the network device includes: In response to receiving the first request, the ninth processing unit is configured to allocate address information to the second terminal device, wherein the address information of the second terminal device satisfies one of the following: The address information of the second terminal device is the same as the address information of the first terminal device; The address information of the second terminal device is different from the address information of the first terminal device; The address information of the second terminal device belongs to a target address information segment, and the target address information segment is associated with a target user, and the target user is a common user of the first terminal device and the second terminal device.

116. The network device according to any one of claims 84-89 and 94, characterized in that: If the target terminal device is the second terminal device, the first request is carried in a PDU session establishment request, and the PDU session request is used to request to establish a PDU session for the target service; or The first request is carried in a PDU session modification request, and the PDU session request is used to request modification of a PDU session used to transmit the target service.

117. The network device according to any one of claims 84 to 95, characterized in that: If the network device is a first core network device, the network device further includes: The second sending unit is used to receive the first request sent by the target terminal device through the access network device.

118. The network device according to claim 117, characterized in that The network device also includes: The third sending unit is used to send the first request to the second core network device.

119. The network device according to any one of claims 84 to 113, characterized in that: The target terminal device is the first terminal device, and the network device is a second core network device, and the network device further includes: In response to receiving the first request, the tenth processing unit is configured to determine the second terminal device.

120. The network device according to claim 119, characterized in that If the first request carries information indicating an association relationship between the first terminal device and the second terminal device, the tenth processing unit is used to determine, based on the association relationship, that the terminal device having the association relationship with the first terminal device is the second terminal device.

121. The network device according to claim 119, characterized in that If the first request carries information for indicating the second terminal device, the tenth processing unit is used to determine the second terminal device based on the information for indicating the second terminal device.

122. The network device according to any one of claims 84 to 113, characterized in that: If the first request includes information for determining the second PDU session, the network device further includes: An eleventh processing unit is used to determine the second PDU session based on the first request.

123. The network device according to any one of claims 84 to 122, characterized in that: The QoS flow used to transmit the target service is part or all of the QoS flows in the associated PDU session.

124. A network device, characterized in that: The network device is a fifth core network device, including: A sending unit is used to send target information to the sixth core network device, where the target information is used to indicate QoS parameters associated with the user, and the user is associated with one or more terminal devices.

125. The network device according to claim 124, characterized in that The third information is carried in a third request, wherein the third request is used to request the creation of an AF session with QoS; or the third request is used to request the update of an AF session with QoS.

126. The network device according to claim 124 or 125, characterized in that: The user-associated QoS parameters are used when the user's target service is migrated between multiple terminal devices associated with the user.

127. A network device, characterized in that: The network device is a sixth core network device, including: A receiving unit is used to receive target information sent by a fifth core network device, where the target information is used to indicate QoS parameters associated with a user, and the user is associated with one or more terminal devices.

128. The network device according to claim 127, characterized in that The third information is carried in a third request, wherein the third request is used to request the creation of an AF session with QoS; or the third request is used to request the update of an AF session to be provided with QoS.

129. The network device according to claim 128, characterized in that The network device also includes: In response to receiving the third request, the first processing unit is configured to associate the transaction reference identifier of the AF session with the user identifier of the user; The first sending unit is used to send a response message to the third request to the fifth core network device, where the response message carries the transaction reference identifier of the AF session and the user identifier of the user.

130. The method of claim 128 or 129, wherein: The method further comprises: The second sending unit is used to send a fourth request for requesting PCC rules to a fourth core network device, where the fourth request carries the user identifier of the user and the QoS parameter.

131. A terminal device, characterized in that: The terminal comprises a transceiver, a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals, so that the terminal executes the method as described in any one of claims 1 to 18.

132. A network device, characterized in that: It includes a transceiver, a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the network device executes the method as described in any one of claims 19-65.

133. A device, characterized in that: It comprises a processor, which is used to call a program from a memory so that the device executes the method as described in any one of claims 1-65.

134. A chip, characterized in that: It comprises a processor, which is used to call a program from a memory so that a device equipped with the chip executes a method as described in any one of claims 1 to 65.

135. A computer-readable storage medium, characterized in that: A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 65.

136. A computer program product, characterized in that It comprises a program which causes a computer to execute the method as claimed in any one of claims 1 to 65.

137. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1-65.

Images