Multicast session handling method, network function entity, apparatus, and storage medium

Abstract

Embodiments of the present application provide a multicast session processing method, a network function entity, a device and a storage medium, wherein the method comprises: receiving a first request sent by a user equipment (UE), the first request being a registration request message or a service request message; obtaining multicast session information of the UE according to the first request; and performing a processing operation related to a multicast session according to the multicast session information. The multicast session processing method provided by the present application synchronizes the multicast session state between the UE and the network through the registration request or the service request, reduces the signaling interaction required by the UE to process the multicast session service, improves the signaling efficiency, saves the signaling resources, and shortens the time for the UE to join or leave the multicast session and receive or transmit the multicast session data.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a multicast session processing method, network functional entity, device and storage medium. Background Technology

[0002] User equipment needs to join a multicast session to receive specific multicast service data.

[0003] In the prior art, when a user equipment (UE) in an idle or active state moves or for other reasons, such as changes in network slicing, changes in the radio access network (RAN) node or even the core network (CN) node serving the UE, the UE needs to complete a registration update or service request process before initiating a PDU session modification process in order to receive data from a multicast session or leave a multicast session it has joined.

[0004] However, in existing solutions, user equipment needs to engage in extensive signaling interactions with the network to receive data from multicast sessions or leave already joined multicast sessions, resulting in resource waste and inefficiency. Summary of the Invention

[0005] This application provides a multicast session processing method, network function entity, apparatus, and storage medium to address the shortcomings of existing technologies where user equipment needs to perform extensive signaling interactions with the network to receive multicast session data or leave already joined multicast sessions, thereby improving signaling efficiency and saving signaling resources.

[0006] In a first aspect, embodiments of this application provide a multicast session processing method, applied in a first AMF, including:

[0007] Receive a first request sent by a user equipment (UE), wherein the first request is a registration request message or a service request message;

[0008] Obtain the multicast session information of the UE according to the first request;

[0009] Based on the multicast session information, perform processing operations related to the multicast session.

[0010] Optionally, if the first request carries the multicast session information of the UE, then obtaining the multicast session information of the UE according to the first request includes:

[0011] Obtain the multicast session information of the UE from the first request.

[0012] Optionally, obtaining the multicast session information of the UE according to the first request includes:

[0013] Based on the first request, the context of the UE is obtained from the second AMF, wherein the context of the UE contains the multicast session information of the UE, the second AMF is a network function entity that provides services to the UE before the UE moves, and the first AMF is a network function entity that provides services to the UE after the UE moves.

[0014] Optionally, the multicast session information includes a first multicast session identifier and / or indication information, wherein the indication information is used to instruct the UE to remain in the first multicast session, which is a multicast session that the UE has joined or requested to join.

[0015] Optionally, performing multicast session-related processing operations based on the multicast session information includes:

[0016] A first network function entity serving the first multicast session is determined, wherein the first network function entity includes: Session Management Function (SMF) or Multicast Broadcast Session Management Function (MB-SMF);

[0017] Send a second request to the first network function entity, the second request carrying the multicast session information;

[0018] Receive a response message to the second request sent by the first network function entity.

[0019] Optionally, the response message for receiving the second request sent by the first network function entity includes:

[0020] Receive a response message from the first network function entity carrying a second request containing the first multicast session identifier and resource allocation request information;

[0021] The method further includes:

[0022] Based on the response message of the second request, a third request is sent to the Radio Access Network Function (RAF) entity, the third request carrying the first multicast session identifier and the resource allocation request information, so that the RAF entity can establish or update the resources of the first multicast session.

[0023] Optionally, the response message to the second request carries a first multicast session identifier and the following information:

[0024] Information instructing the UE to leave the first multicast session; or,

[0025] The UE is denied the right to join the first multicast session.

[0026] Optionally, the method further includes:

[0027] A third request is sent to the Radio Access Network Function (RAF) entity, the third request carrying a first multicast session identifier and information instructing the UE to leave the first multicast session, so that the RAF entity removes the UE's identifier from the context of the first multicast session.

[0028] Optionally, the multicast session information further includes at least one of the following identification information:

[0029] The identifier of the Protocol Data Unit (PDU) session associated with the first multicast session;

[0030] The identifier of the MB-SMF serving the first multicast session and / or the identifier of the SMF;

[0031] The determination of the first network function entity serving the first multicast session includes:

[0032] Based on the at least one identification information, a first network function entity serving the first multicast session is determined.

[0033] Secondly, embodiments of this application also provide a multicast session processing method applied to SMF, including:

[0034] The system receives a second request sent by a first AMF, the second request carrying multicast session information of a user equipment (UE). The multicast session information is obtained by the first AMF after receiving the first request sent by the UE. The first request is a registration request message or a service request message.

[0035] The multicast session of the UE is processed according to the multicast session information carried in the second request.

[0036] Optionally, the multicast session information includes a first multicast session identifier and / or indication information, wherein the indication information is used to instruct the UE to remain in the first multicast session, which is a multicast session that the UE has joined or requested to join.

[0037] Optionally, processing the multicast session of the UE based on the multicast session information carried in the second request includes:

[0038] If the indication information is used to instruct the UE to request to join the first multicast session, and it is determined that the UE's joining the first multicast session is accepted, then a correspondence is established between the UE's identifier and the first multicast session identifier; a response message for the second request is sent to the first AMF, the response message for the second request carrying information accepting the UE's joining the first multicast session; or,

[0039] If the indication information is used to instruct the UE to request to join the first multicast session, and the UE is not within the service area of ​​the first multicast session, then a response message for the second request is sent to the first AMF, the response message for the second request carrying information that the UE is refused to join the first multicast session; or,

[0040] If the indication information is used to instruct the UE to remain in the first multicast session, and the UE is not within the service area of ​​the first multicast session, then a response message for the second request is sent to the first AMF, the response message for the second request carrying information instructing the UE to leave the first multicast session; or,

[0041] If the indication information is used to instruct the UE to leave the first multicast session, then the correspondence between the UE's identifier and the first multicast session identifier is deleted.

[0042] Optionally, processing the multicast session of the UE based on the multicast session information carried in the second request includes:

[0043] If the indication information is used to instruct the UE to request to join the first multicast session, and it is determined that the UE's joining of the first multicast session is accepted, then the identifier of the Radio Access Network Function entity stored in the storage service for the UE is stored in the context of the first multicast session.

[0044] Thirdly, embodiments of this application also provide a multicast session processing method, including:

[0045] Send a first request to the first AMF, wherein the first request is a service request message or a registration request message;

[0046] Receive a response message to the first request sent by the first AMF. The response message to the first request is a registration acceptance message or a service acceptance message. The response message to the first request contains information to accept the UE joining or leaving the first multicast session, or information to instruct the UE to leave the first multicast session, or information to refuse the UE from joining the first multicast session.

[0047] The first multicast session is processed based on the response message of the first request.

[0048] Optionally, the first request carries multicast session information, which includes a first multicast session identifier and indication information. The first multicast session is a multicast session that the UE has joined or a multicast session that it has requested to join. The indication information is used to instruct the UE to remain in the first multicast session, whether it has joined, left, or requested to join.

[0049] Optionally, processing the first multicast session according to the response message of the first request includes:

[0050] If the response message of the first request carries information accepting the UE to join the first multicast session, then the context of the first multicast session is stored;

[0051] If the response message of the first request carries information that the UE is refused entry into the first multicast session, then the context of the first multicast session is deleted.

[0052] Optionally, receiving the response message for the first request sent by the first AMF includes:

[0053] Receive the response message of the first request sent by the first AMF and forwarded by the Radio Access Network Function Entity;

[0054] The method further includes:

[0055] If the response message of the first request carries information accepting the UE to join the first multicast session, then the resources of the first multicast session are established or updated.

[0056] The resources are used to receive service data from the first multicast session.

[0057] Optionally, receiving service data from the first multicast session using the resources includes:

[0058] If the wireless access network function entity does not support multicast services, then the resources are used to receive the service data of the first multicast session via unicast.

[0059] If the wireless access network function entity supports multicast services, then the resources are used to receive the service data of the first multicast session via multicast.

[0060] Fourthly, embodiments of this application also provide an AMF network function entity, including a memory, a transceiver, and a processor:

[0061] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0062] Receive a first request sent by a user equipment (UE), wherein the first request is a registration request message or a service request message;

[0063] Obtain the multicast session information of the UE according to the first request;

[0064] Based on the multicast session information, perform processing operations related to the multicast session.

[0065] Optionally, obtaining the multicast session information of the UE according to the first request includes:

[0066] Based on the first request, the context of the UE is obtained from the second AMF, wherein the context of the UE contains the multicast session information of the UE, and the second AMF is a network function entity that provides services to the UE before the UE moves.

[0067] Optionally, performing multicast session-related processing operations based on the multicast session information includes:

[0068] A first network function entity serving the first multicast session is determined, wherein the first network function entity includes: Session Management Function (SMF) or Multicast Broadcast Session Management Function (MB-SMF);

[0069] Send a second request to the first network function entity, the second request carrying the multicast session information;

[0070] Receive a response message to the second request sent by the first network function entity.

[0071] Optionally, the response message for receiving the second request sent by the first network function entity includes:

[0072] Receive a response message from the first network function entity carrying a second request containing the first multicast session identifier and resource allocation request information;

[0073] The processor is also configured to read the computer program in the memory and perform the following operations:

[0074] Based on the response message of the second request, a third request is sent to the Radio Access Network Function (RAF) entity, the third request carrying the first multicast session identifier and the resource allocation request information, so that the RAF entity can establish or update the resources of the first multicast session.

[0075] Fifthly, embodiments of this application also provide an SMF network function entity, including a memory, a transceiver, and a processor:

[0076] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0077] The system receives a second request sent by a first AMF, the second request carrying multicast session information of a user equipment (UE). The multicast session information is obtained by the first AMF after receiving the first request sent by the UE. The first request is a registration request message or a service request message.

[0078] The multicast session of the UE is processed according to the multicast session information carried in the second request.

[0079] Sixthly, embodiments of this application also provide a user equipment (UE), including a memory, a transceiver, and a processor:

[0080] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0081] Send a first request to the first AMF, wherein the first request is a service request message or a registration request message;

[0082] Receive a response message to the first request sent by the first AMF. The response message to the first request is a registration acceptance message or a service acceptance message. The response message to the first request contains information to accept the UE joining or leaving the first multicast session, or information to instruct the UE to leave the first multicast session, or information to refuse the UE from joining the first multicast session.

[0083] The first multicast session is processed based on the response message of the first request.

[0084] Optionally, the first request carries multicast session information, which includes a first multicast session identifier and indication information. The first multicast session is a multicast session that the UE has joined or a multicast session that it has requested to join. The indication information is used to instruct the UE to remain in the first multicast session, whether it has joined, left, or requested to join.

[0085] Optionally, processing the first multicast session according to the response message of the first request includes:

[0086] If the response message of the first request carries information accepting the UE to join the first multicast session, then the context of the first multicast session is stored;

[0087] If the response message of the first request carries information that the UE is refused entry into the first multicast session, then the context of the first multicast session is deleted.

[0088] Optionally, receiving the response message for the first request sent by the first AMF includes:

[0089] Receive the response message of the first request sent by the first AMF and forwarded by the Radio Access Network Function Entity;

[0090] The processor is also configured to read the computer program in the memory and perform the following operations:

[0091] If the response message of the first request carries information accepting the UE to join the first multicast session, then the resources of the first multicast session are established or updated.

[0092] The resources are used to receive service data from the first multicast session.

[0093] Optionally, receiving service data from the first multicast session using the resources includes:

[0094] If the wireless access network function entity does not support multicast services, then the resources are used to receive the service data of the first multicast session via unicast.

[0095] If the wireless access network function entity supports multicast services, then the resources are used to receive the service data of the first multicast session via multicast.

[0096] Seventhly, embodiments of this application also provide a multicast session processing apparatus, including:

[0097] The first receiving unit is configured to receive a first request sent by a user equipment (UE), wherein the first request is a registration request message or a service request message.

[0098] The first acquisition unit is configured to acquire the multicast session information of the UE according to the first request;

[0099] The execution unit is used to perform processing operations related to the multicast session based on the multicast session information.

[0100] Eighthly, embodiments of this application also provide a multicast session processing apparatus.

[0101] The second receiving unit is used to receive a second request sent by the first AMF. The second request carries multicast session information of the user equipment (UE). The multicast session information is obtained by the first AMF after receiving the first request sent by the UE. The first request is a registration request message or a service request message.

[0102] The first processing unit is used to process the multicast session of the UE according to the multicast session information carried in the second request.

[0103] Ninthly, embodiments of this application also provide a multicast session processing apparatus.

[0104] The third sending unit is used to send a first request to the first AMF, wherein the first request is a service request message or a registration request message;

[0105] The third receiving unit is used to receive the response message of the first request sent by the first AMF. The response message of the first request is a registration acceptance message or a service acceptance message. The response message of the first request includes information on accepting the UE to join or leave the first multicast session, or information on instructing the UE to leave the first multicast session, or information on rejecting the UE to join the first multicast session.

[0106] The second processing unit is used to process the first multicast session according to the response message of the first request.

[0107] In a tenth aspect, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing the processor to perform the steps of the multicast session processing method described in the first, second, and third aspects above.

[0108] Eleventhly, embodiments of this application also provide a computer-readable storage medium storing a computer program for causing the processor to perform the steps of the multicast session processing method described in the first, second, and third aspects above.

[0109] The multicast session processing method, network function entity, device, and storage medium provided in this application realize the synchronization of multicast session status between user equipment (UE) and the network through registration requests or service requests. This reduces the signaling interaction required for UE to process multicast session services, improves signaling efficiency, saves signaling resources, and shortens the time for UE to join or leave a multicast session and receive or transmit multicast session data. Attached Figure Description

[0110] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0111] Figure 1 This is a schematic diagram of the process for a UE to join a multicast session provided by existing technology;

[0112] Figure 2 This is one of the flowcharts illustrating the multicast session processing method provided in the embodiments of this application;

[0113] Figure 3 This is a second flowchart illustrating the multicast session processing method provided in the embodiments of this application;

[0114] Figure 4 This is the third flowchart of the multicast session processing method provided in the embodiments of this application;

[0115] Figure 5 This is the fourth flowchart of the multicast session processing method provided in the embodiments of this application;

[0116] Figure 6 This is the fifth flowchart illustrating the multicast session processing method provided in the embodiments of this application;

[0117] Figure 7 This is the sixth flowchart of the multicast session processing method provided in the embodiments of this application;

[0118] Figure 8 This is a schematic diagram of the structure of the AMF network functional entity provided in the embodiments of this application;

[0119] Figure 9 This is a schematic diagram of the structure of the SMF network functional entity provided in the embodiments of this application;

[0120] Figure 10 This is a schematic diagram of the structure of the user equipment (UE) provided in the embodiments of this application;

[0121] Figure 11 This is one of the structural schematic diagrams of the multicast session processing device provided in the embodiments of this application;

[0122] Figure 12 This is a second schematic diagram of the structure of the multicast session processing device provided in the embodiments of this application;

[0123] Figure 13 This is the third schematic diagram of the multicast session processing device provided in the embodiments of this application. Detailed Implementation

[0124] Data transmission methods used in Internet Protocol (IP) networks include unicast, multicast, and broadcast. Multicast / broadcast refers to "one-to-many communication," meaning the same data is sent from one sending device to multiple receiving devices through technologies such as shared channels and content replication. Compared to unicast, multicast / broadcast has higher network resource utilization efficiency.

[0125] The 5th generation mobile communication system (5G) is the next generation of wireless mobile communication system following the 4th generation mobile communication system (4G), offering greater transmission bandwidth, support for more terminals, and more service types. Currently, 5GS supports unicast transmission. To support more services, such as IPv4 / IPv6 multicast / broadcast, interactive network television, or to optimize the transmission efficiency and network resource utilization of existing services (such as group communication, Internet of Things (IoT) communication, vehicle-to-everything (V2X) communication, software download / updates, etc.), 5GS will support multicast and broadcast services (5G Multicast Broadcast Service, 5G MBS).

[0126] User equipment (UE) needs to join a multicast session to receive specific multicast service data. In existing technology, the UE requests to join a specific multicast session through a Protocol Data Unit (PDU) session modification procedure. Core network (CN) network function entities, such as the Session Management Function (SMF) or Multicast Broadcast Session Management Function (MB-SMF), join the multicast session based on this request and establish a multicast transmission tunnel between the core network gateway (e.g., the Multicast Broadcast User Plane Function (MB-UPF)) and the Wireless Access Network (RAN), thereby sending the multicast session data to the UE.

[0127] Figure 1 This is a schematic diagram of the process for a UE to join a multicast session provided by existing technology, such as... Figure 1As shown, the UE is in an idle state, meaning no signaling connection or data bearer has been established between the UE and the RAN node, or in an inactive state, meaning no signaling connection or data bearer has been established between the UE and the CN. When the UE moves or for other reasons, such as changes in network slicing, or changes in the RAN node or even the core network CN node serving the UE (e.g., changes in the Access and Mobility Management Function (AMF), since the new RAN node and / or CN node does not have the UE's multicast session information, then:

[0128] If the UE wishes to continue receiving data from the multicast session or leave the multicast session (i.e., stop receiving paging messages and data related to the multicast session), the UE needs to first enter the connected state through the registration update or service request process, and then initiate the PDU session modification process to request to join or leave the multicast session it has previously joined.

[0129] If the above steps are not performed, when the network needs to send multicast session data to the UE, since the UE is in an idle or inactive state, the network needs to page the UE. The UE responds to the page through a service request or registration update procedure. Then: the UE initiates a PDU session modification procedure to request to join or leave a previously joined multicast session, or the CN directly initiates a multicast session establishment procedure to the UE, and the UE accepts or rejects it.

[0130] When a UE in an idle or inactive state experiences a change in the network node it is connected to, it needs to engage in extensive signaling interactions with the network. First, it must complete a registration update or service request process, and then initiate a PDU session modification process. Only after these steps are completed can it receive multicast sessions, including data from previously joined multicast sessions, or leave a multicast session, meaning it stops receiving paging messages and data related to that multicast session.

[0131] In view of the above-mentioned problems in the prior art, this application provides a multicast session processing method, network function entity, device and storage medium.

[0132] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0133] Figure 2 This is one of the flowcharts illustrating the multicast session processing method provided in this application embodiment, such as... Figure 2As shown, this application provides a multicast session processing method, the execution subject of which is a first AMF, and the method includes:

[0134] Step 201: Receive a first request sent by the user equipment (UE), wherein the first request is a registration request message or a service request message.

[0135] Specifically, the first AMF receives registration request messages or service request messages sent by the user equipment (UE).

[0136] Under certain conditions, such as moving to a new registration area, requesting an update to UE capabilities, or requesting network information, the UE sends a registration request message to the network to request a registration update; or sends a service request message to request a service update.

[0137] A UE in IDLE or CONNECTED state updates to the registration area through mobility registration, or initiates registration with the 5G system; or initiates periodic registration; or initiates a registration request process when the UE needs to update the capabilities and protocol parameters negotiated through the registration process.

[0138] In IDLE mode, the UE primarily initiates service request procedures by sending uplink signaling messages, user data, or responding to a network paging request. Upon receiving a service request message, the AMF can perform authentication. After establishing a signaling connection with the AMF, the UE or the network can send signaling messages, such as a session establishment request from the UE to the SMF via the AMF's PDU.

[0139] Optionally, during UE movement, the AMF serving the UE may change. If the AMF serving the UE changes, then the first AMF here can be the network function entity that provides services to the UE after the UE moves.

[0140] Step 202: Obtain the multicast session information of the UE according to the first request.

[0141] Specifically, the UE's multicast session information is obtained based on the first request.

[0142] In the first scenario, when the UE sends the first request, it carries the UE's multicast session information in the first request. In this case, the first AMF can directly obtain the UE's multicast session information from the first request.

[0143] In the second scenario, if the UE's movement causes a change in the AMF serving the UE, the UE sends a first request to the changed first AMF. This first request can be a registration request, a request to update UE capabilities, or a request for network information. In this case, the first AMF will determine the second AMF that served the UE before the UE's movement based on the first request, and obtain the UE's context from the second AMF. The second AMF will then carry the UE's multicast session information in the returned UE context.

[0144] Specifically, the first AMF sends a UE context request to other network function entities that provide services to the UE, thereby obtaining the UE's multicast session information. The network function entity providing services to the UE can be the AMF that served the UE before the UE moved, i.e., the second AMF, or it can be the Unified Data Management (UDM). This network function entity provides the UE context to the first AMF, which carries the multicast session information that the UE has joined.

[0145] In the third scenario, when the UE sends the first request, it includes multicast session information. Simultaneously, due to UE movement, the AMF serving the UE changes. The first AMF requests the UE context from the second AMF or UDM. The UE context returned by the second AMF or UDM contains information about the multicast sessions the UE has already joined. If the UE does not request to join a new multicast session, the multicast session information in the UE context may be identical to the multicast session information carried in the first request. The first AMF can obtain the UE's multicast session information in the first request, or it can obtain it from the UE context response message of the second AMF or UDM.

[0146] If a UE requests to join a new multicast session, the multicast session information carried in the UE context is the multicast session information that the UE has already joined, and the first request carries the multicast session information that the UE requests to join. The first AMF determines the complete multicast session information of the UE based on the first request and the UE context.

[0147] Step 203: Perform processing operations related to the multicast session based on the multicast session information.

[0148] Specifically, based on the multicast session information, perform processing operations related to the multicast session.

[0149] After the first AMF obtains the UE's multicast session information, it executes the subsequent registration request process or service request process, and synchronously completes the processing of multicast session services. Multicast session-related services include receiving / transmitting multicast session data, instructing the UE to leave / join a multicast session, etc.

[0150] Specifically, after receiving the first request from the UE, the first AMF sends a response message to the UE for the first request. The response message for the first request is either a registration acceptance message or a service acceptance message, and includes:

[0151] If the UE requests to remain in the first multicast session, the response message to the first request includes information that the UE is accepted to remain in the first multicast session; the UE updates the context of the first multicast session based on the response message to the first request.

[0152] If the UE requests to remain in the first multicast session, the response message to the first request includes information instructing the UE to leave the first multicast session; the UE deletes the context of the first multicast session based on the response message to the first request.

[0153] If the UE requests to leave the first multicast session, the response message to the first request includes information instructing the UE to leave the first multicast session; the UE deletes the context of the first multicast session based on the response message to the first request;

[0154] When a UE requests to join a first multicast session, the response message to the first request includes information accepting the UE's request to join the first multicast session; the UE generates the context of the first multicast session based on the response message to the first request.

[0155] When a UE requests to join the first multicast session, the response message to the first request includes information that the UE is refused to join the first multicast session; the UE determines not to join the first multicast session based on the response message to the first request.

[0156] The multicast session processing method provided in this application realizes the synchronization of multicast session status between user equipment (UE) and the network through registration requests or service requests, reduces the signaling interaction required for UE to process multicast session services, improves signaling efficiency, saves signaling resources, and shortens the time for UE to join or leave multicast sessions and receive or transmit multicast session data.

[0157] Optionally, if the first request carries the multicast session information of the UE, then obtaining the multicast session information of the UE according to the first request includes:

[0158] Obtain the multicast session information of the UE from the first request.

[0159] Specifically, the UE's multicast session information carried in the first request includes at least one of the following:

[0160] (1) One or more multicast session identifiers (MBSsession ID), which can be the multicast session identifier that the UE requests to join, or the multicast session identifier that the UE has already joined;

[0161] (2) Information about the network function (NF) serving the multicast session, such as the MB-SMF ID;

[0162] (3) Identifier of the PDU session associated with the multicast session;

[0163] (4) For a multicast session that the UE has already joined, the indicator of whether the UE remains in the joined state is multicast sessionstatus: 1 indicates that the UE is still in the session; 0 indicates that the UE has left the session;

[0164] (5) For a new multicast session that the UE requests to join, the join request indication and the data network name (DNN) and / or single network slice selection assistance information (S-NSSAI) corresponding to the multicast session.

[0165] For example, suppose the multicast session information carried in the first request includes ID1. ID1 corresponds to a multicast session that the UE has retained. Correspondingly, the first request will also carry a multicast session status indicator, which can be 1, indicating that the UE is still in session ID1; or it can be 0, indicating that the UE has left session ID1.

[0166] For example, suppose the multicast session information carried in the first request also includes ID2. ID2 corresponds to the multicast session that the UE requests to join. Accordingly, the first request will also carry the DNN and S-NSSAI corresponding to this multicast session, so that the network side can determine whether to allow the UE to join session ID2 based on the DNN and S-NSSAI.

[0167] Optionally, obtaining the multicast session information of the UE according to the first request includes:

[0168] Based on the first request, the context of the UE is obtained from the second AMF, wherein the context of the UE contains the multicast session information of the UE, the second AMF is the AMF that provides services to the UE before the UE moves, and the first AMF is the AMF that provides services to the UE after the UE moves.

[0169] Specifically, after receiving the UE's registration request message or service request message, the first AMF determines the second AMF that provided services to the UE before the UE moved, based on the UE identifier, and sends a UE context transmission request to the second AMF.

[0170] The second AMF sends a response message to the first AMF requesting a UE context transfer, which carries the UE context. The UE context contains at least one of the following information:

[0171] (1) One or more multicast session identifiers;

[0172] (2) Information related to network functions serving multicast sessions, such as MB-SMF ID;

[0173] (3) PDU session information currently established by the UE. The PDU session information includes: PDU session identifier, information of the SMF serving the PDU session; for PDU sessions associated with multicast sessions, the PDU session information also includes the identifier of the multicast session.

[0174] Optionally, the multicast session information includes a first multicast session identifier and / or indication information, wherein the indication information is used to instruct the UE to remain in the first multicast session, which is a multicast session that the UE has joined or requested to join.

[0175] Specifically, the UE's multicast session information includes a first multicast session identifier and / or indication information. The UE's multicast session information includes one or more first multicast session identifiers.

[0176] When the UE does not request to join a new multicast session, the first multicast session is the multicast session that the UE has already joined; when the UE requests to join a new multicast session, the first multicast session can be the multicast session that the UE requests to join, or it can be the multicast session that the UE has already joined and the multicast session that the UE requests to join.

[0177] When a UE requests to join a new multicast session, or requests to maintain or leave an already joined multicast session, the UE's multicast session information includes a multicast session identifier and indication information. The indication information is used to instruct the UE to request to join a new multicast session, to maintain or leave an already joined multicast session.

[0178] For a multicast session that a UE has already joined, when the UE requests to remain in the multicast session and the UE is in the service area of ​​the multicast session, the UE's multicast session information may not include the instruction information to keep the UE in the multicast session, and the multicast session will not be processed.

[0179] Optionally, performing multicast session-related processing operations based on the multicast session information includes:

[0180] A first network function entity serving the first multicast session is determined, wherein the first network function entity includes: Session Management Function (SMF) or Multicast Broadcast Session Management Function (MB-SMF);

[0181] Send a second request to the first network function entity, the second request carrying the multicast session information;

[0182] Receive a response message to the second request sent by the first network function entity.

[0183] Specifically, the first AMF determines the SMF or MB-SMF serving the first multicast session, sends a second request for multicast session to the SMF or MB-SMF, the second request carrying the UE's multicast session information, and then receives a response message from the SMF or MB-SMF.

[0184] The second request is used to request an update to the multicast session information.

[0185] The first AMF determines the PDU session associated with the first multicast session and the SMF serving the PDU session based on multicast session information and / or UE context.

[0186] The first AMF sends a PDU session update management context request to the SMF. This PDU session update management context request carries multicast session information and may also carry UE location information, such as the cell ID or tracking area identifier (TAI) of the UE.

[0187] The SMF requests a multicast session information update from the MB-SMF. This request message may carry the AMF identifier and the RAN node identifier. The MB-SMF updates the AMF identifier and the RAN node identifier in the multicast session context. The MB-SMF sends a multicast session information update response message to the SMF. This response message includes the MBS Session ID and at least one of the following:

[0188] Information such as Quality of Service (QoS), Down Link TunnelID, and Multicast Address.

[0189] Based on the response from the MB-SMF, the SMF updates the multicast session information and the information of the PDU sessions associated with the multicast session. For example, if the QoS rules and / or QoS parameters of the multicast QoS Flow change, the SMF updates the QoS rules and / or QoS parameters of the mapped unicast QoS Flow accordingly.

[0190] SMF sends a PDU session update management context request response message to the first AMF.

[0191] For the MB-SMF ID serving the multicast session determined in the UE context, the first AMF sends a multicast session update request to the MB-SMF indicated by the MB-SMF ID. The request message carries the MBS Session ID and the RAN node identifier, and may also include RAN tunnel information.

[0192] Based on the received multicast session information update request, the MB-SMF configures the MB-UPF and updates the AMF ID and RAN nodeID in the multicast session context. The MB-SMF then sends a multicast session request response message to the first AMF.

[0193] Optionally, the response message for receiving the second request sent by the first network function entity includes:

[0194] Receive a response message from the first network function entity carrying a second request containing the first multicast session identifier and resource allocation request information;

[0195] The method further includes:

[0196] Based on the response message of the second request, a third request is sent to the Radio Access Network Function (RAF) entity, the third request carrying the first multicast session identifier and the resource allocation request information, so that the RAF entity can establish or update the resources of the first multicast session.

[0197] Specifically, the first AMF receives a response message to the second request sent by the first network function entity. The response message to the second request carries the first multicast session identifier and resource allocation request information. Based on the response message to the second request, the first AMF sends a third request to the RAN to establish or update the resources of the first multicast session.

[0198] When the first network functional entity is an SMF, the SMF sends a PDU session update session management context response message to the first AMF. This response message carries the MBS Session ID, the MB-SMF ID, and the multicast session information in the N2 information sent to the RAN, including the MBS Session ID, the associated PDU session information, and at least one of the following: QoS information; Common Down Link Tunnel ID; Multicast Address, etc.

[0199] For multicast services provided in a specific area, the SMF can determine whether the UE is currently in the service area of ​​the first multicast session based on the UE's location information and the service area of ​​the first multicast session.

[0200] If the UE is not within the service area of ​​the first multicast session, the SMF requires the UE to leave the first multicast session. That is, the response message to the first AMF carries a PDU session modification indication message, which carries the first multicast session identifier and information instructing the UE to leave the first multicast session.

[0201] For the first multicast session that instructs the UE to leave:

[0202] The SMF updates the information of the PDU session associated with the first multicast session, that is: the MBS Session ID and the mapped unicast QoS information are removed from the PDU session context; if the SMF has saved a list of UEs that have joined the first multicast session, the SMF removes the UE ID from the UE list.

[0203] The SMF's response message to the first AMF does not carry the MB-SMF ID, and the N2 message to the RAN does not carry information about the first multicast session.

[0204] When the first network function entity is MB-SMF, MB-SMF configures MB-UPF according to the received multicast session information update request, and updates AMF ID and RAN node ID to the multicast session context.

[0205] The MB-SMF sends a multicast session information update request response message to the AMF. This response message carries multicast session information provided to the RAN, including the MBS Session ID and at least one of the following:

[0206] QoS information; Common Down Link Tunnel ID; Multicast Address, etc.

[0207] The first AMF sends the multicast session information provided to the RAN to the RAN through the N2 interface. The RAN sends a resource allocation request message to the UE. If the resources for the first multicast session have not been established, the RAN establishes the resources for the first multicast session. If the resources for the first multicast session have been established, the RAN updates the resources for the first multicast session.

[0208] If the RAN supports multicast services, the UE utilizes the resources of the first multicast session to receive the service data of the first multicast session via multicast.

[0209] If the RAN does not support multicast services, the UE uses the resources of the first multicast session to receive the service data of the first multicast session via unicast.

[0210] Optionally, the response message to the second request carries a first multicast session identifier and the following information:

[0211] Information instructing the UE to leave the first multicast session; or,

[0212] The UE is denied the right to join the first multicast session.

[0213] Specifically, the response message to the second request sent by the first network function entity to the first AMF carries a first multicast session identifier and information instructing the UE to leave or denying the UE from joining the first multicast session.

[0214] If the first multicast session is a multicast session that the UE has already joined, the multicast session information carries information instructing the UE to remain in or leave the first multicast session.

[0215] In the case where the first multicast session is a new multicast session that the UE requests to join, the multicast session information carries information indicating that the UE requests to join the first multicast session.

[0216] For multicast services provided in a specific area, the SMF can determine whether the UE is currently in the multicast session service area based on the UE location information and the service area of ​​the multicast session (MBS).

[0217] If a UE requests to maintain its membership in the first multicast session, and the UE is not within the service area of ​​the first multicast session, the SMF determines that the UE cannot maintain its membership in the first multicast session. In this case, the response message of the second request carries information indicating that the UE should leave the first multicast session, such as the first multicast session identifier and a leave instruction.

[0218] The SMF updates the information of the PDU session associated with the first multicast session, namely: removing the first multicast session identifier and the mapped unicast QoS information from the PDU session context; if the SMF has saved a list of UEs that have joined the first multicast session, the SMF removes the UE ID from the UE list.

[0219] If the SMF determines that the UE should remain in the first multicast session within the service area of ​​the first multicast session, then the first AMF can add new RAN node information serving the UE, such as the RAN node identifier, to the multicast session context.

[0220] If the UE is not within the service area of ​​the first multicast session when requesting to join the first multicast session, the SMF will refuse the UE's request to join the first multicast session and include the first multicast session identifier and the indication information for refusing the UE's request to join the first multicast session in the response message to the second request from the first AMF.

[0221] If the UE is within the service area of ​​the first multicast session, and the SMF determines to accept the UE joining the first multicast session, the SMF will add the UE identifier to the UE list of the first multicast session.

[0222] The response message to the second request carries information accepting the UE's joining of the first multicast session.

[0223] Optionally, the method further includes:

[0224] A third request is sent to the Radio Access Network Function (RAF) entity, the third request carrying a first multicast session identifier and information instructing the UE to leave the first multicast session, so that the RAF entity removes the UE's identifier from the context of the first multicast session.

[0225] Specifically, after receiving the response message of the second request sent by the SMF or MB-SMF, the first AMF sends a third request to the RAN through the N2 interface. The third request carries multicast session information and registration / service acceptance messages, as well as a PDU session modification indication message.

[0226] The PDU session modification instruction message carries the first multicast session identifier and information instructing the UE to leave the first multicast session.

[0227] For a multicast session that instructs a UE to leave, the SMF updates the information of the PDU session associated with the multicast session, that is: the first multicast session identifier and the mapped unicast service quality information are removed from the PDU session context; if the SMF has saved a list of UEs that have joined the first multicast session, the SMF removes the UE identifier from the UE list.

[0228] The response message from the SMF to the first AMF carries information indicating that the UE leaves the first multicast session, such as the first multicast session identifier and the leave indication.

[0229] The first AMF sends a third request to the RAN. The RAN forwards the information in the third request to the UE. The UE determines to leave the first multicast session based on the first multicast session identifier and the information indicating that the UE should leave the first multicast session, that is, to delete the context of the multicast session in the UE.

[0230] Optionally, the multicast session information further includes at least one of the following identification information:

[0231] The identifier of the Protocol Data Unit (PDU) session associated with the first multicast session;

[0232] The identifier of the MB-SMF serving the first multicast session and / or the identifier of the SMF;

[0233] The determination of the first network function entity serving the first multicast session includes:

[0234] Based on the at least one identification information, a first network function entity serving the first multicast session is determined.

[0235] Specifically, in this embodiment of the application, the multicast session information includes, in addition to the first multicast session identifier and / or indication information, the following:

[0236] The identifier of the PDU session associated with the first multicast session;

[0237] Information about network functions serving the first multicast session, such as the identifier of the MB-SMF and / or the identifier of the SMF.

[0238] The first AMF determines the PDU session associated with the first multicast session and the SMF serving the PDU session based on the multicast session information in the first request sent by the UE and / or the multicast session information in the UE context.

[0239] Specifically, it includes:

[0240] If the first request sent by the UE contains an identifier of the PDU session associated with the first multicast session, then the PDU session indicated by the PDU session identifier and the SMF serving the PDU session are selected.

[0241] If a PDU session information in the UE context contains multicast session information, then select that PDU session and the SMF serving that PDU session;

[0242] If none of the PDU session information in the UE context contains multicast session information, then based on the DNN and / or S-NSSAI corresponding to the multicast session in the UE registration request, select a PDU session belonging to that DNN and / or S-NSSAI as the PDU session associated with the multicast session, and the SMF serving that PDU session.

[0243] If the UE context contains an identifier of the MB-SMF serving the first multicast session, the first AMF can determine the MB-SMF serving the first multicast session based on the identifier of the MB-SMF.

[0244] The multicast session processing method provided in this application realizes the synchronization of multicast session status between user equipment (UE) and the network through registration requests or service requests, reduces the signaling interaction required for UE to process multicast session services, improves signaling efficiency, saves signaling resources, and shortens the time for UE to join or leave multicast sessions and receive or transmit multicast session data.

[0245] Figure 3 This is a second flowchart illustrating the multicast session processing method provided in this application embodiment, as shown below. Figure 3 As shown in the figure, this application provides a multicast session processing method, the execution subject of which is an SMF, and the method includes:

[0246] Step 301: Receive a second request sent by the first AMF. The second request carries multicast session information of the user equipment (UE). The multicast session information is obtained by the first AMF after receiving the first request sent by the UE. The first request is a registration request message or a service request message.

[0247] Step 302: Process the multicast session of the UE according to the multicast session information carried in the second request.

[0248] The multicast session processing method provided in this application realizes the synchronization of multicast session status between user equipment (UE) and the network through registration requests or service requests, reduces the signaling interaction required for UE to process multicast session services, improves signaling efficiency, saves signaling resources, and shortens the time for UE to join or leave multicast sessions and receive or transmit multicast session data.

[0249] Optionally, the multicast session information includes a first multicast session identifier and / or indication information, wherein the indication information is used to instruct the UE to remain in the first multicast session, which is a multicast session that the UE has joined or requested to join.

[0250] Optionally, processing the multicast session of the UE based on the multicast session information carried in the second request includes:

[0251] If the indication information is used to instruct the UE to request to join the first multicast session, and it is determined that the UE's joining the first multicast session is accepted, then a correspondence is established between the UE's identifier and the first multicast session identifier; a response message for the second request is sent to the first AMF, the response message for the second request carrying information accepting the UE's joining the first multicast session; or,

[0252] If the indication information is used to instruct the UE to request to join the first multicast session, and the UE is not within the service area of ​​the first multicast session, then a response message for the second request is sent to the first AMF, the response message for the second request carrying information that the UE is refused to join the first multicast session; or,

[0253] If the indication information is used to instruct the UE to remain in the first multicast session, and the UE is not within the service area of ​​the first multicast session, then a response message for the second request is sent to the first AMF, the response message for the second request carrying information instructing the UE to leave the first multicast session; or,

[0254] If the indication information is used to instruct the UE to leave the first multicast session, then the correspondence between the UE's identifier and the first multicast session identifier is deleted.

[0255] Optionally, processing the multicast session of the UE based on the multicast session information carried in the second request includes:

[0256] If the indication information is used to instruct the UE to request to join the first multicast session, and it is determined that the UE's joining of the first multicast session is accepted, then the identifier of the Radio Access Network Function entity stored in the storage service for the UE is stored in the context of the first multicast session.

[0257] It should be noted that the multicast session processing method with SMF as the execution subject provided in the embodiments of the present invention can implement all the method steps implemented in the multicast session processing method embodiment with first AMF as the execution subject, and can achieve the same technical effect. Here, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail.

[0258] Figure 4 This is the third flowchart illustrating the multicast session processing method provided in this application embodiment, as shown below. Figure 4 As shown in the figure, this application embodiment provides a multicast session processing method, the execution subject of which is a UE, and the method includes:

[0259] Step 401: Send a first request to the first AMF, wherein the first request is a service request message or a registration request message.

[0260] Step 402: Receive the response message of the first request sent by the first AMF. The response message of the first request is a registration acceptance message or a service acceptance message. The response message of the first request contains information on accepting the UE to join or leave the first multicast session, or information on instructing the UE to leave the first multicast session, or information on rejecting the UE to join the first multicast session.

[0261] Step 403: Process the first multicast session according to the response message of the first request.

[0262] The multicast session processing method provided in this application realizes the synchronization of multicast session status between user equipment (UE) and the network through registration requests or service requests, reduces the signaling interaction required for UE to process multicast session services, improves signaling efficiency, saves signaling resources, and shortens the time for UE to join or leave multicast sessions and receive or transmit multicast session data.

[0263] Optionally, the first request carries multicast session information, which includes a first multicast session identifier and indication information. The first multicast session is a multicast session that the UE has joined or a multicast session that it has requested to join. The indication information is used to instruct the UE to remain in the first multicast session, whether it has joined, left, or requested to join.

[0264] Optionally, processing the first multicast session according to the response message of the first request includes:

[0265] If the response message of the first request carries information accepting the UE to join the first multicast session, then the context of the first multicast session is stored;

[0266] If the response message of the first request carries information that the UE is refused entry into the first multicast session, then the context of the first multicast session is deleted.

[0267] Optionally, receiving the response message for the first request sent by the first AMF includes:

[0268] Receive the response message of the first request sent by the first AMF and forwarded by the Radio Access Network Function Entity;

[0269] The method further includes:

[0270] If the response message of the first request carries information accepting the UE to join the first multicast session, then the resources of the first multicast session are established or updated.

[0271] The resources are used to receive service data from the first multicast session.

[0272] Optionally, receiving service data from the first multicast session using the resources includes:

[0273] If the wireless access network function entity does not support multicast services, then the resources are used to receive the service data of the first multicast session via unicast.

[0274] If the wireless access network function entity supports multicast services, then the resources are used to receive the service data of the first multicast session via multicast.

[0275] It should be noted that the multicast session processing method with UE as the execution subject provided in the embodiments of the present invention can implement all the method steps implemented in the multicast session processing method embodiment with the first AMF as the execution subject, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0276] The multicast session processing method provided in this application is described below with specific embodiments.

[0277] Figure 5 This is the fourth flowchart illustrating the multicast session processing method provided in the embodiments of this application, as follows: Figure 5 As shown, this application provides a multicast session processing method. During the registration process, when an AMF triggers the establishment of a multicast session on a new RAN node, the method includes:

[0278] Step 501: When the UE moves to a new registration area, requests an update to its capabilities, or requests network information, it sends a Registration Request to the network to request a registration update.

[0279] Step 502: If the network function entity serving the UE changes after the UE moves, the new AMF serving the UE after the UE moves determines whether it has a UE context, identifies the old AMF that served the UE before the UE moved based on the UE identifier, and sends a UE context transfer request Namf_Communication_UE ContextTransfer to the old AMF.

[0280] Step 503: The old AMF sends a response message Namf_Communication_UEContextTransfer Response to the new AMF, which carries multicast session information that the UE has joined, including at least one of the following:

[0281] One or more multicast session identifiers (MBS session IDs);

[0282] Network functions (NFs) that serve multicast sessions, such as MB-SMF information and MB-SMF ID;

[0283] The identifier of the PDU session associated with the multicast session: Associated PDU Session ID.

[0284] Step 504: The new AMF generates or updates the multicast session context based on the multicast session information provided by the old AMF. The new AMF can add new RAN node information serving the UE, such as the RAN Node ID, to the multicast session context.

[0285] Step 505: The new AMF determines the PDU session associated with the multicast session and the SMF serving the PDU session based on the PDU session information in the UE context.

[0286] The new AMF sends a PDU session update session management context request (Ns mf_PDUSession_UpdateSession Management Context) to the SMF. This request message carries multicast session information, such as the multicast session identifier (MBSSession ID). The request message may also carry UE location information, such as the cell identifier (Cell ID) or tracking area identifier (TAI) where the UE is located.

[0287] Step 506: The SMF requests a multicast session information update from the MB-SMF. This request message may carry the AMF identifier and the RAN node identifier.

[0288] Step 507: MB-SMF updates the AMF identifier and RAN node identifier in the multicast session context.

[0289] Step 508: MB-SMF sends a multicast session information update response message to SMF. This response message includes the MBSSession ID and at least one of the following:

[0290] Information such as Quality of Service (QoS), Down Link TunnelID, and Multicast Address.

[0291] Step 509: Based on the response from MB-SMF, SMF updates the local multicast session information and updates the information of the PDU session associated with the multicast session. For example, if the QoS rules and / or QoS parameters of the multicast QoS Flow change, SMF updates the QoS rules and / or QoS parameters of the mapped unicast QoS Flow accordingly.

[0292] Step 5010: The SMF sends a PDU session update session management context response message (Nsmf_PDUSession_Update Session Management Context response) to the new AMF. This response message carries the MBSSession ID, the MB-SMF ID, and multicast session information in the N2 information sent to the RAN, including the MBS SessionID, the associated PDU session information, and at least one of the following:

[0293] QoS information; Common Down Link Tunnel ID; Multicast Address, etc.

[0294] For multicast services that are only available in specific areas, the SMF can determine whether the UE is currently in the multicast session service area based on the UE's location information and the service area of ​​the multicast session (MBS).

[0295] If the UE is not within the service area of ​​the multicast session, the SMF requires the UE to leave the multicast session. That is, the response message to the new AMF carries a PDU Session Modification Command message, which carries the Multicast Session ID (MBS Session ID) and information instructing the UE to leave the multicast session.

[0296] For multicast sessions that indicate UE departure:

[0297] The SMF updates the information of the PDU session associated with the multicast session, that is: the MBS Session ID and the mapped unicast QoS information are removed from the PDU session context; if the SMF has saved a list of UEs that have joined the multicast session, the SMF removes the UE ID from the UE list.

[0298] The SMF's response message to the new AMF does not carry the MB-SMF ID, nor does the N2 message to the RAN carry information about the multicast session.

[0299] Steps 506-509, 5011, and 5014-5019 are not executed.

[0300] Step 5011: If step 504 is not executed, the new AMF can generate or update the multicast session context at this time. The new AMF can also add new RAN node information serving the UE, such as the RAN node identifier, to the multicast session context.

[0301] Step 5012: The new AMF sends an N2 message to the RAN. The N2 message carries the multicast session information contained in the Nsmf_PDUSession_Update Session Management Context response of step 5010, as well as the Registration Accept message. The N2 message may also carry a PDU SessionModification Command message.

[0302] Step 5013: The RAN forwards the registration acceptance message to the UE. The RAN can also forward the PDU SessionModification Command message to the UE. The UE determines whether to leave the multicast session based on the MBS Session ID and information instructing the UE to leave the multicast session in the message; that is, the context of the multicast session in the UE is deleted. For other multicast sessions, the UE retains or updates the context of the multicast session in the UE.

[0303] Step 5014: If the RAN supports multicast services, the RAN sends an N2 message to the AMF based on the information of the received multicast session. The N2 message carries the MBS Session ID and may also carry RAN tunnel information.

[0304] Step 5015: The AMF sends a multicast session information update request to the MB-SMF indicated by the MB-SMF ID in step 503 or step 5010. The request message carries the MBS Session ID and RAN Node ID, and may also carry RAN tunnel information.

[0305] Step 5016: MB-SMF configures MB-UPF according to the received multicast session information update request, and updates AMFID and RAN node ID to the multicast session context.

[0306] Step 5017: The MB-SMF sends a multicast session information update request response message to the AMF. This response message carries information about the multicast session provided to the RAN, including the MBS Session ID and at least one of the following:

[0307] QoS information; Common Down Link Tunnel ID; Multicast Address, etc.

[0308] The QoS information, Common Down Link Tunnel ID, and Multicast Address can be sent to the RAN through steps 5010, 5012, or steps 5017, 5018.

[0309] Step 5018: AMF sends an N2 message to the NG-RAN node, which carries information about the multicast session provided by MB-SMF in step 5017.

[0310] Step 5019: The RAN sends a resource allocation request message to the UE. If the resources for the multicast session have not been established, the RAN establishes the resources for the multicast session. If the RAN does not support multicast services, the RAN establishes the resources for the unicast QoS flow mapped to the PDU session associated with the multicast session, and transmits the multicast service data to the UE via unicast.

[0311] Figure 6 This is the fifth flowchart illustrating the multicast session processing method provided in this application embodiment, as shown below. Figure 6 As shown, this application provides a multicast session processing method. When a UE maintains or leaves an already joined multicast session after connecting to a new RAN, the method includes:

[0312] Step 601: When the UE moves to a new registration area, requests an update to its capabilities, or requests network information, it sends a Registration Request to the network to request a registration update. The registration request carries multicast session information that the UE has joined. This multicast session information includes one or more multicast session identifiers and may also include:

[0313] For each multicast session, the indication of whether the UE remains in the joined state (Multicast Session Status) is: 1 indicates that the UE remains in the multicast session; 0 indicates that the UE has left the multicast session.

[0314] The identifier of the PDU session associated with the multicast session (Associated PDU Session ID).

[0315] Step 602: If the network function entity serving the UE changes after the UE moves, the new AMF serving the UE after the UE moves determines whether it has a UE context, identifies the old AMF that served the UE before the UE moved based on the UE identifier, and sends a UE context transfer request Namf_Communication_UE ContextTransfer to the old AMF.

[0316] Step 603: The old AMF sends a response message, Namf_Communication_UEContextTransfer Response, to the new AMF, carrying the UE's context. The UE's context includes information about the UE's currently established PDU sessions, which includes the PDU session identifier and information about the SMF serving the PDU session. For PDU sessions associated with multicast sessions, the PDU session information also includes the multicast session identifier.

[0317] Step 604: The new AMF generates or updates the multicast session context based on the multicast session information in the UE registration request and the UE's uplink / downlink information. The new AMF can add new RAN node information serving the UE, such as the RAN Node ID, to the multicast session context.

[0318] Step 605: The new AMF determines the PDU session associated with the multicast session and the SMF serving the PDU session based on the UE context.

[0319] The new AMF sends a PDU session update session management context request (Nsmf_PDUSession_UpdateSession Management Context) to the SMF. This request message carries multicast session information, including at least one multicast session identifier, and may also include an indication of whether the UE remains joined or left for each multicast session. The request message may also carry UE location information, such as the UE's cell identifier (CellID) or tracking area identifier (TAI).

[0320] Steps 606-609 are the same as steps 506-509.

[0321] Step 6010 is basically the same as step 5010, except that for multicast sessions with a multicast session status of 0, the SMF sets the multicast session status of the multicast session to 0 in the PDU session update session management context response message sent to the new AMF.

[0322] For multicast services that are only available in specific areas, the SMF can determine whether the UE is currently in the multicast session service area based on the UE's location information and the service area of ​​the multicast session (MBS).

[0323] If the UE is not within the service area of ​​the multicast session, the SMF will reject the UE's request to remain in the multicast session, that is, set the multicast session status of the multicast session to 0 in the PDU session update session management context response message.

[0324] For multicast sessions where the multicast session status is 0:

[0325] The SMF updates the information of the PDU session associated with the multicast session, that is: the MBS Session ID and the mapped unicast QoS information are removed from the PDU session context; if the SMF has saved a list of UEs that have joined the multicast session, the SMF removes the UE ID from the UE list.

[0326] The SMF's response message to the new AMF does not carry the MB-SMF ID, nor does the N2 message to the RAN carry information about the multicast session.

[0327] Steps 606-609, 6011, and 6014-6019 are not executed.

[0328] Step 6011 is the same as step 5011.

[0329] Steps 6012-6013 are basically the same as steps 5012-5013, with the following differences:

[0330] The Registration Accept message carries the MBS Session ID and Multicast SessionStatus. For multicast sessions with a Multicast Session Status of 0, if the UE has not yet left the multicast session, the UE leaves the multicast session, i.e., the context of the multicast session in the UE is deleted. For multicast sessions with a multicast session status of 1, the UE retains or updates the context of the multicast session in the UE.

[0331] The N2 message sent by AMF to RAN does not carry the PDU Session Modification Command message, therefore RAN will not send the PDU Session Modification Command message to UE.

[0332] Steps 6014-6019 are the same as steps 5014-5019.

[0333] Figure 7 This is the sixth flowchart illustrating the multicast session processing method provided in this application embodiment, as shown below. Figure 7 As shown in the figure, this application provides a multicast session processing method. When a UE requests to join a new multicast session after connecting to a new RAN, the method includes:

[0334] Step 701: When the UE moves to a new registration area, requests an update to its capabilities, or requests network information, it sends a Registration Request to the network to request a registration update. This request message carries information about the multicast session the UE requests to join, including one or more multicast session identifiers, a join request indication, and may also include the PDU session identifier associated with the multicast session, the DNN corresponding to the multicast session, and / or S-NSSAI information.

[0335] Step 702: If the network function entity serving the UE changes after the UE moves, the new AMF serving the UE after the UE moves determines whether it has a UE context, identifies the old AMF that served the UE before the UE moved based on the UE identifier, and sends a UE context transfer request Namf_Communication_UE ContextTransfer to the old AMF.

[0336] Step 703: The old AMF sends a response message, Namf_Communication_UEContextTransfer Response, to the new AMF, carrying the UE context. The UE context contains information about the UE's currently established PDU sessions, including: PDU Session ID, information about the SMF serving the PDU session, and possibly multicast session information, such as the MBS Session ID.

[0337] Step 704: The new AMF generates or updates the multicast session context based on the multicast session information provided by the old AMF. The new AMF can add new RAN node information serving the UE, such as the RAN Node ID, to the multicast session context.

[0338] Step 705: The new AMF determines the PDU session associated with the multicast session and the SMF serving that PDU session based on the multicast session information and / or UE context information in the UE registration request. Specifically, this is done as follows:

[0339] If the UE registration request contains the PDU session identifier associated with the multicast session, then select that PDU session and the SMF serving that PDU session;

[0340] If the information of a PDU session in the UE context contains multicast session information, then select that PDU session and the SMF serving that PDU session;

[0341] If none of the PDU session information in the UE context contains multicast session information, then based on the DNN and / or S-NSSAI corresponding to the multicast session in the UE registration request, select a PDU session belonging to that DNN and / or S-NSSAI as the PDU session associated with the multicast session, and the SMF serving that PDU session.

[0342] The new AMF sends a PDU session update session management context request (Nsmf_PDUSession_Update Session Management Context) to the designated SMF. This request message carries multicast session information that the UE requests to join, including one or more multicast session identifiers, a join request indication, and may also include the DNN and / or S-NSSAI information corresponding to the multicast session. The request message may also carry UE location information, such as the cell ID or tracking area identifier (TAI) of the UE.

[0343] Steps 706-709 are the same as steps 506-509.

[0344] Step 7010 is basically the same as step 5010, except that:

[0345] For multicast services that are only available in specific areas, the SMF can determine whether the UE is currently in the multicast session service area based on the UE's location information and the service area of ​​the multicast session (MBS).

[0346] If the UE is not within the service area of ​​the multicast session, the SMF will reject the UE's request to join the multicast session, that is, it will include the multicast session identifier and an indication to reject the UE's request to join the multicast session in the response message to the new AMF. For this multicast session, steps 706-709, 7011, and 7014-7019 will not be executed.

[0347] Step 7011 is the same as step 5011.

[0348] Steps 7012-7013 are basically the same as steps 5012-5013, with the following differences:

[0349] The Registration Accept message carries the MBS Session ID and information indicating whether the UE is accepted or rejected from joining the multicast session. For accepting the UE's joining of a multicast session, the UE stores the context of that multicast session. This storage includes both generation and updating. For rejecting the UE's joining of a multicast session, the UE deletes the context of that multicast session.

[0350] The N2 message sent by AMF to RAN does not carry the PDU Session Modification Command message, therefore RAN will not send the PDU Session Modification Command message to UE.

[0351] Steps 7014-7019 are the same as steps 5014-5019.

[0352] Figure 8 This is a schematic diagram of the structure of the AMF network functional entity provided in the embodiments of this application, such as... Figure 8 As shown, this application embodiment provides an AMF network function entity, including a memory 801, a transceiver 802, and a processor 803:

[0353] Memory 801 is used to store computer programs; transceiver 802 is used to send and receive data under the control of processor 803; processor 803 is used to read the computer program in memory 801 and perform the following operations:

[0354] Receive a first request sent by a user equipment (UE), wherein the first request is a registration request message or a service request message;

[0355] Obtain the multicast session information of the UE according to the first request;

[0356] Based on the multicast session information, perform processing operations related to the multicast session.

[0357] Specifically, transceiver 802 is used to receive and send data under the control of processor 803.

[0358] Among them, Figure 8 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 803 and memory represented by memory 801 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides the interface.

[0359] The transceiver 802 may consist of multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, and other transmission media. The processor 803 is responsible for managing the bus architecture and general processing, and the memory 801 can store data used by the processor 803 during operation.

[0360] The processor 803 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0361] Optionally, if the first request carries the multicast session information of the UE, then obtaining the multicast session information of the UE according to the first request includes:

[0362] Obtain the multicast session information of the UE from the first request.

[0363] Optionally, obtaining the multicast session information of the UE according to the first request includes:

[0364] Based on the first request, the context of the UE is obtained from the second AMF, wherein the context of the UE contains the multicast session information of the UE, and the second AMF is a network function entity that provides services to the UE before the UE moves.

[0365] Optionally, the multicast session information includes a first multicast session identifier and / or indication information, wherein the indication information is used to instruct the UE to remain in the first multicast session, which is a multicast session that the UE has joined or requested to join.

[0366] Optionally, performing multicast session-related processing operations based on the multicast session information includes:

[0367] A first network function entity serving the first multicast session is determined, wherein the first network function entity includes: Session Management Function (SMF) or Multicast Broadcast Session Management Function (MB-SMF);

[0368] Send a second request to the first network function entity, the second request carrying the multicast session information;

[0369] Receive a response message to the second request sent by the first network function entity.

[0370] Optionally, the response message for receiving the second request sent by the first network function entity includes:

[0371] Receive a response message from the first network function entity carrying a second request containing the first multicast session identifier and resource allocation request information;

[0372] Processor 803 is also used to read computer programs from memory 801 and perform the following operations:

[0373] Based on the response message of the second request, a third request is sent to the Radio Access Network Function (RAF) entity, the third request carrying the first multicast session identifier and the resource allocation request information, so that the RAF entity can establish or update the resources of the first multicast session.

[0374] Optionally, the response message to the second request carries a first multicast session identifier and the following information:

[0375] Information instructing the UE to leave the first multicast session; or,

[0376] The UE is denied the right to join the first multicast session.

[0377] Optionally, the processor 803 is also used to read the computer program in the memory 801 and perform the following operations:

[0378] A third request is sent to the Radio Access Network Function (RAF) entity, the third request carrying a first multicast session identifier and information instructing the UE to leave the first multicast session, so that the RAF entity removes the UE's identifier from the context of the first multicast session.

[0379] Optionally, the multicast session information further includes at least one of the following identification information:

[0380] The identifier of the Protocol Data Unit (PDU) session associated with the first multicast session;

[0381] The identifier of the MB-SMF serving the first multicast session and / or the identifier of the SMF;

[0382] The determination of the first network function entity serving the first multicast session includes:

[0383] Based on the at least one identification information, a first network function entity serving the first multicast session is determined.

[0384] It should be noted that the AMF network function entity provided in this embodiment of the invention can implement all the method steps implemented in the above embodiment of the multicast session processing method with the first AMF as the execution subject, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0385] Figure 9 This is a structural diagram of the SMF network functional entity provided in the embodiments of this application, such as... Figure 9 As shown, this application embodiment provides an SMF network function entity, including a memory 901, a transceiver 902, and a processor 903:

[0386] Memory 901 is used to store computer programs; transceiver 902 is used to send and receive data under the control of processor 903; processor 903 is used to read the computer program in memory 901 and perform the following operations:

[0387] The system receives a second request sent by a first AMF, the second request carrying multicast session information of a user equipment (UE). The multicast session information is obtained by the first AMF after receiving the first request sent by the UE. The first request is a registration request message or a service request message.

[0388] The multicast session of the UE is processed according to the multicast session information carried in the second request.

[0389] Specifically, transceiver 902 is used to receive and send data under the control of processor 903.

[0390] Among them, Figure 9 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 903 and memory represented by memory 901 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides the interface.

[0391] The transceiver 902 may consist of multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, and other transmission media. The processor 903 is responsible for managing the bus architecture and general processing, and the memory 901 can store data used by the processor 903 during operation.

[0392] The processor 903 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0393] Optionally, the multicast session information includes a first multicast session identifier and / or indication information, wherein the indication information is used to instruct the UE to remain in the first multicast session, which is a multicast session that the UE has joined or requested to join.

[0394] Optionally, processing the multicast session of the UE based on the multicast session information carried in the second request includes:

[0395] If the indication information is used to instruct the UE to request to join the first multicast session, and it is determined that the UE's joining the first multicast session is accepted, then a correspondence is established between the UE's identifier and the first multicast session identifier; a response message for the second request is sent to the first AMF, the response message for the second request carrying information accepting the UE's joining the first multicast session; or,

[0396] If the indication information is used to instruct the UE to request to join the first multicast session, and the UE is not within the service area of ​​the first multicast session, then a response message for the second request is sent to the first AMF, the response message for the second request carrying information that the UE is refused to join the first multicast session; or,

[0397] If the indication information is used to instruct the UE to remain in the first multicast session, and the UE is not within the service area of ​​the first multicast session, then a response message for the second request is sent to the first AMF, the response message for the second request carrying information instructing the UE to leave the first multicast session; or,

[0398] If the indication information is used to instruct the UE to leave the first multicast session, then the correspondence between the UE's identifier and the first multicast session identifier is deleted.

[0399] Optionally, processing the multicast session of the UE based on the multicast session information carried in the second request includes:

[0400] If the indication information is used to instruct the UE to request to join the first multicast session, and it is determined that the UE's joining of the first multicast session is accepted, then the identifier of the Radio Access Network Function entity stored in the storage service for the UE is stored in the context of the first multicast session.

[0401] It should be noted that the SMF network function entity provided in this embodiment of the invention can implement all the method steps implemented in the above embodiment of the multicast session processing method with SMF as the execution subject, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0402] Figure 10 This is a schematic diagram of the structure of the user equipment (UE) provided in the embodiments of this application, such as... Figure 10 As shown, this application provides a user equipment (UE) including a memory 1001, a transceiver 1002, and a processor 1003.

[0403] Memory 1001 is used to store computer programs; transceiver 1002 is used to send and receive data under the control of processor 1003; processor 1003 is used to read the computer program in memory 1001 and perform the following operations:

[0404] Send a first request to the first AMF, wherein the first request is a service request message or a registration request message;

[0405] Receive a response message to the first request sent by the first AMF. The response message to the first request is a registration acceptance message or a service acceptance message. The response message to the first request contains information to accept the UE joining or leaving the first multicast session, or information to instruct the UE to leave the first multicast session, or information to refuse the UE from joining the first multicast session.

[0406] The first multicast session is processed based on the response message of the first request.

[0407] Specifically, transceiver 1002 is used to receive and send data under the control of processor 1003.

[0408] Among them, Figure 10 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1003 and memory represented by memory 1001 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides the interface.

[0409] The transceiver 1002 may consist of multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, and other transmission media. The processor 1003 is responsible for managing the bus architecture and general processing, and the memory 1001 can store data used by the processor 1003 during operation.

[0410] The processor 1003 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0411] Optionally, the first request carries multicast session information, which includes a first multicast session identifier and indication information. The first multicast session is a multicast session that the UE has joined or a multicast session that it has requested to join. The indication information is used to instruct the UE to remain in the first multicast session, whether it has joined, left, or requested to join.

[0412] Optionally, processing the first multicast session according to the response message of the first request includes:

[0413] If the response message of the first request carries information accepting the UE to join the first multicast session, then the context of the first multicast session is stored;

[0414] If the response message of the first request carries information that the UE is refused entry into the first multicast session, then the context of the first multicast session is deleted.

[0415] Optionally, receiving the response message for the first request sent by the first AMF includes:

[0416] Receive the response message of the first request sent by the first AMF and forwarded by the Radio Access Network Function Entity;

[0417] Processor 1003 is also used to read computer programs from memory 1001 and perform the following operations:

[0418] If the response message of the first request carries information accepting the UE to join the first multicast session, then the resources of the first multicast session are established or updated.

[0419] The resources are used to receive service data from the first multicast session.

[0420] Optionally, receiving service data from the first multicast session using the resources includes:

[0421] If the wireless access network function entity does not support multicast services, then the resources are used to receive the service data of the first multicast session via unicast.

[0422] If the wireless access network function entity supports multicast services, then the resources are used to receive the service data of the first multicast session via multicast.

[0423] It should be noted that the user equipment (UE) provided in the embodiments of the present invention can implement all the method steps implemented in the above-mentioned multicast session processing method embodiments with UE as the execution subject, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiments and the beneficial effects will not be described in detail.

[0424] Figure 11 This is one of the structural schematic diagrams of the multicast session processing device provided in the embodiments of this application, such as... Figure 11 As shown in the figure, this application provides a multicast session processing apparatus, which includes:

[0425] The first receiving unit 1101 is used to receive a first request sent by the user equipment UE, wherein the first request is a registration request message or a service request message.

[0426] The first acquisition unit 1102 is used to acquire the multicast session information of the UE according to the first request;

[0427] The execution unit 1103 is used to perform processing operations related to the multicast session based on the multicast session information.

[0428] Optionally, if the first request carries the multicast session information of the UE, then the first acquisition unit includes:

[0429] The first acquisition module is used to acquire the multicast session information of the UE from the first request.

[0430] Optionally, the first acquisition unit includes:

[0431] The second acquisition module is used to acquire the context of the UE from the second AMF based on the first request, wherein the context of the UE includes the multicast session information of the UE, the second AMF is a network function entity that provides services to the UE before the UE moves, and the first AMF is a network function entity that provides services to the UE after the UE moves.

[0432] Optionally, the multicast session information includes a first multicast session identifier and / or indication information, wherein the indication information is used to instruct the UE to remain in the first multicast session, which is a multicast session that the UE has joined or requested to join.

[0433] Optionally, the execution unit includes:

[0434] The first determining module is used to determine the first network function entity serving the first multicast session, wherein the first network function entity includes: Session Management Function (SMF) or Multicast Broadcast Session Management Function (MB-SMF);

[0435] A first sending module is configured to send a second request to the first network function entity, wherein the second request carries the multicast session information.

[0436] The first receiving module is used to receive a response message to the second request sent by the first network function entity.

[0437] Optionally, the first receiving unit includes:

[0438] The second receiving module is used to receive a response message sent by the first network function entity, which carries the first multicast session identifier and resource allocation request information as a second request.

[0439] The device also includes:

[0440] The first sending unit is configured to send a third request to a Radio Access Network Function (RAF) entity based on the response message of the second request. The third request carries a first multicast session identifier and the resource allocation request information, so that the RAF entity can establish or update the resources of the first multicast session.

[0441] Optionally, the response message to the second request carries a first multicast session identifier and the following information:

[0442] Information instructing the UE to leave the first multicast session; or,

[0443] The UE is denied the right to join the first multicast session.

[0444] Optionally, the device further includes:

[0445] The second sending unit is configured to send a third request to a Radio Access Network Function (RAF) entity, the third request carrying a first multicast session identifier and information instructing the UE to leave the first multicast session, so that the RAF entity removes the UE's identifier from the context of the first multicast session.

[0446] Optionally, the multicast session information further includes at least one of the following identification information:

[0447] The identifier of the Protocol Data Unit (PDU) session associated with the first multicast session;

[0448] The identifier of the MB-SMF serving the first multicast session and / or the identifier of the SMF;

[0449] The determination of the first network function entity serving the first multicast session includes:

[0450] Based on the at least one identification information, a first network function entity serving the first multicast session is determined.

[0451] It should be noted that the multicast session processing apparatus provided in this embodiment of the invention can implement all the method steps implemented in the multicast session processing method embodiment with the first AMF as the execution subject, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0452] Figure 12 This is a second schematic diagram of the multicast session processing device provided in the embodiments of this application, as shown below. Figure 12 As shown in the figure, this application provides a multicast session processing apparatus, which includes:

[0453] The second receiving unit 1201 is used to receive a second request sent by the first AMF. The second request carries multicast session information of the user equipment UE. The multicast session information is obtained by the first AMF after receiving the first request sent by the UE. The first request is a registration request message or a service request message.

[0454] The first processing unit 1202 is used to process the multicast session of the UE according to the multicast session information carried in the second request.

[0455] Optionally, the multicast session information includes a first multicast session identifier and / or indication information, wherein the indication information is used to instruct the UE to remain in the first multicast session, which is a multicast session that the UE has joined or requested to join.

[0456] Optionally, the first processing unit includes:

[0457] The first establishment module is configured to establish a correspondence between the UE's identifier and the first multicast session identifier if the indication information is used to instruct the UE to request to join the first multicast session, and it is determined that the UE's joining the first multicast session is accepted;

[0458] The second sending module is used to send a response message of the second request to the first AMF, wherein the response message of the second request carries information accepting the UE to join the first multicast session;

[0459] or,

[0460] The third sending module is configured to send a response message of a second request to the first AMF if the indication information is used to instruct the UE to request to join the first multicast session and the UE is not within the service area of ​​the first multicast session. The response message of the second request carries information that the UE is refused to join the first multicast session.

[0461] or,

[0462] The fourth sending module is configured to send a response message of a second request to the first AMF if the indication information is used to instruct the UE to remain in the first multicast session and the UE is not within the service area of ​​the first multicast session. The response message of the second request carries information instructing the UE to leave the first multicast session.

[0463] or,

[0464] The first deletion module is used to delete the correspondence between the UE's identifier and the first multicast session identifier if the indication information is used to instruct the UE to leave the first multicast session.

[0465] Optionally, the first processing unit includes:

[0466] The first storage module is configured to store the identifier of the UE's radio access network function entity in the context of the first multicast session if the indication information is used to instruct the UE to request to join the first multicast session and it is determined that the UE's joining the first multicast session is accepted.

[0467] It should be noted that the multicast session processing apparatus provided in this embodiment of the invention can implement all the method steps implemented in the multicast session processing method embodiment with SMF as the execution subject, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0468] Figure 13 This is the third schematic diagram of the multicast session processing device provided in the embodiments of this application, as shown below. Figure 13 As shown in the figure, this application provides a multicast session processing apparatus, which includes:

[0469] The third sending unit 1301 is used to send a first request to the first AMF, wherein the first request is a service request message or a registration request message.

[0470] The third receiving unit 1302 is used to receive a response message of the first request sent by the first AMF. The response message of the first request is a registration acceptance message or a service acceptance message. The response message of the first request includes information on accepting the UE to join or leave the first multicast session, or information on instructing the UE to leave the first multicast session, or information on rejecting the UE to join the first multicast session.

[0471] The second processing unit 1303 is used to process the first multicast session according to the response message of the first request.

[0472] Optionally, the first request carries multicast session information, which includes a first multicast session identifier and indication information. The first multicast session is a multicast session that the UE has joined or a multicast session that it has requested to join. The indication information is used to instruct the UE to remain in the first multicast session, whether it has joined, left, or requested to join.

[0473] Optionally, the second processing unit includes:

[0474] The second storage module is used to store the context of the first multicast session if the response message of the first request carries information accepting the UE to join the first multicast session;

[0475] The second deletion module is used to delete the context of the first multicast session if the response message of the first request carries information that the UE is refused to join the first multicast session.

[0476] Optionally, the third receiving unit includes:

[0477] The third receiving module is used to receive the response message of the first request sent by the first AMF and forwarded by the radio access network function entity;

[0478] The device further includes:

[0479] The establishment unit is configured to establish or update the resources of the first multicast session if the response message of the first request carries information accepting the UE to join the first multicast session;

[0480] The fourth receiving unit is used to receive service data of the first multicast session using the resources.

[0481] Optionally, the fourth receiving unit includes:

[0482] The fourth receiving module is used to receive service data of the first multicast session via unicast using the resources if the wireless access network function entity does not support multicast services.

[0483] The fifth receiving module is used to receive service data of the first multicast session via multicast if the wireless access network function entity supports multicast services, using the resources.

[0484] It should be noted that the multicast session processing apparatus provided in this embodiment of the invention can implement all the method steps implemented in the multicast session processing method embodiment with UE as the execution subject, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0485] It should be noted that the division of units / modules in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units / modules in the various embodiments of this application can be integrated into one processing unit / module, or each unit / module can exist physically separately, or two or more units / modules can be integrated into one unit / module. The integrated units / modules described above can be implemented in hardware or as software functional units.

[0486] If the integrated unit / module is implemented as a software functional unit / module and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0487] On the other hand, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing the processor to execute the multicast session processing method provided in the above embodiments, including:

[0488] Receive a first request sent by a user equipment (UE), wherein the first request is a registration request message or a service request message;

[0489] Obtain the multicast session information of the UE according to the first request;

[0490] Based on the multicast session information, perform processing operations related to the multicast session.

[0491] Or, including:

[0492] The system receives a second request sent by a first AMF, the second request carrying multicast session information of a user equipment (UE). The multicast session information is obtained by the first AMF after receiving the first request sent by the UE. The first request is a registration request message or a service request message.

[0493] The multicast session of the UE is processed according to the multicast session information carried in the second request.

[0494] Or, including:

[0495] Send a first request to the first AMF, wherein the first request is a service request message or a registration request message;

[0496] Receive a response message to the first request sent by the first AMF. The response message to the first request is a registration acceptance message or a service acceptance message. The response message to the first request contains information to accept the UE joining or leaving the first multicast session, or information to instruct the UE to leave the first multicast session, or information to refuse the UE from joining the first multicast session.

[0497] The first multicast session is processed based on the response message of the first request.

[0498] It should be noted that the processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0499] Additionally, it should be noted that the term "and / or" in the embodiments of this application describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A existing alone, A and B existing simultaneously, and B existing alone. The character " / " generally indicates that the related objects before and after it have an "or" relationship.

[0500] The terms "first," "second," "target," etc., used in the specification and claims of this application are used to distinguish similar objects and are not used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," "target," etc., are generally of the same class and are not limited in number; for example, a first object can be one or more.

[0501] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0502] The technical solutions provided in this application can be applied to various systems, especially 5G systems. For example, applicable systems include Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Long Term Evolution Advanced (LTE-A), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), and 5G New Radio (NR). All of these systems include terminal equipment and network equipment. The systems may also include a core network component, such as Evolved Packet System (EPS) and 5G system (5GS).

[0503] The terminal devices involved in the embodiments of this application can be devices that provide voice and / or data connectivity to users, handheld devices with wireless connectivity, or other processing devices connected to a wireless modem. The names of the terminal devices may differ in different systems; for example, in a 5G system, a terminal device can be called User Equipment (UE). Wireless terminal devices can communicate with one or more core networks (CNs) via a Radio Access Network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, for example, portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the RAN. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device, but is not limited to these terms in the embodiments of this application.

[0504] The network device involved in this application embodiment can be a base station, which may include multiple cells providing services to terminals. Depending on the specific application, a base station may also be called an access point, or a device in an access network that communicates with a wireless terminal device through one or more sectors on the air interface, or other names. The network device can be used to exchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network device can also coordinate the attribute management of the air interface. For example, the network equipment involved in the embodiments of this application can be a base transceiver station (BTS) in a Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), a NodeB in a Wide-band Code Division Multiple Access (WCDMA) system, an evolved Node B (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a next generation system, a Home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of this application. In some network structures, the network equipment may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and distributed unit may be geographically separated.

[0505] Network devices and terminal devices can each use one or more antennas for Multiple Input Multiple Output (MIMO) transmission. MIMO transmission can be Single User MIMO (SU-MIMO) or Multiple User MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, and can also be diversity transmission, precoding transmission, or beamforming transmission, etc.

[0506] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0507] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0508] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0509] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0510] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A multicast session processing method, characterized in that, Applied to UE, including: Send a first request to the first AMF. The first request is a service request message or a registration request message. The first request carries multicast session information. The multicast session information is used to instruct the UE to keep joining the first multicast session, and the first multicast session is a multicast session that the UE has already joined. Receive a response message to the first request sent by the first AMF. The response message to the first request is a registration acceptance message or a service acceptance message. The response message to the first request includes information that the UE is accepted to keep joining the first multicast session. The first multicast session is processed based on the response message of the first request.

2. The multicast session processing method according to claim 1, characterized in that, The step of processing the first multicast session according to the response message of the first request includes: If the response message of the first request carries information accepting that the UE will remain in the first multicast session, then the context of the first multicast session is updated.

3. The multicast session processing method according to claim 1, characterized in that, The response message received from the first AMF for the first request includes: Receive the response message of the first request sent by the first AMF and forwarded by the Radio Access Network Function Entity; The method further includes: If the response message of the first request carries information accepting the UE to remain in the first multicast session, then update the resources of the first multicast session; The resources are used to receive service data from the first multicast session.

4. The multicast session processing method according to claim 3, characterized in that, The step of receiving service data from the first multicast session using the resources includes: If the wireless access network function entity does not support multicast services, then the resources are used to receive the service data of the first multicast session via unicast. If the wireless access network function entity supports multicast services, then the resources are used to receive the service data of the first multicast session via multicast.

5. A user equipment (UE), characterized in that, Includes memory, transceiver, and processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: Send a first request to the first AMF. The first request is a service request message or a registration request message. The first request carries multicast session information. The multicast session information is used to instruct the UE to keep joining the first multicast session, and the first multicast session is a multicast session that the UE has already joined. Receive a response message to the first request sent by the first AMF. The response message to the first request is a registration acceptance message or a service acceptance message. The response message to the first request includes information that the UE is accepted to keep joining the first multicast session. The first multicast session is processed based on the response message of the first request.

6. The User Equipment (UE) according to claim 5, characterized in that, The step of processing the first multicast session according to the response message of the first request includes: If the response message of the first request carries information accepting the UE to join the first multicast session, then the context of the first multicast session is stored.

7. The User Equipment (UE) according to claim 5, characterized in that, The response message received from the first AMF for the first request includes: Receive the response message of the first request sent by the first AMF and forwarded by the Radio Access Network Function Entity; The processor is also configured to read the computer program in the memory and perform the following operations: If the response message of the first request carries information accepting the UE to join the first multicast session, then the resources of the first multicast session are established or updated. The resources are used to receive service data from the first multicast session.

8. The User Equipment (UE) according to claim 7, characterized in that, The step of receiving service data from the first multicast session using the resources includes: If the wireless access network function entity does not support multicast services, then the resources are used to receive the service data of the first multicast session via unicast. If the wireless access network function entity supports multicast services, then the resources are used to receive the service data of the first multicast session via multicast.

9. A multicast session processing apparatus, characterized in that, include: The third sending unit is used to send a first request to the first AMF. The first request is a service request message or a registration request message. The first request carries multicast session information. The multicast session information is used to instruct the UE to keep joining the first multicast session, and the first multicast session is a multicast session that the UE has already joined. The third receiving unit is used to receive the response message of the first request sent by the first AMF. The response message of the first request is a registration acceptance message or a service acceptance message. The response message of the first request includes information that the UE is accepted to keep joining the first multicast session. The second processing unit is used to process the first multicast session according to the response message of the first request.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that causes the processor to perform the method according to any one of claims 1 to 4.

Images