CN113453160B

CN113453160B - Communication method and related equipment

Info

Publication number: CN113453160B
Application number: CN202010231129.9A
Authority: CN
Inventors: 谢振华; 柯小婉
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-03-27
Filing date: 2020-03-27
Publication date: 2023-04-25
Anticipated expiration: 2040-03-27
Also published as: CN113453160A

Abstract

The invention provides a communication method and related equipment, wherein the communication method comprises the following steps: invoking a multicast session context operation by a second network function, wherein the multicast session context operation carries first multicast information, and the first multicast information comprises at least one of a Temporary Mobile Group Identifier (TMGI), a TMGI list, an Internet Protocol (IP) multicast address and a request type; and based on the first multicast information, indicating a third network function to activate or deactivate dedicated channel resources. The communication method provided by the invention can realize the activation state of the special channel resource selected by the network side, avoid the special channel between the third network function and the terminal occupying the transmission resource of the network side when idle, and improve the utilization rate of the transmission resource of the network side.

Description

Communication method and related equipment

Technical Field

The present invention relates to the field of wireless communications technologies, and in particular, to a communication method and related devices.

Background

In the multicast session process of the wireless communication system, the network side may adopt a dedicated mode or a sharing mode to implement transmission of service data of multiple terminals (UEs). For example, in the fifth generation mobile communication system, in the case of transmitting service data in a dedicated mode, a network function of a network side (such as a core network) may copy a plurality of identical service data, and directly transmit one service data to each of a plurality of other terminals through a dedicated channel between the network function and each terminal; in the case that the network side adopts the sharing mode to transmit the service data, the network function can send the service data to the base station through the sharing channel between the network function and the base station of the cell where the plurality of terminals are located, and then the base station transmits the service data to the plurality of terminals through the dedicated mode or the sharing mode. However, at present, in the multicast session process, there may be a waste of transmission resources on the network side, so that the utilization rate of the transmission resources on the network side is reduced.

Disclosure of Invention

The embodiment of the invention provides a communication method and related equipment, which are used for solving the problem that the utilization rate of transmission resources is low in the multicast session process of a network side.

In order to solve the technical problems, the invention is realized as follows:

in a first aspect, an embodiment of the present invention provides a communication method, applied to a first network function, including:

invoking a multicast session context operation by a second network function, wherein the multicast session context operation carries first multicast information, and the first multicast information comprises at least one of a Temporary Mobile Group Identifier (TMGI), a TMGI list, an Internet Protocol (IP) multicast address and a request type;

and based on the first multicast information, indicating a third network function to activate or deactivate dedicated channel resources.

In a second aspect, an embodiment of the present invention further provides a communication method, applied to a fourth network function, including:

calling a multicast user mode operation by a first network function, wherein the multicast user mode operation carries second multicast information, and the second multicast information comprises at least one of TMGI, TMGI list, IP multicast address and request type;

and based on the second multicast information, returning a first return result to the first network function, wherein the first return result is used for indicating that the mode is changed or the mode being used by the user.

In a third aspect, an embodiment of the present invention further provides a communication method, which is applied to a terminal, including:

and sending a multicast message or a multicast message to a network side, wherein the multicast message or the multicast message carries third multicast information, and the third multicast information comprises at least one of TMGI, TMGI list, IP multicast address and request type.

In a fourth aspect, an embodiment of the present invention further provides a network function, where the network function is a first network function, including:

an operation called module, configured to call a multicast session context operation by a second network function, where the multicast session context operation carries first multicast information, where the first multicast information includes at least one of a temporary mobile group identifier TMGI, a TMGI list, an internet protocol IP multicast address, and a request type;

and the processing module is used for indicating a third network function to activate or deactivate the special channel resource based on the first multicast information.

In a fifth aspect, an embodiment of the present invention further provides a network function, where the network function is a fourth network function, including:

an operation calling module, configured to call a multicast user mode operation by a first network function, where the multicast user mode operation carries second multicast information, where the second multicast information includes at least one of a TMGI, a TMGI list, an IP multicast address, and a request type;

And the result return module is used for returning a first return result to the first network function based on the second multicast information, wherein the first return result is used for indicating a mode change or a mode being used by a user.

In a sixth aspect, an embodiment of the present invention further provides a terminal, including:

a sending module, configured to send a multicast message or a multicast message to a network side, where the multicast message or the multicast message carries third multicast information, where the third multicast information includes at least one of a TMGI, a TMGI list, an IP multicast address, and a request type.

In a seventh aspect, an embodiment of the present invention further provides a network function, including: a memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor performs the steps in the communication method according to the first or second aspect.

In an eighth aspect, an embodiment of the present invention further provides a terminal, including: a memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor, performs the steps in the communication method according to the third aspect.

In a ninth aspect, an embodiment of the present invention further provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor implements the steps of the communication method according to the first, second or third aspects.

In the embodiment of the invention, a multicast session context operation is called by a second network function, wherein the multicast session context operation carries first multicast information, and the first multicast information comprises at least one of a Temporary Mobile Group Identifier (TMGI), a TMGI list, an Internet Protocol (IP) multicast address and a request type; and based on the first multicast information, indicating a third network function to activate or deactivate dedicated channel resources. Therefore, the activation state of the special channel resources can be selected, the special channel between the third network function and the terminal is prevented from occupying the transmission resources of the network side when idle, and the utilization rate of the transmission resources of the network side is improved.

Drawings

Fig. 1 is a schematic structural diagram of a network system according to an embodiment of the present invention;

FIG. 2 is a schematic flow chart of a communication method according to an embodiment of the present invention;

fig. 3 is a schematic flow chart of a communication method in practical application according to an embodiment of the present invention;

FIG. 4 is a second flow chart of the communication method according to the embodiment of the invention in practical application;

FIG. 5 is a third flow chart of the communication method according to the embodiment of the present invention in practical application;

FIG. 6 is a schematic flow chart of a communication method according to an embodiment of the present invention in practical application;

FIG. 7 is a schematic flow chart of a communication method according to an embodiment of the present invention in practical application;

FIG. 8 is a flowchart of a communication method according to an embodiment of the present invention in practical application;

FIG. 9 is a second flow chart of a communication method according to the embodiment of the invention;

FIG. 10 is a third flow chart of a communication method according to an embodiment of the present invention;

fig. 11 is a schematic structural diagram of a first network function according to an embodiment of the present invention;

fig. 12 is a schematic structural diagram of a fourth network function provided by an embodiment of the present invention;

fig. 13 is a schematic structural diagram of a terminal according to an embodiment of the present invention;

fig. 14 is a schematic hardware structure of a terminal according to an embodiment of the present invention;

fig. 15 is a schematic hardware structure of a network side device according to an embodiment of the present invention.

Detailed Description

The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus. Furthermore, the use of "and/or" in the specification and claims means at least one of the connected objects, e.g., a and/or B, meaning that it includes a single a, a single B, and that there are three cases of a and B.

In embodiments of the invention, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g." in an embodiment should not be taken as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

Embodiments of the present invention are described below with reference to the accompanying drawings. The embodiment provided by the invention can be applied to a wireless communication system. The wireless communication system may be a 5G system, or an evolved long term evolution (Evolved Long Term Evolution, elet) system, or a subsequent evolved communication system.

Fig. 1 is a block diagram of a network system according to an embodiment of the present invention, as shown in fig. 1, including a terminal 11 and a network side device 12, where the terminal 11 may be a mobile communication device, for example: it should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present invention, and may be a mobile phone, a tablet (Tablet Personal Computer), a Laptop (Laptop), a personal digital assistant (personal digital assistant, PDA for short), a mobile internet Device (Mobile Internet Device, MID) or a Wearable Device (Wearable Device). The network side device 12 may be a 5G network side device (e.g. a gNB, a 5G NR NB), or may be a 4G network side device (e.g. an eNB), or may be a 3G network side device (e.g. an NB), or a network side device in a subsequent evolution communication system, etc., which should be noted that the specific type of the network side device 12 is not limited in the embodiment of the present invention.

In this embodiment, the network side device 12 may include nodes and network function entities for multicast data transmission, and specifically, the network side device 12 may include base station nodes (such as radio access network (Radio Access Network, RAN) nodes), access and mobility management functions (Access and Mobility Management Function, AMF), session management functions (Session Management Function, SMF), user plane functions (User Plane Function, UPF), multicast SMF (Multicast Broadcast-SMF, MB-SMF), multicast UPF (MB-UPF), and multicast service functions (Multicast Broadcast Service Function, MBSF), where the AMF, UPF, SMF, MB-SMF, MB-UPF, and MBSF are entity devices in the network side device 12, respectively.

Referring to fig. 2, fig. 2 is a flow chart of a communication method provided in the present embodiment, which is applied to a first network function, as shown in fig. 2, and the communication method includes the following steps:

step 201, invoking a multicast session context operation by a second network function, wherein the multicast session context operation carries first multicast information, the first multicast information including at least one of a temporary mobile group identity (Temporary Mobile Group Identifier, TMGI), a TMGI list, an internet protocol (Internet Protocol, IP) multicast address, and a request type;

step 202, based on the first multicast information, the third network function is instructed to activate or deactivate dedicated channel resources.

Here, in the multicast session process, the first network function may instruct the third network function to activate or deactivate the dedicated channel resource based on the multicast information (i.e., the first multicast information) carried by the multicast session context operation under the condition that the multicast session context operation is invoked by the second network function, so as to implement the activation state of selecting the dedicated channel resource by the network side, avoid that the dedicated channel between the third network function and the terminal occupies the transmission resource of the network side when idle, and improve the utilization rate of the transmission resource of the network side.

In the step 201, in the case that the network side performs the multicast session with the terminal, the second network function may invoke the session context operation carrying the first multicast information to the first network function.

In this embodiment, the first multicast information may include at least one of a TMGI, a TMGI list, an IP multicast address, and a request type, for example, the first multicast information may include a TMGI list, an IP multicast address, and a request type, and so on. The content carried in the first multicast information may be preconfigured or agreed by a protocol, which is not limited herein.

In some embodiments, the first multicast information does not contain the TMGI or the TMGI list if the first multicast information includes a request type and the request type indicates an away or session termination, or if the first multicast information does not include a request type.

In addition, in some cases, the network side may further instruct, according to the first multicast information, user departure, session termination, session update, session new, or the like, specifically, the first multicast information includes a request type and the request type is used to instruct user departure or session termination, or instruct user departure or session termination when the first multicast information does not include a TMGI and a TMGI list, or instruct user departure or session termination when the first multicast information does not include a request type.

Here, whether to configure the TMGI or the TMGI list in the first multicast information may be determined according to a type indicated by a request type included in the first multicast information or whether the request type is included in the first multicast information.

It should be noted that, the first multicast information may include other information, for example, the first multicast information may further include an IP address of the terminal, or IP address and port number information of the terminal, etc.; of course, the multicast session context operation may carry other information besides the first multicast information, and specifically, the multicast session context operation may also carry a user identifier of the terminal; alternatively, the multicast session context operation may also carry user plane downlink point information.

In this embodiment, the second network function may call the multicast session context of the first network function by using the multicast session context of the second network function when the terminal sends a multicast message or a multicast message carrying third multicast information to the network side, that is, when the second network function receives the multicast message or the multicast message sent by the terminal, the second network function calls the multicast session context of the first network function in response to the multicast message or the multicast message.

The terminal sends a multicast message or a multicast message carrying third multicast information to the network side, which may be that the terminal directly sends the multicast message or the multicast message to the second network function; alternatively, the terminal may forward the multicast message or the multicast message to the second network function through another network function on the network side, which is not limited herein.

In addition, the multicast message or multicast message may include a protocol data unit (Protocol Data Unit, PDU) session establishment (Session Establishment) message or a PDU session modification (Session Modification) message, etc.; the multicast message may include a Join message of an internet group management protocol (Internet Group Management Protocol, IGMP) protocol, or a Join message of a multicast listener discovery protocol (Multicast Listener Discover, MLD) protocol, etc.

Note that the third multicast information may include at least one of a TMGI, a TMGI list, an IP multicast address, and a request type, and the first multicast information and the third multicast information may be the same or different information, that is, the content included in the first multicast information and the content included in the third multicast information may be the same or different, which is not limited herein.

Likewise, in some embodiments, in a case where the third multicast information includes a request type and the request type indicates leaving or session termination, or in a case where the third multicast information does not include a request type, the third multicast information does not include the TMGI or the TMGI list, so that whether to configure the TMGI or the TMGI list in the third multicast information may also be determined according to a type indicated by a request type included in the third multicast information, or whether a request type is included in the third multicast information.

In addition, the network side may also instruct the user to leave, terminate the session, update the session, or newly establish the session according to third multicast information, specifically, the third multicast information does not include TMGI and TMGI list to instruct the user to leave or terminate the session, or instruct the user to leave or terminate the session when the third multicast information does not include the request type.

In this embodiment, the first network function is a network function entity device in the network side, and may be any network function capable of being invoked for the multicast session context operation. For example, the first network function may be the MB-SMF, or may be composed of the MBSF and the MB-SMF together, or the like.

In addition, the second network function is a network function entity device in the network side, and may be any network function capable of invoking the multicast session context operation of the first network function, and specifically, the second network function may be the AMF or the SMF.

In an exemplary embodiment, in a case where the first network function is composed of the MBSF and the MB-SMF, and the second network function is an SMF, if the SMF receives a multicast message sent by a terminal directly sent by the terminal, or if the SMF receives a multicast sent by the terminal through a user plane and forwarded by the UPF, the SMF invokes a multicast session context operation of the network function composed of the MBSF and the MB-SMF.

In the step 102, after the first network function is called by the second network function to perform the multicast session context operation, the first network function may instruct the third network function to activate or deactivate the dedicated channel resource based on the first multicast information carried in the call multicast session context operation.

In this embodiment, the third network function is a network function entity device in the network side, a dedicated channel for implementing the direct transmission of service data from the network side to the terminal is established between the third network function and the terminal, and the dedicated channel occupies a transmission resource of the network side, and in particular, the third network function may be the MB-UPF.

In addition, the first network function instructs the third network function to activate or deactivate the dedicated channel resource based on the first multicast information, which may be that the first network function generates instruction information according to the first multicast information, sends the instruction information to the third network function, and instructs the third network function to activate or deactivate the dedicated channel resource through the instruction information.

For example, in the case where the first network function is composed of MB-SMF and MBSF together and the third network function is MB-UPF, if the first network function determines, according to the first multicast information, that it needs to switch from the dedicated mode to the shared mode to transmit service data, the first network function generates a deactivation instruction and sends the deactivation instruction to the MB-UPF, where the MB-UPF deactivates the dedicated channel resource of the dedicated channel between the MB-UPF and the terminal when receiving the deactivation instruction.

In some embodiments, the step 102 may include:

calling a multicast user mode operation of the fourth network function based on the first multicast information, wherein the multicast user mode operation carries second multicast information, and the second multicast information comprises at least one of TMGI, TMGI list, IP multicast address and request type;

Receiving a first return result returned by the fourth network function based on the second multicast information, wherein the first return result is used for indicating a mode change or a mode being used by a user;

and based on the first returned result, the third network function is instructed to activate or deactivate dedicated channel resources.

Here, the first network function may invoke the multicast user mode operation of the fourth network function based on the first multicast information, and receive a first return result returned by the fourth network function based on the second multicast information carried by the multicast user mode operation to instruct the third network function to activate or deactivate the dedicated channel resource, so that the fourth network function may select to activate or deactivate the dedicated channel resource.

In this embodiment, the fourth network function is a network function entity device in the network side, and is capable of returning the first return result to the first network function based on the second multicast information carried by the multicast user mode operation. Specifically, in the case where the first network function is MB-SMF, the fourth network function is MBSF.

In addition, the first returned result may include any information indicating that the mode is changed or that the user is using.

In some embodiments, in a case where the first return result is used to indicate that a mode change occurs, the first return result includes:

a mode selection indication and a mode change indication; or alternatively

A mode selection indication and a mode in-use indication, wherein the mode in-use indication is used for indicating a mode being used by a user; or alternatively

The removed TMGI, or IP multicast address, or TMGI list.

The mode selection indication is used for indicating a transmission mode of the service data to be used by the network side, and the mode change indication is used for indicating that the transmission mode to be used is changed from the currently used transmission mode, for example, when the first return result includes the mode selection indication and the mode change indication which indicate the sharing mode, the transmission mode of the service data transmitted by the network side is changed, and the transmission mode is changed to the sharing mode.

In addition, the first return result can also be changed through a mode selection instruction and a mode in a transmission mode adopted by the terminal for transmitting service data at the network side by using the instruction. For example, in the case where the above-described mode selection indication is used to indicate the sharing mode, and the above-described mode is used to indicate the dedicated mode, the first return result may indicate that the transmission mode is changed, and the dedicated mode is changed to the sharing mode.

Of course, if the first return result includes the removed TMGI, or the IP multicast address, or the TMGI list, and the removed TMGI, or the IP multicast address, or the TMGI list is associated with the terminal, the first return result may also indicate that the transmission mode adopted by the network side for transmitting the service data to the terminal is changed.

In other embodiments, where the first return result is used to indicate a mode being used by the user, the first return result includes a mode in use indication, so that the mode being used by the user may be explicitly indicated.

For example, the first return result includes a dedicated indication for indicating that the network side and the terminal are using a dedicated mode for data transmission; or the first return result comprises a sharing indication, wherein the special sharing is used for indicating that the network side and the terminal are transmitting data in a sharing mode.

Of course, in the case that the first return result is used to indicate the mode that the user is using, the first return result may also implicitly indicate the mode that the user is using, for example, may indicate that the user is using a dedicated mode in the case that the first return result is without a mode indication; and in the case that the first returned result includes a mode indication, indicating that the user is using the sharing mode.

It should be noted that, the first return result is used to indicate that the mode is changed or used to indicate that the mode is being used by the user, and may be agreed by a protocol or preconfigured; alternatively, the first feedback result may be flexibly selected according to the second multicast information, for example, when the second multicast information is multicast information 1, the first feedback result is used to indicate that the mode is changed; and in the case that the second multicast information is multicast information 2, the first return result is used to indicate the mode that the user is using.

In some implementations, the first return result indicates that a mode change occurred if the second multicast information includes a request type and the request type indicates an update or a new, or if the second multicast information does not include a request type, or if the second multicast information includes the TMGI or the TMGI list or the IP multicast address.

In this embodiment, the second multicast information may include at least one of a TMGI, a TMGI list, an IP multicast address, and a request type, and the first multicast information and the second multicast information may be the same or different information, that is, the content included in the first multicast information and the content included in the second multicast information may be the same or different, which is not limited herein.

Specifically, when the first multicast information carries a request type and the request type indicates that the user leaves or the session is terminated, the second multicast information does not carry a TMGI or a TMGI list or an IP multicast address, so that whether the second multicast information carries a TMGI or a TMGI list or an IP multicast address can be determined according to the request type carried by the first multicast information.

Similarly, the network side may also instruct the user to leave, terminate the session, update the session, or newly create the session according to the second multicast information, specifically, instruct the user to leave or terminate the session when the second multicast information includes a request type and the request type is used to instruct the user to leave or terminate the session, or instruct the user to leave or terminate the session when the second multicast information does not include a TMGI and a TMGI list, or instruct the user to leave or terminate the session when the second multicast information does not include a request type.

In addition, in the case where the second multicast information includes a request type and the request type indicates departure or session termination, or in the case where the multicast information does not include a request type, the second multicast information does not include the TMGI or the TMGI list, so that whether to configure the TMGI or the TMGI list in the second multicast information may also be determined according to the type indicated by the request type included in the second multicast information, or whether the request type is included in the second multicast information.

In this embodiment, when the first network function receives the first return result returned by the fourth network function, the first network function may instruct the third network function to activate or deactivate the dedicated channel resource based on the first return result.

Specifically, the indicating, based on the first returned result, the third network function to activate or deactivate the dedicated channel resource includes:

in the case that the first returned result indicates that the mode is changed to the dedicated mode, indicating the third network function to activate the dedicated channel resource; or alternatively, the process may be performed,

and in the case that the first returned result indicates that the mode is changed to the sharing mode or that the user is using the dedicated mode, the fourth network function is instructed to deactivate the dedicated channel resource.

Here, under the condition that the first return result indicates that the mode is changed to the sharing mode or indicates that the user is using the dedicated mode, the first network function may instruct the third network function to deactivate the dedicated channel resource, so as to release the transmission resource occupied by the dedicated channel in time, and improve the utilization rate of the transmission resource.

In this embodiment, after the second network function invokes the multicast session context operation of the first network function, the first network function may also return a second return result to the second network function based on the first multicast information carried in the multicast session context operation.

For example, in the case that the second network function invokes the multicast session context operation of the first network function, the first network function invokes the multicast user mode operation of the fourth network function based on the first multicast information carried by the multicast session context operation, the fourth network function returns a first return result to the first network function based on the second multicast information carried by the multicast user mode operation, and the first network function returns a second return result to the second network function based on the first return result.

The first return result and the second return result may be the same or different when the second return result is returned based on the first return result, for example, when the first return result is used to indicate that the mode is changed, the second return result may also include: a mode select indication and a mode change indication, or a mode select indication and a mode in use indication, or a removed TMGI or IP multicast address or TMGI list; or, in the case that the second return result is used for indicating the mode being used by the user, the second return result includes a mode in use indication.

It should be noted that, after the second network function receives the second return result, some operations related to the service data transmission may be performed by the second network function, specifically, the second network function may instruct the fifth network function to activate or deactivate the dedicated channel resource based on the second return result, for example, the second network function is SMF and the fifth network function is UPF, that is, the SMF may instruct the UPF to activate or deactivate the dedicated channel resource based on the second return result, so as to further improve the utilization ratio of the network side transmission resource; alternatively, the second network function may update its own stored information based on the second returned result, and so on.

In this embodiment, the information included in the second returned result may be a protocol contract or a pre-configuration, etc.; alternatively, the information included in the second returned result may be determined based on the first multicast information.

Specifically, after the step 101, the method may further include:

returning a second return result to a second network function based on the first multicast information;

under the condition that the first multicast information indicates that a user leaves or a session is terminated, the second return result does not carry mode selection information or carries user plane downlink point information, wherein the special channel resource is associated with the user plane downlink point information; or alternatively, the process may be performed,

and under the condition that the first multicast information indicates that the user does not leave or the session is not terminated, the second return result carries mode selection information or does not carry user plane downlink point information.

Here, the first network function may determine whether the second returned result carries mode selection information or user plane downlink point information according to whether the first multicast information indicates whether the user leaves or the session is terminated.

Alternatively, in other embodiments, after receiving the first return result returned by the fourth network function based on the multicast user mode operation, the method may further include:

Returning a second return result to the second network function based on the first return result;

under the condition that the first return result indicates a mode which is being used by a user, the second return result does not carry mode selection information or carries user plane downlink point information, wherein the special channel resource is associated with the user plane downlink point information; or alternatively, the process may be performed,

and under the condition that the first return result does not indicate the mode which is being used by the user, the second return result carries mode selection information or does not carry user plane downlink point information.

Here, the first network function may determine whether the second returned result carries mode selection information or user plane downlink point information according to whether the first returned result indicates a mode that the user is using.

It should be noted that, the mode selection information is used to indicate a transmission mode to be used by the network side when transmitting new service data, for example, the mode selection information may include the mode selection instruction; the user plane downlink point information may be at least one of user plane downlink point information stored in advance by the first network function and user plane downlink point information carried by the multicast session context operation.

In addition, the above-mentioned user plane downlink point information may include at least one of an IP address, a port number, and a tunnel identification.

In some embodiments, the multicast session context operation further carries a user identification;

after the multicast session context operation is invoked by the second network function, the method further comprises:

and searching the downlink point information of the user plane corresponding to the user identifier.

Here, in the case that the first network function is called by the second network function to perform the multicast session context operation, the first network function may search whether there is user plane downlink point information corresponding to the user identifier according to the user identifier carried by the multicast session context operation.

It should be noted that, the first network function searches the user plane downlink point information corresponding to the user identifier, where the first network function may perform a related operation according to the searched user plane downlink point information, for example, in a case where the searched user plane downlink point information is different from the user plane downlink point information carried by the multicast session context operation, the first network function updates the stored user plane downlink point information to the user plane downlink point information carried by the multicast session context operation; or the first network function instructs the third network function to release or update the downlink point information of the user plane; or, carrying the searched user plane downlink point information through the second return result, so that the second network function indicates the fifth network function to release or update the user plane downlink point information according to the user plane downlink point information carried by the second return result, and the like.

In addition, in some embodiments, after the step 101, the method may further include:

transmitting identification information to a base station, wherein the identification information comprises:

PDU session identification or flow identification;

at least one of a TMGI, a TMGI list, and an IP multicast address corresponding to the PDU session identification or the flow identification.

Here, the first network function may further send the identification information to the base station after being called the multicast session context operation, thereby improving communication performance of the wireless communication system.

For the convenience of understanding the communication method provided in this embodiment, practical applications of the above communication method in the communication system architecture 1 and the communication system architecture 2, respectively, are provided herein, specifically referring to the following example one and example two.

Example one

As shown in fig. 3 to 5, the communication system architecture 1 performs a multicast session, and the communication system architecture 1 includes a terminal (i.e., UE), an SMF (i.e., second network function), a UPF (i.e., fifth network function), an MB-SMF (i.e., first network function), an MB-UPF (i.e., third network function), and an MBSF (i.e., fourth network function).

As shown in fig. 3, a process of establishing a dedicated channel in a multicast session between a network side and a terminal is specifically as follows:

Step 301, the terminal sends a multicast message 1 to the SMF, for example, a PDU Session Establishment or PDU Session Modification message carrying multicast information (such as multicast information including TMGI or IP multicast address or request type for indicating multicast establishment), or an IGMP (IPv 4) or MLD (IPv 6) Join message is sent through the user plane and forwarded to the SMF by the UPF.

Step 302, the SMF invokes a multicast Session Context operation of the MB-SMF (e.g. invokes an nmbsmf_session context_check operation), where parameters carried by the multicast Session Context operation include a user identifier, multicast information, and user plane downstream point information (the user plane downstream point information includes an IP address, a port number, and a tunnel identifier);

of course, the step 302 may also be implemented by the operation of the SMF calling the AMF and then the operation of the AMF calling the MB-SMF, that is, the AMF calling the multicast session context operation of the MB-SMF (the AMF is the second network function).

Step 303, the MB-SMF invokes a mode Check operation of the MBSF (i.e. multicast user mode operation) based on the multicast information carried by the multicast session context operation, for example, invokes an nmgsf_usermode_check operation, where parameters carried by the mode Check operation include a user identifier and multicast information (e.g. IP multicast address, TMGI, or TMGI list).

Step 304, MB-SMF returns a mode check result, which carries a dedicated indication (i.e., indicates a dedicated mode).

Step 305, the MB-SMF determines that the mode checking result is dedicated, and updates the resources related to the user plane downlink point information of the MB-UPF multicast group, for example, the MB-SMF sends the user plane downlink point information and the IP multicast address to the MB-UPF.

Step 306, the MB-SMF determines that the mode checking result is special, stores the user plane downlink point information, and associates the user plane downlink point information with the user identifier.

Step 307, the MB-SMF returns a multicast session context check result, where the multicast session context check result includes a user identifier and a dedicated indication, and possibly includes user plane downlink point information 1;

of course, the step 307 may be that the MB-SMF returns a result to the AMF, where the returned result includes the user identifier and the dedicated instruction, and the AMF returns the result to the SMF.

Step 308, the SMF determines that the mode selection result is a dedicated mode, and indicates the UPF to forward the data from the user plane downlink point to the dedicated channel indicated by the Session information (such as PDU Session ID, or PDU Session ID and QoS flow identifier (i.e. QFI));

wherein the session information may be selected by the user, e.g., when sending a message via the user plane; or, by SMF; alternatively, the portion selected by the user (e.g., the PDU Session ID contained in the message) is selected by the SMF (e.g., QFI).

The MB-UPF receives the data message sent to the appointed multicast group, forwards the data message to the downlink point of the user plane, and forwards the data received from the downlink point of the user plane to a special channel (namely, realizes the construction of the special channel between the network side and the terminal).

As shown in fig. 4, in a multicast session between a network side and a terminal, a first implementation manner for activating or deactivating dedicated channel resources is specifically as follows:

step 401, the terminal sends a multicast message 2 (i.e. the multicast message described above) to the SMF, for example, a PDU Session Establishment, PDU Session Modification or PDU Session Release message carrying multicast information (i.e. third multicast information), such as the multicast information including TMGI or IP multicast address or request type for indicating multicast update or new creation.

Step 402, the SMF invokes a multicast session context Check operation of the MB-SMF (i.e. the multicast session context operation described above), for example, invokes an nmbssf_session context_check operation, where parameters carried by the multicast session context Check operation include a user identifier, multicast information (i.e. first multicast information), and user plane downlink point information 1 (e.g. IP address, port number, tunnel identifier);

Of course, the step 402 may be an operation of the SMF to call the AMF, where the parameter includes the information, and the AMF (the second network function in this case) calls the MB-SMF.

Step 403, the MB-SMF invokes a mode Check operation of the MBSF (i.e. the multicast user mode operation described above), such as invoking an nmgsf_usermode_check operation, where the parameters carried by the mode Check operation include the user identification and multicast information (i.e. the second multicast information, including the multicast address or TMGI).

Step 404, the MB-SMF receives a mode check result (i.e., a first return result) returned by the MBSF, the result carrying a mode indication (i.e., a mode selection indication), such as a share indication or a dedicated indication, and if the mode previously used by the user (i.e., the mode indicated by the mode in use indication) is different from the mode indication (e.g., the dedicated was previously selected for sharing now, or the shared was previously selected for dedicated now), the result indicates that the mode has changed (i.e., a second return result includes a mode selection indication and a mode in use indication, and if the mode selection indication and the mode in use indication are different, the second return result indicates that the mode has changed).

Step 405, MB-SMF determines that the mode is changed to shared (meaning dedicated before), and searches for corresponding user plane downlink point information 2 through the user identifier (the user plane downlink point information 2 is the user plane downlink point information stored by the MB-SMF before this, as shown in fig. 3).

Step 406, if there is a mode change and the mode indication is shared (i.e. the mode selection indication indicates a shared mode), the MB-SMF instructs the MB-UPF to release the resources whose multicast address is related to the user plane downlink point information 2 (i.e. instructs the third network function to deactivate dedicated channel resources), for example, the MB-SMF sends the user plane downlink point information 2 and the IP multicast address to the MB-UPF, and the MB-SMF may also delete the user plane downlink point information 2 and the associated user identifier; or alternatively, the process may be performed,

if there is an indication of mode change and the mode indication is private (i.e., the mode selection indication indicates the private mode), the MB-SMF updates the resources in the MB-UPF that the IP multicast address is related to the user plane downstream point information 1, i.e., activates (i.e., activates the dedicated channel resources for the third network function), e.g., the MB-SMF sends the user plane downstream point information 1 and the IP multicast address to the MB-UPF; or alternatively, the process may be performed,

if no mode change is indicated, step 406 is not performed.

Step 407, the MB-SMF returns a multicast session context check result (i.e. a second return result), where the multicast session context check result carries a user identifier and mode selection information (such as dedicated/shared), and may further include user plane downlink point information 2 (e.g. the mode selection information indicates that the dedicated mode is included, and the mode selection information indicates that the shared mode is not included) (as shown in fig. 4, [ downlink point information 2] indicates that the multicast session context check result may optionally carry or not carry user plane downlink point information 2);

The step 407 may be that the MB-SMF returns a result to the AMF, where the returned result includes the information (i.e. the information carried by the multicast session context check result in step 407), and then the AMF (in this case, the second network function) returns the result to the SMF.

In step 408, if the SMF determines that the mode selection result is shared, the UPF is instructed to release the resources related to the user plane downlink point information 2 (i.e. deactivate the dedicated transmission resources between the UPF and the terminal), and no data from the user plane downlink point 2 is forwarded.

As shown in fig. 5, in the multicast session between the network side and the terminal, a second implementation manner for activating or deactivating the dedicated channel resources is specifically as follows:

step 501, the terminal sends a multicast Leave message (i.e. the multicast message described above) to the SMF, such as PDU Session Release message carrying multicast information (i.e. third multicast information) (e.g. TMGI or IP multicast address or request type for indicating session termination), or IGMP (IPv 4) or MLD (IPv 6) Leave message (i.e. multicast message) is sent through the user plane and forwarded to the SMF by the UPF.

Step 502, the SMF invokes a multicast session context Check operation of the MB-SMF (i.e. the multicast session context operation described above), such as invoking an nmbssf_session context_check operation, where the multicast session context Check operation carries the user identifier and multicast information (i.e. the first multicast information).

Of course, the step 502 may also be an operation that the SMF invokes the AMF, where the parameters include the information (i.e., the information carried by the multicast session context check operation in step 502), and then the AMF (the second network function in this case) invokes the operation of the MB-SMF.

Step 503, the MB-SMF invokes a mode Delete operation of the MBSF (i.e. the multicast user mode operation described above), such as invoking an nmgsf_usermode_delete operation, where the mode Delete operation carries the user identification and multicast information (i.e. the second multicast information), where the multicast information includes an IP multicast address or TMGI.

Step 504, the MB-SMF receives a mode deletion result returned by the MBSF (i.e., a first return result), and the result indicates a mode being used by the user, such as carrying a dedicated indication or a shared indication (i.e., carrying a mode in use indication for indicating a dedicated mode or a shared mode), or indicating that a shared mode is being used without a mode indication (i.e., an unwritten band mode in use indication to indicate a shared mode).

Step 505, if the MB-SMF determines that the user is using the dedicated mode, the corresponding user plane downlink point information 2 is searched through the user identifier.

Step 506, the MB-SMF instructs the MB-UPF to release the resources whose IP multicast address is related to the user plane downlink point information 2 (i.e. instructs the third network function to deactivate the dedicated channel resource), for example, to send the user plane downlink point information 2 and the IP multicast address to the MB-UPF; and, MB-SMF deletes the user plane downlink point information 2 and associated user identification.

Step 507, the MB-SMF returns a multicast session context check result (i.e. a second return result), where the result includes the user identifier, and further includes the user plane downlink point information 2, and does not include the mode selection information (i.e. the second return result does not carry the mode selection information in the case where the first multicast information indicates that the user leaves or the session terminates).

Of course, the step 507 may be that the MB-SMF returns a result to the AMF, where the returned result includes the information (i.e., the information included in the multicast session context check result of step 507), and the AMF (the second network function in this case) returns a result to the SMF.

Step 508, if the SMF determines that the mode indication (i.e. the mode selection information) is not received, the UPF is instructed to release the resources related to the user plane downlink point information 2 (i.e. the fifth network function is instructed to deactivate the dedicated channel resources), and the data from the user plane downlink point 2 is not forwarded any more.

Example two

As shown in fig. 6 to 8, the communication system architecture 2 performs a multicast session, and the communication architecture 1 includes a terminal (i.e., UE), an AMF (i.e., second network function), an SMF, a UPF (i.e., fifth network function), an MB-SMF (i.e., first network function), an MB-UPF (i.e., third network function), and an MBSF (i.e., fourth network function).

As shown in fig. 6, a process of establishing a dedicated channel in a multicast session between a network side and a terminal is specifically as follows:

step 601, the terminal sends a multicast message to the AMF, such as PDU Session Establishment or PDU Session Modification message carrying multicast information (such as multicast identification TMGI or multicast identification list or multicast address IP multicast address or request type for indicating establishment of a multicast session).

Step 602, the AMF invokes a unicast operation of the SMF, such as nsmf_pdu session_createsmcontext or nsmf_pdu session_updatecfcontext operation, where the unicast operation carries the user identifier.

Step 603, the SMF interacts with the UPF to reserve resources of the dedicated user plane downlink point (such as IP address, port number, and tunnel identifier), and instruct the UPF to forward data from the dedicated user plane downlink point to the dedicated channel indicated by Session information (such as PDU Session ID, or PDU Session ID and QFI).

Step 604, the SMF invokes a unicast operation of the MB-SMF, such as invoking an nsmf_pduse_create or nsmf_pduse_update operation, where the unicast operation carries the user identifier and the dedicated user plane downlink point information.

Step 605, while step 602 is executed, the AMF invokes a multicast session context Check operation of the MB-SMF, for example, invokes an nmbssf_session context_check operation, where the multicast session context Check operation carries a user identifier and multicast information, and may also include a PDU session identifier.

Of course, MB-SMF may associate step 604 with step 605 using the user identity (i.e., both unicast operation and multicast session context check operation carry the user identity), or may associate step 604 with step 605 using the user identity and PDU session identity.

Step 606, the MB-SMF invokes a mode Check operation of the MBSF, such as an nmgsf_usermode_check operation, which carries a user identity and multicast information, which may include an IP multicast address, a TMGI list, or a TMGI.

Step 607, MB-SMF returns a mode check result that carries an indication that the selected mode is private (i.e., the mode select indication is used to indicate the private mode).

In step 608, if the MB-SMF determines that the mode checking result is private, the resources (i.e. the dedicated channel resources are established) of the MB-UPF multicast address and the dedicated user plane downlink point information are updated, for example, the dedicated user plane downlink point information and the multicast address are sent to the MB-UPF.

Step 609, if the MB-SMF determines that the mode checking result is private, storing private user plane downlink point information (such as IP address, port number, and tunnel identifier), and associating the private user plane downlink point information with the user identifier.

Step 610, the MB-SMF returns a multicast session context check result, where the result includes a user identifier and a dedicated indication, and possibly includes downlink point information of a dedicated user plane;

In addition, the MB-SMF may send a TMGI or a TMGI list and a corresponding PDU session identifier to the base station through the AMF, or send a TMGI or a TMGI list and a flow identifier corresponding to each TMGI, so that the base station knows the TMGI associated with the dedicated channel.

The MB-UPF receives the data message sent to the appointed multicast group, forwards the data message to the downlink point of the user plane, and forwards the data received from the downlink point of the user plane to the special channel.

It should be noted that the MB-SMF and the SMF may be considered as a whole, where step 602 and step 605 are combined into one operation step to be performed, for example, one operation call includes all parameters of step 602 and step 605 (i.e. user identifier and multicast information, and may also include PDU session identifier).

As shown in fig. 7, in the multicast session between the network side and the terminal, a third implementation manner for activating or deactivating the dedicated channel resources is specifically as follows:

step 701, the terminal sends a multicast message (i.e. a multicast message carrying third multicast information) to the AMF, such as a PDU Session Modification or Service Request message carrying multicast information (such as TMGI or TMGI list or IP multicast address or Request type for indicating multicast update or new creation).

Step 702, the AMF invokes a unicast operation of the SMF, such as an nsmf_pdu session_ CreateSMContext, nsmf _pdu session_updatecmccontext, or an nsmf_pdu session_release mccontext operation, where the unicast operation carries the user identifier.

In step 703, if the unicast operation is to establish a new user plane (for example, update smcontext is to add a new user plane, or CreateSMContext), the SMF interacts with the UPF to reserve resources of user plane downlink point information 1 (for example, IP address, port number, and tunnel identifier), and instructs the UPF to forward data from the user plane downlink point 1 to a dedicated channel indicated by Session information (for example, PDU Session ID, or PDU Session ID and QFI).

Step 704, the SMF invokes a unicast operation of the MB-SMF, such as invoking an nsmf_pdu session_create, nsmf_pdu session_update, or nsmf_pdu session_release operation, where the unicast operation carries a user identifier, possibly carrying the dedicated user plane downlink point information 1.

Step 705, while the step 702 is executed, the AMF invokes a multicast session context Check operation (i.e. the multicast session context operation described above) of the MB-SMF, such as invoking an nmbsf_session context_check operation, where the multicast session context Check operation carries a user identifier and multicast information (i.e. first multicast information), and may also include a PDU session identifier;

Of course, the MB-SMF may associate the step 704 with the step 705 using the user identifier (i.e., the unicast operation and the multicast session context check operation each carry the user identifier), or may associate the step 704 with the step 705 using the user identifier and the PDU session identifier.

Step 706, the MB-SMF invokes a mode Check operation of the MBSF (i.e. the above-mentioned multicast user mode operation), such as an nmgsf_usermode_check operation, which carries the user identity and multicast information (i.e. the second multicast information), which includes an IP multicast address, a TMGI list, or a TMGI.

Step 707, the MB-SMF receives a mode check result (i.e., a first return result) returned by the MBSF, the result carrying a mode indication (i.e., a mode selection indication), such as a share indication or a dedicated indication, and if the user previously used a different mode than the mode indication (such as previously dedicated now selected for sharing, or previously shared now selected for dedicated), the result also indicates a mode change, such as by a mode change indication (i.e., the first return result also includes a mode change indication), or by a deleted TMGI or TMGI indicating that the mode change occurred.

If the MB-SMF determines that the mode is changed to shared (meaning dedicated before), step 708, the corresponding dedicated user plane downlink point information 2 is searched for by the user id.

Step 709, if the returned result does not indicate the mode change, the MB-SMF returns PDU session operation failure to the SMF, indicates rejection of PDU session operation, and maintains the state;

if the returned result indicates the mode change, if the mode indication is special, the PDU session operation is returned successfully to establish a new user plane; and if the mode indicates sharing, returning to the PUD session operation failure, and maintaining the same.

Step 710, if there is a mode change and the mode indicates sharing, the MB-SMF instructs the MB-UPF to release the resources whose multicast address is related to the dedicated user plane downlink point information 2 (i.e. instructs the third network function to deactivate the dedicated channel resources), for example, to send the user plane downlink point information 2 and the multicast address to the MB-UPF; and, MB-SMF deletes the user plane downlink point information 2 and associated user identification.

If there is a request to indicate a mode change and the mode indication is private, the MB-SMF updates the resources of the MB-UPF multicast address associated with the user plane downstream point information 1 (i.e., instructs the third network function to activate a dedicated channel resource), such as sending the user plane downstream point information 1 and the multicast address to the MB-UPF.

Step 711, the MB-SMF returns a multicast session context check result (i.e. a second return result) to the AMF, where the result includes a user identification and a dedicated indication, and may also include dedicated user plane downlink point information 2.

In addition, the MB-SMF may send a TMGI or a TMGI list and a corresponding PDU session identifier to the base station through the AMF, or send a TMGI or a TMGI list and a flow identifier corresponding to each TMGI, so that the base station may learn a TMGI associated with the dedicated channel.

It should be noted that, the MB-SMF and the SMF may be considered as a whole, where step 702 and step 705 are combined into one operation step to be performed, for example, one operation call includes all parameters of step 702 and step 705 (i.e. user identifier and multicast information, and may also include PDU session identifier).

As shown in fig. 8, in the multicast session between the network side and the terminal, a fourth implementation manner for activating or deactivating dedicated channel resources is specifically as follows:

step 801, the terminal sends a multicast message (i.e. a multicast message carrying third multicast information) to the AMF, such as PDU Session Modification or PDU Session Release message carrying multicast information (such as TMGI or TMGI list or multicast address IP multicast address or request type for indicating session termination), which may not contain TMGI or TMGI list, for indicating that all joined TMGIs are terminated (i.e. the third multicast information does not contain the TMGI or the TMGI list to indicate departure or session termination).

Step 802, the AMF invokes a unicast operation of the SMF, such as nsmf_pdu session_update smcontext or nsmf_pdu session_release mccontext operation, where the unicast operation carries the user identifier.

Step 803, the SMF and UPF interact to release unicast user plane resources.

Step 804, the SMF invokes a unicast operation of the MB-SMF, such as an nsmf_pduse_update or nsmf_pduse_release operation, where the unicast operation carries the user identifier.

Step 805, while executing step 802, the AMF invokes a multicast session context Check operation of the MB-SMF (i.e. the multicast session context operation described above), such as invoking an nmbssf_session context_check operation, where the multicast session context Check operation carries a user identifier and multicast information (i.e. first multicast information), and may also include a PDU session identifier;

of course, the MB-SMF may associate the step 804 with the step 805 using the user identifier (i.e., the unicast operation and the multicast session context check operation each carry the user identifier), or may associate the step 804 with the step 805 using the user identifier and the PDU session identifier.

Step 806, MB-SMF invokes a mode Delete operation of MBSF (i.e., the multicast user mode operation described above), such as an nmssf_usermode_delete operation, or a mode Check operation, such as an nmssf_usermode_check operation, that carries the user identification and multicast information (i.e., the second multicast information) including an IP multicast address, a TMGI list, or a TMGI.

Step 807, the MBSF learns to be a delete operation by calling a type, or determines to be a delete operation by the parameter not including the TMGI list, the TMGI, or the IP multicast address. The MBSF returns a mode deletion result (i.e., a first return result) to the MB-SMF indicating the mode the user is using, such as carrying a dedicated indication or a shared indication, or no mode indication indicating that a shared mode is being used.

Step 808, if the MB-SMF determines that the user is using the dedicated mode, searching for the corresponding user plane downlink point information 2 through the user identifier, otherwise, not executing step 808.

Step 809, the MB-SMF instructs the MB-UPF to release the resources whose IP multicast address is related to the user plane downlink point information 2 (i.e. instructs the third network function to deactivate the dedicated channel resources), for example, to send the user plane downlink point information 2 and the IP multicast address to the MB-UPF; and, MB-SMF deletes the user plane downlink point information 2 and associated user identification.

Step 810, MB-SMF returns a multicast session context check result (i.e. a second return result), where the result includes the user identifier, and possibly includes the user plane downlink point information 2, and does not include the mode selection information. The MB-SMF may further send a TMGI or a TMGI list and a corresponding PDU session identifier to the base station through the AMF, or send a TMGI or a TMGI list and a flow identifier corresponding to each TMGI, so that the base station knows the TMGI associated with the dedicated channel.

It should be noted that the MB-SMF and the SMF may be considered as a whole, where step 802 and step 805 are combined into one operation step to be performed, for example, one operation call includes all parameters of step 802 and step 805 (i.e. user identifier and multicast information, and may also include PDU session identifier).

Referring to fig. 9, fig. 9 is a flow chart of another communication method provided in the present embodiment, which is applied to a fourth network function, as shown in fig. 9, and includes the following steps:

step 901, calling a multicast user mode operation by a first network function, wherein the multicast user mode operation carries second multicast information, and the second multicast information comprises at least one of a TMGI, a TMGI list, an IP multicast address and a request type;

step 902, returning a first return result to the first network function based on the second multicast information, where the first return result is used to indicate that a mode is changed or a mode being used by a user.

Optionally, in the case that the first return result is used to indicate that the mode is changed, the first return result includes:

a mode selection indication and a mode change indication; or alternatively

The removed TMGI, or IP multicast address, or TMGI list.

Optionally, in the case that the first return result is used to indicate a mode being used by the user, the first return result includes a mode in use indication.

Optionally, the second multicast information includes a request type and the request type is used to indicate that the user leaves or the session is terminated, or indicates that the user leaves or the session is terminated when the second multicast information does not include a TMGI and a TMGI list, or indicates that the user leaves or the session is terminated when the second multicast information does not include a request type.

Optionally, in a case where the second multicast information includes a request type and the request type indicates update or new, or in a case where the second multicast information does not include a request type, or in a case where the second multicast information includes the TMGI or the TMGI list or the IP multicast address, the first return result indicates that a mode change occurs.

It should be noted that, as an embodiment of the fourth network function corresponding to the embodiment shown in fig. 2 to 8, a specific implementation manner of the embodiment of the present invention may refer to the related descriptions of the embodiment shown in fig. 2 to 8, and may achieve the same beneficial effects, so that the repeated descriptions are avoided.

Referring to fig. 10, fig. 10 is a flow chart of another communication method provided in the present embodiment, which is applied to a terminal, as shown in fig. 10, and the communication method includes the following steps:

step 1001, a multicast message or a multicast message is sent to a network side, where the multicast message or the multicast message carries third multicast information, and the third multicast information includes at least one of a TMGI, a TMGI list, an IP multicast address, and a request type.

Optionally, in a case where the third multicast information includes a request type and the request type indicates leaving or session termination, or in a case where the third multicast information does not include a request type, the third multicast information does not include the TMGI or the TMGI list.

Optionally, the third multicast information does not include the TMGI or the TMGI list to indicate departure or session termination.

It should be noted that, in the embodiment of the present invention as an embodiment of the terminal corresponding to the embodiment shown in fig. 2 to 8, the specific implementation manner of the embodiment may refer to the related descriptions of the embodiment shown in fig. 2 to 8, and the same beneficial effects may be achieved, so that the description is not repeated here.

Referring to fig. 11, fig. 11 is a schematic structural diagram of a network function according to an embodiment of the present invention, where the network function is a first network function, and as shown in fig. 11, a first network function 1100 includes:

an operation called module 1101, configured to call a multicast session context operation by a second network function, where the multicast session context operation carries first multicast information, and the first multicast information includes at least one of a temporary mobile group identifier TMGI, a TMGI list, an internet protocol IP multicast address, and a request type;

a processing module 1102 is configured to instruct the third network function to activate or deactivate dedicated channel resources based on the first multicast information.

Optionally, the processing module includes:

an operation calling unit, configured to call a multicast user mode operation of the fourth network function based on the first multicast information, where the multicast user mode operation carries second multicast information, where the second multicast information includes at least one of a TMGI, a TMGI list, an IP multicast address, and a request type;

the result receiving unit is used for receiving a first return result returned by the fourth network function based on the second multicast information, wherein the first return result is used for indicating a mode change or a mode being used by a user;

And the processing unit is used for indicating the third network function to activate or deactivate the special channel resource based on the first return result.

Optionally, the processing unit is specifically configured to:

and in the case that the first returned result indicates that the mode is changed to the sharing mode or that the user is using the dedicated mode, the third network function is instructed to deactivate the dedicated channel resource.

Optionally, the first multicast information includes a request type and the request type is used to indicate that the user leaves or the session is terminated, or indicates that the user leaves or the session is terminated when the first multicast information does not include a TMGI and a TMGI list, or indicates that the user leaves or the session is terminated when the first multicast information does not include a request type.

Optionally, the first network function 1100 further includes:

the result returning module is used for returning a second returning result to the second network function based on the first multicast information;

Optionally, the processing module further includes:

a result returning unit, configured to return a second return result to the second network function based on the first return result;

Optionally, in a case where the first multicast information carries a request type and the request type indicates that the user leaves or the session terminates, the second multicast information does not carry a TMGI or a TMGI list or an IP multicast address.

Optionally, the multicast session context operation further carries a user identifier;

The first network function 1100 further includes:

and the searching module is used for searching the user plane downlink point information corresponding to the user identifier.

Optionally, the first network function 1100 further includes:

the base station comprises an identification information sending module, a base station and a base station, wherein the identification information sending module is used for sending identification information to the base station, and the identification information comprises:

PDU session identification or flow identification;

It should be noted that, in the embodiment of the present invention, the first network function 1100 may be a first network function of an implementation manner in the embodiment of the method shown in fig. 2 to 10, and any implementation manner of the first network function in the embodiment of the method may be implemented by the first network function 1100 in the embodiment of the present invention, so as to achieve the same beneficial effects, and for avoiding repetition, no further description is given here.

Referring to fig. 12, fig. 12 is a schematic structural diagram of a network function according to an embodiment of the present invention, where the network function is a fourth network function, as shown in fig. 12, a fourth network function 1200 includes:

an operation calling module 1201, configured to call a multicast user mode operation by a first network function, where the multicast user mode operation carries second multicast information, where the second multicast information includes at least one of a TMGI, a TMGI list, an IP multicast address, and a request type;

A result returning module 1202, configured to return a first return result to the first network function based on the second multicast information, where the first return result is used to indicate a mode change or a mode that is being used by a user.

a mode selection indication and a mode change indication; or alternatively

The removed TMGI, or IP multicast address, or TMGI list.

It should be noted that, in the embodiment of the present invention, the fourth network function 1200 may be a fourth network function of an embodiment of a method shown in fig. 2 to 10, and any implementation of the fourth network function in the embodiment of the method may be implemented by the fourth network function 1200 in the embodiment of the present invention, so that the same beneficial effects are achieved, and for avoiding repetition, a description is omitted here.

Referring to fig. 13, fig. 13 is a terminal provided in an embodiment of the present invention, as shown in fig. 13, a terminal 1300 includes:

a sending module 1301, configured to send a multicast message or a multicast packet to a network side, where the multicast message or the multicast packet carries third multicast information, where the third multicast information includes at least one of a TMGI, a TMGI list, an IP multicast address, and a request type.

It should be noted that, in the embodiment of the present invention, the terminal or the base station node 1300 may be a terminal according to an embodiment of a method shown in fig. 2 to 10, and any implementation of the terminal in the embodiment of the method may be implemented by the terminal 1300 according to the embodiment of the present invention, so that the same advantages are achieved, and for avoiding repetition, a detailed description is omitted herein.

Fig. 14 is a schematic diagram of a hardware architecture of a terminal implementing various embodiments of the present invention, where the terminal 1400 includes, but is not limited to: a radio frequency unit 1401, a network module 1402, an audio output unit 1403, an input unit 1404, a sensor 1405, a display unit 1406, a user input unit 1407, an interface unit 1408, a memory 1409, a processor 1410, a power source 1411, and the like. It will be appreciated by those skilled in the art that the terminal structure shown in fig. 14 is not limiting of the terminal and that the terminal may include more or fewer components than shown, or may combine certain components, or a different arrangement of components. In the embodiment of the invention, the terminal comprises, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer and the like.

Wherein, the radio frequency unit 1401 is used for:

It should be understood that, in the embodiment of the present invention, the radio frequency unit 1401 may be used to receive and send information or signals during a call, specifically, receive downlink data from a base station, and then process the downlink data with the processor 1410; and, the uplink data is transmitted to the base station. Typically, the radio frequency unit 1401 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 1401 may communicate with networks and other devices through a wireless communication system.

The terminal provides wireless broadband internet access to the user through the network module 1402, such as helping the user to send and receive e-mail, browse web pages, access streaming media, etc.

The audio output unit 1403 may convert audio data received by the radio frequency unit 1401 or the network module 1402 or stored in the memory 1409 into an audio signal and output as sound. Also, the audio output unit 1403 may also provide audio output (e.g., a call signal reception sound, a message reception sound, etc.) related to a specific function performed by the terminal 1400. The audio output unit 1403 includes a speaker, a buzzer, a receiver, and the like.

The input unit 1404 is for receiving an audio or video signal. The input unit 1404 may include a graphics processor (Graphics Processing Unit, GPU) 14041 and a microphone 14042, the graphics processor 14041 processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frame may be displayed on the display unit 1406. The image frames processed by the graphics processor 14041 may be stored in memory 1409 (or other storage medium) or transmitted via the radio frequency unit 1401 or the network module 1402. The microphone 14042 can receive sound and can process such sound into audio data. The processed audio data may be converted into a format output that can be transmitted to the mobile communication base station via the radio frequency unit 1401 in the case of a telephone call mode.

Terminal 1400 also includes at least one sensor 1405, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 14061 according to the brightness of ambient light, and the proximity sensor can turn off the display panel 14061 and the backlight when the terminal 1400 moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the acceleration in all directions (generally three axes), and can detect the gravity and direction when the accelerometer sensor is stationary, and can be used for recognizing the terminal gesture (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration recognition related functions (such as pedometer and knocking), and the like; the sensor 1405 may further include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, and the like, which are not described herein.

The display unit 1406 is used to display information input by a user or information provided to the user. The display unit 1406 may include a display panel 14061, and the display panel 14061 may be configured in the form of a liquid crystal display (Liquid Crystal Display, LCD), an Organic Light-Emitting Diode (OLED), or the like.

The user input unit 1407 is operable to receive input numeric or character information and to generate key signal inputs relating to user settings and function indications of the terminal. Specifically, the user input unit 1407 includes a touch panel 14071 and other input devices 14072. The touch panel 14071, also referred to as a touch screen, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the touch panel 14071 or thereabout using any suitable object or attachment such as a finger, stylus, or the like). The touch panel 14071 may include two parts, a touch detection device and a touch indicator. The touch detection device detects the touch azimuth of a user, detects a signal brought by touch operation and transmits the signal to the touch indicator; the touch indicator receives touch information from the touch detection device and converts it into touch point coordinates, which are then sent to the processor 1410, and receives and executes commands sent from the processor 1410. Further, the touch panel 14071 may be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. The user input unit 1407 may include other input devices 14072 in addition to the touch panel 14071. In particular, other input devices 14072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume indication keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

Further, the touch panel 14071 may be overlaid on the display panel 14071, and when the touch panel 14071 detects a touch operation thereon or nearby, the touch operation is transmitted to the processor 1410 to determine a type of touch event, and then the processor 1410 provides a corresponding visual output on the display panel 14061 according to the type of touch event. Although in fig. 14, the touch panel 14071 and the display panel 14061 are two independent components to implement the input and output functions of the terminal, in some embodiments, the touch panel 14071 and the display panel 14061 may be integrated to implement the input and output functions of the terminal, which is not limited herein.

The interface unit 1408 is an interface to which an external device is connected to the terminal 1400. For example, the external devices may include a wired or wireless headset port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. Interface unit 1408 may be used to receive input (e.g., data information, power, etc.) from an external device and to transmit the received input to one or more elements within terminal 1400 or may be used to transmit data between terminal 1400 and an external device.

Memory 1409 may be used to store software programs as well as various data. The memory 1409 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like; the storage data area may store data (such as audio data, phonebook, etc.) created according to the use of the handset, etc. In addition, memory 1409 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.

The processor 1410 is an indication center of the terminal, connects various parts of the entire terminal using various interfaces and lines, and performs various functions of the terminal and processes data by running or executing software programs and modules stored in the memory 1409, and calling data stored in the memory 1409, thereby performing overall monitoring of the terminal. Processor 1410 may include one or more processing units; preferably, the processor 1410 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 1410.

Terminal 1400 can also include a power supply 1411 (e.g., a battery) for powering the various components, as well as a power supply 1411 that can be logically coupled to processor 1410 via a power management system such that charge, discharge, and power consumption management functions can be implemented via the power management system.

In addition, the terminal 1400 includes some functional modules, which are not shown, and will not be described herein.

Preferably, the embodiment of the present invention further provides a terminal, which includes a processor 1410, a memory 1409, and a computer program stored in the memory 1409 and capable of running on the processor 1410, where the computer program when executed by the processor 1410 implements each process of the above embodiment of the method for obtaining reference time information, and the same technical effects can be achieved, and for avoiding repetition, a detailed description is omitted herein.

It should be noted that, in this embodiment, the terminal 1400 may be any terminal of any implementation manner in the method embodiment of the present invention, and any implementation manner of the terminal in the method embodiment of the present invention may be implemented by the terminal 1400 in this embodiment, and the same beneficial effects are achieved, which are not described herein.

Fig. 15 is a block diagram of a network side device according to an embodiment of the present invention. The network side device may be the first network function or the fourth network function in the above-described method embodiment. As shown in fig. 15, the network-side device 1500 includes: a processor 1501, a transceiver 1502, a memory 1503 and a bus interface, wherein:

In the case where the network side device 1500 is the first network function:

a processor 1501 for:

Optionally, the processor 1501 is specifically configured to:

Optionally, the processor 1501 is further configured to:

the processor 1501 is further configured to:

Optionally, the processor 1501 is further configured to:

PDU session identification or flow identification;

In the case where the network side device 1500 is the fourth network function:

a processor 1501 for:

a mode selection indication and a mode change indication; or alternatively

The removed TMGI, or IP multicast address, or TMGI list.

In fig. 15, a bus architecture may be comprised of any number of interconnected buses and bridges, and in particular one or more processors represented by the processor 1501 and various circuits of the memory represented by the memory 1503. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 1502 may be a number of elements, i.e. include a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The user interface 1504 may also be an interface capable of interfacing with an inscribed desired device for a different terminal, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 1501 is responsible for managing the bus architecture and general processing, and the memory 1503 may store data used by the processor 1501 in performing operations.

It should be noted that, in this embodiment, the network side device 1500 may be the first network function, the second network function, or the base station node according to any implementation manner in the method embodiment of the present invention, and any implementation manner of the first network function, the second network function, or the base station node in the method embodiment of the present invention may be implemented by the network side device 1500 in this embodiment, and the same beneficial effects are achieved, which are not described herein.

The embodiment of the present invention further provides a computer readable storage medium, on which a computer program is stored, where the computer program when executed by a processor implements the above processes corresponding to the embodiments of the first network function, the second network function, the terminal or the base station node, and the same technical effects can be achieved, and for avoiding repetition, a detailed description is omitted herein. Wherein the computer readable storage medium is selected from Read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present invention.

The foregoing is merely illustrative of the present invention, and the present invention is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present invention. Therefore, the protection scope of the invention is subject to the protection scope of the claims.

Claims

1. A communication method applied to a first network function, comprising:

2. The method of claim 1, wherein the instructing a third network function to activate or deactivate dedicated channel resources based on the first multicast information comprises:

calling a multicast user mode operation of a fourth network function based on the first multicast information, wherein the multicast user mode operation carries second multicast information, and the second multicast information comprises at least one of TMGI, TMGI list, IP multicast address and request type;

3. The method of claim 2, wherein the instructing the third network function to activate or deactivate dedicated channel resources based on the first returned result comprises:

4. The method of claim 1, wherein the first multicast information contains a request type and the request type is used to indicate a user to leave or terminate a session, or to indicate a user to leave or terminate a session when the first multicast information does not contain a TMGI and a TMGI list, or to indicate a user to leave or terminate a session when the first multicast information does not contain a request type.

5. The method of claim 1, wherein after the multicast session context operation is invoked by the second network function, further comprising:

6. The method of claim 2, wherein after receiving the first return result returned by the fourth network function based on the multicast user mode operation, further comprising:

7. The method of claim 2, wherein the second multicast information does not carry a TMGI or TMGI list or an IP multicast address if the first multicast information carries a request type and the request type indicates that a user is away or a session is terminated.

8. The method of claim 1, wherein the multicast session context operation further carries a user identification;

9. The method of claim 1, wherein after the multicast session context operation is invoked by the second network function, further comprising:

PDU session identification or flow identification;

10. A communication method applied to a fourth network function, comprising:

returning a first return result to the first network function based on the second multicast information, wherein the first return result is used for indicating a mode change or a mode being used by a user;

wherein the first network function instructs a third network function to activate or deactivate dedicated channel resources based on the first returned result.

11. The method of claim 10, wherein in the case where the first returned result is used to indicate that a mode change occurred, the first returned result comprises:

a mode selection indication and a mode change indication; or alternatively

The removed TMGI, or IP multicast address, or TMGI list.

12. The method of claim 10, wherein the first returned result includes a mode in use indication in the event that the first returned result is used to indicate a mode being used by a user.

13. The method of claim 10, wherein the second multicast information contains a request type and the request type is used to indicate a user to leave or terminate a session, or wherein the second multicast information does not contain a TMGI and a TMGI list indicates a user to leave or terminate a session, or wherein the second multicast information does not contain a request type indicates a user to leave or terminate a session.

14. The method of claim 10, wherein the first returned result indicates a mode change if the second multicast information includes a request type and the request type indicates an update or a new, or if the second multicast information does not include a request type, or if the second multicast information includes the TMGI or the TMGI list or the IP multicast address.

15. A communication method applied to a terminal, comprising:

sending a multicast message or a multicast message to a network side, wherein the multicast message or the multicast message carries third multicast information, and the third multicast information comprises at least one of a TMGI, a TMGI list, an IP multicast address and a request type;

The network side comprises a second network function, and the second network function calls multicast session context operation to the first network function in response to the multicast message or the multicast message; the multicast session context operation carries first multicast information, wherein the first multicast information comprises at least one of a Temporary Mobile Group Identifier (TMGI), a TMGI list, an Internet Protocol (IP) multicast address and a request type; the first network function instructs a third network function to activate or deactivate dedicated channel resources based on the first multicast information.

16. The method of claim 15, wherein the third multicast information does not contain the TMGI or the TMGI list if the third multicast information includes a request type and the request type indicates an away or session termination, or if the third multicast information does not include a request type.

17. The method of claim 15, wherein the third multicast information does not include the TMGI or the TMGI list to indicate departure or session termination.

18. A network function, a first network function, comprising:

19. The network function of claim 18, wherein the processing module comprises:

an operation calling unit, configured to call a multicast user mode operation of a fourth network function based on the first multicast information, where the multicast user mode operation carries second multicast information, and the second multicast information includes at least one of a TMGI, a TMGI list, an IP multicast address, and a request type;

20. The network function according to claim 19, wherein the processing unit is specifically configured to:

21. The network function of claim 18, wherein the first multicast information includes a request type and the request type is used to indicate a user to leave or terminate a session, or to indicate a user to leave or terminate a session when the first multicast information does not include a TMGI and a TMGI list, or to indicate a user to leave or terminate a session when the first multicast information does not include a request type.

22. The network function of claim 18, wherein the first network function further comprises:

23. The network function of claim 19, wherein the processing module further comprises:

24. The network function of claim 19, wherein the second multicast information does not carry a TMGI or TMGI list or an IP multicast address if the first multicast information carries a request type and the request type indicates that a user is away or a session is terminated.

25. The network function of claim 18, wherein the multicast session context operations further carry a user identification;

the first network function further includes:

26. The network function of claim 18, wherein the first network function further comprises:

PDU session identification or flow identification;

27. A network function, a fourth network function, comprising:

The result return module is used for returning a first return result to the first network function based on the second multicast information, wherein the first return result is used for indicating a mode change or a mode being used by a user; wherein the first network function instructs a third network function to activate or deactivate dedicated channel resources based on the first returned result.

28. The network function of claim 27, wherein in the case where the first returned result is used to indicate that a mode change has occurred, the first returned result includes:

a mode selection indication and a mode change indication; or alternatively

The removed TMGI, or IP multicast address, or TMGI list.

29. The network function of claim 27, wherein the first returned result includes a mode in use indication if the first returned result is used to indicate a mode being used by a user.

30. The network function of claim 27, wherein the second multicast information contains a request type and the request type is used to indicate a user to leave or terminate a session, or wherein the second multicast information does not contain a TMGI and a TMGI list indicates a user to leave or terminate a session, or wherein the second multicast information does not contain a request type indicates a user to leave or terminate a session.

31. The network function of claim 27, wherein the first return result indicates a mode change if the second multicast information contains a request type and the request type indicates an update or a new creation, or if the second multicast information does not contain a request type, or if the second multicast information contains the TMGI or the TMGI list or the IP multicast address.

32. A terminal, comprising:

a sending module, configured to send a multicast message or a multicast message to a network side, where the multicast message or the multicast message carries third multicast information, where the third multicast information includes at least one of a TMGI, a TMGI list, an IP multicast address, and a request type;

33. The terminal of claim 32, wherein the third multicast information does not contain the TMGI or the TMGI list if the third multicast information includes a request type and the request type indicates an away or session termination, or if the third multicast information does not include a request type.

34. The terminal of claim 32, wherein the third multicast information does not include the TMGI or the TMGI list to indicate departure or session termination.

35. A network function, comprising: memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor, implements the steps in the communication method according to any one of claims 1 to 14.

36. A terminal, comprising: memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor, implements the steps in the communication method according to any of claims 15 to 17.

37. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps in the communication method according to any of claims 1 to 17.