Multi-terminal Federation Session Management Method, Network-side Device and Terminal

Abstract

The present application discloses a multi-terminal joint session management method, a network-side device, and a terminal, belonging to the field of wireless communication technologies. The multi-terminal joint session management method according to the embodiments of the present application includes: a first core network element obtains the address information of a second terminal from a first message, where the first message is related to a PDU session corresponding to a first terminal; the first core network element determines a target core network element corresponding to the second terminal according to the address information of the second terminal; the first core network element sends a second message to the target core network element, and the second message is used to request the target core network element to reserve PDU session resources and / or establish QoS flows for the second terminal.

Description

Technical Field

[0001] This application belongs to the field of wireless communication technologies, and particularly relates to a multi-terminal joint session management method, a network-side device, and a terminal. Background Art

[0002] A terminal realizes data forwarding and reception with an application server through a Protocol Data Unit (PDU) session. Under current technologies, PDU sessions between different terminals are independent and have no relevance to each other. A terminal receiving and forwarding data through its own PDU session will not affect the PDU sessions of other terminals.

[0003] However, with the deployment of personal networks, a user may have different types of terminals, and different terminals perform different functions in the home network, such as speakers, cameras, TVs, etc. The user may control other types of terminals through a mobile phone to implement corresponding functions, such as the mobile phone controlling media data to be played on the TV and audio data to be played on the speaker. In this case, the current PDU session management technology cannot jointly manage PDU sessions between different terminals. Summary of the Invention

[0004] Embodiments of this application provide a multi-terminal joint session management method, a network-side device, and a terminal, which can solve the problem of how to implement joint session management between multiple terminals.

[0005] In a first aspect, a multi-terminal joint session management method is provided. The method includes:

[0006] A first core network element obtains address information of a second terminal from a first message, where the first message is related to a PDU session corresponding to a first terminal;

[0007] The first core network element determines a target core network element corresponding to the second terminal according to the address information of the second terminal;

[0008] The first core network element sends a second message to the target core network element, where the second message is used to request the target core network element to reserve PDU session resources and / or establish a QoS flow for the second terminal.

[0009] In a second aspect, a multi-terminal joint session management method is provided, including:

[0010] A target core network element receives a second message related to a PDU session corresponding to a first terminal, where the second message is used to request the target core network element to reserve PDU session resources and / or establish a QoS flow for a second terminal;

[0011] The target core network element performs relevant operations according to the second message, and the relevant operations include at least one of the following operations:

[0012] Generate or update the PCC rule of the PDU session corresponding to the second terminal;

[0013] Execute the PDU session update process corresponding to the second terminal and add the corresponding QoS flow.

[0014] In a third aspect, a multi-terminal joint session management method is provided, including:

[0015] The terminal sends a second request message, which is used to request to transfer part of the service data stream to be transmitted on the PDU session corresponding to the second terminal, and the second request message includes the address information of the second terminal.

[0016] In a fourth aspect, a multi-terminal joint session management method is provided, including:

[0017] The first network-side device receives a second request message sent by the first terminal, which is used to request to transfer part of the service data stream to be transmitted on the PDU session corresponding to the second terminal, and the second request message includes the address information of the second terminal;

[0018] The first network-side device sends a first request message according to the second request message, which is used to request the core network to reserve PDU session resources and / or establish a QoS flow for the second terminal, and the first request message includes the address information of the second terminal.

[0019] In a fifth aspect, a multi-terminal joint session management device is provided, including:

[0020] An acquisition module, configured to acquire the address information of the second terminal from the first message, where the first message is related to the PDU session corresponding to the first terminal;

[0021] A determination module, configured to determine a target core network element corresponding to the second terminal according to the address information of the second terminal;

[0022] A sending module, configured to send a second message to the target core network element, where the second message is used to request the target core network element to reserve PDU session resources and / or establish a QoS flow for the second terminal.

[0023] In a sixth aspect, a multi-terminal joint session management device is provided, including:

[0024] A receiving module, configured to receive a second message related to a PDU session corresponding to a first terminal, where the second message is used to request the target core network element to reserve PDU session resources for a second terminal and / or establish a QoS flow;

[0025] An execution module, configured to perform related operations according to the second message, where the related operations include at least one of the following operations:

[0026] Generate or update a PCC rule for a PDU session corresponding to the second terminal;

[0027] Perform a PDU session update process corresponding to the second terminal and add a corresponding QoS flow.

[0028] In a seventh aspect, a multi-terminal federated session management device is provided, including:

[0029] A sending module, configured to send a second request message, where the second request message is used to request to transfer part of the service data stream to be transmitted on a PDU session corresponding to a second terminal, and the second request message includes address information of the second terminal.

[0030] In an eighth aspect, a multi-terminal federated session management device is provided, including:

[0031] A receiving module, configured to receive a second request message sent by a first terminal, where the second request message is used to request to transfer part of the service data stream to be transmitted on a PDU session corresponding to a second terminal, and the second request message includes address information of the second terminal;

[0032] A sending module, configured to send a first request message according to the second request message, where the first request message is used to request the core network to reserve PDU session resources for the second terminal and / or establish a QoS flow, and the first request message includes address information of the second terminal.

[0033] In a ninth aspect, a core network element is provided. The terminal includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0034] In a tenth aspect, a core network element is provided, which includes a processor and a communication interface. The processor is configured to obtain the address information of a second terminal from a first message, where the first message is related to a PDU session corresponding to a first terminal; determine a target core network element corresponding to the second terminal according to the address information of the second terminal. The communication interface is configured to send a second message to the target core network element, and the second message is used to request the target core network element to reserve PDU session resources and / or establish QoS flows for the second terminal.

[0035] In an eleventh aspect, a core network element is provided, which includes a processor and a communication interface. The communication interface is configured to receive a second message related to a PDU session corresponding to a first terminal, and the second message is used to request the target core network element to reserve PDU session resources and / or establish QoS flows for a second terminal. The processor is configured to perform related operations according to the second message, and the related operations include at least one of the following operations:

[0036] Generate or update a PCC rule for the PDU session corresponding to the second terminal;

[0037] Execute a PDU session update process corresponding to the second terminal and add a corresponding QoS flow.

[0038] In a twelfth aspect, a terminal is provided. The terminal includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, the steps of the method described in the third aspect are implemented.

[0039] In a thirteenth aspect, a terminal is provided, which includes a processor and a communication interface. The communication interface is configured to send a second request message, and the second request message is used to request to transfer a part of service data flows to be transmitted on the PDU session corresponding to the second terminal. The second request message includes the address information of the second terminal.

[0040] In a fourteenth aspect, a network-side device is provided. The network-side device includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, the steps of the method described in the fourth aspect are implemented.

[0041] In a fifteenth aspect, a network-side device is provided, including a processor and a communication interface. The communication interface is configured to receive a second request message sent by a first terminal. The second request message is used to request to transfer part of the service data stream to be transmitted on a PDU session corresponding to a second terminal. The second request message includes the address information of the second terminal. A first request message is sent according to the second request message. The first request message is used to request the core network to reserve PDU session resources for the second terminal and / or establish a QoS flow. The first request message includes the address information of the second terminal.

[0042] In a sixteenth aspect, a readable storage medium is provided. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the steps of the methods described in the first aspect, the second aspect, the third aspect, or the fourth aspect are implemented.

[0043] In a seventeenth aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to run programs or instructions to implement the methods described in the first aspect, the second aspect, the third aspect, or the fourth aspect.

[0044] In an eighteenth aspect, a computer program / program product is provided. The computer program / program product is stored in a non-volatile storage medium. The program / program product is executed by at least one processor to implement the steps of the methods described in the first aspect, the second aspect, the third aspect, or the fourth aspect.

[0045] In the embodiments of the present application, PDU session resources can be reserved for other terminals and / or a Quality of Service (QoS) flow can be established in the PDU session process of one terminal, so as to realize the joint management of sessions between multiple terminals. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 It is a block diagram of a wireless communication system applicable to the embodiments of the present application;

[0047] Figure 2 It is a schematic flowchart of a multi-terminal joint session management method according to an embodiment of the present application;

[0048] Figure 3 It is a schematic flowchart of a multi-terminal joint session management method according to an embodiment of the present application;

[0049] Figure 4 It is a schematic flowchart of a multi-terminal joint session management method according to an embodiment of the present application;

[0050] Figure 5 It is a schematic flowchart of a multi-terminal joint session management method according to an embodiment of the present application;

[0051] Figure 6 It is the fifth flowchart of the multi-terminal joint session management method according to the embodiment of the present application;

[0052] Figure 7 It is the sixth flowchart of the multi-terminal joint session management method according to the embodiment of the present application;

[0053] Figure 8 It is the seventh flowchart of the multi-terminal joint session management method according to the embodiment of the present application;

[0054] Figure 9 It is the flowchart of the multi-terminal joint session management method according to the first embodiment of the present application;

[0055] Figure 10 It is the flowchart of the multi-terminal joint session management method according to the second embodiment of the present application;

[0056] Figure 11 It is the flowchart of the multi-terminal joint session management method according to the third embodiment of the present application;

[0057] Figure 12 It is one of the structural diagrams of the multi-terminal joint session management device according to the embodiment of the present application;

[0058] Figure 13 It is the second structural diagram of the multi-terminal joint session management device according to the embodiment of the present application;

[0059] Figure 14 It is the third structural diagram of the multi-terminal joint session management device according to the embodiment of the present application;

[0060] Figure 15 It is the fourth structural diagram of the multi-terminal joint session management device according to the embodiment of the present application;

[0061] Figure 16 It is the structural diagram of the communication device according to the embodiment of the present application;

[0062] Figure 17 It is the hardware structural diagram of the terminal according to the embodiment of the present application;

[0063] Figure 18 It is the hardware structural diagram of the network-side device according to the embodiment of the present application. Detailed implementation manners

[0064] Next, the technical solutions in the embodiments of the present application will be clearly described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope protected by the present application.

[0065] The terms "first", "second", etc. in the description and claims of this application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances so that the embodiments of this application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same kind, without limiting the number of objects. For example, the first object can be one or multiple. In addition, "and / or" in the description and claims means at least one of the connected objects, and the character " / " generally indicates an "or" relationship between the associated objects before and after.

[0066] It is worth noting that the technology described in the embodiments of this application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, and can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of this application are often used interchangeably, and the described technology can be used in the systems and radio technologies mentioned above, as well as in other systems and radio technologies. The following description describes the New Radio (NR) system for example purposes, and the NR term is used in most of the following descriptions, but these technologies can also be applied to applications other than NR system applications, such as the 6th Generation (6G) communication system. th Generation, 6G) communication system.

[0067] Figure 1A block diagram of a wireless communication system to which embodiments of the present application can be applied is shown. The wireless communication system includes a terminal 11 and a network-side device 12. Among them, the terminal 11 can also be referred to as a terminal device or a user terminal (User Equipment, UE). The terminal 11 can be a mobile phone, a tablet personal computer, a laptop computer or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device or a vehicle-mounted device (VUE), a pedestrian terminal (PUE), etc. Terminal-side devices. Wearable devices include smart watches, bracelets, earphones, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network-side device 12 can be a base station or a core network. Among them, the base station can be referred to as Node B, evolved Node B, access point, base transceiver station (Base Transceiver Station, BTS), radio base station, radio transceiver, basic service set (Basic Service Set, BSS), extended service set (Extended Service Set, ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting and receiving point (Transmitting Receiving Point, TRP) or some other suitable term in the art. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

[0068] Next, with reference to the accompanying drawings, the multi-terminal joint session management method, network-side device, and terminal provided by the embodiments of the present application will be described in detail through some embodiments and their application scenarios.

[0069] Please refer to Figure 2 , Figure 2 which is one of the flow diagrams of the multi-terminal joint session management method according to the embodiments of the present application. The multi-terminal joint session management method includes:

[0070] Step 21: The first core network element obtains the address information of the second terminal from the first message, and the first message is related to the PDU session corresponding to the first terminal;

[0071] The address information of the second terminal is, for example, the IP address information of the second terminal.

[0072] The number of the second terminals can be one or multiple.

[0073] Step 22: The first core network element determines a target core network element corresponding to the second terminal according to the address information of the second terminal;

[0074] Step 23: The first core network element sends a second message to the target core network element, and the second message is used to request the target core network element to reserve PDU session resources and / or establish a QoS flow for the second terminal.

[0075] In the embodiment of the present application, the first core network element may reserve PDU session resources and / or establish a QoS flow for the second terminal in the PDU session process corresponding to the first terminal, so as to implement the combined session management between multiple terminals.

[0076] In some embodiments of the present application, optionally, the address information of the second terminal is implicitly carried by a flow description field in the first message.

[0077] In some other embodiments of the present application, optionally, the address information of the second terminal may also be explicitly carried by a separate field in the first message.

[0078] In some embodiments of the present application, optionally:

[0079] The first core network element is a Network Exposure Function (NEF);

[0080] The first message is a first request message received by the NEF, and the first request message is used to request the core network to reserve PDU session resources and / or establish a QoS flow for the second terminal, and the first request message includes the address information of the second terminal;

[0081] The target core network element is a second Policy Control Function (PCF) entity corresponding to the second terminal;

[0082] The second message is a policy authorization request message, and the policy authorization request message is used to indicate generating or updating a Policy Control and Charging (PCC) rule for the PDU session corresponding to the second terminal.

[0083] Please refer to Figure 3 , Figure 3This is the second flowchart of the multi-terminal joint session management method according to the embodiments of the present application. The multi-terminal joint session management method includes:

[0084] Step 31: The NEF receives a first request message related to a PDU session corresponding to a first terminal. The first request message is used to request the core network to reserve PDU session resources for a second terminal and / or establish a QoS flow. The first request message includes the address information of the second terminal.

[0085] That is to say, the first request message is a message related to the PDU session corresponding to the first terminal. The first request message includes the address information of the first terminal. Different from the message related to the PDU session corresponding to the first terminal in the prior art, the first request message further includes the address information of an additional terminal (i.e., the second terminal).

[0086] In addition, the first request message may further include identification information for indicating that the first request message is used for multi-terminal joint session management.

[0087] Step 32: The NEF obtains the address information of the second terminal from the first request message.

[0088] The address information of the second terminal is, for example, the IP address information of the second terminal.

[0089] The number of the second terminals may be one or multiple.

[0090] In the embodiments of the present application, optionally, the address information of the second terminal is explicitly carried through a separate field in the first request message, so that the NEF can identify the address information of the second terminal.

[0091] Step 33: The NEF determines a second PCF corresponding to the second terminal according to the address information of the second terminal.

[0092] Step 34: The NEF sends a policy authorization request message to the second PCF. The policy authorization request message is used to indicate generating or updating a PCC rule for the PDU session corresponding to the second terminal. Thus, the second PCF generates or updates the PCC rule for the PDU session corresponding to the second terminal, and sends the generated or updated PCC rule to a second SMF corresponding to the second terminal. The second SMF performs a PDU session update process corresponding to the second terminal and adds a corresponding QoS flow.

[0093] In some other embodiments of the present application, if the address information of the second terminal is implicitly carried by the flow description field in the first request message, the NEF may not be able to read the address information of the second terminal. At this time, the NEF can only send a policy authorization request message to the first PCF corresponding to the first terminal based on the address information of the first terminal in the first request message, and then the first PCF determines the target core network element (for the specific identification process, see the following content).

[0094] In some embodiments of the present application, optionally:

[0095] The first core network element is the first PCF corresponding to the first terminal;

[0096] The first message is the policy authorization request message received by the first PCF, and the policy authorization request message is used to indicate the generation or update of the PCC rule for the PDU session corresponding to the second terminal. The policy authorization request message contains the address information of the second terminal;

[0097] The target core network element is the second SMF corresponding to the second terminal;

[0098] The second message is the generated or updated PCC rule.

[0099] Please refer to Figure 4 , Figure 4 , which is the third schematic diagram of the process of the multi-terminal joint session management method according to the embodiments of the present application. The multi-terminal joint session management method includes:

[0100] Step 41: The first PCF obtains the address information of the second terminal from the policy authorization request message related to the PDU session corresponding to the first terminal;

[0101] The address information of the second terminal is, for example, the IP address information of the second terminal.

[0102] The number of the second terminals can be one or more.

[0103] Step 42: The first PCF determines the second SMF corresponding to the second terminal according to the address information of the second terminal;

[0104] Step 43: The first PCF generates or updates the PCC rule for the PDU session corresponding to the second terminal according to the policy authorization request message.

[0105] Step 44: The first PCF sends the generated or updated PCC rule to the second SMF to instruct the second SMF to execute the PDU session update process corresponding to the second terminal and add a message for the corresponding QoS flow.

[0106] In some embodiments of the present application, optionally:

[0107] The first core network element is the first PCF corresponding to the first terminal;

[0108] The first message is a policy authorization request message received by the first PCF, and the policy authorization request message is used to indicate generating or updating a PCC rule for a PDU session corresponding to the second terminal, and the policy authorization request message includes address information of the second terminal;

[0109] The target core network element is the second PCF corresponding to the second terminal;

[0110] The second message is the policy authorization request message.

[0111] Please refer to Figure 5 , Figure 5 , which is the fourth flow diagram of the multi-terminal association session management method according to the embodiments of the present application. The multi-terminal association session management method includes:

[0112] Step 51: The first PCF obtains the address information of the second terminal from a policy authorization request message related to a PDU session corresponding to the first terminal;

[0113] The address information of the second terminal is, for example, the IP address information of the second terminal.

[0114] The number of the second terminals can be one or more.

[0115] Step 52: The first PCF determines the second PCF corresponding to the second terminal according to the address information of the second terminal;

[0116] Step 53: The first PCF forwards the policy authorization request message to the second PCF, so that the second PCF generates or updates a PCC rule for a PDU session corresponding to the second terminal, and sends the generated or updated PCC rule to the second SMF corresponding to the second terminal, and the second SMF performs a PDU session update process corresponding to the second terminal and adds a corresponding QoS flow.

[0117] Please refer to Figure 6 , Figure 6 , which is the fifth flow diagram of the multi-terminal association session management method according to the embodiments of the present application. The multi-terminal association session management method includes:

[0118] Step 61: The target core network element receives a second message related to the PDU session corresponding to the first terminal, where the second message is used to request the target core network element to reserve PDU session resources for the second terminal and / or establish a QoS flow;

[0119] Step 62: The target core network element performs related operations according to the second message, and the related operations include at least one of the following operations:

[0120] Generate or update the PCC rule of the PDU session corresponding to the second terminal;

[0121] Execute the PDU session update process corresponding to the second terminal and add the corresponding QoS flow.

[0122] In the embodiment of the present application, the target core network element can reserve PDU session resources for the second terminal and / or establish a QoS flow in the PDU session process corresponding to the first terminal, so as to implement the combined session management between multiple terminals.

[0123] In some embodiments of the present application, optionally:

[0124] The target core network element is the second PCF corresponding to the second terminal;

[0125] The second message is a policy authorization request message, and the policy authorization request message is used to instruct the second PCF to generate or update the PCC rule of the PDU session corresponding to the second terminal;

[0126] The related operations performed by the target core network element according to the second message include:

[0127] The second PCF generates or updates the PCC rule of the PDU session corresponding to the second terminal, and sends the generated or updated PCC rule to the second SMF corresponding to the second terminal.

[0128] In some embodiments of the present application, optionally:

[0129] The target core network element is the second SMF corresponding to the second terminal;

[0130] The second message is the generated or updated PCC rule;

[0131] The related operations performed by the target core network element according to the second message include:

[0132] Execute the PDU session update process corresponding to the second terminal and add the corresponding QoS flow.

[0133] Please refer to Figure 7 , Figure 7FIG. 6 is a schematic flowchart of a multi-terminal joint session management method according to an embodiment of the present application. The multi-terminal joint session management method includes:

[0134] Step 71: The terminal sends a second request message for requesting to transfer part of the service data stream to be transmitted on the PDU session corresponding to the second terminal. The second request message includes the address information of the second terminal.

[0135] In the embodiment of the present application, one terminal can trigger the transfer of part of the service data stream to be transmitted on the PDU session of other terminals, so as to realize the joint session management between multiple terminals.

[0136] In the embodiment of the present application, optionally, the second request message further includes at least one of the following:

[0137] Service descriptor;

[0138] Service flow template.

[0139] Wherein, the service descriptor is used to indicate the service that the terminal needs to transfer. The service flow template is used to indicate the service flow that the terminal needs to transfer.

[0140] In the embodiment of the present application, optionally, the address information is IP address information.

[0141] In the embodiment of the present application, optionally, the terminal sending the second request message includes: the terminal sends the second request message to the application server through the application layer.

[0142] Please refer to Figure 8 , Figure 8 FIG. 7 is a schematic flowchart of a multi-terminal joint session management method according to an embodiment of the present application. The multi-terminal joint session management method includes:

[0143] Step 81: The first network-side device receives a second request message sent by the first terminal for requesting to transfer part of the service data stream to be transmitted on the PDU session corresponding to the second terminal. The second request message includes the address information of the second terminal;

[0144] Step 82: The first network-side device sends a first request message according to the second request message for requesting the core network to reserve PDU session resources and / or establish a QoS flow for the second terminal. The first request message includes the address information of the second terminal.

[0145] In the embodiment of the present application, one terminal can trigger the transfer of part of the service data stream to be transmitted on the PDU session of other terminals, so as to realize the joint session management between multiple terminals.

[0146] In an embodiment of the present application, optionally, the second request message is further used to request to forward a part of the data stream of the service corresponding to the PDU session corresponding to the terminal to the second terminal.

[0147] In an embodiment of the present application, optionally:

[0148] The address information of the second terminal is implicitly carried by the flow description field in the first request message;

[0149] Or

[0150] The address information of the second terminal is explicitly carried by a separate field in the first request message.

[0151] In an embodiment of the present application, optionally, the address information is IP address information.

[0152] In an embodiment of the present application, optionally, the first network-side device is an AF, and the AF may be a core network element or a third-party network element.

[0153] Next, with reference to the accompanying drawings, the multi-terminal joint session management method provided in the embodiments of the present application will be illustrated by some application scenarios.

[0154] Embodiment 1 of the present application: The NEF (the first core network element) determines the target PCF (the target core network element).

[0155] Please refer to Figure 9 , the multi-terminal joint session management method of Embodiment 1 of the present application includes the following steps:

[0156] Step 0: The first terminal (UE#1) sends a second request message (i.e., the App layer message in the figure) to the application server (AF) through the application layer. Among them, the second request message is used to request to transfer a part of the service data stream to the PDU session corresponding to the second terminal (UE#2) for transmission. The second request message carries the address information of the second terminal. For example, the content carried by the second request message is (UE#2addr, multi path requirement), where UE#2addr is the address information of the second terminal, and multi path requirement is used to indicate that the second request message is used for multi-terminal joint session management.

[0157] The address information of the second terminal may be, for example, the IP address of the second terminal. The second request message may carry the address information of at least one second terminal.

[0158] In an embodiment of the present application, optionally, the second request message further includes at least one of the following:

[0159] Service descriptor

[0160] Service flow template

[0161] Wherein, the service descriptor is used to indicate the service that the terminal needs to transfer. The service flow template is used to indicate the service flow that the terminal needs to transfer.

[0162] Step 1: The AF determines, according to the second request message, to request the core network to reserve PDU session resources and / or establish a QoS flow for the second terminal, and sends a first request message (i.e., Nnef_AFsessionWithQoS_Createrequest in the figure) to the NEF. The first request message is used to request the core network to reserve PDU session resources and / or establish a QoS flow for the second terminal, and the first request message contains the address information of the second terminal.

[0163] In the embodiment shown in the figure, the first request message further includes the following content: UE address, AFIdentifier, Flow description(s)), [UE#2Addr,], QoS reference, Alternative ServiceRequirements (optional), where UE address is the address information of the first terminal, AF Identifier is the identifier of the AF, Flow description(s) is the flow description field, [UE#2Addr,] is the address information of the second terminal, QoS reference is the QoS reference information, and Alternative Service Requirements (optional) are optional service requirements.

[0164] The first request message can carry the address information of the second terminal in one of the following two ways:

[0165] Implicitly carried through the flow description field (Flow descriptor) in the first request message; (i.e., the address information of the second terminal is included in the Flow descriptor)

[0166] Or

[0167] Explicitly carried through a separate field in the first request message, which is used to indicate that the Flow descriptor is used to reserve PDU session resources for the second terminal and establish a corresponding QoS flow.

[0168] In the embodiment of the present application, the address information of the second terminal is explicitly carried through a separate field (i.e., [UE#2Addr,]) in the first request message, so that the NEF can read the separate field and obtain the address information of the second terminal;

[0169] Step 2: After receiving the first request message, the NEF authenticates and authorizes the first request message of the AF, obtains the address information of the second terminal in the first request message, and determines the second PCF (i.e., the target core network element) corresponding to the second terminal according to the address information of the second terminal.

[0170] Step 3: The NEF sends a policy authorization request message (i.e., Npcf_PolicyAuthorization_Create request) to the second PCF. The policy authorization request message is used to indicate the generation or update of the trigger policy control and charging (Policy Control and Charging, PCC) rules for the PDU session corresponding to the second terminal.

[0171] In the embodiment shown in the figure, the policy authorization request message further includes the following content: UE address, AFIdentifier, Flow description(s)), [UE#2Addr,] QoS reference, Alternative Service Requirements (optional), where UE address is the address information of the first terminal, AF Identifier is the identifier of the AF, Flow description(s) is the flow description field, [UE#2Addr,] is the address information of the second terminal, QoS reference is the QoS reference information, and Alternative Service Requirements (optional) are optional service requirements.

[0172] Based on the fact that the Flow descriptor in the policy authorization request message corresponds to the PDU session of the second terminal, the second PCF triggers the generation or update of the PCC rules, and sends the generated or updated PCC rules to the second SMF corresponding to the second terminal, for performing the PDU session update process corresponding to the second terminal and adding the corresponding QoS flow.

[0173] Step 4: The second PCF sends a response (i.e., Npcf_PolicyAuthorization_Create response) to the NEF for the policy authorization request message.

[0174] Step 5: The NEF sends a response to the first request message to the AF (i.e., Nnef_AFsessionWithQoS_Create response).

[0175] Step 6: The NEF sends a policy authorization subscription request (Npcf_PolicyAuthorization_Subscribe) to the second PCF, thereby completing the PDU session resource reservation process.

[0176] In the second embodiment of this application: The PCF (the first core network element) determines the target SMF (the target core network element).

[0177] Please refer to Figure 10 , the multi-terminal association session management method of the embodiment of this application includes the following steps:

[0178] Step 0: The first terminal (UE#1) sends a second request message (i.e., the App layer message in the figure) to the application server (AF) through the application layer. The second request message is used to request to transfer part of the service data stream to the PDU session corresponding to the second terminal (UE#2). The second request message carries the address information of the second terminal. For example, the content carried by the second request message is (UE#2addr, multi path requirement), where UE#2addr is the address information of the second terminal, and multi path requirement is used to indicate that the second request message is used for multi-terminal association session management.

[0179] The address information of the second terminal may be, for example, the IP address of the second terminal. The second request message may carry the address information of at least one second terminal.

[0180] In the embodiment of this application, optionally, the second request message further includes at least one of the following:

[0181] Service descriptor;

[0182] Service flow template.

[0183] Among them, the service descriptor is used to indicate the service that the terminal needs to transfer. The service flow template is used to indicate the service flow that the terminal needs to transfer.

[0184] Step 1: According to the second request message, the AF determines to request the core network to reserve PDU session resources and / or establish QoS flows for the second terminal, and sends a first request message (i.e., Nnef_AFsessionWithQoS_Createrequest in the figure) to the NEF. The first request message is used to request the core network to reserve PDU session resources and / or establish QoS flows for the second terminal, and the first request message contains the address information of the second terminal.

[0185] In the embodiment shown in the figure, the first request message further includes the following content: UE address, AFIdentifier, Flow description(s)), [UE#2Addr,], QoS reference, Alternative Service Requirements (optional), where UE address is the address information of the first terminal, AF Identifier is the identifier of the AF, Flow description(s) is the flow description field, [UE#2Addr,] is the address information of the second terminal, QoS reference is the QoS reference information, and Alternative Service Requirements (optional) are optional service requirements.

[0186] The first request message can carry the address information of the second terminal in one of the following two ways:

[0187] Implicitly carried through the flow description field (Flow descriptor) in the first request message; (i.e., the address information of the second terminal is included in the Flow descriptor)

[0188] Or

[0189] Explicitly carried through a separate field in the first request message, which is used to indicate that the Flow descriptor is used to reserve PDU session resources for the second terminal and establish the corresponding QoS flow.

[0190] In the embodiment of the present application, the address information of the second terminal is explicitly carried through a separate field (i.e., [UE#2Addr,]) in the first request message.

[0191] Step 2: After receiving the first request message, the NEF authenticates and authorizes the first request message of the AF.

[0192] Step 3: The NEF sends a policy authorization request message (i.e., Npcf_PolicyAuthorization_Create request) to the first PCF corresponding to the first terminal according to the first request message. The policy authorization request message is used to indicate the generation or update of PCC rules for the PDU session corresponding to the second terminal, and the address information of the second terminal is carried in the policy authorization request message.

[0193] If the first request message implicitly carries the address information of the second terminal through a flow descriptor field, similarly, the policy authorization request message also implicitly carries the address information of the second terminal through a flow descriptor field.

[0194] If the first request message explicitly carries the address information of the second terminal through a separate field, similarly, the policy authorization request message also explicitly carries the address information of the second terminal through a separate field.

[0195] In the embodiment shown in the figure, the policy authorization request message further includes the following content: UE address, AFIdentifier, Flow description(s)), [UE#2Addr,], QoS reference, Alternative Service Requirements (optional), where UE address is the address information of the first terminal, AF Identifier is the identifier of the AF, Flow description(s) is the flow descriptor field, [UE#2Addr,] is the address information of the second terminal, QoS reference is the QoS reference information, and Alternative Service Requirements (optional) are optional service requirements.

[0196] Step 4: The first PCF sends a response to the policy authorization request message (i.e., Npcf_PolicyAuthorization_Create response) to the NEF.

[0197] Step 5: The first PCF determines the second SMF corresponding to the second terminal according to the address information of the second terminal in the policy authorization request message.

[0198] Step 6: The first PCF triggers the generation or update of Policy Control and Charging (PCC) rules based on the fact that the Flow descriptor in the policy authorization request message corresponds to the PDU session of the second terminal, and sends the generated or updated PCC rules to the second SMF corresponding to the second terminal, for performing the PDU session update process corresponding to the second terminal and adding the corresponding QoS flow, that is, performing the SM Policy Association Modification procedure.

[0199] Embodiment 3 of this application: The PCF (the first core network element) determines the target PCF (the target core network element).

[0200] Please refer to Figure 11 , the multi-terminal joint session management method of the embodiments of this application includes the following steps:

[0201] Step 0: The first terminal (UE#1) sends a second request message (i.e., the App layer message in the figure) to the application server (AF) through the application layer. Among them, the second request message is used to request to transfer part of the service data stream to be transmitted on the PDU session corresponding to the second terminal. The second request message carries the address information of the second terminal. For example, the content carried by the second request message is (UE#2addr, multi path requirement), where UE#2addr is the address information of the second terminal, and multi path requirement is used to indicate that the second request message is for multi-terminal joint session management.

[0202] The address information of the second terminal may be, for example, the IP address of the second terminal. The second request message may carry the address information of at least one second terminal.

[0203] In the embodiments of this application, optionally, the second request message further includes at least one of the following:

[0204] Service descriptor;

[0205] Service flow template.

[0206] Among them, the service descriptor is used to indicate the service that the terminal needs to transfer. The service flow template is used to indicate the service flow that the terminal needs to transfer.

[0207] Step 1: According to the second request message, AF determines to request the core network to reserve PDU session resources and / or establish QoS flows for the second terminal, and sends a first request message (i.e., Nnef_AFsessionWithQoS_Createrequest in the figure) to the NEF. The first request message is used to request the core network to reserve PDU session resources and / or establish QoS flows for the second terminal, and the first request message contains the address information of the second terminal.

[0208] In the embodiment shown in the figure, the first request message further includes the following content: UE address, AFIdentifier, Flow description(s)), [UE#2Addr,], QoS reference, Alternative Service Requirements (optional), where UE address is the address information of the first terminal, AF Identifier is the identifier of the AF, Flow description(s) is the flow description field, [UE#2Addr,] is the address information of the second terminal, QoS reference is the QoS reference information, and Alternative Service Requirements (optional) are the optional service requirements.

[0209] The first request message can carry the address information of the second terminal in one of the following two ways:

[0210] Implicitly carried through the flow description field (Flow descriptor) in the first request message; (i.e., the address information of the second terminal is included in the Flow descriptor)

[0211] Or

[0212] Explicitly carried through a separate field in the first request message, which is used to indicate that the Flow descriptor is used to reserve PDU session resources for the second terminal and establish the corresponding QoS flow.

[0213] In the embodiment of this application, the address information of the second terminal is implicitly carried through the flow description field (Flow descriptor) in the first request message.

[0214] Step 2: After receiving the first request message, the NEF authenticates and authorizes the first request message of the AF.

[0215] Step 3: The NEF sends a policy authorization request message (i.e., Npcf_PolicyAuthorization_Create request) to the first PCF corresponding to the first terminal according to the first request message. The policy authorization request message is used to indicate the generation or update of the PCC rules for the PDU session corresponding to the second terminal, and the address information of the second terminal is carried in the policy authorization request.

[0216] If the first request message implicitly carries the address information of the second terminal through the flow descriptor, similarly, the policy authorization request message also implicitly carries the address information of the second terminal through the flow descriptor.

[0217] If the first request message explicitly carries the address information of the second terminal through a separate field, similarly, the policy authorization request message also explicitly carries the address information of the second terminal through a separate field.

[0218] In the embodiment shown in the figure, the policy authorization request message further includes the following content: UE address, AFIdentifier, Flow description(s)), [UE#2Addr,], QoS reference, Alternative Service Requirements (optional), where UE address is the address information of the first terminal, AF Identifier is the identifier of the AF, Flow description(s) is the flow descriptor field, [UE#2Addr,] is the address information of the second terminal, QoS reference is the QoS reference information, and Alternative Service Requirements (optional) are optional service requirements.

[0219] Step 4: The first PCF determines the second PCF corresponding to the second terminal according to the address information of the second terminal in the policy authorization request message.

[0220] Step 5: The first PCF forwards the received policy authorization request message (i.e., Npcf_PolicyAuthorization_Create request) to the second PCF.

[0221] Step 6: The second PCF triggers the generation or update of Policy Control and Charging (PCC) rules based on the fact that the Flow descriptor in the policy authorization request message corresponds to the PDU session of the second terminal, and sends the generated or updated PCC rules to the second SMF corresponding to the second terminal, for performing the PDU session update process corresponding to the second terminal and adding corresponding QoS flows, that is, performing the SM Policy Association Modification procedure.

[0222] Steps 7 and 8: The second PCF sends a response to the policy authorization request message (i.e., Npcf_PolicyAuthorization_Create response) to the NEF through the first PCF.

[0223] It should be noted that for the multi-terminal joint session management method provided in the embodiments of the present application, the execution entity may be a multi-terminal joint session management device, or a control module in the multi-terminal joint session management device for executing the multi-terminal joint session management method. In the embodiments of the present application, the multi-terminal joint session management device is used as an example to execute the multi-terminal joint session management method to illustrate the multi-terminal joint session management device provided in the embodiments of the present application.

[0224] Please refer to Figure 12 , the embodiments of the present application also provide a multi-terminal joint session management device 120, including:

[0225] An obtaining module 121, configured to obtain the address information of the second terminal from the first message, where the first message is related to the PDU session corresponding to the first terminal;

[0226] A determining module 122, configured to determine a target core network network element corresponding to the second terminal according to the address information of the second terminal;

[0227] A sending module 123, configured to send a second message to the target core network network element, where the second message is used to request the target core network network element to reserve PDU session resources and / or establish a Quality of Service (QoS) flow for the second terminal.

[0228] Optionally, the address information of the second terminal is implicitly carried by a flow description field in the first message;

[0229] Or

[0230] The address information of the second terminal is explicitly carried by a separate field in the first message.

[0231] Optionally, the multi-terminal joint session management device 120 is the NEF;

[0232] The first message is the first request message received by the NEF, and the first request message is used to request the core network to reserve PDU session resources and / or establish a QoS flow for the second terminal. The first request message includes the address information of the second terminal;

[0233] The target core network element is the second policy control function entity PCF corresponding to the second terminal;

[0234] The second message is a policy authorization request message, and the policy authorization request message is used to indicate the generation or update of a PCC rule for the PDU session corresponding to the second terminal.

[0235] Optionally, the multi-terminal joint session management device 120 is the first PCF corresponding to the first terminal;

[0236] The first message is the policy authorization request message received by the first PCF, and the policy authorization request message is used to indicate the generation or update of a policy control and charging PCC rule for the PDU session corresponding to the second terminal. The policy authorization request message includes the address information of the second terminal;

[0237] The target core network element is the second session management function SMF corresponding to the second terminal;

[0238] The second message is the generated or updated PCC rule.

[0239] Optionally, the multi-terminal joint session management device 120 is the first PCF corresponding to the first terminal;

[0240] The first message is the policy authorization request message received by the first PCF, and the policy authorization request message is used to indicate the generation or update of a PCC rule for the PDU session corresponding to the second terminal. The policy authorization request message includes the address information of the second terminal;

[0241] The target core network element is the second PCF corresponding to the second terminal;

[0242] The second message is the policy authorization request message.

[0243] Optionally, the address information is IP address information.

[0244] The multi-terminal joint session management device provided by the embodiments of the present application can implement Figures 2 - 5 each process implemented by the method embodiments and achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0245] Please refer to Figure 13 , the embodiment of the present application further provides a multi-terminal joint session management device 130, including:

[0246] A receiving module 131, configured to receive a second message related to a PDU session corresponding to a first terminal, where the second message is used to request the target core network element to reserve PDU session resources for a second terminal and / or establish a QoS flow;

[0247] An execution module 132, configured to perform related operations according to the second message, where the related operations include at least one of the following operations:

[0248] Generate or update a PCC rule for the PDU session corresponding to the second terminal;

[0249] Execute the PDU session update process corresponding to the second terminal and add a corresponding QoS flow.

[0250] Optionally, the multi-terminal joint session management device 130 is a second PCF corresponding to the second terminal;

[0251] The second message is a policy authorization request message, and the policy authorization request message is used to instruct the second PCF to generate or update a PCC rule for the PDU session corresponding to the second terminal;

[0252] The execution module 132 is configured to generate or update a PCC rule for the PDU session corresponding to the second terminal, and send the generated or updated PCC rule to a second SMF corresponding to the second terminal.

[0253] Optionally, the multi-terminal joint session management device 130 is a second SMF corresponding to the second terminal;

[0254] The second message is a generated or updated PCC rule;

[0255] The execution module 132 is configured to execute the PDU session update process corresponding to the second terminal and add a corresponding QoS flow.

[0256] The multi-terminal joint session management device provided by the embodiment of the present application can implement Figure 6 each process implemented by the method embodiment, and achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0257] Please refer to Figure 14 , the embodiment of the present application further provides a multi-terminal joint session management device 140, including:

[0258] A sending module 141, configured to send a second request message for requesting to transfer part of service data streams to be transmitted on a PDU session corresponding to a second terminal, where the second request message includes address information of the second terminal.

[0259] In an embodiment of the present application, optionally, the second request message further includes at least one of the following:

[0260] A service descriptor;

[0261] A service flow template.

[0262] Wherein, the service descriptor is used to indicate the service that the terminal needs to transfer. The service flow template is used to indicate the service flow that the terminal needs to transfer.

[0263] Optionally, the address information is IP address information.

[0264] Optionally, the sending module 141 is configured to send the second request message to an application server through an application layer.

[0265] The multi-terminal association session management device in an embodiment of the present application may be a device, a device with an operating system, or an electronic device, or may be a component, an integrated circuit, or a chip in a terminal. The device or the electronic device may be a mobile terminal or a non-mobile terminal. Exemplarily, the mobile terminal may include, but is not limited to, the types of the terminal 11 listed above, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a personal computer (PC), a television (TV), a teller machine, or a self-service machine, etc., which are not specifically limited in the embodiment of the present application.

[0266] The multi-terminal association session management device provided in an embodiment of the present application can implement Figure 7 each process implemented by the method embodiment and achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0267] Please refer to Figure 15 , an embodiment of the present application further provides a multi-terminal association session management device 150, including:

[0268] A receiving module 151, configured to receive a second request message sent by a first terminal, where the second request message is used to request to transfer part of service data streams to be transmitted on a PDU session corresponding to a second terminal, and the second request message includes address information of the second terminal;

[0269] A sending module 152, configured to send a first request message according to the second request message, where the first request message is used to request the core network to reserve PDU session resources and / or establish a QoS flow for the second terminal, and the first request message includes address information of the second terminal.

[0270] Optionally, the address information of the second terminal is implicitly carried through a flow description field in the first request message;

[0271] Or

[0272] The address information of the second terminal is explicitly carried through a separate field in the first request message.

[0273] Optionally, the address information is IP address information.

[0274] Optionally, the multi-terminal association session management device 150 is an AF.

[0275] The multi-terminal association session management device provided in the embodiments of the present application can implement Figure 8 each process implemented by the method embodiments, and achieve the same technical effects. To avoid repetition, details are not described herein again.

[0276] Optionally, as Figure 16 shown, the embodiments of the present application further provide a communication device 160, including a processor 161 and a memory 162, and a program or instruction stored in the memory 162 and executable on the processor 161. For example, when the communication device 160 is a terminal, when the program or instruction is executed by the processor 161, it implements each process of the multi-terminal association session management method embodiment executed by the terminal, and can achieve the same technical effects. When the communication device 160 is a network-side device, when the program or instruction is executed by the processor 161, it implements each process of the multi-terminal association session management method embodiment executed by the network-side device (the first core network element, the target core network element, or the first network-side device), and can achieve the same technical effects. To avoid repetition, details are not described herein again.

[0277] The embodiments of the present application further provide a terminal, including a processor and a communication interface. The communication interface is configured to send a second request message, where the second request message is used to request to transfer some service data streams to be transmitted on the PDU session corresponding to the second terminal, and the second request message includes address information of the second terminal. This terminal embodiment corresponds to the method embodiment on the terminal side. Each implementation process and implementation manner of the above method embodiment can be applied to this terminal embodiment, and can achieve the same technical effects. Specifically, Figure 17 FIG. is a schematic hardware structure diagram of a terminal for implementing the embodiments of the present application.

[0278] The terminal 170 includes, but is not limited to, at least some components such as a radio frequency unit 171, a network module 172, an audio output unit 173, an input unit 174, a sensor 175, a display unit 176, a user input unit 177, an interface unit 178, a memory 179, and a processor 1710.

[0279] Those skilled in the art can understand that the terminal 170 may further include a power supply (such as a battery) for powering each component. The power supply can be logically connected to the processor 1710 through a power management system, so as to manage functions such as charging, discharging, and power consumption management through the power management system. Figure 17 The terminal structure shown does not limit the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have a different component arrangement, which will not be elaborated here.

[0280] It should be understood that in the embodiments of the present application, the input unit 174 may include a graphics processing unit (GPU) 1741 and a microphone 1742. The graphics processor 1741 processes the image data of a static picture or video obtained by an image capturing device (such as a camera) in a video capture mode or an image capture mode. The display unit 176 may include a display panel 1761, and the display panel 1761 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 177 includes a touch panel 1771 and other input devices 1772. The touch panel 1771 is also called a touch screen. The touch panel 1771 may include two parts: a touch detection device and a touch controller. The other input devices 1772 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be elaborated here.

[0281] In the embodiments of the present application, after receiving the downlink data from the network side device, the radio frequency unit 171 processes it for the processor 1710; in addition, it sends the uplink data to the network side device. Generally, the radio frequency unit 171 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0282] The memory 179 can be used to store software programs or instructions as well as various data. The memory 179 mainly includes a program or instruction storage area and a data storage area. Among them, the program or instruction storage area can store an operating system, application programs or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 179 can include high-speed random access memory and can also include non-volatile memory. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. For example, at least one disk storage device, a flash memory device, or other non-volatile solid-state storage devices.

[0283] The processor 1710 can include one or more processing units; optionally, the processor 1710 can integrate an application processor and a modem processor. Among them, the application processor mainly processes an operating system, a user interface, and application programs or instructions, etc., and the modem processor mainly processes wireless communication, such as a baseband processor. It can be understood that the above-mentioned modem processor may not be integrated into the processor 1710 either.

[0284] Among them, the radio frequency unit 171 is used to send a second request message, and the second request message is used to request to transfer a part of the service data stream to be transmitted on the PDU session corresponding to the second terminal. The second request message includes the address information of the second terminal.

[0285] In an embodiment of the present application, optionally, the second request message further includes at least one of the following:

[0286] A service descriptor;

[0287] A service flow template.

[0288] Among them, the service descriptor is used to indicate the service that the terminal needs to transfer. The service flow template is used to indicate the service flow that the terminal needs to transfer.

[0289] Optionally, the address information is IP address information.

[0290] Optionally, the radio frequency unit 171 sends the second request message to the application server through the application layer.

[0291] In an embodiment of the present application, it can be triggered by one terminal to transfer a part of the service data stream to be transmitted on the PDU session of other terminals, so as to implement the joint session management between multiple terminals.

[0292] The embodiment of the present application further provides a network-side device, including a processor and a communication interface, where:

[0293] The processor is configured to obtain the address information of a second terminal from a first message, where the first message is related to a PDU session corresponding to a first terminal; determine a target core network element corresponding to the second terminal according to the address information of the second terminal, and the communication interface is configured to send a second message to the target core network element, where the second message is used to request the target core network element to reserve PDU session resources for the second terminal and / or establish a QoS flow.

[0294] Alternatively, the communication interface is configured to receive a second message related to a PDU session corresponding to a first terminal, where the second message is used to request the target core network element to reserve PDU session resources for a second terminal and / or establish a QoS flow; the processor is configured to perform related operations according to the second message, and the related operations include at least one of the following operations: generating or updating a PCC rule of a PDU session corresponding to the second terminal; performing a PDU session update process corresponding to the second terminal and adding a corresponding QoS flow.

[0295] Alternatively, the communication interface is configured to receive a second request message sent by a first terminal, where the second request message is used to request to transfer part of the service data stream to be transmitted on a PDU session corresponding to the second terminal, and the second request message includes the address information of the second terminal; send a first request message according to the second request message, where the first request message is used to request the core network to reserve PDU session resources for the second terminal and / or establish a QoS flow, and the first request message includes the address information of the second terminal.

[0296] This embodiment of the network-side device corresponds to the method embodiment of the above network-side device (the first core network element, the target core network element, or the first network-side device). Each implementation process and implementation manner of the above method embodiment can be applied to this embodiment of the network-side device, and the same technical effects can be achieved.

[0297] Specifically, the embodiment of the present application further provides a network-side device. As Figure 18 shown, the network device 1800 includes: an antenna 181, a radio frequency device 182, and a baseband device 183. The antenna 181 is connected to the radio frequency device 182. In the uplink direction, the radio frequency device 182 receives information through the antenna 181 and sends the received information to the baseband device 183 for processing. In the downlink direction, the baseband device 183 processes the information to be sent and sends it to the radio frequency device 182. The radio frequency device 182 processes the received information and then sends it out through the antenna 181.

[0298] The above frequency band processing device may be located in the baseband device 183. The methods performed by the network-side device in the above embodiments may be implemented in the baseband device 183, which includes a processor 184 and a memory 185.

[0299] The baseband device 183 may include, for example, at least one baseband board, on which a plurality of chips are provided, such as Figure 18 shown, where one of the chips is, for example, the processor 184, which is connected to the memory 185 to call a program in the memory 185 and execute the network device operations shown in the above method embodiments.

[0300] The baseband device 183 may further include a network interface 186 for interacting with the radio frequency device 182. This interface is, for example, a common public radio interface (CPRI for short).

[0301] Specifically, the network-side device in the embodiments of the present application further includes: instructions or programs stored on the memory 185 and executable on the processor 184. The processor 184 calls the instructions or programs in the memory 185 to execute Figure 5 、 Figure 6 or Figure 8 the methods performed by the respective modules shown, and achieve the same technical effects. To avoid repetition, they are not elaborated here.

[0302] The embodiments of the present application further provide a readable storage medium, on which a program or instructions are stored. When the program or instructions are executed by a processor, the various processes of the above embodiments of the multi-terminal joint session management method are implemented, and the same technical effects can be achieved. To avoid repetition, they are not elaborated here.

[0303] Wherein, the processor is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, etc.

[0304] The embodiments of the present application further provide a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above embodiments of the multi-terminal joint session management method, and the same technical effects can be achieved. To avoid repetition, they are not elaborated here.

[0305] It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, system chip, chip system, or system-on-chip, etc.

[0306] Another embodiment of the present application provides a computer program / program product. The computer program / program product is stored in a non-volatile storage medium. The program / program product is executed by at least one processor to implement each process of the above-mentioned multi-terminal federated session management method embodiment, and can achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0307] It should be noted that in this article, the terms "including", "comprising" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including one..." does not exclude the existence of additional identical elements in the process, method, article or device including that element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the reverse order according to the functions involved. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0308] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. The computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions for causing a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present application.

[0309] The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms without departing from the purpose of the present application and the scope protected by the claims, and all of them belong to the protection scope of the present application.

Claims

1. A multi-terminal federated session management method, characterized in that, Including: A first core network element obtains address information of a second terminal from a first message, where the first message is related to a protocol data unit (PDU) session corresponding to a first terminal; The first core network element determines a target core network element corresponding to the second terminal according to the address information of the second terminal; The first core network element sends a second message to the target core network element, where the second message is used to request the target core network element to reserve PDU session resources for the second terminal and / or establish a quality of service (QoS) flow.

2. The method according to claim 1, wherein: The address information of the second terminal is implicitly carried by a flow description field in the first message; Or The address information of the second terminal is explicitly carried by a separate field in the first message.

3. The method according to claim 1 or 2, wherein: The first core network element is a network exposure function (NEF); The first message is a first request message received by the NEF, where the first request message is used to request the core network to reserve PDU session resources for the second terminal and / or establish a QoS flow, and the first request message includes the address information of the second terminal; The target core network element is a second policy control function (PCF) entity corresponding to the second terminal; The second message is a policy authorization request message, where the policy authorization request message is used to indicate generating or updating a PCC rule for a PDU session corresponding to the second terminal.

4. The method according to claim 1 or 2, wherein: The first core network element is a first PCF corresponding to the first terminal; The first message is a policy authorization request message received by the first PCF, where the policy authorization request message is used to indicate generating or updating a policy control and charging (PCC) rule for a PDU session corresponding to the second terminal, and the policy authorization request message includes the address information of the second terminal; The target core network element is a second session management function (SMF) corresponding to the second terminal; The second message is a generated or updated PCC rule.

5. The method according to claim 1 or 2, wherein: The first core network element is a first PCF corresponding to the first terminal; The first message is a policy authorization request message received by the first PCF, where the policy authorization request message is used to indicate generating or updating a PCC rule for a PDU session corresponding to the second terminal, and the policy authorization request message includes the address information of the second terminal; The target core network element is a second PCF corresponding to the second terminal; The second message is the policy authorization request message.

6. The method according to claim 1, characterized in that The address information is IP address information.

7. A multi-terminal joint session management method, characterized in that, Including: The terminal sends a second request message to a first network - side device. The second request message is used to request to transfer part of the service data flow to be transmitted on the PDU session corresponding to a second terminal. The second request message contains the address information of the second terminal, so that the first network - side device can send a first request message according to the second request message. The first request message is used to request the core network to reserve PDU session resources for the second terminal and / or establish a QoS flow. The first request message contains the address information of the second terminal.

8. The method according to claim 7, wherein The second request message further includes at least one of the following: Service descriptor; Service flow template.

9. The method according to claim 7, wherein The address information is IP address information.

10. The method according to claim 7, characterized in that, The terminal sending the second request message includes: The terminal sends the second request message to an application server through the application layer.

11. A multi-terminal joint session management method, characterized in that, Including: A first network - side device receives a second request message sent by a first terminal. The second request message is used to request to transfer part of the service data flow to be transmitted on the PDU session corresponding to a second terminal. The second request message contains the address information of the second terminal; The first network - side device sends a first request message according to the second request message. The first request message is used to request the core network to reserve PDU session resources for the second terminal and / or establish a QoS flow. The first request message contains the address information of the second terminal.

12. According to the method of claim 11, wherein, The address information of the second terminal is implicitly carried through a flow description field in the first request message; Or The address information of the second terminal is explicitly carried through a separate field in the first request message.

13. The method according to claim 11, characterized in that, The address information is IP address information.

14. The method according to claim 11, wherein The first network - side device is an Application Function (AF).

15. A multi-terminal joint session management device, characterized in that, Including: An acquisition module, configured to acquire the address information of the second terminal from a first message. The first message is related to the PDU session corresponding to the first terminal; A determination module, configured to determine a target core - network network element corresponding to the second terminal according to the address information of the second terminal; A sending module, configured to send a second message to the target core - network network element. The second message is used to request the target core - network network element to reserve PDU session resources for the second terminal and / or establish a QoS flow.

16. According to the apparatus of claim 15, wherein, The address information of the second terminal is implicitly carried through a flow description field in the first message; Or The address information of the second terminal is explicitly carried through a separate field in the first message.

17. According to the apparatus of claim 15 or 16, wherein, The multi - terminal association session management apparatus is a Network Exposure Function (NEF); The first message is the first request message received by the NEF. The first request message is used to request the core network to reserve PDU session resources for the second terminal and / or establish a QoS flow. The first request includes the address information of the second terminal; The target core - network network element is a second Policy Control Function (PCF) entity corresponding to the second terminal; The second message is a policy authorization request message, which is used to indicate generating or updating a PCC rule for a PDU session corresponding to the second terminal.

18. The apparatus according to claim 15 or 16, wherein the multi-terminal association session management apparatus is a first PCF corresponding to the first terminal; the first message is a policy authorization request message received by the first PCF, which is used to indicate generating or updating a policy control and charging PCC rule for a PDU session corresponding to the second terminal, and the policy authorization request message includes address information of the second terminal; the target core network element is a second session management function SMF corresponding to the second terminal; the second message is an updated PCC rule.

19. The apparatus according to claim 15 or 16, wherein the multi-terminal association session management apparatus is a first PCF corresponding to the first terminal; the first message is a policy authorization request message received by the first PCF, which is used to indicate generating or updating a PCC rule for a PDU session corresponding to the second terminal, and the policy authorization request message includes the address information of the second terminal; the target core network element is a second PCF corresponding to the second terminal; the second message is the policy authorization request message.

20. The device according to claim 15, characterized in that The address information is IP address information.

21. A multi-terminal joint session management device, characterized in that, Comprising: a sending module, configured to send a second request message to a first network-side device, where the second request message is used to request transferring part of service data flows to be transmitted on a PDU session corresponding to the second terminal, and the second request message includes the address information of the second terminal, so that the first network-side device can send a first request message according to the second request message, and the first request message is used to request the core network to reserve PDU session resources and / or establish a QoS flow for the second terminal, and the first request message includes the address information of the second terminal.

22. The device according to claim 21, characterized in that, The second request message further includes at least one of the following: a service descriptor; a service flow template.

23. The device according to claim 21, characterized in that, The address information is IP address information.

24. The apparatus according to claim 21, wherein the sending module is configured to send the second request message to an application server through an application layer.

25. A multi-terminal joint session management device, characterized in that, Comprising: a receiving module, configured to receive a second request message sent by a first terminal, where the second request message is used to request transferring part of service data flows to be transmitted on a PDU session corresponding to the second terminal, and the second request message includes the address information of the second terminal; a sending module, configured to send a first request message according to the second request message, where the first request message is used to request the core network to reserve PDU session resources and / or establish a QoS flow for the second terminal, and the first request message includes the address information of the second terminal.

26. The apparatus according to claim 25, wherein the address information of the second terminal is implicitly carried by a flow description field in the first request message; or The address information of the second terminal is explicitly carried through a separate field in the first request message.

27. The device according to claim 25, characterized in that, The address information is IP address information.

28. A core network element, characterized in that, It includes a processor, a memory, and a program or instructions stored on the memory and executable on the processor. When the program or instructions are executed by the processor, the steps of the multi-terminal federated session management method according to any one of claims 1 to 6 are implemented.

29. A terminal, characterized in that, It includes a processor, a memory, and a program or instructions stored on the memory and executable on the processor. When the program or instructions are executed by the processor, the steps of the multi-terminal federated session management method according to any one of claims 7 to 10 are implemented.

30. A network-side device, characterized in that, It includes a processor, a memory, and a program or instructions stored on the memory and executable on the processor. When the program or instructions are executed by the processor, the steps of the multi-terminal federated session management method according to any one of claims 11 to 14 are implemented.

31. A readable storage medium, characterized in that, A program or instructions are stored on the readable storage medium. When the program or instructions are executed by a processor, the multi-terminal federated session management method according to any one of claims 1 to 6 is implemented, or the steps of the multi-terminal federated session management method according to any one of claims 7 to 10 are implemented, or the steps of the multi-terminal federated session management method according to any one of claims 11 to 14 are implemented.

Images