WO2023000884A1 - 多播会话处理方法、网络功能实体、装置及存储介质 - Google Patents

多播会话处理方法、网络功能实体、装置及存储介质 Download PDF

Info

Publication number
WO2023000884A1
WO2023000884A1 PCT/CN2022/099440 CN2022099440W WO2023000884A1 WO 2023000884 A1 WO2023000884 A1 WO 2023000884A1 CN 2022099440 W CN2022099440 W CN 2022099440W WO 2023000884 A1 WO2023000884 A1 WO 2023000884A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast session
request
information
multicast
session
Prior art date
Application number
PCT/CN2022/099440
Other languages
English (en)
French (fr)
Inventor
段小嫣
Original Assignee
大唐移动通信设备有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 大唐移动通信设备有限公司 filed Critical 大唐移动通信设备有限公司
Priority to EP22845050.8A priority Critical patent/EP4376539A1/en
Publication of WO2023000884A1 publication Critical patent/WO2023000884A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the present application relates to the technical field of communication, and in particular to a method for processing a multicast session, a network function entity, a device, and a storage medium.
  • User equipment needs to receive specific multicast service data by joining a multicast session.
  • the radio access network RAN node serving the user equipment or even the core network CN When the node changes, the user equipment needs to complete the registration update or service request process first, and then initiate the PDU session modification process before receiving the data of the multicast session or leaving the joined multicast session.
  • UE User Equipment
  • the user equipment needs to perform more signaling interactions with the network to receive the data of the multicast session or to leave the joined multicast session, resulting in waste of resources and low efficiency.
  • the embodiment of the present application provides a multicast session processing method, network functional entity, device, and storage medium to solve the problem that in the prior art, the user equipment needs to perform more signaling interactions with the network to receive the data of the multicast session or to leave The defect of the multicast session that has been joined improves signaling efficiency and saves signaling resources.
  • the embodiment of the present application provides a method for processing a multicast session, which is applied in the first AMF, including:
  • the multicast session information perform processing operations related to the multicast session.
  • the acquiring the multicast session information of the UE according to the first request includes:
  • the acquiring the multicast session information of the UE according to the first request includes:
  • the second AMF is a network function entity that provides services for the UE before the UE moves;
  • the first AMF A network function entity that provides services for the UE after the UE moves.
  • the multicast session information includes a first multicast session identifier and/or indication information, where the indication information is used to instruct the UE to keep joining, leave or request to join the first multicast session, the
  • the first multicast session is a multicast session that the UE has joined or a multicast session that the UE has requested to join.
  • the performing a processing operation related to the multicast session according to the multicast session information includes:
  • the first network function entity includes: a session management function SMF or a multicast broadcast session management function MB-SMF;
  • the receiving the response message of the second request sent by the first network function entity includes:
  • the method also includes:
  • the radio access network functional entity According to the response message of the second request, send a third request to the radio access network functional entity, where the third request carries the first multicast session identifier and the resource allocation request information, so that the radio access A network function entity establishes or updates resources of the first multicast session.
  • the response message of the second request carries the first multicast session identifier and the following information:
  • the method also includes:
  • the radio access network function entity sends a third request to a radio access network function entity, where the third request carries the first multicast session identifier and information instructing the UE to leave the first multicast session, so that the radio access network function
  • the entity removes the identity of the UE from the context of the first multicast session.
  • the multicast session information also includes at least one of the following identification information:
  • the determining the first network function entity serving the first multicast session includes:
  • the embodiment of the present application also provides a multicast session processing method applied to SMF, including:
  • the second request carries multicast session information of the user equipment UE, and the multicast session information is obtained after the first AMF receives the first request sent by the UE obtained, the first request is a registration request message or a service request message;
  • the multicast session information includes a first multicast session identifier and/or indication information, where the indication information is used to instruct the UE to keep joining, leave or request to join the first multicast session, the
  • the first multicast session is a multicast session that the UE has joined or a multicast session that the UE has requested to join.
  • processing the multicast session of the UE according to the multicast session information carried in the second request includes:
  • the indication information is used to indicate that the UE requests to join the first multicast session, and it is determined to accept the UE to join the first multicast session, establish the identity of the UE and the first multicast session Correspondence between session identifiers; sending a second request response message to the first AMF, where the second request response message carries information for accepting the UE to join the first multicast session; or,
  • the indication information is used to indicate that the UE requests to join the first multicast session, and the UE is not in the service area of the first multicast session, send the second request to the first AMF A response message, where the response message of the second request carries information denying the UE to join the first multicast session; or,
  • the indication information is used to instruct the UE to keep joining the first multicast session, and the UE is not in the service area of the first multicast session, send the second request to the first AMF A response message, the response message of the second request carries information indicating that the UE leaves the first multicast session; or,
  • the indication information is used to instruct the UE to leave the first multicast session, delete the correspondence between the identifier of the UE and the identifier of the first multicast session.
  • processing the multicast session of the UE according to the multicast session information carried in the second request includes:
  • the indication information is used to indicate that the UE requests to join the first multicast session, and it is determined to accept the UE to join the first multicast session, store the service in the context of the first multicast session An identifier of a radio access network functional entity for the UE.
  • the embodiment of the present application also provides a method for processing a multicast session, including:
  • 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 accepting UE joining or leaving the first request Information about a multicast session, or information indicating that the UE leaves the first multicast session, or information that refuses the UE to join the first multicast session;
  • the first request carries multicast session information
  • the multicast session information 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 requested to join, where the indication information is used to instruct the UE to keep joining, leave or request to join the first multicast session.
  • processing the first multicast session according to the response message of the first request includes:
  • response message of the first request carries the information of accepting the UE to join the first multicast session, storing the context of the first multicast session;
  • the response message of the first request carries information denying the UE to join the first multicast session or instructing the UE to leave the first multicast session, delete the context of the first multicast session .
  • the receiving a response message of the first request sent by the first AMF includes:
  • the method also includes:
  • response message of the first request carries the information of accepting the UE to join the first multicast session, establishing or updating the resource of the first multicast session;
  • the receiving service data of the first multicast session by using the resource includes:
  • radio access network functional entity does not support multicast services, use the resources to receive service data of the first multicast session in a unicast manner;
  • the radio access network functional entity supports multicast services, use the resources to receive service data of the first multicast session in a multicast manner.
  • the embodiment of the present application also provides an AMF network functional entity, including a memory, a transceiver, and a processor:
  • the memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:
  • the multicast session information perform processing operations related to the multicast session.
  • the acquiring the multicast session information of the UE according to the first request includes:
  • the second AMF is a network function entity that provides services for the UE before the UE moves.
  • the performing a processing operation related to the multicast session according to the multicast session information includes:
  • the first network function entity includes: a session management function SMF or a multicast broadcast session management function MB-SMF;
  • the receiving the response message of the second request sent by the first network function entity includes:
  • the processor is also configured to read a computer program in the memory and perform the following operations:
  • the radio access network functional entity According to the response message of the second request, send a third request to the radio access network functional entity, where the third request carries the first multicast session identifier and the resource allocation request information, so that the radio access A network function entity establishes or updates resources of the first multicast session.
  • the embodiment of the present application also provides an SMF network function entity, including a memory, a transceiver, and a processor:
  • the memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:
  • the second request carries multicast session information of the user equipment UE, and the multicast session information is obtained after the first AMF receives the first request sent by the UE obtained, the first request is a registration request message or a service request message;
  • the embodiment of the present application further provides a user equipment UE, including a memory, a transceiver, and a processor:
  • the memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:
  • 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 accepting UE joining or leaving the first request Information about a multicast session, or information indicating that the UE leaves the first multicast session, or information that refuses the UE to join the first multicast session;
  • the first request carries multicast session information
  • the multicast session information 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 requested to join, where the indication information is used to instruct the UE to keep joining, leave or request to join the first multicast session.
  • processing the first multicast session according to the response message of the first request includes:
  • response message of the first request carries the information of accepting the UE to join the first multicast session, storing the context of the first multicast session;
  • the response message of the first request carries information denying the UE to join the first multicast session or instructing the UE to leave the first multicast session, delete the context of the first multicast session .
  • the receiving a response message of the first request sent by the first AMF includes:
  • the processor is also configured to read a computer program in the memory and perform the following operations:
  • response message of the first request carries the information of accepting the UE to join the first multicast session, establishing or updating the resource of the first multicast session;
  • the receiving service data of the first multicast session by using the resource includes:
  • radio access network functional entity does not support multicast services, use the resources to receive service data of the first multicast session in a unicast manner;
  • the radio access network functional entity supports multicast services, use the resources to receive service data of the first multicast session in a multicast manner.
  • the embodiment of the present application further provides a device for processing a multicast session, including:
  • the first receiving unit is configured to receive a first request sent by the user equipment UE, where the first request is a registration request message or a service request message;
  • a first acquiring unit configured to acquire multicast session information of the UE according to the first request
  • An executing unit configured to execute processing operations related to the multicast session according to the multicast session information.
  • the embodiment of the present application also provides a multicast session processing device
  • the second receiving unit is configured to receive a second request sent by the first AMF, where the second request carries multicast session information of the user equipment UE, and the multicast session information is obtained by the first AMF after receiving the Obtained after the first request sent by the UE, where the first request is a registration request message or a service request message;
  • the first processing unit is configured to process the multicast session of the UE according to the multicast session information carried in the second request.
  • the embodiment of the present application also provides a multicast session processing device
  • a third sending unit configured to send a first request to the first AMF, where the first request is a service request message or a registration request message;
  • a third receiving unit configured to receive a response message to the first request sent by the first AMF, where the response message to the first request is a registration acceptance message or a service acceptance message, and in the response message to the first request Containing information for accepting the UE to join or leave the first multicast session, or information for instructing the UE to leave the first multicast session, or information for refusing the UE to join the first multicast session;
  • the second processing unit is configured to process the first multicast session according to the response message of the first request.
  • the embodiment of the present application further provides a processor-readable storage medium, the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the above-mentioned first aspect. 1.
  • the embodiment of the present application further provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and the computer program is used to make the processor perform the above-mentioned first aspect, the first aspect The steps of the multicast session processing method described in the second aspect and the third aspect.
  • the multicast session processing method, network functional entity, device, and storage medium realize the synchronization of the multicast session state between the user equipment UE and the network through a registration request or a service request, reducing the time required for the UE to process multicast session services.
  • the required signaling interaction improves signaling efficiency, saves signaling resources, and shortens the time for UEs to join or leave a multicast session and receive or transmit multicast session data.
  • FIG. 1 is a schematic flow diagram of a UE joining a multicast session provided by the prior art
  • FIG. 2 is one of the schematic flow charts of the multicast session processing method provided by the embodiment of the present application.
  • FIG. 3 is the second schematic flow diagram of the multicast session processing method provided by the embodiment of the present application.
  • FIG. 4 is the third schematic flow diagram of the multicast session processing method provided by the embodiment of the present application.
  • FIG. 5 is a fourth schematic flow diagram of a method for processing a multicast session provided by an embodiment of the present application.
  • FIG. 6 is the fifth schematic flow diagram of the multicast session processing method provided by the embodiment of the present application.
  • FIG. 7 is the sixth schematic flow diagram of the multicast session processing method provided by the embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of an AMF network functional entity provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of an SMF network functional entity provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a user equipment UE provided by an embodiment of the present application.
  • FIG. 11 is one of the structural schematic diagrams of a device for processing a multicast session provided by an embodiment of the present application.
  • Fig. 12 is the second structural schematic diagram of the multicast session processing device provided by the embodiment of the present application.
  • FIG. 13 is a third structural schematic diagram of a device for processing a multicast session provided by an embodiment of the present application.
  • the data set transmission methods adopted in the Internet Protocol (Internet Protocol, IP) network include unicast, multicast and broadcast.
  • Multicast/Broadcast refers to "one-to-many communication", that is, the same data is sent from one sending device to multiple receiving devices through technologies such as shared channel and content replication. Compared with unicast, multicast/broadcast is more efficient in the use of network resources.
  • the 5th generation mobile communication system is a new generation of wireless mobile communication system following the 4th generation mobile communication system (4G system), providing greater transmission Bandwidth, support more terminal numbers and more business types.
  • 5GS supports unicast transmission.
  • IPv4/IPv6 multicast/broadcast interactive IP TV
  • existing services such as group communication, Internet of Things communication (Internet of Things, IoT), vehicle network communication (vehicle to everything, V2X ), software download/update, etc.
  • 5GS will support multicast and broadcast services (5G Multicast Broadcast Service, 5G MBS).
  • User equipment UE needs to receive specific multicast service data by joining a multicast session.
  • the UE requests to join a specific multicast session through a protocol data unit (Protocol Data Unit, PDU) session modification process, and a core network (Core Network, CN) network functional entity, such as a session management function (Session Management Function, SMF) ), multicast broadcast session management function (Multicast Broadcast Session Management Function, MB-SMF), based on the request, UE is added to the multicast session, and a core network gateway is established, such as multicast broadcast user plane function (Multicast Broadcast User Plane Function , MB-UPF) and the multicast transmission tunnel between the wireless access network (Wireless Access Network, RAN), so as to send the data of the multicast session to the UE.
  • a protocol data unit Protocol Data Unit
  • PDU Protocol Data Unit
  • Core Network, CN Core Network
  • SMF Session Management Function
  • MB-SMF multicast Broadcast Session Management Function
  • Fig. 1 is a schematic flow diagram of a UE joining a multicast session provided by the prior art.
  • the UE is in the idle state, that is, no signaling connection and data bearer have been established between the UE and the RAN node, or in an inactive state, that is, There is no signaling connection and data bearer established between the UE and the CN.
  • the RAN node serving the UE or even the CN node of the core network such as the Access and Mobility Management Function (AMF) changes, due to the new
  • AMF Access and Mobility Management Function
  • the UE needs to first enter the connected state through the registration update or service request process, and then initiate a PDU
  • the session modification process requests to join or leave a previously joined multicast session.
  • the network needs to page the UE because the UE is in the idle state or inactive state, and the UE responds to the paging through the service request or registration update process, and then: the UE initiates The PDU session modification process requests to join or leave the previously joined multicast session, or the CN directly initiates the multicast session establishment process to the UE, and the UE accepts or rejects it.
  • the UE in the idle (IDLE) state or inactive state changes the network node it accesses, it needs to perform more signaling interactions with the network, first complete the registration update or service request process, and then initiate the PDU session modification process.
  • the multicast session including the data of the previously joined multicast session, can only be received after the aforementioned steps are completed, or leave the multicast session, that is, stop accepting paging messages and data related to the multicast session.
  • embodiments of the present application provide a multicast session processing method, network functional entity, device, and storage medium.
  • Fig. 2 is one of the flow diagrams of the multicast session processing method provided by the embodiment of the present application.
  • the embodiment of the present application provides a multicast session processing method, the execution subject of which is the first AMF, and the method includes :
  • Step 201 Receive a first request sent by a user equipment UE, where the first request is a registration request message or a service request message.
  • the first AMF receives a registration request message or a service request message sent by the user equipment UE.
  • the UE Under certain conditions, such as moving to a new registration area (Registration Area), requesting to update UE capabilities or requesting network information, the UE sends a Registration Request (Registration Request) message to the network to request registration update; or sends a service request (Service Request) ) message requesting service update.
  • Registration Request Registration Request
  • Service Request Service Request
  • the UE in the IDLE state or CONNECTED state updates to the registration area through mobility registration, or when the UE initially registers with the 5G system; or when the UE initiates periodic registration; or when the UE needs to update the capabilities and protocol parameters negotiated through the registration process, initiate Registration Request Process.
  • the UE in the IDLE state is mainly for sending uplink signaling messages, user data, or responding to a network paging request to initiate a service request process.
  • the AMF can perform identity verification.
  • the UE or the network can send a signaling message, such as a PDU session establishment request from the UE to the SMF via the AMF.
  • the AMF serving the UE may change.
  • the first AMF here may be a network function entity serving the UE after the UE moves.
  • Step 202 Acquire the multicast session information of the UE according to the first request.
  • the multicast session information of the UE is acquired according to the first request.
  • the first request when the UE sends the first request, the first request carries the multicast session information of the UE, then the first AMF can directly obtain the multicast session information of the UE from the first request.
  • the UE when the AMF serving the UE changes due to UE movement, the UE sends a first request to the changed first AMF.
  • the first request may be a registration request, requesting to update UE capabilities or request network information.
  • the first AMF will determine the second AMF serving the UE before the UE moves according to the first request, and obtain the UE context from the second AMF, and the second AMF will carry the UE context in the returned UE context Multicast session information.
  • the first AMF sends a UE context (UE Context) request to other network function entities providing services for the UE, so as to acquire multicast session information of the UE.
  • the network function entity that provides services for the UE may be the AMF serving the UE before the UE moves, that is, the second AMF, or it may be a unified data management function (Unified Data Management, UDM), and the network function entity provides the UE with the first AMF.
  • UDM Unified Data Management
  • the UE context carries the multicast session information (Multicast Session Message) that the UE has joined.
  • the first request when the UE sends the first request, the first request carries multicast session information, and at the same time, the AMF serving the UE changes due to the movement of the UE, and the first AMF requests the second AMF or UDM for the UE context , and the UE context returned by the second AMF or UDM carries the multicast session information that the UE has joined. If the UE does not request to join a new multicast session, the multicast session information in the UE context may be consistent with the multicast session information carried in the first request.
  • the first AMF may obtain the multicast session information of the UE in the first request, and the first AMF may also obtain the multicast session information of the UE from the UE context response message of the second AMF or UDM.
  • the multicast session information carried in the UE context is the multicast session information that the UE has joined, and the first request carries the multicast session information that the UE requests to join.
  • the first AMF determines to obtain complete multicast session information of the UE according to the first request and the UE context.
  • Step 203 Perform processing operations related to the multicast session according to the multicast session information.
  • processing operations related to the multicast session are performed according to the multicast session information.
  • the first AMF After the first AMF acquires the multicast session information of the UE, it executes the subsequent registration request process or service request process, and completes the processing of the multicast session service synchronously.
  • Services related to the multicast session include receiving/transmitting multicast session data, instructing the UE to leave/join the multicast session, and so on.
  • the first AMF after receiving the first request sent by the UE, the first AMF sends a response message of the first request to the UE.
  • the response message of the first request is a registration acceptance message or a service acceptance message, and includes:
  • the response message of the first request includes the information that the UE keeps joining the first multicast session; the UE updates the information of the first multicast session according to the response message of the first request. context;
  • the response message of the first request includes information indicating that the UE leaves the first multicast session; the UE deletes the context of the first multicast session according to the response message of the first request ;
  • the response message of the first request includes information indicating that the UE leaves the first multicast session; the UE deletes the context of the first multicast session according to the response message of the first request;
  • the response message of the first request includes the information of accepting the UE to join the first multicast session; the UE generates the context of the first multicast session according to the response message of the first request;
  • the response message of the first request includes the information of rejecting the UE to join the first multicast session; the UE determines not to join the first multicast session according to the response message of the first request.
  • the multicast session processing method provided by the embodiment of the present application realizes the synchronization of the multicast session state between the user equipment UE and the network through a registration request or a service request, reduces the signaling interaction required by the UE to process the multicast session service, and improves the signal quality. Signaling efficiency is saved, signaling resources are saved, and the time for UEs to join or leave a multicast session and receive or transmit multicast session data is shortened.
  • the acquiring the multicast session information of the UE according to the first request includes:
  • the multicast session information of the UE carried in the first request includes at least one of the following:
  • MBS session ID Multicast Broadcast Session Identity, MBS session ID
  • MBS session ID Multicast Broadcast Session Identity
  • Network Function Network Function, NF
  • MB-SMF ID Information of the network function serving the multicast session
  • the join request indication For a new multicast session requested by the UE to join, the join request indication and the data network name (Data Network Name, DNN) corresponding to the multicast session and/or Single Network Slice Selection Assistance Information (Single Network Slice Selection Assistance Information, S-NSSAI).
  • DNN Data Network Name
  • S-NSSAI Single Network Slice Selection Assistance Information
  • the multicast session information carried in the first request includes ID1.
  • the multicast session corresponding to ID1 is the multicast session that the UE keeps joining.
  • the first request will also carry a multicast session status indicator, which can be 1, indicating that the UE is still joining the session ID1; or 0, indicating that the UE is leaving the session ID1.
  • the multicast session information carried in the first request also includes ID2.
  • the multicast session corresponding to ID2 is a multicast session requested by the UE to join.
  • the DNN and S-NSSAI corresponding to the multicast session will also be carried in the first request, so that the network side can determine whether the UE is allowed to join the session ID2 according to the DNN and S-NSSAI.
  • the acquiring the multicast session information of the UE according to the first request includes:
  • the second AMF is an AMF that provides services for the UE before the UE moves;
  • the first AMF is the An AMF that provides services for the UE after the UE moves.
  • the first AMF determines the second AMF serving the UE before the UE moves according to the UE identifier, and sends a UE context transfer request to the second AMF.
  • the second AMF sends a response message of the UE context transmission request to the first AMF, where the response message carries the UE context, so that the first AMF can obtain the multicast session information of the UE.
  • the UE context contains at least one of the following information:
  • the PDU session information includes: the PDU session identifier, the information of the SMF serving the PDU session; for the PDU session associated with the multicast session, the PDU session information also includes the The ID of the multicast session.
  • the multicast session information includes a first multicast session identifier and/or indication information, where the indication information is used to instruct the UE to keep joining, leave or request to join the first multicast session, the
  • the first multicast session is a multicast session that the UE has joined or a multicast session that the UE has requested to join.
  • the multicast session information of the UE includes the first multicast session identifier and/or indication information.
  • the multicast session information of the UE includes one or more first multicast session identifiers.
  • the first multicast session is a multicast session that the UE has already joined; when the UE requests to join a new multicast session, the first multicast session may be a multicast session that the UE requests to join The session may also be a multicast session that the UE has joined and a multicast session that the UE requests to join.
  • the multicast session information of the UE includes the multicast session identifier and indication information.
  • the indication information is used to instruct the UE to request to join a new multicast session, or to instruct the UE to keep joining the already joined multicast session, or to instruct the UE to leave the already joined multicast session.
  • the multicast session information of the UE may not include an indication that the UE keeps joining the multicast session information, do not process the multicast session.
  • the performing a processing operation related to the multicast session according to the multicast session information includes:
  • the first network function entity includes: a session management function SMF or a multicast broadcast session management function MB-SMF;
  • the first AMF determines the SMF or MB-SMF serving the first multicast session, sends a second request to the SMF or MB-SMF for the multicast session, and the second request carries the multicast session information of the UE, Then receive the response message of SMF or MB-SMF.
  • the second request is used for requesting to update the multicast session information.
  • the first AMF determines the PDU session associated with the first multicast session and the SMF serving the PDU session according to the multicast session information and/or the UE context.
  • the first AMF sends a PDU session update management context request to the SMF
  • the PDU session update management context request carries multicast session information, and may also carry UE location information, such as the cell ID (Cell ID) where the UE is located or the tracking area identifier TAI.
  • Cell ID the cell ID
  • TAI tracking area identifier
  • the SMF requests the MB-SMF to update the multicast session information, and the request message may carry the AMF identifier and the RAN node identifier.
  • MB-SMF updates the AMF ID and RAN node ID into the multicast session context.
  • MB-SMF sends a response message of multicast session information update to SMF, the response message includes MBS Session ID and at least one of the following information:
  • QoS Quality of Service
  • Down Link Tunnel ID Down Link Tunnel ID
  • Multicast Address etc.
  • the SMF updates the multicast session information and the PDU session information associated with the multicast session according to the MB-SMF response, for example: if the QoS rules and/or QoS parameters of the multicast QoS Flow (QoS Flow) change, Correspondingly update the QoS rules and/or QoS parameters of the mapped unicast QoS Flow.
  • the SMF sends a PDU session update management context request response message to the first AMF.
  • the first AMF sends a multicast session update request to the MB-SMF indicated by the MB-SMF ID, and the request message carries the MBS Session ID and the RAN node identifier, RAN tunnel information may also be included.
  • 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.
  • the MB-SMF sends a multicast session request response message to the first AMF.
  • the receiving the response message of the second request sent by the first network function entity includes:
  • the method also includes:
  • the radio access network functional entity According to the response message of the second request, send a third request to the radio access network functional entity, where the third request carries the first multicast session identifier and the resource allocation request information, so that the radio access A network function entity establishes or updates resources of the first multicast session.
  • the first AMF receives the response message of the second request sent by the first network function entity, and the response message of the second request carries the first multicast session identifier and resource allocation request information; according to the response message of the second request, A third request is sent to the RAN for establishing or updating resources of the first multicast session.
  • the SMF sends a PDU session update session management context response message to the first AMF, the response message carries the MBS Session ID, the MB-SMF ID, and is carried in the N2 information to the RAN
  • the information of the multicast session includes MBS Session ID, information of the associated PDU session and at least one of the following information: QoS information; common downlink tunnel ID (Common Down Link Tunnel ID); multicast address (Multicast Address), etc.
  • the SMF can judge whether the UE is currently in the service area of the first multicast session according to the location information of the UE and the service area of the first multicast session.
  • the SMF requires the UE to leave the first multicast session, that is, a PDU session modification indication message is carried in the response message to the first AMF, and the indication message carries the first multicast session
  • a PDU session modification indication message is carried in the response message to the first AMF, and the indication message carries the first multicast session
  • the SMF updates the information of the PDU session associated with the first multicast session, that is, deletes the MBS Session ID and the mapped unicast QoS information from the PDU session context; if the SMF saves the list of UEs joining the first multicast session, SMF deletes the UE ID from the UE list;
  • the MB-SMF ID is not carried in the response message sent by the SMF to the first AMF, and the information of the first multicast session is not carried in the N2 information sent to the RAN.
  • 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.
  • the MB-SMF sends a multicast session information update request response message to the AMF, which carries the multicast session information provided to the RAN, including the MBS Session ID and at least one of the following:
  • the first AMF sends the above-mentioned multicast session information provided to the RAN to the RAN through the N2 interface, and the RAN sends a resource allocation request message to the UE. resources for the session; in case the resources for the first multicast session have been established, updating the resources for the first multicast session.
  • the UE uses the resources of the first multicast session to receive service data of the first multicast session in a multicast manner.
  • the UE uses the resources of the first multicast session to receive service data of the first multicast session in a unicast manner.
  • the response message of the second request carries the first multicast session identifier and the following information:
  • the response message of the second request sent by the first network functional entity to the first AMF carries the identifier of the first multicast session and information indicating that the UE leaves or refuses the UE to join the first multicast session.
  • the multicast session information carries information indicating that the UE keeps joining or leaving the first multicast session.
  • the multicast session information carries information indicating that the UE requests to join the first multicast session.
  • the SMF can judge whether the UE is currently in the multicast session service area according to the UE location information and the multicast session service area (MBS Service Area).
  • the SMF determines that the UE cannot keep joining the first multicast session, and the response message of the second request carries the indication Information about the UE leaving the first multicast session, such as the identifier of the first multicast session and the leaving indication.
  • the SMF updates the information of the PDU session associated with the first multicast session, that is, deletes the first multicast session identifier and the mapped unicast QoS information from the PDU session context; if the SMF saves the UE that joined the first multicast session list, SMF deletes the UE ID from the UE list.
  • the first AMF may add the new RAN node information serving the UE, such as the RAN node ID, to the multicast session in context.
  • the SMF refuses the UE to join the first multicast session, and carries the second request in the response message to the first AMF.
  • the SMF adds the UE identifier to the UE list of the first multicast session.
  • the response message of the second request carries information that the UE is accepted to join the first multicast session.
  • the method also includes:
  • the radio access network function entity sends a third request to a radio access network function entity, where the third request carries the first multicast session identifier and information instructing the UE to leave the first multicast session, so that the radio access network function
  • the entity removes the identity of the UE from the context of the first multicast session.
  • the first AMF after receiving the response message of the second request sent by the SMF or MB-SMF, the first AMF sends the third request to the RAN through the N2 interface.
  • the third request carries the multicast session information and the registration/service acceptance message, and also carries the PDU session modification indication message.
  • the PDU session modification indication message carries the identifier of the first multicast session and information indicating that the UE leaves the first multicast session.
  • the SMF updates the information of the PDU session associated with the multicast session, that is, deletes the first multicast session identifier and the mapped unicast QoS information from the PDU session context; In the UE list of the first multicast session, the SMF deletes the UE identifier from the UE list.
  • the response message sent by 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.
  • the third request sent by the first AMF to the RAN the RAN forwards the information in the third request to the UE, and the UE determines to leave the first multicast session according to the first multicast session identifier and the information indicating that the UE leaves the first multicast session, That is: delete the context of the multicast session in the UE.
  • the multicast session information also includes at least one of the following identification information:
  • the determining the first network function entity serving the first multicast session includes:
  • the multicast session information also includes:
  • Information about the network function serving the first multicast session such as the ID of the MB-SMF and/or the ID of the SMF.
  • the first AMF determines the PDU session associated with the first multicast session and the SMF serving the PDU session according to the multicast session information in the first request sent by the UE and/or the multicast session information in the UE context.
  • the UE If the first request sent by the UE includes the identifier of the PDU session associated with the first multicast session, select the PDU session indicated by the PDU session identifier and the SMF serving the PDU session;
  • a PDU session information in the UE context includes multicast session information, select the PDU session and the SMF serving the PDU session;
  • a PDU session is the PDU session associated with the multicast session, and the SMF serving the PDU session.
  • the first AMF may determine the MB-SMF serving the first multicast session according to the identifier of the MB-SMF.
  • the multicast session processing method provided by the embodiment of the present application realizes the synchronization of the multicast session state between the user equipment UE and the network through a registration request or a service request, reduces the signaling interaction required by the UE to process the multicast session service, and improves the signal quality. Signaling efficiency is saved, signaling resources are saved, and the time for UEs to join or leave a multicast session and receive or transmit multicast session data is shortened.
  • FIG. 3 is the second schematic flow diagram of the multicast session processing method provided by the embodiment of the present application.
  • the embodiment of the present application provides a multicast session processing method, the execution subject of which is SMF, and the method includes:
  • Step 301 Receive a second request sent by the first AMF, the second request carries multicast session information of the user equipment UE, and the multicast session information is 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.
  • Step 302 Process the multicast session of the UE according to the multicast session information carried in the second request.
  • the multicast session processing method provided by the embodiment of the present application realizes the synchronization of the multicast session state between the user equipment UE and the network through a registration request or a service request, reduces the signaling interaction required by the UE to process the multicast session service, and improves the signal quality. Signaling efficiency is saved, signaling resources are saved, and the time for UEs to join or leave a multicast session and receive or transmit multicast session data is shortened.
  • the multicast session information includes a first multicast session identifier and/or indication information, where the indication information is used to instruct the UE to keep joining, leave or request to join the first multicast session, the
  • the first multicast session is a multicast session that the UE has joined or a multicast session that the UE has requested to join.
  • processing the multicast session of the UE according to the multicast session information carried in the second request includes:
  • the indication information is used to indicate that the UE requests to join the first multicast session, and it is determined to accept the UE to join the first multicast session, establish the identity of the UE and the first multicast session Correspondence between session identifiers; sending a second request response message to the first AMF, where the second request response message carries information for accepting the UE to join the first multicast session; or,
  • the indication information is used to indicate that the UE requests to join the first multicast session, and the UE is not in the service area of the first multicast session, send the second request to the first AMF A response message, where the response message of the second request carries information denying the UE to join the first multicast session; or,
  • the indication information is used to instruct the UE to keep joining the first multicast session, and the UE is not in the service area of the first multicast session, send the second request to the first AMF A response message, the response message of the second request carries information indicating that the UE leaves the first multicast session; or,
  • the indication information is used to instruct the UE to leave the first multicast session, delete the correspondence between the identifier of the UE and the identifier of the first multicast session.
  • processing the multicast session of the UE according to the multicast session information carried in the second request includes:
  • the indication information is used to indicate that the UE requests to join the first multicast session, and it is determined to accept the UE to join the first multicast session, store the service in the context of the first multicast session An identifier of a radio access network functional entity for the UE.
  • the above-mentioned multicast session processing method with the SMF as the execution subject can realize all the method steps implemented in the above-mentioned embodiment of the multicast session processing method with the first AMF as the execution subject , and can achieve the same technical effect, the same parts and beneficial effects in this embodiment as in the method embodiment will not be described in detail here.
  • Fig. 4 is the third schematic flow diagram of the method for processing a multicast session provided by the embodiment of the present application.
  • the embodiment of the present application provides a method for processing a multicast session, the execution subject of which is UE, and the method includes:
  • Step 401 Send a first request to the first AMF, where the first request is a service request message or a registration request message.
  • Step 402 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, and the response message to the first request includes accepting UE joining Or information about leaving the first multicast session, or information indicating that the UE leaves the first multicast session, or information about refusing the UE to join the first multicast session.
  • Step 403 Process the first multicast session according to the response message of the first request.
  • the multicast session processing method provided by the embodiment of the present application realizes the synchronization of the multicast session state between the user equipment UE and the network through a registration request or a service request, reduces the signaling interaction required by the UE to process the multicast session service, and improves the signal quality. Signaling efficiency is saved, signaling resources are saved, and the time for UEs to join or leave a multicast session and receive or transmit multicast session data is shortened.
  • the first request carries multicast session information
  • the multicast session information 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 requested to join, where the indication information is used to instruct the UE to keep joining, leave or request to join the first multicast session.
  • processing the first multicast session according to the response message of the first request includes:
  • response message of the first request carries the information of accepting the UE to join the first multicast session, storing the context of the first multicast session;
  • the response message of the first request carries information denying the UE to join the first multicast session or instructing the UE to leave the first multicast session, delete the context of the first multicast session .
  • the receiving a response message of the first request sent by the first AMF includes:
  • the method also includes:
  • response message of the first request carries the information of accepting the UE to join the first multicast session, establishing or updating the resource of the first multicast session;
  • the receiving service data of the first multicast session by using the resource includes:
  • radio access network functional entity does not support multicast services, use the resources to receive service data of the first multicast session in a unicast manner;
  • the radio access network functional entity supports multicast services, use the resources to receive service data of the first multicast session in a multicast manner.
  • the above multicast session processing method with the UE as the execution subject can realize 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, the same parts and beneficial effects in this embodiment as in the method embodiment will not be described in detail here.
  • Fig. 5 is the fourth schematic flow diagram of the multicast session processing method provided by the embodiment of the present application. As shown in Fig. 5, the embodiment of the present application provides a multicast session processing method. When the RAN node is established, the method includes:
  • Step 501 when the UE moves to a new registration area (Registration Area), requests to update UE capabilities, or requests network information, etc., it sends a registration request to the network to request a registration update.
  • a new registration area Registration Area
  • requests to update UE capabilities, or requests network information, etc. it sends a registration request to the network to request a registration update.
  • 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 judges whether it has UE context (UE Context), and determines the service before the UE moves according to the UE identity For the old AMF of the UE, send the UE context transfer request Namf_Communication_UE Context Transfer to the old AMF.
  • UE Context UE context
  • Step 503 the old AMF sends the response message Namf_Communication_UEContextTransfer Response of the UE context transfer request to the new AMF, and the response message carries the multicast session information that the UE has joined, including at least one of the following:
  • One or more multicast session identification MBS session ID One or more multicast session identification MBS session ID
  • Network function NF serving multicast sessions such as MB-SMF information, MB-SMF ID;
  • the identifier of the PDU session associated with the multicast session Associated PDU Session ID is the identifier of the PDU session associated with the multicast session Associated PDU Session ID.
  • Step 504 the new AMF generates or updates the multicast session context according to 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 identifier RAN Node ID, to the multicast session context.
  • Step 505 the new AMF determines the PDU session associated with the multicast session and the SMF serving the PDU session according to the PDU session information in the UE context.
  • the new AMF sends a PDU session update session management context request (Nsmf_PDU Session_Update Session Management Context) to the SMF.
  • the request message carries multicast session information, such as a multicast session identifier (MBS Session ID).
  • MMS Session ID multicast session identifier
  • the request message can also carry UE Location information, such as the cell ID (Cell ID) where the UE is located or the tracking area identifier TAI.
  • Step 506 the SMF requests the MB-SMF to update the multicast session information, and the request message may carry the AMF identifier and the RAN node identifier.
  • Step 507 MB-SMF updates the AMF ID and RAN node ID into the multicast session context.
  • Step 508 MB-SMF sends a response message of multicast session information update to SMF, the response message includes MBS Session ID and at least one of the following information:
  • QoS Quality of Service
  • Down Link Tunnel ID Down Link Tunnel ID
  • Multicast Address etc.
  • Step 509 SMF updates the local multicast session information according to the response of the MB-SMF, and updates the information of the PDU session associated with the multicast session, for example: if the QoS rule and/or QoS of the multicast quality of service flow (QoS Flow) If the parameters change, the SMF will update the QoS rules and/or QoS parameters of the mapped unicast QoS Flow accordingly.
  • QoS Flow QoS quality of service flow
  • 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, the response message carries the MBS Session ID, the MB-SMF ID, and carries the multicast session in the N2 information to the RAN information, including MBS Session ID, information about the associated PDU session, and at least one of the following:
  • the SMF can judge whether the UE is currently in the multicast session service area according to the UE location information and the multicast session service area (MBS Service Area).
  • PDU Session Modification Command PDU Session Modification Command
  • MMS Session ID Multicast session identification
  • the SMF updates the information of the PDU session associated with the multicast session, that is, deletes the MBS Session ID and the mapped unicast QoS information from the PDU session context; if the SMF saves the list of UEs joining the multicast session, the SMF will The UE ID is deleted from the UE list;
  • the response message from the SMF to the new AMF does not carry the MB-SMF ID, and the N2 information to the RAN does not carry the information of the multicast session.
  • Steps 506-509, 5011, 5014-5019 are not executed.
  • Step 5011 if step 504 is not performed, the new AMF may 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 RAN node identifier, to the multicast session context.
  • Step 5012 the new AMF sends an N2 message to the RAN, and the N2 message carries the information of the multicast session contained in the Nsmf_PDUSession_Update Session Management Context response of step 5010, and a registration acceptance (Registration Accept) message, and the N2 message may also carry the PDU Session Modification Command message.
  • Step 5013 RAN forwards the registration acceptance message to UE.
  • the RAN can also forward the PDU Session Modification Command message to the UE, and the UE determines to leave the multicast session according to the MBS Session ID in the message and the information instructing the UE to leave the multicast session, that is, delete the context of the multicast session in the UE.
  • the UE retains or updates the context of the multicast session in the UE.
  • Step 5014 If the RAN supports the multicast service, the RAN sends an N2 message to the AMF according to the received multicast session information.
  • the N2 message carries the MBS Session ID and may also carry the RAN tunnel information.
  • Step 5015 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 MBS Session ID and RAN Node ID, and may also carry RAN tunnel information.
  • Step 5016 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.
  • Step 5017 MB-SMF sends a multicast session information update request response message to AMF, the response message carries the information of the multicast session provided to RAN, including MBS Session ID and at least one of the following:
  • QoS information can be sent to RAN through steps 5010, 5012 or steps 5017, 5018.
  • Common Downlink Tunnel ID Common Downlink Tunnel ID
  • Multicast Address Multicast Address
  • Step 5018 AMF sends N2 message to NG-RAN node, and the N2 message carries the multicast session information provided by MB-SMF in step 5017.
  • the RAN sends a resource allocation request message to the UE, and establishes resources for the multicast session if the resources for the multicast session have not been established. If the RAN does not support the multicast service, the RAN establishes the resources of the unicast QoS flow mapped to the multicast QoS flow for the PDU session associated with the multicast session, and transmits the multicast service data to the UE in a unicast manner.
  • FIG. 6 is the fifth schematic flow diagram of the multicast session processing method provided by the embodiment of the present application.
  • the embodiment of the present application provides a multicast session processing method, which keeps joining or When leaving a joined multicast session, the method consists of:
  • Step 601. When the UE moves to a new registration area (Registration Area), requests to update UE capabilities or requests network information, etc., it sends a Registration Request to the network to request a registration update.
  • the registration request carries the multicast session information that the UE has joined, and the multicast session information includes one or more multicast session identifiers, and may also include:
  • Multicast Session Status 1 means that the UE keeps joining the multicast session; 0 means that the UE leaves the multicast session;
  • the identifier of the PDU session associated with the multicast session (Associated PDU Session ID).
  • 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 judges whether it has a UE context (UE Context), and determines the service before the UE moves according to the UE identity. For the old AMF of the UE, send the UE context transfer request Namf_Communication_UE Context Transfer to the old AMF.
  • UE Context UE context
  • Step 603 The old AMF sends a response message Namf_Communication_UEContextTransfer Response to the new AMF, which carries the UE context.
  • the context of the UE includes the PDU session information currently established by the UE, and the PDU session information includes the PDU session identifier and the information of the SMF serving the PDU session. For a PDU session associated with a multicast session, the PDU session information also includes a multicast session identifier.
  • Step 604 the new AMF generates or updates the multicast session context according to the multicast session information in the UE registration request and the context of the UE.
  • the new AMF can add new RAN node information serving the UE, such as the RAN node identifier RAN Node ID, to the multicast session context.
  • Step 605 the new AMF determines the PDU session associated with the multicast session and the SMF serving the PDU session according to the UE context.
  • the new AMF sends a PDU session update session management context request (Nsmf_PDUSession_Update Session Management Context) to the SMF.
  • the request message carries multicast session information, including at least one multicast session identifier, and may also include that for each multicast session, the UE maintains Join or leave status indication (multicast session status).
  • the request message may also carry UE location information, such as the cell identifier (Cell ID) where the UE is located or the tracking area identifier TAI.
  • Steps 606-609 are the same as steps 506-509.
  • Step 6010 is basically the same as step 5010, except that for a multicast session whose multicast session status is 0, the SMF sends a PDU session update session management context response message to the new AMF to set the multicast session status of the multicast session to is 0.
  • the SMF can judge whether the UE is currently in the multicast session service area according to the UE location information and the multicast session service area (MBS Service Area).
  • the SMF rejects the UE's request to keep joining the multicast session, that is, the multicast session status of the multicast session is set to 0 in the PDU session update session management context response message.
  • the SMF updates the information of the PDU session associated with the multicast session, that is, deletes the MBS Session ID and the mapped unicast QoS information from the PDU session context; if the SMF saves the list of UEs joining the multicast session, the SMF will The UE ID is deleted from the UE list;
  • the response message from the SMF to the new AMF does not carry the MB-SMF ID, and the N2 information to the RAN does not carry the information of the multicast session.
  • Steps 606-609, 6011, 6014-6019 are not executed.
  • Step 6011 is the same as step 5011.
  • Steps 6012-6013 are basically the same as steps 5012-5013, the difference lies in:
  • the Registration Accept message carries MBS Session ID and Multicast Session Status. For a multicast session whose Multicast Session Status is 0, if the UE has not left the multicast session, the UE leaves the multicast session, that is, deletes the context of the multicast session in the UE. For a multicast session whose multicast session status is 1, the UE retains or updates the context of the multicast session in the UE.
  • the N2 message sent by the AMF to the RAN does not carry the PDU Session Modification Command message, so the RAN will not send the PDU Session Modification Command message to the UE.
  • Steps 6014-6019 are the same as steps 5014-5019.
  • FIG. 7 is the sixth schematic flow diagram of the multicast session processing method provided by the embodiment of the present application. As shown in FIG. 7 , the embodiment of the present application provides a multicast session processing method. For a multicast session, the method includes:
  • Step 701 when the UE moves to a new registration area (Registration Area), requests to update UE capabilities or requests network information, etc., sends a Registration Request to the network to request registration update.
  • the request message carries information about the multicast session that the UE requests to join, including one or more multicast session identifiers, a join request indication, and may also include a PDU session identifier associated with the multicast session, a DNN corresponding to the multicast session, and/or S-NSSAI information.
  • 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 judges whether it has the context (UE Context) of the UE itself, and determines the UE serving the UE before moving according to the UE identity.
  • the old AMF of the UE sends a UE context transfer request Namf_Communication_UE Context Transfer to the old AMF.
  • Step 703 The old AMF sends a response message Namf_Communication_UEContextTransfer Response to the new AMF, which carries the UE context.
  • the UE context contains the PDU session information currently established by the UE, including: PDU Session ID, information of the SMF serving the PDU session, and may also contain multicast session information, such as MBS Session ID.
  • Step 704 the new AMF generates or updates the multicast session context according to 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 identifier RAN Node ID, to the multicast session context.
  • Step 705 the new AMF determines the PDU session associated with the multicast session and the SMF serving the PDU session according to the multicast session information and/or UE context information in the UE registration request. Specifically, it is determined as follows:
  • the UE registration request contains the PDU session identifier associated with the multicast session, select the PDU session and the SMF serving the PDU session;
  • the information of a PDU session in the UE context includes multicast session information, select the PDU session and the SMF serving the PDU session;
  • a PDU session is a PDU session associated with a multicast session, and an SMF serving the PDU session.
  • the new AMF sends a PDU session update session management context request (Nsmf_PDUSession_Update Session Management Context) to the determined SMF.
  • the request message carries the multicast session information that the UE requests to join, including one or more multicast session identifiers, join request instructions, and DNN and/or S-NSSAI information corresponding to the multicast session may be included.
  • the request message may also carry UE location information, such as the cell ID (Cell ID) where the UE is located or the tracking area ID TAI.
  • Steps 706-709 are the same as steps 506-509.
  • Step 7010 is basically the same as step 5010, the difference lies in:
  • the SMF can judge whether the UE is currently in the multicast session service area according to the UE location information and the multicast session service area (MBS Service Area).
  • the SMF rejects the UE's request to join the multicast session, that is, the response message to the new AMF carries the multicast session identifier and an indication of rejecting the UE to join the multicast session. For this multicast session, steps 706-709, 7011, 7014-7019 are not performed.
  • Step 7011 is the same as step 5011.
  • Steps 7012-7013 are basically the same as steps 5012-5013, the difference lies in:
  • the Registration Accept message carries the MBS Session ID and the information of receiving or rejecting the UE to join the multicast session.
  • the UE For a multicast session accepted by the UE, the UE stores the context of the multicast session. Storing includes generating or updating.
  • the UE For the multicast session that rejects the UE to join, the UE deletes the context of the multicast session;
  • the N2 message sent by the AMF to the RAN does not carry the PDU Session Modification Command message, so the RAN will not send the PDU Session Modification Command message to the UE.
  • Steps 7014-7019 are the same as steps 5014-5019.
  • FIG. 8 is a schematic structural diagram of the AMF network functional entity provided by the embodiment of the present application. As shown in Figure 8, the embodiment of the present application provides an AMF network functional entity, including a memory 801, a transceiver 802, and a processor 803:
  • the memory 801 is used to store computer programs; the transceiver 802 is used to send and receive data under the control of the processor 803; the processor 803 is used to read the computer programs in the memory 801 and perform the following operations:
  • the multicast session information perform processing operations related to the multicast session.
  • the transceiver 802 is configured to receive and send data under the control of the processor 803 .
  • the bus architecture may include any number of interconnected buses and bridges, specifically, one or more processors represented by the processor 803 and various circuits of the memory represented by the memory 801 are linked together.
  • the bus architecture can also link together various other circuits such as peripherals, voltage regulators, and power management circuits, etc., which are well known in the art and therefore will not be further described herein.
  • the bus interface provides the interface.
  • Transceiver 802 may be a plurality of elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical cables, 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 when performing operations.
  • the processor 803 can be a central processing unit (CPU), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field-Programmable Gate Array, FPGA) or a complex programmable logic device (Complex Programmable Logic Device, CPLD), the processor can also adopt a multi-core architecture.
  • CPU central processing unit
  • ASIC Application Specific Integrated Circuit
  • FPGA field programmable gate array
  • CPLD Complex Programmable Logic Device
  • the acquiring the multicast session information of the UE according to the first request includes:
  • the acquiring the multicast session information of the UE according to the first request includes:
  • the second AMF is a network function entity that provides services for the UE before the UE moves.
  • the multicast session information includes a first multicast session identifier and/or indication information, where the indication information is used to instruct the UE to keep joining, leave or request to join the first multicast session, the
  • the first multicast session is a multicast session that the UE has joined or a multicast session that the UE has requested to join.
  • the performing a processing operation related to the multicast session according to the multicast session information includes:
  • the first network function entity includes: a session management function SMF or a multicast broadcast session management function MB-SMF;
  • the receiving the response message of the second request sent by the first network function entity includes:
  • the processor 803 is also used to read the computer program in the memory 801 and perform the following operations:
  • the radio access network functional entity According to the response message of the second request, send a third request to the radio access network functional entity, where the third request carries the first multicast session identifier and the resource allocation request information, so that the radio access A network function entity establishes or updates resources of the first multicast session.
  • the response message of the second request carries the first multicast session identifier and the following information:
  • the processor 803 is also configured to read the computer program in the memory 801 and perform the following operations:
  • the radio access network function entity sends a third request to a radio access network function entity, where the third request carries the first multicast session identifier and information instructing the UE to leave the first multicast session, so that the radio access network function
  • the entity removes the identity of the UE from the context of the first multicast session.
  • the multicast session information also includes at least one of the following identification information:
  • the determining the first network function entity serving the first multicast session includes:
  • the above-mentioned AMF network function entity provided by the embodiment of the present application can implement all the method steps implemented by the above-mentioned embodiment of the multicast session processing method with the first AMF as the execution subject, and can achieve the same technical effect, the same parts and beneficial effects in this embodiment as those in the method embodiment will not be described in detail here.
  • FIG. 9 is a schematic structural diagram of the SMF network functional entity provided by the embodiment of the present application. As shown in Figure 9, the embodiment of the present application provides a SMF network functional entity, including a memory 901, a transceiver 902, and a processor 903:
  • the memory 901 is used to store computer programs; the transceiver 902 is used to send and receive data under the control of the processor 903; the processor 903 is used to read the computer programs in the memory 901 and perform the following operations:
  • the second request carries multicast session information of the user equipment UE, and the multicast session information is obtained after the first AMF receives the first request sent by the UE obtained, the first request is a registration request message or a service request message;
  • the transceiver 902 is configured to receive and send data under the control of the processor 903 .
  • the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 903 and various circuits of the memory represented by the memory 901 are linked together.
  • the bus architecture can also link together various other circuits such as peripherals, voltage regulators, and power management circuits, etc., which are well known in the art and therefore will not be further described herein.
  • the bus interface provides the interface.
  • Transceiver 902 may be a plurality of elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical cables, 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 when performing operations.
  • the processor 903 can be a central processing unit (CPU), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field-Programmable Gate Array, FPGA) or a complex programmable logic device (Complex Programmable Logic Device, CPLD), the processor can also adopt a multi-core architecture.
  • CPU central processing unit
  • ASIC Application Specific Integrated Circuit
  • FPGA field programmable gate array
  • CPLD Complex Programmable Logic Device
  • the multicast session information includes a first multicast session identifier and/or indication information, where the indication information is used to instruct the UE to keep joining, leave or request to join the first multicast session, the
  • the first multicast session is a multicast session that the UE has joined or a multicast session that the UE has requested to join.
  • processing the multicast session of the UE according to the multicast session information carried in the second request includes:
  • the indication information is used to indicate that the UE requests to join the first multicast session, and it is determined to accept the UE to join the first multicast session, establish the identity of the UE and the first multicast session Correspondence between session identifiers; sending a second request response message to the first AMF, where the second request response message carries information for accepting the UE to join the first multicast session; or,
  • the indication information is used to indicate that the UE requests to join the first multicast session, and the UE is not in the service area of the first multicast session, send the second request to the first AMF A response message, where the response message of the second request carries information denying the UE to join the first multicast session; or,
  • the indication information is used to instruct the UE to keep joining the first multicast session, and the UE is not in the service area of the first multicast session, send the second request to the first AMF A response message, the response message of the second request carries information indicating that the UE leaves the first multicast session; or,
  • the indication information is used to instruct the UE to leave the first multicast session, delete the correspondence between the identifier of the UE and the identifier of the first multicast session.
  • processing the multicast session of the UE according to the multicast session information carried in the second request includes:
  • the indication information is used to indicate that the UE requests to join the first multicast session, and it is determined to accept the UE to join the first multicast session, store the service in the context of the first multicast session An identifier of a radio access network functional entity for the UE.
  • the SMF network function entity provided by the embodiment of the present application can implement all the method steps implemented by the above-mentioned embodiment of the multicast session processing method with the SMF as the execution subject, and can achieve the same technical effect. Parts and beneficial effects in this embodiment that are the same as those in the method embodiment will not be described in detail here.
  • FIG. 10 is a schematic structural diagram of a user equipment UE provided by an embodiment of the present application. As shown in FIG. 10, an embodiment of the present application provides a user equipment UE, including a memory 1001, a transceiver 1002, and a processor 1003:
  • the memory 1001 is used to store computer programs; the transceiver 1002 is used to send and receive data under the control of the processor 1003; the processor 1003 is used to read the computer programs in the memory 1001 and perform the following operations:
  • 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 accepting UE joining or leaving the first request Information about a multicast session, or information indicating that the UE leaves the first multicast session, or information that refuses the UE to join the first multicast session;
  • the transceiver 1002 is configured to receive and send data under the control of the processor 1003 .
  • the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 1003 and various circuits of the memory represented by the memory 1001 are linked together.
  • the bus architecture can also link together various other circuits such as peripherals, voltage regulators, and power management circuits, etc., which are well known in the art and therefore will not be further described herein.
  • the bus interface provides the interface.
  • Transceiver 1002 may be a plurality of elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical cables, 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 when performing operations.
  • the processor 1003 can be a central processing unit (CPU), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field-Programmable Gate Array, FPGA) or a complex programmable logic device (Complex Programmable Logic Device, CPLD), the processor can also adopt a multi-core architecture.
  • CPU central processing unit
  • ASIC Application Specific Integrated Circuit
  • FPGA field programmable gate array
  • CPLD Complex Programmable Logic Device
  • the first request carries multicast session information
  • the multicast session information 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 requested to join, where the indication information is used to instruct the UE to keep joining, leave or request to join the first multicast session.
  • processing the first multicast session according to the response message of the first request includes:
  • response message of the first request carries the information of accepting the UE to join the first multicast session, storing the context of the first multicast session;
  • the response message of the first request carries information denying the UE to join the first multicast session or instructing the UE to leave the first multicast session, delete the context of the first multicast session .
  • the receiving a response message of the first request sent by the first AMF includes:
  • the processor 1003 is also used to read the computer program in the memory 1001 and perform the following operations:
  • response message of the first request carries the information of accepting the UE to join the first multicast session, establishing or updating the resource of the first multicast session;
  • the receiving service data of the first multicast session by using the resource includes:
  • radio access network functional entity does not support multicast services, use the resources to receive service data of the first multicast session in a unicast manner;
  • the radio access network functional entity supports multicast services, use the resources to receive service data of the first multicast session in a multicast manner.
  • the above-mentioned user equipment UE provided by the embodiment of the present application can implement all the method steps implemented by the above-mentioned embodiment of the multicast session processing method with the UE as the execution subject, and can achieve the same technical effect.
  • the parts and beneficial effects in this embodiment that are the same as those in the method embodiment will not be described in detail here.
  • FIG. 11 is one of the structural schematic diagrams of the multicast session processing device provided by the embodiment of the present application. As shown in FIG. 11 , the embodiment of the present application provides a multicast session processing device, which includes:
  • the first receiving unit 1101 is configured to receive a first request sent by the user equipment UE, where the first request is a registration request message or a service request message;
  • a first acquiring unit 1102 configured to acquire multicast session information of the UE according to the first request
  • the executing unit 1103 is configured to execute processing operations related to the multicast session according to the multicast session information.
  • the first obtaining unit includes:
  • a first obtaining module configured to obtain the multicast session information of the UE from the first request.
  • the first acquisition unit includes:
  • the second obtaining module is configured to obtain the multicast session information of the UE from a second AMF based on the first request, and the second AMF is a network function that provides services for the UE before the UE moves
  • the first AMF is a network function entity that provides services for the UE after the UE moves.
  • the multicast session information includes a first multicast session identifier and/or indication information, where the indication information is used to instruct the UE to keep joining, leave or request to join the first multicast session, the
  • the first multicast session is a multicast session that the UE has joined or a multicast session that the UE has requested to join.
  • the execution unit includes:
  • the first determining module is configured to determine a first network function entity serving the first multicast session, wherein the first network function entity includes: a session management function SMF or a multicast broadcast session management function MB-SMF;
  • a first sending module configured to send a second request to the first network function entity, where the second request carries the multicast session information
  • the first receiving module is configured to receive a response message to the second request sent by the first network function entity.
  • the first receiving unit includes:
  • a second receiving module configured to receive a response message to a second request that is sent by the first network function entity and carries the first multicast session identifier and resource allocation request information
  • the unit also includes:
  • a first sending unit configured to send a third request to a radio access network functional entity according to a response message of the second request, where the third request carries the first multicast session identifier and the resource allocation request information, and enabling the radio access network functional entity to establish or update resources of the first multicast session.
  • the response message of the second request carries the first multicast session identifier and the following information:
  • the device also includes:
  • a second sending unit configured to send a third request to a radio access network function entity, where the third request carries a first multicast session identifier and information instructing the UE to leave the first multicast session, so that The radio access network functional entity deletes the identity of the UE from the context of the first multicast session.
  • the multicast session information also includes at least one of the following identification information:
  • the determining the first network function entity serving the first multicast session includes:
  • the above multicast session processing device provided in the embodiment of the present application can realize 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 effects, the same parts and beneficial effects in this embodiment as those in the method embodiment will not be described in detail here.
  • FIG. 12 is the second structural schematic diagram of the multicast session processing device provided by the embodiment of the present application. As shown in FIG. 12 , the embodiment of the present application provides a multicast session processing device, which includes:
  • the second receiving unit 1201 is configured to receive a second request sent by the first AMF, where the second request carries multicast session information of the user equipment UE, and the multicast session information is obtained by the first AMF after receiving the acquired after the first request sent by the UE, where the first request is a registration request message or a service request message;
  • the first processing unit 1202 is configured to process the multicast session of the UE according to the multicast session information carried in the second request.
  • the multicast session information includes a first multicast session identifier and/or indication information, where the indication information is used to instruct the UE to keep joining, leave or request to join the first multicast session, the
  • the first multicast session is a multicast session that the UE has joined or a multicast session that the UE has requested to join.
  • the first processing unit includes:
  • a first establishing module configured to establish an identity of the UE if the indication information is used to indicate that the UE requests to join the first multicast session and it is determined to accept the UE to join the first multicast session Correspondence with the first multicast session identifier;
  • the second sending module is configured to send a second request response message to the first AMF, where the second request response message carries information for accepting the UE to join the first multicast session;
  • a third sending module configured to, if the indication information is used to indicate that the UE requests to join the first multicast session, and the UE is not in the service area of the first multicast session, send the message to the second multicast session
  • An AMF sends a response message to the second request, where the response message to the second request carries information denying the UE to join the first multicast session;
  • a fourth sending module configured to, if the indication information is used to instruct the UE to keep joining the first multicast session, and the UE is not in the service area of the first multicast session, send the message to the second multicast session
  • An AMF sends a response message to the second request, where the response message to the second request carries information indicating that the UE leaves the first multicast session;
  • a first deleting module configured to delete the correspondence between the identifier of the UE and the identifier of the first multicast session if the indication information is used to instruct the UE to leave the first multicast session.
  • the first processing unit includes:
  • a first storage module configured to, if the indication information is used to indicate that the UE requests to join the first multicast session, and it is determined to accept the UE to join the first multicast session, then in the first multicast session Store the identifier of the radio access network function entity serving the UE in the context of the broadcast session.
  • the above-mentioned multicast session processing device provided by the embodiment of the present application can realize all the method steps realized by the above-mentioned embodiment of the multicast session processing method with SMF as the execution subject, and can achieve the same technical effect , the same parts and beneficial effects in this embodiment as those in the method embodiment will not be described in detail here.
  • FIG. 13 is the third schematic structural diagram of the multicast session processing device provided by the embodiment of the present application. As shown in FIG. 13 , the embodiment of the present application provides a multicast session processing device, which includes:
  • the third sending unit 1301 is configured to send a first request to the first AMF, where the first request is a service request message or a registration request message;
  • the third receiving unit 1302 is configured to 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, and the response message to the first request Including information accepting the UE to join or leave the first multicast session, or instructing the UE to leave the first multicast session, or refusing the UE to join the first multicast session;
  • the second processing unit 1303 is configured to process the first multicast session according to the response message of the first request.
  • the first request carries multicast session information
  • the multicast session information 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 requested to join, where the indication information is used to instruct the UE to keep joining, leave or request to join the first multicast session.
  • the second processing unit includes:
  • the second storage module is configured to store the context of the first multicast session if the response message of the first request carries the information of accepting the UE to join the first multicast session;
  • a second deletion module configured to delete the UE if the response message to the first request carries information denying the UE to join the first multicast session or instructing the UE to leave the first multicast session.
  • the context of the first multicast session is configured to delete the UE if the response message to the first request carries information denying the UE to join the first multicast session or instructing the UE to leave the first multicast session.
  • the third receiving unit includes:
  • a third receiving module configured to receive a response message to the first request sent by the first AMF and forwarded by a radio access network functional entity;
  • the device also includes:
  • An establishing unit configured to establish or update resources of the first multicast session if the response message of the first request carries information that accepts the UE to join the first multicast session;
  • the fourth receiving unit is configured to use the resource to receive the service data of the first multicast session.
  • the fourth receiving unit includes:
  • the fourth receiving module is configured to use the resource to receive the service data of the first multicast session in a unicast manner if the radio access network functional entity does not support the multicast service;
  • the fifth receiving module is configured to use the resources to receive the service data of the first multicast session in a multicast manner if the radio access network functional entity supports multicast services.
  • the above multicast session processing device provided by the embodiment of the present application can implement all the method steps implemented by the above embodiment of the multicast session processing method with the UE as the execution subject, and can achieve the same technical effect , the same parts and beneficial effects in this embodiment as those in the method embodiment will not be described in detail here.
  • each functional unit/module in each embodiment of the present application may be integrated into one processing unit/module, each unit/module may exist separately physically, or two or more units/modules may be integrated into one processing unit/module. unit/module.
  • the above-mentioned integrated units/modules can be implemented in the form of hardware or in the form of software functional units.
  • the integrated unit/module is realized in the form of a software function unit/module and sold or used as an independent product, it can be stored in a processor-readable storage medium.
  • the technical solution of the present application is essentially or part of the contribution to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disc and other media that can store program codes. .
  • the embodiments of the present application also provide a processor-readable storage medium, the processor-readable storage medium stores a computer program, and the computer program is used to make the processor execute the above-mentioned embodiments.
  • Multicast session processing methods including:
  • the multicast session information perform processing operations related to the multicast session.
  • the second request carries multicast session information of the user equipment UE, and the multicast session information is obtained by the first AMF after receiving the first request sent by the UE obtained, the first request is a registration request message or a service request message;
  • 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 accepting UE joining or leaving the first request Information about a multicast session, or information indicating that the UE leaves the first multicast session, or information that refuses the UE to join the first multicast session;
  • the processor-readable storage medium may be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (such as floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.) , optical memory (such as CD, DVD, BD, HVD, etc.), and semiconductor memory (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state hard drive (SSD)), etc.
  • magnetic storage such as floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.
  • optical memory such as CD, DVD, BD, HVD, etc.
  • semiconductor memory such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state hard drive (SSD)
  • first”, “second”, “object” and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific sequence or sequence. It should be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application can be practiced in sequences other than those illustrated or described herein, and that "first”, “second”, “object”
  • the objects distinguished by etc. are generally one type, and the number of objects is not limited. For example, there may be one or more first objects.
  • the applicable system may be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet Wireless business (general packet radio service, GPRS) system, long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD) system, Long term evolution advanced (LTE-A) system, universal mobile telecommunications system (UMTS), worldwide interoperability for microwave access (WiMAX) system, 5G new air interface (New Radio, NR) system, etc.
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • GPRS general packet Wireless business
  • long term evolution long term evolution
  • LTE long term evolution
  • LTE frequency division duplex frequency division duplex
  • TDD time division duplex
  • LTE-A Long term evolution advanced
  • UMTS universal mobile telecommunications
  • the terminal device involved in this embodiment of the present application may be a device that provides voice and/or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem.
  • the name of the terminal equipment may be different.
  • the terminal equipment may be called User Equipment (User Equipment, UE).
  • the wireless terminal equipment can communicate with one or more core networks (Core Network, CN) via the radio access network (Radio Access Network, RAN), and the wireless terminal equipment can be a mobile terminal equipment, such as a mobile phone (or called a "cellular "telephones) and computers with mobile terminal equipment, such as portable, pocket, hand-held, computer built-in or vehicle-mounted mobile devices, which exchange language and/or data with the radio access network.
  • a mobile terminal equipment such as a mobile phone (or called a "cellular "telephones) and computers with mobile terminal equipment, such as portable, pocket, hand-held, computer built-in or vehicle-mounted mobile devices, which exchange language and/or data with the radio access network.
  • PCS Personal Communication Service
  • SIP Session Initiated Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • Wireless terminal equipment can also be called system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point , remote terminal (remote terminal), access terminal (access terminal), user terminal (user terminal), user agent (user agent), and user device (user device), which are not limited in this embodiment of the application.
  • the network device involved in this embodiment of the present application may be a base station, and the base station may include multiple cells that provide services for terminals.
  • the base station can also be called an access point, or it can be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names.
  • the network device can be used to interchange received over-the-air frames with Internet Protocol (IP) packets and act as a router between the wireless terminal device and the rest of the access network, which can include the Internet Protocol (IP) communication network.
  • IP Internet Protocol
  • Network devices may also coordinate attribute management for the air interface.
  • the network device involved in the embodiment of the present application may be a network device (Base Transceiver Station, BTS) in Global System for Mobile communications (GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA) ), it can also be a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or it can be an evolved network device in a long-term evolution (long term evolution, LTE) system (evolutional Node B, eNB or e-NodeB), 5G base station (gNB) in the 5G network architecture (next generation system), can also be a home evolved base station (Home evolved Node B, HeNB), relay node (relay node) , a home base station (femto), a pico base station (pico), etc., are not limited in this embodiment of the present application.
  • a network device may include a centralized unit (centralized unit, CU) node and a distributed unit (distributed unit, DU) node,
  • MIMO transmission can be Single User MIMO (Single User MIMO, SU-MIMO) or multi-user MIMO (Multiple User MIMO, MU-MIMO). According to the shape and number of root antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, or diversity transmission, precoding transmission, or beamforming transmission, etc.
  • the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) having computer-usable program code embodied therein.
  • processor-executable instructions may also be stored in a processor-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, such that the instructions stored in the processor-readable memory produce a manufacturing product, the instruction device realizes the functions specified in one or more procedures of the flow chart and/or one or more blocks of the block diagram.
  • processor-executable instructions 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
  • the executed instructions provide steps for implementing the functions specified in the procedure or procedures of the flowchart and/or the block or blocks of the block diagrams.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例提供一种多播会话处理方法、网络功能实体、装置及存储介质，其中方法包括：接收用户设备UE发送的第一请求，所述第一请求为注册请求消息或业务请求消息；根据所述第一请求获取所述UE的多播会话信息；根据所述多播会话信息，执行与多播会话相关的处理操作。本申请提供的多播会话处理方法，通过注册请求或业务请求实现用户设备UE与网络间多播会话状态的同步，减少了UE处理多播会话业务所需要的信令交互，提高了信令效率，节省了信令资源，同时缩短了UE加入或离开多播会话以及接收或传输多播会话数据的时间。

Description

多播会话处理方法、网络功能实体、装置及存储介质
相关申请的交叉引用
本申请要求于2021年07月23日提交的申请号为2021108391573，发明名称为“多播会话处理方法、网络功能实体、装置及存储介质”的中国专利申请的优先权，其通过引用方式全部并入本文。
技术领域
本申请涉及通信技术领域，尤其涉及一种多播会话处理方法、网络功能实体、装置及存储介质。
背景技术
用户设备需要通过加入多播会话来接收特定的多播业务数据。
现有技术中，处于空闲态或者激活态的用户设备，由于用户设备(User Equipment，UE)发生移动或者其他原因，例如网络切片变化，服务于用户设备的无线接入网RAN节点甚至核心网CN节点发生变化，用户设备需要先完成注册更新或者业务请求流程，再发起PDU会话修改流程，才能接收多播会话的数据或者离开已经加入的多播会话。
然而，现有技术的方案中，用户设备需要与网络进行较多的信令交互才能接收多播会话的数据或者离开已经加入的多播会话，导致资源浪费和效率低下。
发明内容
本申请实施例提供一种多播会话处理方法、网络功能实体、装置及存储介质，用以解决现有技术中用户设备需要与网络进行较多的信令交互才能接收多播会话的数据或者离开已经加入的多播会话的缺陷，提高信令效率，节省信令资源。
第一方面，本申请实施例提供一种多播会话处理方法，应用于第一AMF 中，包括：
接收用户设备UE发送的第一请求，所述第一请求为注册请求消息或业务请求消息；
根据所述第一请求获取所述UE的多播会话信息；
根据所述多播会话信息，执行与多播会话相关的处理操作。
可选地，若所述第一请求中携带所述UE的多播会话信息，则所述根据所述第一请求获取所述UE的多播会话信息，包括：
从所述第一请求中获取所述UE的多播会话信息。
可选地，所述根据所述第一请求获取所述UE的多播会话信息，包括：
基于所述第一请求，从第二AMF中获取所述UE的多播会话信息，所述第二AMF为所述UE发生移动之前为所述UE提供服务的网络功能实体；所述第一AMF为所述UE发生移动之后为所述UE提供服务的网络功能实体。
可选地，所述多播会话信息包含第一多播会话标识和/或指示信息，所述指示信息用于指示所述UE保持加入、离开或请求加入所述第一多播会话，所述第一多播会话为所述UE已加入的多播会话或请求加入的多播会话。
可选地，所述根据所述多播会话信息，执行与多播会话相关的处理操作，包括：
确定服务于第一多播会话的第一网络功能实体，其中，所述第一网络功能实体包括：会话管理功能SMF或多播广播会话管理功能MB-SMF；
向所述第一网络功能实体发送第二请求，所述第二请求中携带所述多播会话信息；
接收所述第一网络功能实体发送的第二请求的响应消息。
可选地，所述接收所述第一网络功能实体发送的第二请求的响应消息，包括：
接收所述第一网络功能实体发送的携带所述第一多播会话标识和资源分配请求信息的第二请求的响应消息；
所述方法还包括：
根据所述第二请求的响应消息，向无线接入网络功能实体发送第三请求， 所述第三请求中携带第一多播会话标识和所述资源分配请求信息，以使所述无线接入网络功能实体建立或更新所述第一多播会话的资源。
可选地，所述第二请求的响应消息携带第一多播会话标识和以下信息：
指示所述UE离开所述第一多播会话的信息；或，
拒绝所述UE加入所述第一多播会话的信息。
可选地，所述方法还包括：
向无线接入网络功能实体发送第三请求，所述第三请求中携带第一多播会话标识和指示所述UE离开所述第一多播会话的信息，以使所述无线接入网络功能实体从所述第一多播会话的上下文中删除所述UE的标识。
可选地，所述多播会话信息还包括以下至少一项标识信息：
第一多播会话关联的协议数据单元PDU会话的标识；
服务于所述第一多播会话的MB-SMF的标识和/或SMF的标识；
所述确定服务于第一多播会话的第一网络功能实体，包括：
依据所述至少一项标识信息,确定服务于所述第一多播会话的第一网络功能实体。
第二方面，本申请实施例还提供一种多播会话处理方法，应用于SMF，包括：
接收第一AMF发送的第二请求，所述第二请求中携带用户设备UE的多播会话信息，所述多播会话信息是所述第一AMF在接收到所述UE发送的第一请求之后获取的，所述第一请求为注册请求消息或业务请求消息；
根据所述第二请求中携带的多播会话信息，对所述UE的多播会话进行处理。
可选地，所述多播会话信息包含第一多播会话标识和/或指示信息，所述指示信息用于指示所述UE保持加入、离开或请求加入所述第一多播会话，所述第一多播会话为所述UE已加入的多播会话或请求加入的多播会话。
可选地，所述根据所述第二请求中携带的多播会话信息，对所述UE的多播会话进行处理，包括：
若所述指示信息用于指示所述UE请求加入所述第一多播会话，且确定 接受所述UE加入所述第一多播会话，则建立所述UE的标识与所述第一多播会话标识之间的对应关系；向所述第一AMF发送第二请求的响应消息，所述第二请求的响应消息中携带接受所述UE加入所述第一多播会话的信息；或，
若所述指示信息用于指示所述UE请求加入所述第一多播会话，且所述UE不在所述第一多播会话的服务区域内，则向所述第一AMF发送第二请求的响应消息，所述第二请求的响应消息中携带拒绝所述UE加入所述第一多播会话的信息；或，
若所述指示信息用于指示所述UE保持加入所述第一多播会话，且所述UE不在所述第一多播会话的服务区域内，则向所述第一AMF发送第二请求的响应消息，所述第二请求的响应消息中携带指示所述UE离开所述第一多播会话的信息；或，
若所述指示信息用于指示所述UE离开所述第一多播会话，则删除所述UE的标识与所述第一多播会话标识之间的对应关系。
可选地，所述根据所述第二请求中携带的多播会话信息，对所述UE的多播会话进行处理，包括：
若所述指示信息用于指示所述UE请求加入所述第一多播会话，且确定接受所述UE加入所述第一多播会话，则在所述第一多播会话的上下文中存储服务于所述UE的无线接入网络功能实体的标识。
第三方面，本申请实施例还提供一种多播会话处理方法，包括：
向第一AMF发送第一请求，所述第一请求为业务请求消息或注册请求消息；
接收所述第一AMF发送的所述第一请求的响应消息，所述第一请求的响应消息为注册接受消息或业务接受消息，所述第一请求的响应消息中包含接受UE加入或离开第一多播会话的信息，或，指示所述UE离开第一多播会话的信息，或，拒绝所述UE加入第一多播会话的信息；
根据所述第一请求的响应消息，对所述第一多播会话进行处理。
可选地，所述第一请求中携带多播会话信息，所述多播会话信息包含第一多播会话标识和指示信息，所述第一多播会话为所述UE已加入的多播会 话或请求加入的多播会话，所述指示信息用于指示所述UE保持加入、离开或请求加入所述第一多播会话。
可选地，所述根据所述第一请求的响应消息，对所述第一多播会话进行处理，包括：
若第一请求的响应消息中携带接受所述UE加入所述第一多播会话的信息，则存储所述第一多播会话的上下文；
若第一请求的响应消息中携带拒绝所述UE加入所述第一多播会话的信息或指示所述UE离开所述第一多播会话的信息，则删除所述第一多播会话的上下文。
可选地，所述接收所述第一AMF发送的所述第一请求的响应消息，包括：
接收无线接入网络功能实体转发的所述第一AMF发送的所述第一请求的响应消息；
所述方法还包括：
若所述第一请求的响应消息中携带接受所述UE加入所述第一多播会话的信息，则建立或更新所述第一多播会话的资源；
利用所述资源接收所述第一多播会话的业务数据。
可选地，所述利用所述资源接收所述第一多播会话的业务数据，包括：
若无线接入网络功能实体不支持多播业务，则利用所述资源，通过单播方式接收所述第一多播会话的业务数据；
若无线接入网络功能实体支持多播业务，则利用所述资源，通过多播方式接收所述第一多播会话的业务数据。
第四方面，本申请实施例还提供一种AMF网络功能实体，包括存储器，收发机，处理器：
存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行以下操作：
接收用户设备UE发送的第一请求，所述第一请求为注册请求消息或业务请求消息；
根据所述第一请求获取所述UE的多播会话信息；
根据所述多播会话信息，执行与多播会话相关的处理操作。
可选地，所述根据所述第一请求获取所述UE的多播会话信息，包括：
基于所述第一请求，从第二AMF中获取所述UE的多播会话信息，所述第二AMF为所述UE发生移动之前为所述UE提供服务的网络功能实体。
可选地，所述根据所述多播会话信息，执行与多播会话相关的处理操作，包括：
确定服务于第一多播会话的第一网络功能实体，其中，所述第一网络功能实体包括：会话管理功能SMF或多播广播会话管理功能MB-SMF；
向所述第一网络功能实体发送第二请求，所述第二请求中携带所述多播会话信息；
接收所述第一网络功能实体发送的第二请求的响应消息。
可选地，所述接收所述第一网络功能实体发送的第二请求的响应消息，包括：
接收所述第一网络功能实体发送的携带所述第一多播会话标识和资源分配请求信息的第二请求的响应消息；
所述处理器还用于读取所述存储器中的计算机程序并执行以下操作：
根据所述第二请求的响应消息，向无线接入网络功能实体发送第三请求，所述第三请求中携带第一多播会话标识和所述资源分配请求信息，以使所述无线接入网络功能实体建立或更新所述第一多播会话的资源。
第五方面，本申请实施例还提供一种SMF网络功能实体，包括存储器，收发机，处理器：
存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行以下操作：
接收第一AMF发送的第二请求，所述第二请求中携带用户设备UE的多播会话信息，所述多播会话信息是所述第一AMF在接收到所述UE发送的第一请求之后获取的，所述第一请求为注册请求消息或业务请求消息；
根据所述第二请求中携带的多播会话信息，对所述UE的多播会话进行处理。
第六方面，本申请实施例还提供一种用户设备UE，包括存储器，收发机，处理器：
存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行以下操作：
向第一AMF发送第一请求，所述第一请求为业务请求消息或注册请求消息；
接收所述第一AMF发送的所述第一请求的响应消息，所述第一请求的响应消息为注册接受消息或业务接受消息，所述第一请求的响应消息中包含接受UE加入或离开第一多播会话的信息，或，指示所述UE离开第一多播会话的信息，或，拒绝所述UE加入第一多播会话的信息；
根据所述第一请求的响应消息，对所述第一多播会话进行处理。
可选地，所述第一请求中携带多播会话信息，所述多播会话信息包含第一多播会话标识和指示信息，所述第一多播会话为所述UE已加入的多播会话或请求加入的多播会话，所述指示信息用于指示所述UE保持加入、离开或请求加入所述第一多播会话。
可选地，所述根据所述第一请求的响应消息，对所述第一多播会话进行处理，包括：
若第一请求的响应消息中携带接受所述UE加入所述第一多播会话的信息，则存储所述第一多播会话的上下文；
若第一请求的响应消息中携带拒绝所述UE加入所述第一多播会话的信息或指示所述UE离开所述第一多播会话的信息，则删除所述第一多播会话的上下文。
可选地，所述接收所述第一AMF发送的所述第一请求的响应消息，包括：
接收无线接入网络功能实体转发的所述第一AMF发送的所述第一请求的响应消息；
所述处理器还用于读取所述存储器中的计算机程序并执行以下操作：
若所述第一请求的响应消息中携带接受所述UE加入所述第一多播会话的信息，则建立或更新所述第一多播会话的资源；
利用所述资源接收所述第一多播会话的业务数据。
可选地，所述利用所述资源接收所述第一多播会话的业务数据，包括：
若无线接入网络功能实体不支持多播业务，则利用所述资源，通过单播方式接收所述第一多播会话的业务数据；
若无线接入网络功能实体支持多播业务，则利用所述资源，通过多播方式接收所述第一多播会话的业务数据。
第七方面，本申请实施例还提供一种多播会话处理装置，包括：
第一接收单元，用于接收用户设备UE发送的第一请求，所述第一请求为注册请求消息或业务请求消息；
第一获取单元，用于根据所述第一请求获取所述UE的多播会话信息；
执行单元，用于根据所述多播会话信息，执行与多播会话相关的处理操作。
第八方面，本申请实施例还提供一种多播会话处理装置
第二接收单元，用于接收第一AMF发送的第二请求，所述第二请求中携带用户设备UE的多播会话信息，所述多播会话信息是所述第一AMF在接收到所述UE发送的第一请求之后获取的，所述第一请求为注册请求消息或业务请求消息；
第一处理单元，用于根据所述第二请求中携带的多播会话信息，对所述UE的多播会话进行处理。
第九方面，本申请实施例还提供一种多播会话处理装置
第三发送单元，用于向第一AMF发送第一请求，所述第一请求为业务请求消息或注册请求消息；
第三接收单元，用于接收所述第一AMF发送的所述第一请求的响应消息，所述第一请求的响应消息为注册接受消息或业务接受消息，所述第一请求的响应消息中包含接受UE加入或离开第一多播会话的信息，或，指示所述UE离开第一多播会话的信息，或，拒绝所述UE加入第一多播会话的信息；
第二处理单元，用于根据所述第一请求的响应消息，对所述第一多播会话进行处理。
第十方面，本申请实施例还提供一种处理器可读存储介质，所述处理器可读存储介质存储有计算机程序，所述计算机程序用于使所述处理器执行如上所述第一方面、第二方面和第三方面所述的多播会话处理方法的步骤。
第十一方面，本申请实施例还提供一种计算机可读存储介质，所述计算机读存储介质存储有计算机程序，所述计算机程序用于使所述处理器执行如上所述第一方面、第二方面和第三方面所述的多播会话处理方法的步骤。
本申请实施例提供的多播会话处理方法、网络功能实体、装置及存储介质，通过注册请求或业务请求实现用户设备UE与网络间多播会话状态的同步，减少了UE处理多播会话业务所需要的信令交互，提高了信令效率，节省了信令资源，同时缩短了UE加入或离开多播会话以及接收或传输多播会话数据的时间。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍，显而易见地，下面描述中的附图是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是现有技术提供的UE加入多播会话的流程示意图；
图2是本申请实施例提供的多播会话处理方法的流程示意图之一；
图3是本申请实施例提供的多播会话处理方法的流程示意图之二；
图4是本申请实施例提供的多播会话处理方法的流程示意图之三；
图5是本申请实施例提供的多播会话处理方法的流程示意图之四；
图6是本申请实施例提供的多播会话处理方法的流程示意图之五；
图7是本申请实施例提供的多播会话处理方法的流程示意图之六；
图8是本申请实施例提供的AMF网络功能实体的结构示意图；
图9是本申请实施例提供的SMF网络功能实体的结构示意图；
图10是本申请实施例提供的用户设备UE的结构示意图；
图11是本申请实施例提供的多播会话处理装置的结构示意图之一；
图12是本申请实施例提供的多播会话处理装置的结构示意图之二；
图13是本申请实施例提供的多播会话处理装置的结构示意图之三。
具体实施方式
网际互连协议(Internet Protocol，IP)网络中采用的数据集传输方式包括单播、多播与广播。多播/广播(Multicast/Broadcast)是指“一对多通信”，即相同的数据，通过共享信道和内容复制等技术，由一个发送设备发送到多个接收设备。与单播相比，多播/广播具有更高的网络资源使用效率。
第5代移动通信系统(the 5th generation mobile communication system，5G system)是继第4代移动通信系统(the 4th generation mobile communication system，4G system)后的新一代无线移动通信系统，提供更大的传输带宽、支持更多的终端数目和更多的业务类型。目前5GS支持单播传输。为了支持更多业务，例如IPv4/IPv6多播/广播、交互式网络电视，或优化现有业务(例如组通信、物联网通信(Internet of Things，IoT)、车辆网通信(vehicle to everything，V2X)、软件下载/更新等)的传输效率和网络资源使用效率，5GS将支持多播和广播业务(5G Multicast Broadcast Service，5G MBS)。
用户设备UE需要通过加入多播会话来接收特定的多播业务数据。现有技术中，UE通过协议数据单元(Protocol Data Unit，PDU)会话修改流程请求加入特定的多播会话，核心网(Core Network，CN)网络功能实体，例如会话管理功能(Session Management Function，SMF)、多播广播会话管理功能(Multicast Broadcast Session Management Function，MB-SMF)，基于该请求将UE加入该多播会话，并建立核心网网关，例如多播广播用户平面功能(Multicast Broadcast User Plane Function，MB-UPF)与无线接入网(Wireless Access Network，RAN)之间的多播传输隧道，从而将该多播会话的数据发送给UE。
图1是现有技术提供的UE加入多播会话的流程示意图，如图1所示，UE处于空闲态，即UE与RAN节点之间没有建立信令连接与数据承载，或非激活态，即UE与CN之间没有建立信令连接与数据承载。当UE发生移动 或者其他原因，例如网络切片发生变化，服务于UE的RAN节点甚至核心网CN节点，例如接入与移动性管理功能(Access and Mobility Management Function，AMF)发生改变时，由于新的RAN节点和/或CN节点中没有UE的多播会话信息，那么：
若UE希望继续接收该多播会话的数据或离开该多播会话，即停止接受该多播会话相关的寻呼消息和数据，UE需要首先通过注册更新或业务请求流程进入连接态，再发起PDU会话修改流程来请求加入或离开之前加入过的多播会话。
若上述步骤不执行，当网络需要发送多播会话数据给UE时，由于UE处于空闲态或非激活态，网络需要寻呼UE，UE通过业务请求或注册更新流程响应寻呼，然后：UE发起PDU会话修改流程来请求加入或离开之前加入过的多播会话，或CN直接向UE发起多播会话建立过程，UE接受或拒绝。
处于空闲(IDLE)态或者非激活态的UE在接入的网络节点发生改变时，需要与网络进行较多的信令交互，先完成注册更新或业务请求流程，再发起PDU会话修改流程。前述步骤完成后才能接收多播会话，包括之前加入的多播会话的数据，或离开多播会话，即停止接受该多播会话相关寻呼的消息和数据。
由于现有技术中的上述问题，本申请实施例提供了一种多播会话处理方法、网络功能实体、装置及存储介质。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，并不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
图2是本申请实施例提供的多播会话处理方法的流程示意图之一，如图2所示，本申请实施例提供一种多播会话处理方法，其执行主体为第一AMF，该方法包括：
步骤201、接收用户设备UE发送的第一请求，所述第一请求为注册请求消息或业务请求消息。
具体来说，第一AMF接收用户设备UE发送的注册请求消息或业务请求消息。
UE在一定条件下，例如移动到新的注册区域(Registration Area)、请求更新UE能力或请求网络信息时，向网络发送注册请求(Registration Request)消息，请求注册更新；或者发送业务请求(Service Request)消息，请求业务更新。
处于IDLE态或者CONNECTED态的UE通过移动性注册更新到注册区域，或者UE初始化注册到5G系统时；或者UE发起周期性注册时；或者UE需要更新通过注册流程协商的能力和协议参数时，发起注册请求流程。
处于IDLE态的UE主要是为了发送上行信令消息，用户数据，或者应答一个网络寻呼请求发起业务请求流程。接收业务请求消息后，AMF可执行认证身份。与AMF建立信令连接后，UE或者网络可以发送信令消息，比如从UE到SMF，经由AMF的PDU会话建立请求。
可选地，在UE移动的过程中，服务于UE的AMF可能发生变化，如果服务于UE的AMF发生变化，那么这里的第一AMF可以为UE发生移动之后为UE提供服务的网络功能实体。
步骤202、根据所述第一请求获取所述UE的多播会话信息。
具体来说，根据第一请求获取UE的多播会话信息。
第一种情况，UE在发送第一请求时，在第一请求中携带有UE的多播会话信息，那么第一AMF可以直接从第一请求中获取UE的多播会话信息。
第二种情况，由于UE移动导致服务于UE的AMF发生变化，那么UE向发生变化后的第一AMF发送第一请求，该第一请求可以为注册请求，请求更新UE能力或请求网络信息。此时，第一AMF将根据第一请求，确定UE移动之前为UE提供服务的第二AMF，并从第二AMF中获取UE的上下文，第二AMF将在返回的UE的上下文中携带UE的多播会话信息。
具体地，第一AMF向为UE提供服务的其它网络功能实体发送UE上下文(UE Context)请求，从而获取UE的多播会话信息。为UE提供服务的网络功能实体可以是UE发生移动前服务于UE的AMF，即第二AMF，也可以 是统一数据管理功能(Unified Data Management，UDM)，该网络功能实体向第一AMF提供UE上下文，该UE上下文中携带有UE已加入的多播会话信息(Multicast Session Message)。
第三种情况，UE在发送第一请求时，在第一请求中携带有多播会话信息，同时由于UE移动导致服务于UE的AMF发生变化，第一AMF向第二AMF或者UDM请求UE上下文，而在第二AMF或者UDM返回的UE上下文中携带有UE已加入的多播会话信息。如果UE没有请求加入新的多播会话，则UE上下文中的多播会话信息和第一请求中携带的多播会话信息内容可能是一致的。第一AMF可以在第一请求中获取UE的多播会话信息，第一AMF也可以从第二AMF或者UDM的UE上下文响应消息中获取UE的多播会话信息。
如果UE请求加入新的多播会话，则UE上下文中携带的多播会话信息为UE已加入的多播会话信息，第一请求中携带有UE请求加入的多播会话信息。第一AMF根据第一请求和UE上下文确定得到UE完整的多播会话信息。
步骤203、根据所述多播会话信息，执行与多播会话相关的处理操作。
具体来说，根据多播会话信息，执行与多播会话相关的处理操作。
在第一AMF获取到UE的多播会话信息后，执行后续的注册请求流程或者业务请求流程，同步完成多播会话业务的处理。多播会话相关的业务包括接收/传输多播会话数据、指示UE离开/加入多播会话等。
具体地，在第一AMF接收UE发送的第一请求后，向UE发送第一请求的响应消息。第一请求的响应消息为注册接受消息或业务接受消息，同时包括：
在UE请求保持加入第一多播会话的情况下，第一请求的响应消息中包括接受UE保持加入第一多播会话的信息；UE根据该第一请求的响应消息更新第一多播会话的上下文；
在UE请求保持加入第一多播会话的情况下，第一请求的响应消息中包括指示UE离开第一多播会话的信息；UE根据该第一请求的响应消息删除第一多播会话的上下文；
在UE请求离开第一多播会话的情况下，第一请求的响应消息中包括指示UE离开第一多播会话的信息；UE根据该第一请求的响应消息删除第一多播会话的上下文；
在UE请求加入第一多播会话的情况下，第一请求的响应消息中包括接受UE加入第一多播会话的信息；UE根据该第一请求的响应消息生成第一多播会话的上下文；
在UE请求加入第一多播会话的情况下，第一请求的响应消息中包括拒绝UE加入第一多播会话的信息；UE根据该第一请求的响应消息确定不加入第一多播会话。
本申请实施例提供的多播会话处理方法，通过注册请求或业务请求实现用户设备UE与网络间多播会话状态的同步，减少了UE处理多播会话业务所需要的信令交互，提高了信令效率，节省了信令资源，同时缩短了UE加入或离开多播会话以及接收或传输多播会话数据的时间。
可选地，若所述第一请求中携带所述UE的多播会话信息，则所述根据所述第一请求获取所述UE的多播会话信息，包括：
从所述第一请求中获取所述UE的多播会话信息。
具体来说，第一请求中携带的UE的多播会话信息中包括以下至少一项：
(1)一个或多个多播会话标识(Multicast Broadcast Session Identity，MBS session ID)，可以是UE请求加入的多播会话标识，也可以是UE已经加入的多播会话标识；
(2)服务于多播会话的网络功能(Network Function，NF)的信息，例如MB-SMF ID；
(3)多播会话关联的PDU会话的标识；
(4)对于UE已经加入的多播会话，UE是否保持加入状态的指示multicast session status：1表示UE仍然加入该会话；0表示UE离开该会话；
(5)对于UE请求加入的新的多播会话，加入请求指示以及多播会话对应的数据网络名称(Data Network Name，DNN)和/或单一网络切片选择辅助信息(Single Network Slice Selection Assistance Information，S-NSSAI)。
例如，假设第一请求中携带的多播会话信息中包括ID1。其中，ID1对应的多播会话为UE保持加入的多播会话。相对应的，在第一请求中还将携带多播会话状态指示，该指示可以为1，即表示UE仍然加入该会话ID1；也可以为0，表示UE离开该会话ID1。
再例如：假设第一请求中携带的多播会话信息中还包括ID2。其中，ID2对应的多播会话为UE请求加入的多播会话。相应的，在第一请求中还将携带该多播会话对应的DNN和S-NSSAI，以便于网络侧根据DNN和S-NSSAI确定是否有允许该UE加入该会话ID2。
可选地，所述根据所述第一请求获取所述UE的多播会话信息，包括：
基于所述第一请求，从第二AMF中获取所述UE的多播会话信息，所述第二AMF为所述UE发生移动之前为所述UE提供服务的AMF；所述第一AMF为所述UE发生移动之后为所述UE提供服务的AMF。
具体来说，第一AMF在接收到UE的注册请求消息或业务请求消息后，根据UE标识确定UE发生移动前为UE提供服务的第二AMF，向第二AMF发送UE上下文传输请求。
第二AMF向第一AMF发送UE上下文传输请求的响应消息，该响应消息中携带UE上下文，使得第一AMF能够获取到UE的多播会话信息。UE上下文中包含以下至少一项信息：
(1)一个或多个多播会话标识；
(2)服务于多播会话的网络功能的信息，例如MB-SMF ID；
(3)UE当前已建立的PDU会话信息.其中，PDU会话信息中包括：PDU会话标识，服务于PDU会话的SMF的信息；对于与多播会话关联的PDU会话，PDU会话信息中还包括该多播会话的标识。
可选地，所述多播会话信息包含第一多播会话标识和/或指示信息，所述指示信息用于指示所述UE保持加入、离开或请求加入所述第一多播会话，所述第一多播会话为所述UE已加入的多播会话或请求加入的多播会话。
具体来说，UE的多播会话信息包括第一多播会话标识和/或指示信息。其中，UE的多播会话信息中包括一个或多个第一多播会话标识。
在UE没有请求加入新的多播会话时，第一多播会话为UE已经加入的多播会话；在UE请求加入新的多播会话时，第一多播会话可以为UE请求加入的多播会话，也可以为UE已经加入的多播会话和UE请求加入的多播会话。
在UE请求加入新的多播会话，以及请求保持加入或离开已加入的多播会话时，UE的多播会话信息中包括多播会话标识，还包括指示信息。指示信息用于指示UE请求加入新的多播会话，或者指示UE保持加入已经加入的多播会话，或者指示UE离开已经加入的多播会话。
对于UE已加入的多播会话，在UE请求保持加入该多播会话且该UE在该多播会话的服务区域时，UE的多播会话信息中可以不包括指示UE保持加入多播会话的指示信息，不对该多播会话进行处理。
可选地，所述根据所述多播会话信息，执行与多播会话相关的处理操作，包括：
确定服务于第一多播会话的第一网络功能实体，其中，所述第一网络功能实体包括：会话管理功能SMF或多播广播会话管理功能MB-SMF；
向所述第一网络功能实体发送第二请求，所述第二请求中携带所述多播会话信息；
接收所述第一网络功能实体发送的第二请求的响应消息。
具体来说，第一AMF确定服务于第一多播会话的SMF或者MB-SMF，向SMF或者MB-SMF发送多播会话发送第二请求，第二请求中携带有UE的多播会话信息，然后接收SMF或者MB-SMF的响应消息。
其中，第二请求用于请求更新多播会话信息。
第一AMF根据多播会话信息和/或UE上下文，确定与第一多播会话关联的PDU会话，以及服务于该PDU会话的SMF。
第一AMF向SMF发送PDU会话更新管理上下文请求，该PDU会话更新管理上下文请求中携带多播会话信息，还可以携带UE位置信息，例如UE所在的小区标识(Cell ID)或跟踪区域标识TAI。
SMF向MB-SMF请求多播会话信息更新，该请求消息中可以携带AMF标识、RAN节点标识。MB-SMF将AMF标识和RAN节点标识更新到多播 会话上下文中。MB-SMF向SMF发送多播会话信息更新的响应消息，该响应消息中包括MBS Session ID和以下至少一项信息：
服务质量(Quality of Service，QoS)信息、下行隧道标识(Down Link Tunnel ID)、多播地址(Multicast Address)等。
SMF依据MB-SMF的响应，更新多播会话信息，并更新多播会话关联的PDU会话的信息，例如：若多播服务质量流(QoS Flow)的QoS规则和/或QoS参数发生变化，SMF相应更新映射的单播QoS Flow的QoS规则和/或QoS参数。
SMF向第一AMF发送PDU会话更新管理上下文请求响应消息。
对于UE上下文中确定的服务于多播会话的MB-SMF ID，第一AMF向MB-SMF ID指示的MB-SMF发送多播会话更新请求，该请求消息中携带MBS Session ID和RAN节点标识，还可以包括RAN隧道信息。
MB-SMF根据接收到的多播会话信息更新请求，配置MB-UPF,并将AMF ID、RAN node ID更新到多播会话上下文中。MB-SMF向第一AMF发送多播会话请求响应消息。
可选地，所述接收所述第一网络功能实体发送的第二请求的响应消息，包括：
接收所述第一网络功能实体发送的携带所述第一多播会话标识和资源分配请求信息的第二请求的响应消息；
所述方法还包括：
根据所述第二请求的响应消息，向无线接入网络功能实体发送第三请求，所述第三请求中携带第一多播会话标识和所述资源分配请求信息，以使所述无线接入网络功能实体建立或更新所述第一多播会话的资源。
具体来说，第一AMF接收第一网络功能实体发送的第二请求的响应消息，第二请求的响应消息中携带第一多播会话标识和资源分配请求信息；根据第二请求的响应消息，向RAN发送第三请求，用于建立或更新第一多播会话的资源。
在第一网络功能实体为SMF的情况下，SMF向第一AMF发送PDU会 话更新会话管理上下文响应消息，该响应消息中携带MBS Session ID、MB-SMF ID，并且在给RAN的N2信息中携带多播会话的信息，包括MBS Session ID、关联的PDU会话的信息和以下至少一项信息：QoS信息；公共下行隧道标识(Common Down Link Tunnel ID)；多播地址(Multicast Address)等。
对于在特定区域提供的多播业务，SMF可以根据UE位置信息和第一多播会话的服务区域，判断UE当前是否在第一多播会话的服务区域。
若UE不在第一多播会话的服务区域内，则SMF要求UE离开第一多播会话，即：在给第一AMF的响应消息中携带PDU会话修改指示消息，该指示消息中携带第一多播会话标识和指示UE离开第一多播会话的信息。
对于指示UE离开的第一多播会话:
SMF更新第一多播会话关联的PDU会话的信息，即：将该MBS Session ID和映射的单播QoS信息从该PDU会话上下文中删除；若SMF保存了加入第一多播会话的UE列表，SMF将该UE ID从该UE列表中删除；
SMF给第一AMF的响应消息中不携带MB-SMF ID，给RAN的N2信息中也不携带第一多播会话的信息。
在第一网络功能实体为MB-SMF的情况下，MB-SMF根据接收到的多播会话信息更新请求，配置MB-UPF，并将AMF ID、RAN node ID更新到多播会话上下文中。
MB-SMF向AMF发送多播会话信息更新请求响应消息，该响应消息中携带提供给RAN的多播会话信息，包括MBS Session ID和以下至少一项：
QoS信息；公共下行隧道标识(Common Down Link Tunnel ID)；多播地址(Multicast Address)等。
第一AMF将上述提供给RAN的多播会话信息通过N2接口发送给RAN，RAN向UE发送资源分配请求消息，在第一多播会话的资源未建立的情况下，建立用于第一多播会话的资源；在第一多播会话的资源已建立的情况下，更新用于第一多播会话的资源。
如果RAN支持多播业务，则UE利用第一多播会话的资源，通过多播方 式接收第一多播会话的业务数据。
如果RAN不支持多播业务，则UE利用第一多播会话的资源，通过单播方式接收第一多播会话的业务数据。
可选地，所述第二请求的响应消息携带第一多播会话标识和以下信息：
指示所述UE离开所述第一多播会话的信息；或，
拒绝所述UE加入所述第一多播会话的信息。
具体来说，在第一网络功能实体发送给第一AMF的第二请求的响应消息中携带第一多播会话标识，以及指示UE离开或者拒绝UE加入第一多播会话的信息。
在第一多播会话为UE已加入的多播会话的情况下，多播会话信息中携带指示UE保持加入或离开第一多播会话的信息。
在第一多播会话为UE请求加入的新的多播会话的情况下，多播会话信息中携带指示UE请求加入第一多播会话的信息。
对于在特定区域提供的多播业务，SMF可以根据UE位置信息和多播会话的服务区域(MBS Service Area)，判断UE当前是否在多播会话服务区。
对于UE请求保持加入的第一多播会话，若UE不在第一多播会话的服务区域内，则SMF确定UE不能保持加入第一多播会话，则第二请求的响应消息中携带指示所述UE离开第一多播会话的信息，例如第一多播会话标识和离开指示。
SMF更新第一多播会话关联的PDU会话的信息，即：将第一多播会话标识和映射的单播QoS信息从该PDU会话上下文中删除；若SMF保存了加入第一多播会话的UE列表，SMF将该UE ID从该UE列表中删除。
若UE在第一多播会话的服务区域内，SMF确定接受UE保持加入第一多播会话，则第一AMF可以将服务于UE的新的RAN节点信息，例如RAN节点标识添加到多播会话上下文中。
对于UE请求加入的第一多播会话，若UE不在第一多播会话的服务区域内，则SMF拒绝UE加入第一多播会话，在给第一AMF的第二请求的响应消息中携带第一多播会话标识和拒绝UE加入第一多播会话的指示信息。
若UE在第一多播会话的服务区域内，且SMF确定接受UE加入第一多播会话，SMF将UE标识添加至第一多播会话的UE列表中。第二请求的响应消息中携带接受UE加入第一多播会话的信息。
可选地，所述方法还包括：
向无线接入网络功能实体发送第三请求，所述第三请求中携带第一多播会话标识和指示所述UE离开所述第一多播会话的信息，以使所述无线接入网络功能实体从所述第一多播会话的上下文中删除所述UE的标识。
具体来说，第一AMF在接收到SMF或MB-SMF发送的第二请求的响应消息之后，通过N2接口向RAN发送第三请求。第三请求中携带多播会话信息和注册/业务接受消息，还携带PDU会话修改指示消息。
PDU会话修改指示消息中携带第一多播会话标识和指示UE离开第一多播会话的信息。
对于指示UE离开的多播会话，SMF更新多播会话关联的PDU会话的信息，即：将第一多播会话标识和映射的单播服务质量信息从PDU会话上下文中删除；若SMF保存了加入第一多播会话的UE列表，SMF将UE标识从UE列表中删除。
则SMF给第一AMF的响应消息携带指示所述UE离开第一多播会话的信息，例如第一多播会话标识和离开指示。
第一AMF向RAN发送的第三请求，RAN将第三请求中的信息转发给UE，UE根据第一多播会话标识和指示UE离开第一多播会话的信息确定离开第一多播会话，即：删除UE中多播会话的上下文。
可选地，所述多播会话信息还包括以下至少一项标识信息：
第一多播会话关联的协议数据单元PDU会话的标识；
服务于所述第一多播会话的MB-SMF的标识和/或SMF的标识；
所述确定服务于第一多播会话的第一网络功能实体，包括：
依据所述至少一项标识信息,确定服务于所述第一多播会话的第一网络功能实体。
具体来说，本申请实施例中多播会话信息除包括第一多播会话标识和/或 指示信息外，还包括：
第一多播会话关联的PDU会话的标识；
服务于第一多播会话的网络功能的信息，例如MB-SMF的标识和/或SMF的标识。
第一AMF根据UE发送的第一请求中的多播会话信息和/或UE上下文中的多播会话信息，确定与第一多播会话关联的PDU会话，以及服务于该PDU会话的SMF。
具体包括：
若UE发送的第一请求中包含第一多播会话关联的PDU会话的标识，则选择该PDU会话标识指示的PDU会话，以及服务于该PDU会话的SMF；
若UE上下文中某PDU会话信息包含多播会话信息，则选择该PDU会话，以及服务于该PDU会话的SMF；
若UE上下文中的所有PDU会话的信息中都不包含多播会话信息，则根据UE注册请求中的多播会话对应的DNN和/或S-NSSAI，选择属于该DNN和/或S-NSSAI的一个PDU会话作为多播会话关联的PDU会话，以及服务于该PDU会话的SMF。
若UE上下文中包含服务于第一多播会话的MB-SMF的标识，第一AMF可以根据该MB-SMF的标识，确定服务于所述第一多播会话的MB-SMF。
本申请实施例提供的多播会话处理方法，通过注册请求或业务请求实现用户设备UE与网络间多播会话状态的同步，减少了UE处理多播会话业务所需要的信令交互，提高了信令效率，节省了信令资源，同时缩短了UE加入或离开多播会话以及接收或传输多播会话数据的时间。
图3是本申请实施例提供的多播会话处理方法的流程示意图之二，如图3所示，本申请实施例提供一种多播会话处理方法，其执行主体为SMF，该方法包括：
步骤301、接收第一AMF发送的第二请求，所述第二请求中携带用户设备UE的多播会话信息，所述多播会话信息是所述第一AMF在接收到所述UE发送的第一请求之后获取的，所述第一请求为注册请求消息或业务请求消 息。
步骤302、根据所述第二请求中携带的多播会话信息，对所述UE的多播会话进行处理。
本申请实施例提供的多播会话处理方法，通过注册请求或业务请求实现用户设备UE与网络间多播会话状态的同步，减少了UE处理多播会话业务所需要的信令交互，提高了信令效率，节省了信令资源，同时缩短了UE加入或离开多播会话以及接收或传输多播会话数据的时间。
可选地，所述多播会话信息包含第一多播会话标识和/或指示信息，所述指示信息用于指示所述UE保持加入、离开或请求加入所述第一多播会话，所述第一多播会话为所述UE已加入的多播会话或请求加入的多播会话。
可选地，所述根据所述第二请求中携带的多播会话信息，对所述UE的多播会话进行处理，包括：
若所述指示信息用于指示所述UE请求加入所述第一多播会话，且确定接受所述UE加入所述第一多播会话，则建立所述UE的标识与所述第一多播会话标识之间的对应关系；向所述第一AMF发送第二请求的响应消息，所述第二请求的响应消息中携带接受所述UE加入所述第一多播会话的信息；或，
若所述指示信息用于指示所述UE请求加入所述第一多播会话，且所述UE不在所述第一多播会话的服务区域内，则向所述第一AMF发送第二请求的响应消息，所述第二请求的响应消息中携带拒绝所述UE加入所述第一多播会话的信息；或，
若所述指示信息用于指示所述UE保持加入所述第一多播会话，且所述UE不在所述第一多播会话的服务区域内，则向所述第一AMF发送第二请求的响应消息，所述第二请求的响应消息中携带指示所述UE离开所述第一多播会话的信息；或，
若所述指示信息用于指示所述UE离开所述第一多播会话，则删除所述UE的标识与所述第一多播会话标识之间的对应关系。
可选地，所述根据所述第二请求中携带的多播会话信息，对所述UE的多播会话进行处理，包括：
若所述指示信息用于指示所述UE请求加入所述第一多播会话，且确定接受所述UE加入所述第一多播会话，则在所述第一多播会话的上下文中存储服务于所述UE的无线接入网络功能实体的标识。
在此需要说明的是，本申请实施例提供的上述以SMF为执行主体的多播会话处理方法，能够实现上述以第一AMF为执行主体的多播会话处理方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
图4是本申请实施例提供的多播会话处理方法的流程示意图之三，如图4所示，本申请实施例提供一种多播会话处理方法，其执行主体为UE，该方法包括：
步骤401、向第一AMF发送第一请求，所述第一请求为业务请求消息或注册请求消息。
步骤402、接收所述第一AMF发送的所述第一请求的响应消息，所述第一请求的响应消息为注册接受消息或业务接受消息，所述第一请求的响应消息中包含接受UE加入或离开第一多播会话的信息，或，指示所述UE离开第一多播会话的信息，或，拒绝所述UE加入第一多播会话的信息。
步骤403、根据所述第一请求的响应消息，对所述第一多播会话进行处理。
本申请实施例提供的多播会话处理方法，通过注册请求或业务请求实现用户设备UE与网络间多播会话状态的同步，减少了UE处理多播会话业务所需要的信令交互，提高了信令效率，节省了信令资源，同时缩短了UE加入或离开多播会话以及接收或传输多播会话数据的时间。
可选地，所述第一请求中携带多播会话信息，所述多播会话信息包含第一多播会话标识和指示信息，所述第一多播会话为所述UE已加入的多播会话或请求加入的多播会话，所述指示信息用于指示所述UE保持加入、离开或请求加入所述第一多播会话。
可选地，所述根据所述第一请求的响应消息，对所述第一多播会话进行处理，包括：
若第一请求的响应消息中携带接受所述UE加入所述第一多播会话的信息，则存储所述第一多播会话的上下文；
若第一请求的响应消息中携带拒绝所述UE加入所述第一多播会话的信息或指示所述UE离开所述第一多播会话的信息，则删除所述第一多播会话的上下文。
可选地，所述接收所述第一AMF发送的所述第一请求的响应消息，包括：
接收无线接入网络功能实体转发的所述第一AMF发送的所述第一请求的响应消息；
所述方法还包括：
若所述第一请求的响应消息中携带接受所述UE加入所述第一多播会话的信息，则建立或更新所述第一多播会话的资源；
利用所述资源接收所述第一多播会话的业务数据。
可选地，所述利用所述资源接收所述第一多播会话的业务数据，包括：
若无线接入网络功能实体不支持多播业务，则利用所述资源，通过单播方式接收所述第一多播会话的业务数据；
若无线接入网络功能实体支持多播业务，则利用所述资源，通过多播方式接收所述第一多播会话的业务数据。
在此需要说明的是，本申请实施例提供的上述以UE为执行主体的多播会话处理方法，能够实现上述以第一AMF为执行主体的多播会话处理方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
下面以具体的实施例对本申请提供的多播会话处理方法进行说明。
图5是本申请实施例提供的多播会话处理方法的流程示意图之四，如图5所示，本申请实施例提供一种多播会话处理方法，在注册过程中AMF触发多播会话在新的RAN节点建立时，该方法包括：
步骤501、UE在移动到新的注册区域(Registration Area)、请求更新U E能力或者请求网络信息等时，向网络发送注册请求Registration Request，请求注册更新。
步骤502、如果UE发生移动后服务于UE的网络功能实体发生变化，那么UE发生移动后服务于UE的新AMF判断自身有无UE的上下文(UE Co ntext)，根据UE标识确定UE移动前服务于UE的旧AMF，向旧AMF发送UE上下文传输请求Namf_Communication_UE Context Transfer。
步骤503、旧AMF向新AMF发送UE上下文传输请求的响应消息Namf_Communication_UEContextTransfer Response，该响应消息中携带UE已加入的多播会话信息，包括以下至少一项：
一个或多个多播会话标识MBS session ID；
服务于多播会话的网络功能NF，例如MB-SMF的信息，MB-SMF ID；
多播会话关联的PDU会话的标识Associated PDU Session ID。
步骤504、新AMF根据旧AMF提供的多播会话信息，生成或更新多播会话上下文。新AMF可以将服务于UE的新的RAN节点信息，例如RAN节点标识RAN Node ID添加到多播会话上下文中。
步骤505、新AMF根据UE上下文中PDU会话的信息，确定与多播会话关联的PDU会话，以及服务于该PDU会话的SMF。
新AMF向该SMF发送PDU会话更新会话管理上下文请求(Nsmf_PDU Session_Update Session Management Context)，该请求消息中携带多播会话信息，例如多播会话标识(MBS Session ID)，该请求消息中还可以携带UE位置信息，例如UE所在的小区标识(Cell ID)或跟踪区域标识TAI。
步骤506、SMF向MB-SMF请求多播会话信息更新，该请求消息中可以携带AMF标识、RAN节点标识。
步骤507、MB-SMF将AMF标识和RAN节点标识更新到多播会话上下文中。
步骤508、MB-SMF向SMF发送多播会话信息更新的响应消息，该响应消息中包括MBS Session ID和以下至少一项信息：
服务质量(Quality of Service，QoS)信息、下行隧道标识(Down Link Tunnel ID)、多播地址(Multicast Address)等。
步骤509、SMF依据MB-SMF的响应，更新本地的多播会话信息，并更 新多播会话关联的PDU会话的信息，例如：若多播服务质量流(QoS Flow)的QoS规则和/或QoS参数发生变化，SMF相应更新映射的单播QoS Flow的QoS规则和/或QoS参数。
步骤5010、SMF向新AMF发送PDU会话更新会话管理上下文响应消息(Nsmf_PDUSession_Update Session Management Context response)，该响应消息中携带MBS Session ID、MB-SMF ID，并且在给RAN的N2信息中携带多播会话的信息，包括MBS Session ID、关联的PDU会话的信息和以下至少一项：
QoS信息；公共下行隧道标识(Common Down Link Tunnel ID)；多播地址(Multicast Address)等。
对于仅在特定区域提供的多播业务，SMF可以根据UE位置信息和多播会话的服务区域(MBS Service Area)，判断UE当前是否在多播会话服务区。
若UE不在多播会话的服务区域内，则SMF要求UE离开该多播会话，即：在给新AMF的响应消息中携带PDU会话修改指示(PDU Session Modification Command)消息，该指示消息中携带多播会话标识(MBS Session ID)和指示UE离开该多播会话的信息。
对于指示UE离开的多播会话:
SMF更新多播会话关联的PDU会话的信息，即：将该MBS Session ID和映射的单播QoS信息从该PDU会话上下文中删除；若SMF保存了加入该多播会话的UE列表，SMF将该UE ID从该UE列表中删除；
SMF给新AMF的响应消息中不携带MB-SMF ID，给RAN的N2信息中也不携带该多播会话的信息。
步骤506-509、5011、5014-5019不执行。
步骤5011、若步骤504未执行，新AMF可以在此时生成或更新多播会话上下文。新AMF可以将服务于该UE的新的RAN节点信息，例如RAN节点标识，也添加到该多播会话上下文中。
步骤5012、新AMF向RAN发送N2消息，该N2消息中携带步骤5010的Nsmf_PDUSession_Update Session Management Context response中包含的 多播会话的信息，以及注册接受(Registration Accept)消息，该N2消息中还可以携带PDU Session Modification Command消息。
步骤5013、RAN将注册接受消息转发给UE。RAN还可以将PDU Session Modification Command消息转发给UE，UE根据该消息中的MBS Session ID和指示UE离开多播会话的信息确定离开该多播会话，即：删除UE中该多播会话的上下文。对于其它多播会话，UE保留或更新UE中该多播会话的上下文。
步骤5014、若RAN支持多播业务，RAN依据接收到的多播会话的信息，向AMF发送N2消息，该N2消息中携带MBS Session ID，还可以携带RAN隧道信息。
步骤5015、AMF向步骤503或步骤5010中MB-SMF ID指示的MB-SMF发送多播会话信息更新请求，该请求消息中携带MBS Session ID和RAN Node ID，还可以携带RAN隧道信息。
步骤5016、MB-SMF根据接收到的多播会话信息更新请求，配置MB-UPF，并将AMF ID、RAN node ID更新到多播会话上下文中。
步骤5017、MB-SMF向AMF发送多播会话信息更新请求响应消息，该响应消息中携带提供给RAN的多播会话的信息，包括MBS Session ID和以下至少一项：
QoS信息；公共下行隧道标识(Common Down Link Tunnel ID)；多播地址(Multicast Address)等。
其中，QoS信息、公共下行隧道标识(Common Down Link Tunnel ID)和多播地址(Multicast Address)可以通过步骤5010、5012或步骤5017、5018发送给RAN。
步骤5018、AMF向NG-RAN节点发送N2消息，该N2消息中携带步骤5017中MB-SMF提供的多播会话的信息。
步骤5019、RAN向UE发送资源分配请求消息，在多播会话的资源未建立的情况下，建立用于多播会话的资源。若RAN不支持多播业务，则RAN为多播会话关联的PDU会话建立多播QoS flow映射的单播QoS flow的资源， 通过单播方式将多播业务数据传输给UE。
图6是本申请实施例提供的多播会话处理方法的流程示意图之五，如图6所示，本申请实施例提供一种多播会话处理方法，在UE连接到新的RAN后保持加入或离开已经加入的多播会话时，该方法包括：
步骤601、UE在移动到新的注册区域(Registration Area)、请求更新UE能力或者请求网络信息等时，向网络发送注册请求Registration Request，请求注册更新。注册请求中携带UE已加入的多播会话信息，该多播会话信息包括一个或多个多播会话标识，还可以包括：
对于每个多播会话，UE是否保持加入状态的指示(Multicast Session Status)：1表示UE保持加入该多播会话；0表示UE离开该多播会话；
多播会话关联的PDU会话的标识(Associated PDU Session ID)。
步骤602、如果UE发生移动后服务于UE的网络功能实体发生变化，那么UE发生移动后服务于UE的新AMF判断自身有无UE的上下文(UE Co ntext)，根据UE标识确定UE移动前服务于UE的旧AMF，向旧AMF发送UE上下文传输请求Namf_Communication_UE Context Transfer。
步骤603、旧AMF向新AMF发送UE上下文传输请求的响应消息Namf_Communication_UEContextTransfer Response，该响应消息中携带UE的上下文。UE的上下文中包含UE当前已建立的PDU会话信息，该PDU会话信息中包含PDU会话标识以及服务于PDU会话的SMF的信息。对于多播会话关联的PDU会话，PDU会话信息中还包含多播会话标识。
步骤604、新AMF根据UE注册请求中的多播会话信息和UE的上下，生成或更新多播会话上下文。新AMF可以将服务于UE的新的RAN节点信息，例如RAN节点标识RAN Node ID添加到多播会话上下文中。
步骤605、新AMF根据UE上下文，确定与多播会话关联的PDU会话，以及服务于该PDU会话的SMF。
新AMF向该SMF发送PDU会话更新会话管理上下文请求(Nsmf_PDUSession_Update Session Management Context)，该请求消息中携带多播会话信息，包括至少一个多播会话标识，还可以包括对于每个多播会 话，UE保持加入还是离开的状态指示(multicast session status)。该请求消息中还可以携带UE位置信息，例如UE所在的小区标识(Cell ID)或跟踪区域标识TAI。
步骤606-609、同步骤506-509。
步骤6010、与步骤5010的内容基本相同，不同点在于其中对于multicast session status为0的多播会话，SMF向新AMF发送PDU会话更新会话管理上下文响应消息中将该多播会话的multicast session status置为0。
对于仅在特定区域提供的多播业务，SMF可以根据UE位置信息和多播会话的服务区域(MBS Service Area)，判断UE当前是否在多播会话服务区。
若UE不在多播会话的服务区域内，则SMF拒绝UE保持加入该多播会话的请求，即在PDU会话更新会话管理上下文响应消息中将该多播会话的multicast session status置为0。
对于multicast session status为0的多播会话：
SMF更新多播会话关联的PDU会话的信息，即：将该MBS Session ID和映射的单播QoS信息从该PDU会话上下文中删除；若SMF保存了加入该多播会话的UE列表，SMF将该UE ID从该UE列表中删除；
SMF给新AMF的响应消息中不携带MB-SMF ID，给RAN的N2信息中也不携带该多播会话的信息。
步骤606-609、6011、6014-6019不执行。
步骤6011、同步骤5011。
步骤6012-6013、与步骤5012-5013的内容基本相同，不同点在于：
Registration Accept消息中携带MBS Session ID和Multicast Session Status。对于Multicast Session Status为0的多播会话，若UE尚未离开该多播会话，则UE离开该多播会话，即：删除UE中该多播会话的上下文。对于multicast session status为1的多播会话，UE保留或更新UE中该多播会话的上下文。
AMF向RAN发送的N2消息中不携带PDU Session Modification Command消息，故而RAN也不会向UE发送PDU Session Modification  Command消息。
步骤6014-6019、同步骤5014-5019。
图7是本申请实施例提供的多播会话处理方法的流程示意图之六，如图7所示，本申请实施例提供一种多播会话处理方法，在UE连接到新的RAN后请求加入新的多播会话时，该方法包括：
步骤701、UE在移动到新的注册区域(Registration Area)、请求更新UE能力或者请求网络信息等时，向网络发送注册请求Registration Request，请求注册更新。该请求消息中携带UE请求加入的多播会话的信息，包括一个或多个多播会话标识、加入请求指示，还可以包括多播会话关联的PDU会话标识、多播会话对应的DNN和/或S-NSSAI信息。
步骤702、如果UE发生移动后服务于UE的网络功能实体发生变化，那么UE发生移动后服务于UE的新AMF判断自身有无UE的上下文(UE Context)，根据UE标识确定UE移动前服务于UE的旧AMF，向旧AMF发送UE上下文传输请求Namf_Communication_UE Context Transfer。
步骤703、旧AMF向新AMF发送UE上下文传输请求的响应消息Namf_Communication_UEContextTransfer Response，该响应消息中携带UE上下文。UE上下文中包含UE当前已建立的PDU会话信息，包括:PDU Session ID、服务于PDU会话的SMF的信息，还可能包含多播会话的信息，例如MBS Session ID。
步骤704、新AMF根据旧AMF提供的多播会话信息，生成或更新多播会话上下文。新AMF可以将服务于UE的新的RAN节点信息，例如RAN节点标识RAN Node ID添加到多播会话上下文中。
步骤705、新AMF根据UE注册请求中的多播会话的信息和/或UE上下文信息，确定与多播会话关联的PDU会话，以及服务于该PDU会话的SMF。具体地，按以下方式进行确定：
若UE注册请求中包含多播会话关联的PDU会话标识，则选择该PDU会话，以及服务于该PDU会话的SMF；
若UE上下文中某PDU会话的信息包含多播会话信息，则选择该PDU 会话，以及服务于该PDU会话的SMF；
若UE上下文中所有PDU会话的信息中都不包含多播会话信息，则根据UE注册请求中的多播会话对应的DNN和/或S-NSSAI，选择属于该DNN和/或S-NSSAI的一个PDU会话作为多播会话关联的PDU会话，以及服务于该PDU会话的SMF。
新AMF向确定的SMF发送PDU会话更新会话管理上下文请求(Nsmf_PDUSession_Update Session Management Context)，该请求消息中携带UE请求加入的多播会话信息，包括一个或多个多播会话标识、加入请求指示，还可以包括多播会话对应的DNN和/或S-NSSAI信息。该请求消息中还可以携带UE位置信息，例如UE所在的小区标识(Cell ID)或跟踪区域标识TA I。
步骤706-709、同步骤506-509。
步骤7010、与步骤5010的内容基本相同，不同点在于：
对于仅在特定区域提供的多播业务，SMF可以根据UE位置信息和多播会话的服务区域(MBS Service Area)，判断UE当前是否在多播会话服务区。
若UE不在多播会话的服务区域内，则SMF拒绝UE请求加入该多播会话的请求，即在给新AMF的响应消息中携带该多播会话标识和拒绝UE加入该多播会话的指示。对于该多播会话，步骤706-709、7011、7014-7019不执行。
步骤7011、同步骤5011。
步骤7012-7013、与步骤5012-5013的内容基本相同，不同点在于：
Registration Accept消息中携带MBS Session ID和接收或拒绝UE加入该多播会话的信息。对于接受UE加入的多播会话，UE存储该多播会话的上下文。存储包括生成或更新。对于拒绝UE加入的多播会话，UE删除该多播会话的上下文；
AMF向RAN发送的N2消息中不携带PDU Session Modification Command消息，故而RAN也不会向UE发送PDU Session Modification Command消息。
步骤7014-7019、同步骤5014-5019。
图8是本申请实施例提供的AMF网络功能实体的结构示意图，如图8所示，本申请实施例提供一种AMF网络功能实体，包括存储器801，收发机802，处理器803：
存储器801，用于存储计算机程序；收发机802，用于在处理器803的控制下收发数据；处理器803，用于读取存储器801中的计算机程序并执行以下操作：
接收用户设备UE发送的第一请求，所述第一请求为注册请求消息或业务请求消息；
根据所述第一请求获取所述UE的多播会话信息；
根据所述多播会话信息，执行与多播会话相关的处理操作。
具体来说，收发机802，用于在处理器803的控制下接收和发送数据。
其中，在图8中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器803代表的一个或多个处理器和存储器801代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。
收发机802可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元，这些传输介质包括无线信道、有线信道、光缆等传输介质。处理器803负责管理总线架构和通常的处理，存储器801可以存储处理器803在执行操作时所使用的数据。
处理器803可以是中央处理器(CPU)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field－Programmable Gate Array，FPGA)或复杂可编程逻辑器件(Complex Programmable Logic Device，CPLD)，处理器也可以采用多核架构。
可选地，若所述第一请求中携带所述UE的多播会话信息，则所述根据所述第一请求获取所述UE的多播会话信息，包括：
从所述第一请求中获取所述UE的多播会话信息。
可选地，所述根据所述第一请求获取所述UE的多播会话信息，包括：
基于所述第一请求，从第二AMF中获取所述UE的多播会话信息，所述第二AMF为所述UE发生移动之前为所述UE提供服务的网络功能实体。
可选地，所述多播会话信息包含第一多播会话标识和/或指示信息，所述指示信息用于指示所述UE保持加入、离开或请求加入所述第一多播会话，所述第一多播会话为所述UE已加入的多播会话或请求加入的多播会话。
可选地，所述根据所述多播会话信息，执行与多播会话相关的处理操作，包括：
确定服务于第一多播会话的第一网络功能实体，其中，所述第一网络功能实体包括：会话管理功能SMF或多播广播会话管理功能MB-SMF；
向所述第一网络功能实体发送第二请求，所述第二请求中携带所述多播会话信息；
接收所述第一网络功能实体发送的第二请求的响应消息。
可选地，所述接收所述第一网络功能实体发送的第二请求的响应消息，包括：
接收所述第一网络功能实体发送的携带所述第一多播会话标识和资源分配请求信息的第二请求的响应消息；
处理器803还用于读取存储器801中的计算机程序并执行以下操作：
根据所述第二请求的响应消息，向无线接入网络功能实体发送第三请求，所述第三请求中携带第一多播会话标识和所述资源分配请求信息，以使所述无线接入网络功能实体建立或更新所述第一多播会话的资源。
可选地，所述第二请求的响应消息携带第一多播会话标识和以下信息：
指示所述UE离开所述第一多播会话的信息；或，
拒绝所述UE加入所述第一多播会话的信息。
可选地，处理器803还用于读取存储器801中的计算机程序并执行以下操作：
向无线接入网络功能实体发送第三请求，所述第三请求中携带第一多播会话标识和指示所述UE离开所述第一多播会话的信息，以使所述无线接入 网络功能实体从所述第一多播会话的上下文中删除所述UE的标识。
可选地，所述多播会话信息还包括以下至少一项标识信息：
第一多播会话关联的协议数据单元PDU会话的标识；
服务于所述第一多播会话的MB-SMF的标识和/或SMF的标识；
所述确定服务于第一多播会话的第一网络功能实体，包括：
依据所述至少一项标识信息,确定服务于所述第一多播会话的第一网络功能实体。
在此需要说明的是，本申请实施例提供的上述AMF网络功能实体，能够实现上述以第一AMF为执行主体的多播会话处理方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
图9是本申请实施例提供的SMF网络功能实体的结构示意图，如图9所示，本申请实施例提供一种SMF网络功能实体，包括存储器901，收发机902，处理器903：
存储器901，用于存储计算机程序；收发机902，用于在所述处理器903的控制下收发数据；处理器903，用于读取所述存储器901中的计算机程序并执行以下操作：
接收第一AMF发送的第二请求，所述第二请求中携带用户设备UE的多播会话信息，所述多播会话信息是所述第一AMF在接收到所述UE发送的第一请求之后获取的，所述第一请求为注册请求消息或业务请求消息；
根据所述第二请求中携带的多播会话信息，对所述UE的多播会话进行处理。
具体来说，收发机902，用于在处理器903的控制下接收和发送数据。
其中，在图9中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器903代表的一个或多个处理器和存储器901代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。
收发机902可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元，这些传输介质包括无线信道、有线信道、光缆等传输介质。处理器903负责管理总线架构和通常的处理，存储器901可以存储处理器903在执行操作时所使用的数据。
处理器903可以是中央处理器(CPU)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field－Programmable Gate Array，FPGA)或复杂可编程逻辑器件(Complex Programmable Logic Device，CPLD)，处理器也可以采用多核架构。
可选地，所述多播会话信息包含第一多播会话标识和/或指示信息，所述指示信息用于指示所述UE保持加入、离开或请求加入所述第一多播会话，所述第一多播会话为所述UE已加入的多播会话或请求加入的多播会话。
可选地，所述根据所述第二请求中携带的多播会话信息，对所述UE的多播会话进行处理，包括：
若所述指示信息用于指示所述UE请求加入所述第一多播会话，且确定接受所述UE加入所述第一多播会话，则建立所述UE的标识与所述第一多播会话标识之间的对应关系；向所述第一AMF发送第二请求的响应消息，所述第二请求的响应消息中携带接受所述UE加入所述第一多播会话的信息；或，
若所述指示信息用于指示所述UE请求加入所述第一多播会话，且所述UE不在所述第一多播会话的服务区域内，则向所述第一AMF发送第二请求的响应消息，所述第二请求的响应消息中携带拒绝所述UE加入所述第一多播会话的信息；或，
若所述指示信息用于指示所述UE保持加入所述第一多播会话，且所述UE不在所述第一多播会话的服务区域内，则向所述第一AMF发送第二请求的响应消息，所述第二请求的响应消息中携带指示所述UE离开所述第一多播会话的信息；或，
若所述指示信息用于指示所述UE离开所述第一多播会话，则删除所述UE的标识与所述第一多播会话标识之间的对应关系。
可选地，所述根据所述第二请求中携带的多播会话信息，对所述UE的 多播会话进行处理，包括：
若所述指示信息用于指示所述UE请求加入所述第一多播会话，且确定接受所述UE加入所述第一多播会话，则在所述第一多播会话的上下文中存储服务于所述UE的无线接入网络功能实体的标识。
在此需要说明的是，本申请实施例提供的上述SMF网络功能实体，能够实现上述以SMF为执行主体的多播会话处理方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
图10是本申请实施例提供的用户设备UE的结构示意图，如图10所示，本申请实施例提供一种用户设备UE，包括存储器1001，收发机1002，处理器1003：
存储器1001，用于存储计算机程序；收发机1002，用于在所述处理器1003的控制下收发数据；处理器1003，用于读取所述存储器1001中的计算机程序并执行以下操作：
向第一AMF发送第一请求，所述第一请求为业务请求消息或注册请求消息；
接收所述第一AMF发送的所述第一请求的响应消息，所述第一请求的响应消息为注册接受消息或业务接受消息，所述第一请求的响应消息中包含接受UE加入或离开第一多播会话的信息，或，指示所述UE离开第一多播会话的信息，或，拒绝所述UE加入第一多播会话的信息；
根据所述第一请求的响应消息，对所述第一多播会话进行处理。
具体来说，收发机1002，用于在处理器1003的控制下接收和发送数据。
其中，在图10中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1003代表的一个或多个处理器和存储器1001代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。
收发机1002可以是多个元件，即包括发送机和接收机，提供用于在传输 介质上与各种其他装置通信的单元，这些传输介质包括无线信道、有线信道、光缆等传输介质。处理器1003负责管理总线架构和通常的处理，存储器1001可以存储处理器1003在执行操作时所使用的数据。
处理器1003可以是中央处理器(CPU)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field－Programmable Gate Array，FPGA)或复杂可编程逻辑器件(Complex Programmable Logic Device，CPLD)，处理器也可以采用多核架构。
可选地，所述第一请求中携带多播会话信息，所述多播会话信息包含第一多播会话标识和指示信息，所述第一多播会话为所述UE已加入的多播会话或请求加入的多播会话，所述指示信息用于指示所述UE保持加入、离开或请求加入所述第一多播会话。
可选地，所述根据所述第一请求的响应消息，对所述第一多播会话进行处理，包括：
若第一请求的响应消息中携带接受所述UE加入所述第一多播会话的信息，则存储所述第一多播会话的上下文；
若第一请求的响应消息中携带拒绝所述UE加入所述第一多播会话的信息或指示所述UE离开所述第一多播会话的信息，则删除所述第一多播会话的上下文。
可选地，所述接收所述第一AMF发送的所述第一请求的响应消息，包括：
接收无线接入网络功能实体转发的所述第一AMF发送的所述第一请求的响应消息；
处理器1003还用于读取存储器1001中的计算机程序并执行以下操作：
若所述第一请求的响应消息中携带接受所述UE加入所述第一多播会话的信息，则建立或更新所述第一多播会话的资源；
利用所述资源接收所述第一多播会话的业务数据。
可选地，所述利用所述资源接收所述第一多播会话的业务数据，包括：
若无线接入网络功能实体不支持多播业务，则利用所述资源，通过单播方式接收所述第一多播会话的业务数据；
若无线接入网络功能实体支持多播业务，则利用所述资源，通过多播方式接收所述第一多播会话的业务数据。
在此需要说明的是，本申请实施例提供的上述用户设备UE，能够实现上述以UE为执行主体的多播会话处理方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
图11是本申请实施例提供的多播会话处理装置的结构示意图之一，如图11所示，本申请实施例提供一种多播会话处理装置，该装置包括：
第一接收单元1101，用于接收用户设备UE发送的第一请求，所述第一请求为注册请求消息或业务请求消息；
第一获取单元1102，用于根据所述第一请求获取所述UE的多播会话信息；
执行单元1103，用于根据所述多播会话信息，执行与多播会话相关的处理操作。
可选地，若所述第一请求中携带所述UE的多播会话信息，则第一获取单元包括：
第一获取模块，用于从所述第一请求中获取所述UE的多播会话信息。
可选地，所述第一获取单元包括：
第二获取模块，用于基于所述第一请求，从第二AMF中获取所述UE的多播会话信息，所述第二AMF为所述UE发生移动之前为所述UE提供服务的网络功能实体；所述第一AMF为所述UE发生移动之后为所述UE提供服务的网络功能实体。
可选地，所述多播会话信息包含第一多播会话标识和/或指示信息，所述指示信息用于指示所述UE保持加入、离开或请求加入所述第一多播会话，所述第一多播会话为所述UE已加入的多播会话或请求加入的多播会话。
可选地，执行单元包括：
第一确定模块，用于确定服务于第一多播会话的第一网络功能实体，其中，所述第一网络功能实体包括：会话管理功能SMF或多播广播会话管理功 能MB-SMF；
第一发送模块，用于向所述第一网络功能实体发送第二请求，所述第二请求中携带所述多播会话信息；
第一接收模块，用于接收所述第一网络功能实体发送的第二请求的响应消息。
可选地，所述第一接收单元包括：
第二接收模块，用于接收所述第一网络功能实体发送的携带所述第一多播会话标识和资源分配请求信息的第二请求的响应消息；
该装置还包括：
第一发送单元，用于根据所述第二请求的响应消息，向无线接入网络功能实体发送第三请求，所述第三请求中携带第一多播会话标识和所述资源分配请求信息，以使所述无线接入网络功能实体建立或更新所述第一多播会话的资源。
可选地，所述第二请求的响应消息携带第一多播会话标识和以下信息：
指示所述UE离开所述第一多播会话的信息；或，
拒绝所述UE加入所述第一多播会话的信息。
可选地，该装置还包括：
第二发送单元，用于向无线接入网络功能实体发送第三请求，所述第三请求中携带第一多播会话标识和指示所述UE离开所述第一多播会话的信息，以使所述无线接入网络功能实体从所述第一多播会话的上下文中删除所述UE的标识。
可选地，所述多播会话信息还包括以下至少一项标识信息：
第一多播会话关联的协议数据单元PDU会话的标识；
服务于所述第一多播会话的MB-SMF的标识和/或SMF的标识；
所述确定服务于第一多播会话的第一网络功能实体，包括：
依据所述至少一项标识信息,确定服务于所述第一多播会话的第一网络功能实体。
在此需要说明的是，本申请实施例提供的上述多播会话处理装置，能够 实现上述以第一AMF为执行主体的多播会话处理方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
图12是本申请实施例提供的多播会话处理装置的结构示意图之二，如图12所示，本申请实施例提供一种多播会话处理装置，该装置包括：
第二接收单元1201，用于接收第一AMF发送的第二请求，所述第二请求中携带用户设备UE的多播会话信息，所述多播会话信息是所述第一AMF在接收到所述UE发送的第一请求之后获取的，所述第一请求为注册请求消息或业务请求消息；
第一处理单元1202，用于根据所述第二请求中携带的多播会话信息，对所述UE的多播会话进行处理。
可选地，所述多播会话信息包含第一多播会话标识和/或指示信息，所述指示信息用于指示所述UE保持加入、离开或请求加入所述第一多播会话，所述第一多播会话为所述UE已加入的多播会话或请求加入的多播会话。
可选地，所述第一处理单元包括：
第一建立模块，用于若所述指示信息用于指示所述UE请求加入所述第一多播会话，且确定接受所述UE加入所述第一多播会话，则建立所述UE的标识与所述第一多播会话标识之间的对应关系；
第二发送模块，用于向所述第一AMF发送第二请求的响应消息，所述第二请求的响应消息中携带接受所述UE加入所述第一多播会话的信息；
或，
第三发送模块，用于若所述指示信息用于指示所述UE请求加入所述第一多播会话，且所述UE不在所述第一多播会话的服务区域内，则向所述第一AMF发送第二请求的响应消息，所述第二请求的响应消息中携带拒绝所述UE加入所述第一多播会话的信息；
或，
第四发送模块，用于若所述指示信息用于指示所述UE保持加入所述第一多播会话，且所述UE不在所述第一多播会话的服务区域内，则向所述第 一AMF发送第二请求的响应消息，所述第二请求的响应消息中携带指示所述UE离开所述第一多播会话的信息；
或，
第一删除模块，用于若所述指示信息用于指示所述UE离开所述第一多播会话，则删除所述UE的标识与所述第一多播会话标识之间的对应关系。
可选地，第一处理单元包括：
第一存储模块，用于若所述指示信息用于指示所述UE请求加入所述第一多播会话，且确定接受所述UE加入所述第一多播会话，则在所述第一多播会话的上下文中存储服务于所述UE的无线接入网络功能实体的标识。
在此需要说明的是，本申请实施例提供的上述多播会话处理装置，能够实现上述以SMF为执行主体的多播会话处理方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
图13是本申请实施例提供的多播会话处理装置的结构示意图之三，如图13所示，本申请实施例提供一种多播会话处理装置，该装置包括：
第三发送单元1301，用于向第一AMF发送第一请求，所述第一请求为业务请求消息或注册请求消息；
第三接收单元1302，用于接收所述第一AMF发送的所述第一请求的响应消息，所述第一请求的响应消息为注册接受消息或业务接受消息，所述第一请求的响应消息中包含接受UE加入或离开第一多播会话的信息，或，指示所述UE离开第一多播会话的信息，或，拒绝所述UE加入第一多播会话的信息；
第二处理单元1303，用于根据所述第一请求的响应消息，对所述第一多播会话进行处理。
可选地，所述第一请求中携带多播会话信息，所述多播会话信息包含第一多播会话标识和指示信息，所述第一多播会话为所述UE已加入的多播会话或请求加入的多播会话，所述指示信息用于指示所述UE保持加入、离开或请求加入所述第一多播会话。
可选地，所述第二处理单元包括：
第二存储模块，用于若第一请求的响应消息中携带接受所述UE加入所述第一多播会话的信息，则存储所述第一多播会话的上下文；
第二删除模块，用于若第一请求的响应消息中携带拒绝所述UE加入所述第一多播会话的信息或指示所述UE离开所述第一多播会话的信息，则删除所述第一多播会话的上下文。
可选地，所述第三接收单元包括：
第三接收模块，用于接收无线接入网络功能实体转发的所述第一AMF发送的所述第一请求的响应消息；
所述装置还包括：
建立单元，用于若所述第一请求的响应消息中携带接受所述UE加入所述第一多播会话的信息，则建立或更新所述第一多播会话的资源；
第四接收单元，用于利用所述资源接收所述第一多播会话的业务数据。
可选地，所述第四接收单元包括：
第四接收模块，用于若无线接入网络功能实体不支持多播业务，则利用所述资源，通过单播方式接收所述第一多播会话的业务数据；
第五接收模块，用于若无线接入网络功能实体支持多播业务，则利用所述资源，通过多播方式接收所述第一多播会话的业务数据。
在此需要说明的是，本申请实施例提供的上述多播会话处理装置，能够实现上述以UE为执行主体的多播会话处理方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
需要说明的是，本申请实施例中对单元/模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。另外，在本申请各个实施例中的各功能单元/模块可以集成在一个处理单元/模块中，也可以是各个单元/模块单独物理存在，也可以两个或两个以上单元/模块集成在一个单元/模块中。上述集成的单元/模块既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元/模块如果以软件功能单元/模块的形式实现并作为独立的产品销售或使用时，可以存储在一个处理器可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
另一方面，本申请实施例还提供一种处理器可读存储介质，所述处理器可读存储介质存储有计算机程序，所述计算机程序用于使所述处理器执行上述各实施例提供的多播会话处理方法，包括：
接收用户设备UE发送的第一请求，所述第一请求为注册请求消息或业务请求消息；
根据所述第一请求获取所述UE的多播会话信息；
根据所述多播会话信息，执行与多播会话相关的处理操作。
或者，包括：
接收第一AMF发送的第二请求，所述第二请求中携带用户设备UE的多播会话信息，所述多播会话信息是所述第一AMF在接收到所述UE发送的第一请求之后获取的，所述第一请求为注册请求消息或业务请求消息；
根据所述第二请求中携带的多播会话信息，对所述UE的多播会话进行处理。
或者，包括：
向第一AMF发送第一请求，所述第一请求为业务请求消息或注册请求消息；
接收所述第一AMF发送的所述第一请求的响应消息，所述第一请求的响应消息为注册接受消息或业务接受消息，所述第一请求的响应消息中包含接受UE加入或离开第一多播会话的信息，或，指示所述UE离开第一多播会话 的信息，或，拒绝所述UE加入第一多播会话的信息；
根据所述第一请求的响应消息，对所述第一多播会话进行处理。
需要说明的是：所述处理器可读存储介质可以是处理器能够存取的任何可用介质或数据存储设备，包括但不限于磁性存储器(例如软盘、硬盘、磁带、磁光盘(MO)等)、光学存储器(例如CD、DVD、BD、HVD等)、以及半导体存储器(例如ROM、EPROM、EEPROM、非易失性存储器(NAND FLASH)、固态硬盘(SSD))等。
另外需要说明的是：本申请实施例中术语“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请的说明书和权利要求书中的术语“第一”、“第二”、“目标”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”、“目标”等所区分的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。
本申请实施例中术语“多个”是指两个或两个以上，其它量词与之类似。
本申请实施例提供的技术方案可以适用于多种系统，尤其是5G系统。例如适用的系统可以是全球移动通讯(global system of 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)系统、5G新空口(New Radio, NR)系统等。这多种系统中均包括终端设备和网络设备。系统中还可以包括核心网部分，例如演进的分组系统(Evloved Packet System,EPS)、5G系统(5GS)等。
本申请实施例涉及的终端设备，可以是指向用户提供语音和/或数据连通性的设备，具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备等。在不同的系统中，终端设备的名称可能也不相同，例如在5G系统中，终端设备可以称为用户设备(User Equipment，UE)。无线终端设备可以经无线接入网(Radio Access Network,RAN)与一个或多个核心网(Core Network,CN)进行通信，无线终端设备可以是移动终端设备，如移动电话(或称为“蜂窝”电话)和具有移动终端设备的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。例如，个人通信业务(Personal Communication Service，PCS)电话、无绳电话、会话发起协议(Session Initiated Protocol，SIP)话机、无线本地环路(Wireless Local Loop，WLL)站、个人数字助理(Personal Digital Assistant，PDA)等设备。无线终端设备也可以称为系统、订户单元(subscriber unit)、订户站(subscriber station)，移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点(access point)、远程终端设备(remote terminal)、接入终端设备(access terminal)、用户终端设备(user terminal)、用户代理(user agent)、用户装置(user device)，本申请实施例中并不限定。
本申请实施例涉及的网络设备，可以是基站，该基站可以包括多个为终端提供服务的小区。根据具体应用场合不同，基站又可以称为接入点，或者可以是接入网中在空中接口上通过一个或多个扇区与无线终端设备通信的设备，或者其它名称。网络设备可用于将收到的空中帧与网际协议(Internet Protocol，IP)分组进行相互更换，作为无线终端设备与接入网的其余部分之间的路由器，其中接入网的其余部分可包括网际协议(IP)通信网络。网络设备还可协调对空中接口的属性管理。例如，本申请实施例涉及的网络设备可以是全球移动通信系统(Global System for Mobile communications，GSM) 或码分多址接入(Code Division Multiple Access，CDMA)中的网络设备(Base Transceiver Station，BTS)，也可以是带宽码分多址接入(Wide-band Code Division Multiple Access，WCDMA)中的网络设备(NodeB)，还可以是长期演进(long term evolution，LTE)系统中的演进型网络设备(evolutional Node B，eNB或e-NodeB)、5G网络架构(next generation system)中的5G基站(gNB)，也可以是家庭演进基站(Home evolved Node B，HeNB)、中继节点(relay node)、家庭基站(femto)、微微基站(pico)等，本申请实施例中并不限定。在一些网络结构中，网络设备可以包括集中单元(centralized unit，CU)节点和分布单元(distributed unit，DU)节点，集中单元和分布单元也可以地理上分开布置。
网络设备与终端设备之间可以各自使用一根或多根天线进行多输入多输出(Multi Input Multi Output,MIMO)传输，MIMO传输可以是单用户MIMO(Single User MIMO,SU-MIMO)或多用户MIMO(Multiple User MIMO,MU-MIMO)。根据根天线组合的形态和数量，MIMO传输可以是2D-MIMO、3D-MIMO、FD-MIMO或massive-MIMO，也可以是分集传输或预编码传输或波束赋形传输等。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机可执行指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机可执行指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的 功能的装置。
这些处理器可执行指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的处理器可读存储器中，使得存储在该处理器可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些处理器可执行指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (32)

  1. 一种多播会话处理方法，其特征在于，应用于接入与移动性管理功能第一AMF中，包括：
    接收用户设备UE发送的第一请求，所述第一请求为注册请求消息或业务请求消息；
    根据所述第一请求获取所述UE的多播会话信息；
    根据所述多播会话信息，执行与多播会话相关的处理操作。
  2. 根据权利要求1所述的多播会话处理方法，其特征在于，若所述第一请求中携带所述UE的多播会话信息，则所述根据所述第一请求获取所述UE的多播会话信息，包括：
    从所述第一请求中获取所述UE的多播会话信息。
  3. 根据权利要求1所述的多播会话处理方法，其特征在于，所述根据所述第一请求获取所述UE的多播会话信息，包括：
    基于所述第一请求，从第二AMF中获取所述UE的多播会话信息，所述第二AMF为所述UE发生移动之前为所述UE提供服务的网络功能实体；所述第一AMF为所述UE发生移动之后为所述UE提供服务的网络功能实体。
  4. 根据权利要求1至3任一项所述的多播会话处理方法，其特征在于，所述多播会话信息包含第一多播会话标识和/或指示信息，所述指示信息用于指示所述UE保持加入、离开或请求加入所述第一多播会话，所述第一多播会话为所述UE已加入的多播会话或请求加入的多播会话。
  5. 根据权利要求1所述的多播会话处理方法，其特征在于，所述根据所述多播会话信息，执行与多播会话相关的处理操作，包括：
    确定服务于第一多播会话的第一网络功能实体，其中，所述第一网络功能实体包括：会话管理功能SMF或多播广播会话管理功能MB-SMF；
    向所述第一网络功能实体发送第二请求，所述第二请求中携带所述多播会话信息；
    接收所述第一网络功能实体发送的第二请求的响应消息。
  6. 根据权利要求5所述的多播会话处理方法，其特征在于，所述接收所 述第一网络功能实体发送的第二请求的响应消息，包括：
    接收所述第一网络功能实体发送的携带所述第一多播会话标识和资源分配请求信息的第二请求的响应消息；
    所述方法还包括：
    根据所述第二请求的响应消息，向无线接入网络功能实体发送第三请求，所述第三请求中携带第一多播会话标识和所述资源分配请求信息，以使所述无线接入网络功能实体建立或更新所述第一多播会话的资源。
  7. 根据权利要求5所述的多播会话处理方法，其特征在于，所述第二请求的响应消息携带第一多播会话标识和以下信息：
    指示所述UE离开所述第一多播会话的信息；或，
    拒绝所述UE加入所述第一多播会话的信息。
  8. 根据权利要求5所述的多播会话处理方法，其特征在于，所述方法还包括：
    向无线接入网络功能实体发送第三请求，所述第三请求中携带第一多播会话标识和指示所述UE离开所述第一多播会话的信息，以使所述无线接入网络功能实体从所述第一多播会话的上下文中删除所述UE的标识。
  9. 根据权利要求5所述的多播会话处理方法，其特征在于，所述多播会话信息还包括以下至少一项标识信息：
    第一多播会话关联的协议数据单元PDU会话的标识；
    服务于所述第一多播会话的MB-SMF的标识和/或SMF的标识；
    所述确定服务于第一多播会话的第一网络功能实体，包括：
    依据所述至少一项标识信息,确定服务于所述第一多播会话的第一网络功能实体。
  10. 一种多播会话处理方法，其特征在于，应用于SMF，包括：
    接收第一AMF发送的第二请求，所述第二请求中携带用户设备UE的多播会话信息，所述多播会话信息是所述第一AMF在接收到所述UE发送的第一请求之后获取的，所述第一请求为注册请求消息或业务请求消息；
    根据所述第二请求中携带的多播会话信息，对所述UE的多播会话进行 处理。
  11. 根据权利要求10所述的多播会话处理方法，其特征在于，所述多播会话信息包含第一多播会话标识和/或指示信息，所述指示信息用于指示所述UE保持加入、离开或请求加入所述第一多播会话，所述第一多播会话为所述UE已加入的多播会话或请求加入的多播会话。
  12. 根据权利要求11所述的多播会话处理方法，其特征在于，所述根据所述第二请求中携带的多播会话信息，对所述UE的多播会话进行处理，包括：
    若所述指示信息用于指示所述UE请求加入所述第一多播会话，且确定接受所述UE加入所述第一多播会话，则建立所述UE的标识与所述第一多播会话标识之间的对应关系；向所述第一AMF发送第二请求的响应消息，所述第二请求的响应消息中携带接受所述UE加入所述第一多播会话的信息；或，
    若所述指示信息用于指示所述UE请求加入所述第一多播会话，且所述UE不在所述第一多播会话的服务区域内，则向所述第一AMF发送第二请求的响应消息，所述第二请求的响应消息中携带拒绝所述UE加入所述第一多播会话的信息；或，
    若所述指示信息用于指示所述UE保持加入所述第一多播会话，且所述UE不在所述第一多播会话的服务区域内，则向所述第一AMF发送第二请求的响应消息，所述第二请求的响应消息中携带指示所述UE离开所述第一多播会话的信息；或，
    若所述指示信息用于指示所述UE离开所述第一多播会话，则删除所述UE的标识与所述第一多播会话标识之间的对应关系。
  13. 根据权利要求11所述的多播会话处理方法，其特征在于，所述根据所述第二请求中携带的多播会话信息，对所述UE的多播会话进行处理，包括：
    若所述指示信息用于指示所述UE请求加入所述第一多播会话，且确定接受所述UE加入所述第一多播会话，则在所述第一多播会话的上下文中存储服务于所述UE的无线接入网络功能实体的标识。
  14. 一种多播会话处理方法，其特征在于，应用于UE，包括：
    向第一AMF发送第一请求，所述第一请求为业务请求消息或注册请求消息；
    接收所述第一AMF发送的所述第一请求的响应消息，所述第一请求的响应消息为注册接受消息或业务接受消息，所述第一请求的响应消息中包含接受UE加入或离开第一多播会话的信息，或，指示所述UE离开第一多播会话的信息，或，拒绝所述UE加入第一多播会话的信息；
    根据所述第一请求的响应消息，对所述第一多播会话进行处理。
  15. 根据权利要求14所述的多播会话处理方法，其特征在于，所述第一请求中携带多播会话信息，所述多播会话信息包含第一多播会话标识和指示信息，所述第一多播会话为所述UE已加入的多播会话或请求加入的多播会话，所述指示信息用于指示所述UE保持加入、离开或请求加入所述第一多播会话。
  16. 根据权利要求14所述的多播会话处理方法，其特征在于，所述根据所述第一请求的响应消息，对所述第一多播会话进行处理，包括：
    若第一请求的响应消息中携带接受所述UE加入所述第一多播会话的信息，则存储所述第一多播会话的上下文；
    若第一请求的响应消息中携带拒绝所述UE加入所述第一多播会话的信息或指示所述UE离开所述第一多播会话的信息，则删除所述第一多播会话的上下文。
  17. 根据权利要求14所述的多播会话处理方法，其特征在于，所述接收所述第一AMF发送的所述第一请求的响应消息，包括：
    接收无线接入网络功能实体转发的所述第一AMF发送的所述第一请求的响应消息；
    所述方法还包括：
    若所述第一请求的响应消息中携带接受所述UE加入所述第一多播会话的信息，则建立或更新所述第一多播会话的资源；
    利用所述资源接收所述第一多播会话的业务数据。
  18. 根据权利要求17所述的多播会话处理方法，其特征在于，所述利用所述资源接收所述第一多播会话的业务数据，包括：
    若无线接入网络功能实体不支持多播业务，则利用所述资源，通过单播方式接收所述第一多播会话的业务数据；
    若无线接入网络功能实体支持多播业务，则利用所述资源，通过多播方式接收所述第一多播会话的业务数据。
  19. 一种AMF网络功能实体，其特征在于，包括存储器，收发机，处理器：
    存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行以下操作：
    接收用户设备UE发送的第一请求，所述第一请求为注册请求消息或业务请求消息；
    根据所述第一请求获取所述UE的多播会话信息；
    根据所述多播会话信息，执行与多播会话相关的处理操作。
  20. 根据权利要求19所述的AMF网络功能实体，其特征在于，所述根据所述第一请求获取所述UE的多播会话信息，包括：
    基于所述第一请求，从第二AMF中获取所述UE的多播会话信息，所述第二AMF为所述UE发生移动之前为所述UE提供服务的网络功能实体。
  21. 根据权利要求19所述的AMF网络功能实体，其特征在于，所述根据所述多播会话信息，执行与多播会话相关的处理操作，包括：
    确定服务于第一多播会话的第一网络功能实体，其中，所述第一网络功能实体包括：会话管理功能SMF或多播广播会话管理功能MB-SMF；
    向所述第一网络功能实体发送第二请求，所述第二请求中携带所述多播会话信息；
    接收所述第一网络功能实体发送的第二请求的响应消息。
  22. 根据权利要求21所述的AMF网络功能实体，其特征在于，所述接收所述第一网络功能实体发送的第二请求的响应消息，包括：
    接收所述第一网络功能实体发送的携带所述第一多播会话标识和资源分 配请求信息的第二请求的响应消息；
    所述处理器还用于读取所述存储器中的计算机程序并执行以下操作：
    根据所述第二请求的响应消息，向无线接入网络功能实体发送第三请求，所述第三请求中携带第一多播会话标识和所述资源分配请求信息，以使所述无线接入网络功能实体建立或更新所述第一多播会话的资源。
  23. 一种SMF网络功能实体，其特征在于，包括存储器，收发机，处理器：
    存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行以下操作：
    接收第一AMF发送的第二请求，所述第二请求中携带用户设备UE的多播会话信息，所述多播会话信息是所述第一AMF在接收到所述UE发送的第一请求之后获取的，所述第一请求为注册请求消息或业务请求消息；
    根据所述第二请求中携带的多播会话信息，对所述UE的多播会话进行处理。
  24. 一种用户设备UE，其特征在于，包括存储器，收发机，处理器：
    存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行以下操作：
    向第一AMF发送第一请求，所述第一请求为业务请求消息或注册请求消息；
    接收所述第一AMF发送的所述第一请求的响应消息，所述第一请求的响应消息为注册接受消息或业务接受消息，所述第一请求的响应消息中包含接受UE加入或离开第一多播会话的信息，或，指示所述UE离开第一多播会话的信息，或，拒绝所述UE加入第一多播会话的信息；
    根据所述第一请求的响应消息，对所述第一多播会话进行处理。
  25. 根据权利要求24所述的用户设备UE，其特征在于，所述第一请求中携带多播会话信息，所述多播会话信息包含第一多播会话标识和指示信息，所述第一多播会话为所述UE已加入的多播会话或请求加入的多播会话，所述指示信息用于指示所述UE保持加入、离开或请求加入所述第一多播会话。
  26. 根据权利要求24所述的用户设备UE，其特征在于，所述根据所述第一请求的响应消息，对所述第一多播会话进行处理，包括：
    若第一请求的响应消息中携带接受所述UE加入所述第一多播会话的信息，则存储所述第一多播会话的上下文；
    若第一请求的响应消息中携带拒绝所述UE加入所述第一多播会话的信息或指示所述UE离开所述第一多播会话的信息，则删除所述第一多播会话的上下文。
  27. 根据权利要求24所述的用户设备UE，其特征在于，所述接收所述第一AMF发送的所述第一请求的响应消息，包括：
    接收无线接入网络功能实体转发的所述第一AMF发送的所述第一请求的响应消息；
    所述处理器还用于读取所述存储器中的计算机程序并执行以下操作：
    若所述第一请求的响应消息中携带接受所述UE加入所述第一多播会话的信息，则建立或更新所述第一多播会话的资源；
    利用所述资源接收所述第一多播会话的业务数据。
  28. 根据权利要求27所述的用户设备UE，其特征在于，所述利用所述资源接收所述第一多播会话的业务数据，包括：
    若无线接入网络功能实体不支持多播业务，则利用所述资源，通过单播方式接收所述第一多播会话的业务数据；
    若无线接入网络功能实体支持多播业务，则利用所述资源，通过多播方式接收所述第一多播会话的业务数据。
  29. 一种多播会话处理装置，其特征在于，包括：
    第一接收单元，用于接收用户设备UE发送的第一请求，所述第一请求为注册请求消息或业务请求消息；
    第一获取单元，用于根据所述第一请求获取所述UE的多播会话信息；
    执行单元，用于根据所述多播会话信息，执行与多播会话相关的处理操作。
  30. 一种多播会话处理装置，其特征在于，包括：
    第二接收单元，用于接收第一AMF发送的第二请求，所述第二请求中携带用户设备UE的多播会话信息，所述多播会话信息是所述第一AMF在接收到所述UE发送的第一请求之后获取的，所述第一请求为注册请求消息或业务请求消息；
    第一处理单元，用于根据所述第二请求中携带的多播会话信息，对所述UE的多播会话进行处理。
  31. 一种多播会话处理装置，其特征在于，包括：
    第三发送单元，用于向第一AMF发送第一请求，所述第一请求为业务请求消息或注册请求消息；
    第三接收单元，用于接收所述第一AMF发送的所述第一请求的响应消息，所述第一请求的响应消息为注册接受消息或业务接受消息，所述第一请求的响应消息中包含接受UE加入或离开第一多播会话的信息，或，指示所述UE离开第一多播会话的信息，或，拒绝所述UE加入第一多播会话的信息；
    第二处理单元，用于根据所述第一请求的响应消息，对所述第一多播会话进行处理。
  32. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机程序，所述计算机程序用于使所述处理器执行权利要求1至18任一项所述的方法。
PCT/CN2022/099440 2021-07-23 2022-06-17 多播会话处理方法、网络功能实体、装置及存储介质 WO2023000884A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP22845050.8A EP4376539A1 (en) 2021-07-23 2022-06-17 Multicast session processing method, network function entity, apparatus, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110839157.3 2021-07-23
CN202110839157.3A CN115696217A (zh) 2021-07-23 2021-07-23 多播会话处理方法、网络功能实体、装置及存储介质

Publications (1)

Publication Number Publication Date
WO2023000884A1 true WO2023000884A1 (zh) 2023-01-26

Family

ID=84980074

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/099440 WO2023000884A1 (zh) 2021-07-23 2022-06-17 多播会话处理方法、网络功能实体、装置及存储介质

Country Status (3)

Country Link
EP (1) EP4376539A1 (zh)
CN (1) CN115696217A (zh)
WO (1) WO2023000884A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117156599B (zh) * 2023-08-10 2024-04-09 杭州必博半导体有限公司 会话交互方法、装置、系统、设备、存储介质及程序产品

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111448808A (zh) * 2018-01-03 2020-07-24 康维达无线有限责任公司 用于IoT应用的5G网络中的多播和广播服务
CN112740820A (zh) * 2018-09-19 2021-04-30 高通股份有限公司 多播空闲模式行为和寻呼
WO2021138558A1 (en) * 2020-01-03 2021-07-08 Nokia Technologies Oy Selecting session management function capable of storing internet protocol multicast
WO2021136468A1 (zh) * 2020-01-02 2021-07-08 维沃移动通信有限公司 多播业务会话操作的方法、装置和通信设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111448808A (zh) * 2018-01-03 2020-07-24 康维达无线有限责任公司 用于IoT应用的5G网络中的多播和广播服务
CN112740820A (zh) * 2018-09-19 2021-04-30 高通股份有限公司 多播空闲模式行为和寻呼
WO2021136468A1 (zh) * 2020-01-02 2021-07-08 维沃移动通信有限公司 多播业务会话操作的方法、装置和通信设备
WO2021138558A1 (en) * 2020-01-03 2021-07-08 Nokia Technologies Oy Selecting session management function capable of storing internet protocol multicast

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
VIVO: "KI #1, Sol #4: Update to solution 4", 3GPP DRAFT; S2-2004102, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting ;20200601 - 20200612, 22 May 2020 (2020-05-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051890109 *

Also Published As

Publication number Publication date
EP4376539A1 (en) 2024-05-29
CN115696217A (zh) 2023-02-03

Similar Documents

Publication Publication Date Title
US11395256B2 (en) Communication method, device, and system
US20220408162A1 (en) Multicast service transmission method and apparatus
WO2022033168A1 (zh) 一种mbs业务数据传输方法和网络侧装置及设备
WO2022028276A1 (zh) 业务处理方法、信息指示方法、终端和网络设备
WO2022083484A1 (zh) 数据传输控制方法、装置及存储介质
WO2022073491A1 (zh) 切换方法、装置、终端设备、网络设备及存储介质
WO2021051320A1 (zh) 一种业务数据传输方法及装置、网络设备、终端设备
WO2023000884A1 (zh) 多播会话处理方法、网络功能实体、装置及存储介质
WO2022037441A1 (zh) Mbms业务的传输模式指示方法、装置及存储介质
WO2022152092A1 (zh) 数据传输控制方法和装置
WO2022156439A1 (zh) 信息传输方法、装置、基站及介质
WO2022083411A1 (zh) 辅小区变换的错误类型的判定方法及设备
WO2023020276A1 (zh) 组播广播业务数据传输方法、装置、设备以及存储介质
WO2022116842A1 (zh) 消息通知方法、装置、终端设备、中继设备及存储介质
WO2023072014A1 (zh) 相对定位方法、电子设备、装置及存储介质
WO2023284474A1 (zh) Amf选择方法、设备、装置及存储介质
WO2024027687A1 (zh) QoE测量报告的处理方法及装置
WO2023066009A1 (zh) 内生业务的传输方法、装置及存储介质
WO2023231767A1 (zh) 定时提前值传输方法、装置及存储介质
WO2024022199A1 (zh) 信息传输方法、装置及存储介质
WO2024027626A1 (zh) QoE测量配置方法、主节点及辅节点
WO2024016915A1 (zh) PDU set的发送方法、通信节点及装置
WO2022042139A1 (zh) 多媒体广播多播业务mbms业务的传输区域处理方法
WO2019028918A1 (zh) 一种设备发现方法及相关设备
WO2022199233A1 (zh) 寻呼方法、装置及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22845050

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022845050

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022845050

Country of ref document: EP

Effective date: 20240223