Method and apparatus for providing multicast and broadcast services in a mobile communication network

Abstract

The present disclosure relates to a communication technology and a system thereof for integrating IoT technology with a 5G communication system supporting a higher data transmission rate than a 4G system. The present disclosure can be applied to smart services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail business, security and safety related services, etc.) based on 5G communication technology and IoT related technologies. The present invention provides a method for providing MBS services in a communication system.

Description

Technical Field

[0001] The present disclosure relates to an apparatus and method for providing multicast / broadcast services. Background Art

[0002] In order to meet the needs of wireless data services that have exploded due to the deployment of 4G communication systems and the increase of multimedia services, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also called "super 4G network" communication systems or "post-LTE" systems. 5G communication systems are considered to be implemented in ultra-high frequency (mmWave) bands (e.g., 60GHz bands) to increase data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance in ultra-high frequency bands, beamforming, massive multiple input multiple output (massive MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed in 5G communication systems. In addition, in 5G communication systems, based on advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, cooperative communications, coordinated multi-point (CoMP), receiving end interference elimination, etc., development of system network improvements is underway. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) are also developed as advanced coding modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) are used as advanced access technologies.

[0003] The Internet, as a human-centered connected network in which humans generate and consume information, is now developing towards the Internet of Things (IoT), in which distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE), which is a combination of IoT technology and big data processing technology through connection with cloud servers, has emerged. As technical elements required for IoT implementation (such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology"), sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. have been studied recently. Such an IoT environment can provide smart Internet technology services that create new value for human life by collecting and analyzing data generated between networked things. Through the integration and combination between existing information technology (IT) and various industrial applications, IoT can be applied to various fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communications (MTC), and machine-to-machine (M2M) communications can be implemented through beamforming, MIMO, and array antennas. Cloud radio access network (cloud RAN) as an application of the above-mentioned big data processing technology can also be considered as an example of the fusion of 5G technology and IoT technology. In order to send the same data to multiple terminals gathered in a specific area in a mobile communication network, data can be sent to each terminal via unicast, but for resource efficiency, it is necessary to provide data services via multicast / broadcast. Summary of the invention

[0005] Technical issues

[0006] In order to send the same data to multiple terminals gathered in a specific area in a mobile communication network, it is necessary to provide services through multicast / broadcast. For example, in order to provide media services (e.g., TV / audio services), vehicle-to-everything (V2X) services, or large-scale cellular Internet of Things (CIoT) services to multiple terminals in a specific area, a method for sending data via multicast / broadcast is required, and for this purpose, information about the services currently delivered between the terminal and the network via multicast / broadcast and the service authentication process should be provided. The present disclosure proposes an effective control method for providing 5G-based multicast / broadcast services to terminals.

[0007] Technical Solution

[0008] According to an embodiment of the present disclosure, a method performed by a session management function (SMF) in a wireless communication system may include: receiving a first message from a terminal, the first message including information about a request to establish a protocol data unit (PDU) session for a multicast broadcast service (MBS); sending a second message to an application server (AS) including information for requesting authentication of the PDU session; receiving a third message from the AS as a response to the second message; and sending a fourth message to the terminal including information about the MBS.

[0009] Sending the second message may include: receiving a fifth message including subscription information of the terminal from a unified data management (UDM); and sending a second message to the AS based on the subscription information, wherein the subscription information includes information of the MBS, information about whether the MBS is authorized to the subscriber, user identifier information to be used for the MBS, information about whether the MBS data network name (DNN) is authorized, and at least one of identifier information of the AS.

[0010] The second message may include current location information of the terminal or user identifier information to be used for the MBS.

[0011] The fourth message may include at least one of identifier information of the MBS, slice identifier information corresponding to the MBS, key information of the MBS, multicast Internet Protocol (IP) address information of the MBS server, and service session start time information of the MBS.

[0012] According to another embodiment of the present disclosure, a method performed by a terminal in a wireless communication system may include: sending a first message to a session management function (SMF), the first message including information about a request to establish a protocol data unit (PDU) session for a multicast broadcast service (MBS); and receiving a second message including information about the MBS from the SMF when an application server (AS) successfully performs authentication of the PDU session.

[0013] Authentication of the PDU session may be performed based on subscription information of the terminal received from Unified Data Management (UDM).

[0014] The first message may include at least one of Data Network Name (DNN) information of the MBS, identifier information of the MBS, and information on Authentication and Authorization (AA) of the MBS.

[0015] The second message may include at least one of identifier information of the MBS, slice identifier information corresponding to the MBS, key information of the MBS, multicast Internet Protocol (IP) address information of the MBS server, and service session start time information of the MBS.

[0016] According to another embodiment of the present disclosure, the SMF in a wireless communication system may include: a transceiver; and a controller, configured to receive a first message from a terminal via the transceiver, the first message including information about a request to establish a protocol data unit (PDU) session for a multicast broadcast service (MBS), send a second message including information for requesting authentication of the PDU session to an application server (AS) via the transceiver, receive a third message in response to the second message from the AS via the transceiver, and send a fourth message including information about the MBS to the terminal via the transceiver.

[0017] According to another embodiment of the present disclosure, a terminal in a wireless communication system may include: a transceiver; and a controller, configured to send a first message to a session management function (SMF) via the transceiver, the first message including information about a request to establish a protocol data unit (PDU) session for a multicast broadcast service (MBS), and receive a second message including information about the MBS from the SMF via the transceiver when an application server (AS) successfully performs authentication of the PDU session.

[0018] Advantageous Effects of the Invention

[0019] According to an embodiment of the present disclosure, 5G-based multicast / broadcast services can be provided to terminals. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 is a diagram showing a 5G system structure according to an embodiment of the present disclosure;

[0021] Figure 2 is a diagram showing a 5G system structure according to another embodiment of the present disclosure;

[0022] Figure 3 A process for MBS service authentication and service information delivery for a terminal according to an embodiment of the present disclosure is shown;

[0023] Figure 4 is a diagram illustrating a procedure for subscriber authentication / authorization for supporting MBS according to an embodiment of the present disclosure;

[0024] Figure 5 is a diagram illustrating a process for MBS service authentication and terminal control according to an embodiment of the present disclosure;

[0025] Figure 6 is a diagram illustrating operations of a terminal and a network according to an embodiment of the present disclosure;

[0026] Figure 7 is a diagram illustrating a process for providing MBS service information by using an MBS service authentication process through an embodiment of the present disclosure;

[0027] Figure 8 is a diagram illustrating a process for providing MBS service information by using a control plane through an embodiment of the present disclosure;

[0028] Fig. 9 shows the structure of a terminal according to an embodiment of the present disclosure;

[0029] Fig.10 shows the structure of a base station according to an embodiment of the present disclosure; and

[0030] Fig.11 The network entity structure according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0031] Hereinafter, the operating principle of the present disclosure will be described in detail with reference to the accompanying drawings. In the following description of the present disclosure, when it is determined that the description may make the subject matter of the present disclosure unnecessarily unclear, the detailed description of the known functions or configurations incorporated herein will be omitted. The terms to be described below are defined in consideration of the functions in the present disclosure, and may differ depending on the user, the user's intention or custom. Therefore, the definition of the terms should be based on the content of the entire specification.

[0032] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted or schematically shown. In addition, the size of each element does not fully reflect the actual size. In the accompanying drawings, the same or corresponding elements have the same reference numerals.

[0033] By referring to the embodiments described in detail below in conjunction with the accompanying drawings, the advantages and features of the present disclosure and the ways to achieve them will become apparent. However, the present disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided only to fully disclose the present disclosure and inform those skilled in the art of the scope of the present disclosure, and the present disclosure is limited only by the scope of the attached claims. Throughout the specification, the same or similar reference numerals represent the same or similar elements.

[0034] In this article, it will be understood that each box of the flowchart diagram and the combination of boxes in the flowchart diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create a component for implementing the function specified in one or more flowchart boxes. These computer program instructions can also be stored in a computer-available or computer-readable memory, which can instruct the computer or other programmable data processing device to operate in a particular manner, so that the instructions stored in the computer-available or computer-readable memory produce an article of instruction components including the functions specified in one or more flowchart boxes. Computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are performed on a computer or other programmable device, thereby generating a computer-implemented process, so that the instructions executed on a computer or other programmable device provide steps for implementing the functions specified in one or more flowchart boxes.

[0035] In addition, each frame of the flow chart can represent a module, a code segment or a code portion, which includes one or more executable instructions for implementing (multiple) specified logical functions. It should also be noted that in some alternative implementations, the functions mentioned in the frame may not appear in order. For example, two frames shown in succession can actually be performed substantially simultaneously, or these frames can sometimes be performed in reverse order, depending on the functions involved.

[0036] As used herein, "unit" refers to a software element or hardware element that performs a predetermined function, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). However, "unit" does not always have the meaning of being limited to software or hardware. "Unit" can be constructed to be stored in an addressable storage medium or to execute one or more processors. Therefore, "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, processes, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays and parameters. The elements and functions provided by "unit" can be combined into a smaller number of elements or "units", or divided into a larger number of elements or "units". In addition, elements and "units" can be implemented as copying one or more CPUs in equipment or secure multimedia cards. In addition, "unit" in an embodiment can include one or more processors.

[0037] Hereinafter, the operating principle of the present disclosure will be described in detail with reference to the accompanying drawings. In the following description of the present disclosure, when it is determined that the description may make the subject matter of the present disclosure unnecessarily unclear, the detailed description of the known functions or configurations incorporated herein will be omitted. The terms to be described below are defined in consideration of the functions in the present disclosure, and may be different according to the user, the user's intention or habit. Therefore, the definition of the terms should be based on the content of the entire specification. In the following description, a base station is an entity that allocates resources to a terminal, and may be at least one of a gNode B, an eNode B, a node B, a base station (BS), a wireless access unit, a base station controller, and a node on a network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. Of course, the examples of base stations and terminals are not limited thereto. The following description of the present disclosure is directed to a technology for receiving broadcast information from a base station by a terminal in a wireless communication system. The present disclosure relates to a communication technology and a system thereof for integrating IoT technology with a fifth generation (5G) communication system, which is designed to support a higher data transmission rate than a fourth generation (4G) system. The present disclosure can be applied to smart services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail commerce, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology.

[0038] As used in the following description, for the sake of convenience, terms related to broadcast information, terms related to control information, terms related to communication coverage, terms related to state changes (e.g., events), terms related to network entities, terms related to messages, terms related to device elements, etc. are illustratively used. Therefore, the present disclosure is not limited to the terms used below, and other terms related to subjects having equivalent technical meanings may be used.

[0039] As used in the following description, for the sake of convenience, terms used to identify access nodes, terms related to network entities, terms related to messages, terms related to interfaces between network entities, terms related to various identification information, etc. are illustratively used. Therefore, the present disclosure is not limited to the terms used below, and other terms related to subjects having equivalent technical meanings may be used.

[0040] In the following description of the present disclosure, for the convenience of description, the terms and names defined in the 5G system standard will be used. However, the present disclosure is not limited to these terms and names, and can be applied to systems that comply with other standards in the same manner.

[0041] Figure 1 is a diagram showing a 5G system structure according to an embodiment of the present disclosure.

[0042] refer to Figure 1 , the 5G system may include user equipment (UE), next generation (NG)-radio access network (RAN), access and mobility management function (AMF), session management function (SMF)-M, user plane function (UPF)-M, policy control function (PCF), unified data management (UDM), network exposure function (NEF), 5G broadcast / multicast service center (5BMSC) and / or 5GMBS (5MBS) content provider.

[0043] UE refers to a terminal (user terminal), and may include, for example, a terminal capable of receiving an MBS service and / or a general unicast communication-based service.

[0044] NG-RAN is a base station that provides a wireless communication function by interworking with the 5G system and may include a base station using NR (New Radio) and / or a base station supporting E-UTRA.

[0045] The AMF is a network function (NF) that manages wireless network access and mobility of a terminal (UE).

[0046] The SMF is an NF that manages sessions of a terminal, and session information includes QoS information, charging information, and packet processing information.

[0047] UPF is the NF that processes user plane services and is controlled by SMF.

[0048] In an embodiment of the present disclosure, it is described that among the functions of an existing MBMS-GW for providing MBS, the control plane part is contained in the SMF so as to be configured to the SMF-M, and the user plane part among the MBMS-GW functions is contained in the UPF so as to be configured to the UPF-M. In this case, the SMF-M and the UPF-M can support both the processing of existing unicast communication-based services and the processing of MBS. In this specification, the SMF that supports both the processing of unicast communication-based services and the processing of MBS is referred to as SMF-M to distinguish it from the SMF that only supports the processing of unicast communication-based services, but the two may be collectively referred to as SMF. Similarly, the UPF that supports both the processing of unicast communication-based services and the processing of MBS is referred to as UPF-M to distinguish it from the UPF that only supports the processing of unicast communication-based services, but the two may be collectively referred to as UPF.

[0049] The 5BMSC may support authentication of MBS, interaction with external MBS content providers, and content delivery. In an embodiment of the present disclosure, the 5BMSC may also be divided into a control plane function (5BMSC-CP) and a user plane function (5BMSC-UP).

[0050] Depending on the embodiment, SMF-M may be divided into SMF for processing unicast communication (service based on unicast communication) and MBSMF for processing MBS, and UPF-M may be divided into UPF for processing unicast communication and MBUPF for processing MBS. This will be referred to below. Figure 2 Give a description.

[0051] Figure 2 is a diagram showing a 5G system structure according to another embodiment of the present disclosure.

[0052] refer to Figure 2 , the 5G system may include a user equipment (UE), a new generation (NG)-radio access network (RAN), an access and mobility management function (AMF), a session management function (SMF), an MBSMF, a user plane function (UPF), an MBUPF, a policy control function (PCF), a unified data management (UDM), a network exposure function (NEF), a 5G broadcast / multicast service center (5BMSC) and / or a 5MBS content provider. That is, the 5G system may also include an MBSMF and an MBUPF for processing MBS.

[0053] exist Figure 1 and Figure 2In order for the control plane to control the user plane, rules to be used when the control plane processes user plane traffic (or packets) can be generated and delivered to the user plane. Figure 1 In the structure of , SMF-M generates rules for packet processing of MBS and processing of unicast services, and delivers the generated rules to UPF-M. Figure 2 In the structure, MBSMF and MBUPF operate separately from SMF and UPF, rules for controlling unicast services are generated by SMF and delivered to UPF, and rules for controlling MBS services are generated by MBSMF and delivered to MBUPF.

[0054] Figure 3 A process for MBS service authentication and service information delivery for a terminal according to an embodiment of the present disclosure is shown.

[0055] Operation S3010. The terminal (UE) performs a process for registering with the network, and the process starts with the terminal sending a registration request message to the AMF. The terminal may include information indicating whether MBS or 5G MBS (5MBS) is supported (e.g., an MBS indicator) in the request message to inform the network whether the terminal itself supports MBS or 5MBS. If the terminal has information about MBS services that the terminal itself wants to receive (e.g., a service identifier or slice information, etc.), this may be specified in the request message so as to be sent.

[0056] Operation S3020. The AMF uses the subscription information (subscription data) of the terminal to process the registration request of the terminal. If the terminal has already registered with the network, the subscription information of the terminal may be stored in the AMF, or may be stored as part of the UE context received from another AMF / MME. Alternatively, if the process is to handle a new registration, the AMF receives the subscription information from the UDM (or HSS). If a commercial operator performs MBS control based on subscription information, the subscription information may include the subscriber's MBS service information, and the information may include whether the MBS service is authorized, basic information about the MBS service (e.g., temporary mobile group identity (TMGI), service URL, etc.), a data network name (DNN) associated with the MBS service, and one or more of the NW slice IDs associated with the MBS service.

[0057] Operation S3030: A registration process is performed, and during the process, the user may be authenticated to access the 3GPP network.

[0058] Operation S3040. If an additional authentication / authorization process (service authentication / authorization) for MBS is required for the subscriber, the process may be performed using information exchange between the AMF, the authentication server function (AUSF), and the 5BMSC (or a separate authentication authorization accounting (AAA) server), and a process for exchanging authentication information with the terminal may be performed when necessary. During this process, when an authentication request is sent to the AUSF, the AMF may deliver to the AUSF information received from the terminal and MBS related information (e.g., MBS service identifier, etc.) among the subscription information received from the UDM.

[0059] Operation S3050. For each MBS provided by the network (i.e., for each MBS identifier), the AMF receives the MBS security key (MBS service key) to be delivered to the terminal. If operation S3040 is performed, the reception of the MBS key may be performed during operation S3040. The identifier of a specific MBS provided by the network may be a TMGI or a multicast broadcast service (MBS) ID. During this process, if MBS service-related parameters, a multicast IP address of an MBS server, a service session start time, or packet transmission associated with an MBS service are required, an identifier of the MBS slice (S-NSSAI or single network slice selection assistance information) may be included when MBS service control in units of a data network name (DNN) and / or slice to be used by the terminal is applied. Optionally, the MBS server may operate as an AS to deliver or receive information for providing MBS services to the 5G system in the form of a policy through the PCF. In this case, the MBS server may exchange information directly with the PCF or with the PCF through the NEF, and the PCF may deliver the information again to another NF of the 5GC in the form of a policy.

[0060] Operation S3060. If it is necessary to assign an IP address for receiving IP multicast (broadcast) packets to the terminal, the AMF may assign an IP address to the terminal, and if an IP address is stored in the AMF, the stored IP address may be used, or an IP address assignment (MBS session request) may be requested from the NF (SMF-M or MBSMF) that manages the session of the MBS. In this case, the IP address to be assigned to the terminal may be assigned differently according to each MBS service, each subscriber, and the group to which a specific subscriber belongs. To this end, the message for requesting the AMF to perform IP address assignment may include one or more of the aforementioned information (e.g., MBS ID, TMGI, group ID, DNN, etc.).

[0061] Operation S3070. If the AMF requests the NF (SMF-M or MBSMF) managing the MBS session for IP address assignment, the NF that has received the request (for each MBS service, for each subscriber, and for the multicast group to which a specific subscriber belongs) can determine the IP address to be assigned to the terminal by using the subscriber / terminal information included in the request message, and can respond (MBS session response) using the IP address. In this case, the IP address assigned to the terminal included in the response (response message) can be configured differently for each MBS service, for each subscriber, and for each multicast group to which a specific subscriber belongs.

[0062] Operation S3080. The AMF delivers information of the MBS to the terminal by using a non-access stratum (NAS) message. For example, if the registration process started in operation S3010 is not completed, the AMF may deliver the information to the terminal by using a registration accept message. Alternatively, if the registration process is completed before performing operation S3080, the AMF may deliver the information to the terminal via a UE configuration update (UCU) process. The information delivered to the terminal may include at least one of an MBS identifier allowed for the terminal, a slice identifier corresponding to a specific MBS, an MBS service key, an IP address to be used by the terminal, a transmission start time, an IP address of a multicast transmission server, and a DNN to be used by the terminal when packet transmission associated with an MBS service is required.

[0063] Operation S3090. The terminal performs a process for receiving MBS transmission by using the received information.

[0064] Figure 4 is a diagram illustrating a procedure for subscriber authentication / authorization supporting MBS according to an embodiment of the present disclosure.

[0065] Operation S4010. The terminal (UE) performs a process for registering with the network, and the process starts with the terminal sending a registration request message to the AMF. The terminal may include information indicating whether MBS or 5MBS is supported (e.g., an MBS indicator) in the request message to inform the network whether the terminal itself supports MBS or 5MBS. If the terminal has information about MBS services that the terminal itself wants to receive (e.g., a service identifier or slice information, etc.), this may be specified in the request message so as to be sent.

[0066] Operation S4020. The AMF uses the subscription information (subscription data) of the terminal to process the registration request of the terminal. If the terminal has already registered with the network, the subscription information of the terminal may be stored in the AMF, or may be stored as part of the UE context received from another AMF / MME. Alternatively, if the process is to handle a new registration, the AMF receives the subscription information from the UDM (or HSS). If a commercial operator performs MBS control based on subscription information, the subscription information may include the subscriber's MBS service information, and the information may include whether the MBS service is authorized, basic information about the MBS service (e.g., TMGI, service URL, etc.), a DNN associated with the MBS service, and one or more of the NW slice IDs associated with the MBS service.

[0067] Operation S4030. A registration process is performed, and during the process, the subscriber may be authenticated to access the 3GPP network.

[0068] Operation S4040. The AMF delivers a message (Registration Accept) to the terminal to inform that registration has been allowed. If 5MBS is provided by a specific slice and an additional authentication process is required for this, the AMF may include an indication that an additional authentication process for the slice is in progress (or required) while delivering a Registration Accept message to the terminal.

[0069] Operation S4050. The AMF performs a slice-specific authentication / authorization process for the MBS slice. For example, if the registration acceptance message includes an indication that additional authentication of the MBS slice is required, the AMF may perform an authentication / authorization process for the MBS slice (slice authentication / authorization process). During this process, while delivering a NAS MM transmission message to the terminal, the AMF may inform that a slice identifier (S-NSSAI) of the MBS slice and an identifier (Extensible Authentication Protocol (EAP) ID) of the terminal for MBS authentication are requested. In addition, the AMF may include an MBS identifier (e.g., TMGI, etc.) indicating a specific MBS in the NAS MM transmission message. In response to this, the terminal sends a NAS MM transmission message to the AMF, including a slice identifier and a subscriber identifier response for the MBS. If a specific MBS needs to be referred to, the terminal may include the MBS identifier in the NAS MM transmission message. The AMF then performs authentication / authorization of the MBS slice to the AAA server via the AUSF. In this case, when authentication / authorization is additionally requested for a specific MBS among the MBSs that can be provided in the MBS slice, the AMF may deliver a message including an MBS identifier, or if the service provision is authorized only for a specific MBS, the AAA server may inform the AMF and the terminal of this by including the MBS identifier in the response message. The AMF delivers the EAP message received via the AUSF to the terminal. During this process, the terminal may receive one or more additional information of the MBS service (e.g., whether the MBS service is authorized, basic information about the MBS service (TMGI, service URL, etc.), MBS key, DNN associated with the MBS service, NW slice ID associated with the MBS service, multicast IP address of the MBS server, and service session start time) via the EAP message received from the network. If the AMF of the terminal needs to be changed or the slice information of the terminal needs to be updated via an additional authentication process for the slice, the AMF may deliver the information to the terminal by using the UE Configuration Update (UCU) process. If authentication of the MBS slice fails, and when the slice selected and requested to be accessed by the terminal is only the MBS slice, or when the terminal is not allowed to access slices other than the MBS slice, the AMF may perform a deregistration procedure for the terminal.

[0070] Operation S4060. If the detailed MBS information is not delivered to the terminal via the slice authentication / authorization process, the AMF may perform subsequent operations to deliver additional information of the MBS to the terminal. For each MBS provided by the network (i.e., for each MBS identifier), the AMF receives the MBS security key (or MBS service key) to be delivered to the terminal. The identifier of a specific MBS provided by the network may be a TMGI or a multicast broadcast service (MBS) ID. The AMF may receive information about the MBS service, whether the MBS service is authorized, the DNN associated with the MBS service, the NW slice ID associated with the MBS service, the multicast IP address of the MBS server, and / or the service session start time. Alternatively, the MBS server may operate as an AS to deliver or receive information for providing MBS services to the 5G system in the form of a policy through the PCF. In this case, the MBS server may exchange information directly with the PCF, or may exchange information with the PCF through the NEF, and the PCF may deliver the information again to another NF of the 5GC in the form of a policy.

[0071] Operation S4070. If it is necessary to assign an IP address for receiving IP multicast (broadcast) packets to the terminal, the AMF may assign an IP address to the terminal, and if an IP address is stored in the AMF, the stored IP address may be used, or an IP address assignment (MBS session request) may be requested from the NF (SMF-M or MBSMF) that manages the session of the MBS. In this case, the IP address to be assigned to the terminal may be assigned differently according to each MBS service, each subscriber, and the group to which a specific subscriber belongs. To this end, the message for requesting the assignment of an IP address by the AMF may include one or more of the aforementioned information (e.g., MBSID, TMGI, group ID, DNN, etc.).

[0072] Operation S4080. If the AMF requests the NF (SMF-M or MBSMF) managing the MBS session for IP address assignment, the NF having received the request may determine the IP address to be assigned to the terminal by using the subscriber / terminal information included in the request message (for each MBS service, for each subscriber, and for the multicast group to which a specific subscriber belongs), and may respond (MBS session response) using the IP address. In this case, the IP address assigned to the terminal included in the response (response message) may be configured differently for each MBS service, for each subscriber, and for each multicast group to which a specific subscriber belongs.

[0073] Operation S4090. The AMF may deliver the information of the MBS to the terminal by using a NAS message. For example, if the registration process started in operation S4010 is not completed, the AMF may deliver the information to the terminal by using a registration accept message. Alternatively, if the registration process is completed before operation S4090 is performed, the AMF may deliver the information to the terminal via a UE configuration update (UCU) process. The information delivered to the terminal may include an MBS identifier allowed for the terminal, a slice identifier corresponding to a specific MBS, an MBS service key, an IP address to be used by the terminal, a transmission start time, a DNN to be used in the event that a separate session with the MBS server needs to be established, and at least one of the IP addresses of the multicast transmission server. Depending on the embodiment, the process may be performed in conjunction with the UCU performed at the end of operation S4050 to update the final terminal slice information according to slice authentication.

[0074] Operation S4100. The terminal may perform a process for receiving MBS transmission by using the received information.

[0075] Figure 5 is a diagram illustrating a process for MBS service authentication and terminal control according to an embodiment of the present disclosure.

[0076] Operation S5010. When necessary, the terminal (UE) starts a process for establishing (configuring, generating) a protocol data unit (PDU) session for the MBS service for initial access to or service reception of the MBS service. The terminal sends a PDU session establishment request (PDU session configuration (generation) request message) to the SMF (SMF-M in this embodiment) via the AMF, and the message may include a DNN (MBS DNN) configured for the MBS service, or may include an identifier indicating that the session is for the MBS service. The message may also include additional information for secondary authentication / authorization of the MBS service (e.g., an SM PDU DN request container).

[0077] Operation S5020. The AMF receives a request message from the terminal and, if necessary, receives subscription information / data of the terminal and information for SMF selection from the UDM. The subscription information may include information for controlling MBS services, whether the MBS service is authorized to the subscriber, whether the MBS DNN is authorized to the subscriber, etc. The AMF selects an SMF for providing the MBS service by using the UE context, the subscription information, and the information included in the request message of the terminal.

[0078] Operation S5030. The AMF sends a request message (create SM context request) for generating a PDU session to the selected SMF. The create SM context request sent by the AMF may include a PDU session generation request message sent by the terminal and information for session generation (e.g., DNN, PDU, session ID, etc.), and may include the current location information of the terminal (user location information) and / or information for controlling MBS services.

[0079] Operation S5040. The SMF may process the session generation request received from the AMF, and during the process, may receive the subscription information of the corresponding subscriber from the UDM. The subscription information received by the SMF may include not only basic session information, but also information of the MBS service, whether the MBS service is authorized to the subscriber, a user identifier (universal public subscription identifier (GPSI)) for each service of the MBS service, whether the MBS DNN is authorized to the subscriber, and / or an identifier (e.g., name, address, etc.) of an application server (AS) used to interact with the subscribed MBS service.

[0080] Operation S5050. The SMF performs secondary authentication / authorization on the session by using the subscription information and the session generation request made by the terminal. The SMF generates an authentication and authorization request message (AA request) and sends it to a server (5BMSC or a separate application server (AS)) providing MBS services via the UPF (UPF-M in this embodiment). The request message sent by the SMF may include the SM PDU DN request received from the terminal, and may include the current location information (user location information) of the terminal. The request message sent by the SMF may include a user identifier (GPSI) for the MBS service of the subscriber.

[0081] Operation S5060. An authentication / authorization process is performed between the terminal and a server (5BMSC or a separate application server) providing MBS services. During this process, the server and the terminal exchange messages (e.g., SMPDU DN containers) for authentication via SMF (authentication message exchange). During this process, if location-based service control is required, the MBS server may determine whether to allow the service considering the received current location of the terminal, or may determine and deliver service parameters considering the location.

[0082] Operation S5070. If the server finally accepts the request for secondary authentication and authorization of the MBS user, an authentication and authorization response message (AA response) for notifying the success of the authentication is sent, and the message may include information of the MBS service. The information delivered to the terminal may include one or more of an MBS identifier allowed for the terminal, a slice identifier corresponding to a specific MBS, an MBS service key, an IP address to be used by the terminal, a transmission start time, and an IP address of a multicast transmission server. This information may be included in, for example, DN authorization data included in the response message so as to be sent to the terminal.

[0083] Operation S5080. The terminal performs a process for receiving MBS transmission by using the received information.

[0084] Figure 6 is a diagram illustrating operations of a terminal and a network according to an embodiment of the present disclosure.

[0085] Figure 6 Operations S6010 to S6030 and Figure 3 Operations S3010 to S3030 are the same as those of FIG. 1 , and accordingly, repeated descriptions will be omitted.

[0086] Operation S6040. A server (MBS server) providing MBS services (e.g., 5BMSC or a separate application server (AS)) registers information for service provision in the 5G system. This process can be performed by the MBS server via the NEF as a service exposure function, for example, the MBS server can call a service (Nnef) of the NEF and deliver parameters for service provision to the NEF. The Nnef service used by the MBS server can be, for example, Nnef_AFsessionWithQoS for generating a session for sending or receiving information between the MBS server and the NEF, or can be Nnef_serviceParameter or Nnef_ParameterProvision for enabling the MBS server to deliver service-related parameters. In this case, the MBS server operates as an AF (application function) of the NEF. The NEF can directly store and use the information received from the MBS server, can store the information in a unified data repository (UDR) and use it when necessary, or can cause another NF to view the information. Information about MBS services may include an MBS service identifier (e.g., TMGI), an MBS security key, a service session start time, an IP address to be used for multicast transmission, and one or more of a DNN to be used together when unicast transmission is required. If location-based MBS service control is required, the MBS service information may be configured differently for each specific location information (e.g., information capable of identifying a location, such as a cell identifier, a tracking area identifier, or GPS information). Alternatively, the MBS server may operate as an AS to deliver or receive information for providing MBS services to the 5G system in the form of a policy through the PCF. In this case, the MBS server may exchange information directly with the PCF, or may exchange information with the PCF through the NEF, and the PCF may deliver the information again to another NF of the 5GC in the form of a policy.

[0087] Operation S6050. During registration, if an authentication process occurs and the AUSF receives an authentication request for a subscriber or MBS service, the AUSF may send a request to the UDR to receive service parameters related to the MBS. The request message of the AUSF may include an identifier of the targeted MBS service, an identifier of the subscriber, and / or an identifier of the MBS service user. If location-based service control is required, the AUSF may also deliver the current location information of the terminal received from the AMF. The NEF or UDR that has received the request determines the validity of the request, and if the MBS service can be provided to the corresponding subscriber / user, the information about the MBS service described in operation S6040 is loaded and sent in the response message. If location-based service control is required, the MBS service information may be determined taking into account the current location of the terminal.

[0088] Operation S6060. If the detailed MBS information is not delivered to the terminal via a separate slice authentication / authorization process, the AMF may perform subsequent operations to deliver additional information of the MBS to the terminal. For each MBS provided by the network (i.e., for each MBS identifier), the AMF receives an MBS security key (or MBS service key) to be delivered to the terminal. The identifier of a specific MBS provided by the network may be a TMGI or a multicast broadcast service (MBS) ID. The AMF may receive information of the MBS service, whether the MBS service is authorized, the DNN associated with the MBS service, the NW slice ID associated with the MBS service, the multicast IP address of the MBS server, and / or the service session start time.

[0089] Operation S6070. If it is necessary to assign an IP address for receiving IP multicast (broadcast) packets to the terminal, the AMF may assign an IP address to the terminal, and if an IP address is stored in the AMF, the stored IP address may be used, or an IP address assignment (MBS session request) may be requested from the NF (SMF-M or MBSMF) that manages the session of the MBS. In this case, the IP address to be assigned to the terminal may be assigned differently according to each MBS service, each subscriber, and the group to which a specific subscriber belongs. To this end, the message for requesting the assignment of an IP address by the AMF may include one or more of the aforementioned information (e.g., MBSID, TMGI, group ID, DNN, etc.).

[0090] Operation S6080. If the AMF requests the NF (SMF-M or MBSMF) managing the MBS session for IP address allocation, the NF having received the request determines the IP address to be allocated to the terminal by using the subscriber / terminal information included in the request message, and responds (MBS session response) using the IP address. In this case, the IP address allocated to the terminal included in the response (response message) may be configured differently for each MBS service, for each subscriber, and for each multicast group to which a specific subscriber belongs.

[0091] Operation S6090. The AMF delivers the information of the MBS to the terminal by using a NAS message. For example, if the registration process started in operation S6010 is not completed, the AMF may deliver the information to the terminal by using a registration accept message. Alternatively, if the registration process is completed before operation S6090 is performed, the AMF may deliver the information to the terminal via a UE configuration update (UCU) process. The information delivered to the terminal may include an MBS identifier allowed for the terminal, a slice identifier corresponding to a specific MBS, an MBS service key, an IP address to be used by the terminal, a transmission start time, a DNN to be used in the event that a separate session with the MBS server needs to be established, and at least one of the IP addresses of the multicast transmission server. Depending on the embodiment, the process may be performed in conjunction with the UCU performed at the end of operation S6060 to update the final terminal slice information according to slice authentication.

[0092] Operations S6100 to S6110. The terminal performs an operation of receiving a multicast / broadcast service by using the received information, and starts a PDU session generation process if it is necessary to generate a separate PDU session using the received DNN.

[0093] Figure 7 is a diagram illustrating a process of providing MBS service information by using an MBS service authentication procedure through an embodiment of the present disclosure.

[0094] Figure 7 Operations S7010 to S7030 and Figure 3 Operations S3010 to S3030 and Figure 6 Operations S6010 to S6030 are the same as those of FIG. 1 , and accordingly, repeated descriptions will be omitted.

[0095] In operation S7030, this embodiment corresponds to the case where the AMF sends a request for authentication / authorization for MBS to the AUSF. In this embodiment, the authentication of the 5MBS service can be included in the authentication of the subscriber's 5G network access / registration, and the authentication between the 5G system and the MBS service provision NF can be used to send MBS service information (parameters).

[0096] Operation S7040. The AUSF sends a request (AA request) for providing authentication and information about the MBS service to the terminal. If the 5BMSC providing the MBS service is directly linked to the AUSF, the AUSF requests the information by directly calling the NF service provided by the 5BMSC, or if the link is made via the NEF, the 5BMSC requests the information from the NEF. If the terminal provides a separate MBS service identifier at the time of the registration request, or if the subscription information includes information that can identify the MBS service, the AUSF takes this into account, otherwise, the AUSF selects the 5BMSC by using the subscriber's MBS user identifier (GPSI) to send the request directly, or if the request should be made via the NEF, the AUSF includes the information in the request message so that the NEF can discover the target 5BMSC. If the request is made via the NEF, the NEF discovers the target 5BMSC by using the received information, and sends a service information request to the 5BMSC in response to the AUSF's request. If location-based service control is required, the AUSF can receive the terminal's location information (user location information) from the AMF and include it in the request message.

[0097] Operation S7050. The 5BMSC having received a request for service information or authentication for an MBS service may determine, if necessary, whether the provision of the MBS service is authorized to the corresponding subscriber or user. If location-based service control is required in operation S7040 and the location information of the terminal is received, the 5BMSC may determine whether to allow the service in consideration of the current location of the terminal, or may determine and deliver service parameters in consideration of the location. The 5BMSC may deliver information on the MBS service as a response (AA response) to the NF (NEF or AUSF) that has sent the request, and information on the MBS service (MBS service information) may include an MBS service identifier (e.g., TMGI), an MBS security key, a service session start time, an IP address for multicast transmission, and / or a DNN to be used when unicast transmission is also required. If the NEF receives the corresponding information, the NEF delivers the information on the MBS service to the AUSF that has sent the request.

[0098] Operation S7060. The AUSF may send the received MBS service information to the AMF via an AA response, and the MBS service information may include an MBS service identifier (e.g., TMGI), an MBS security key, a service session start time, an IP address to be used for multicast transmission, and / or a DNN to be used when unicast transmission is also required.

[0099] Operations S7070 to S7110 and Figure 6Operations S6070 to S6110 are the same as those of FIG. 1 , and accordingly, repeated descriptions will be omitted.

[0100] Figure 8 is a diagram illustrating a process of providing MBS service information by using a control plane through an embodiment of the present disclosure.

[0101] Figure 8 Operations S8010 to S8030 and Figure 3 Operations S3010 to S3030 and Figure 6 Operations S6010 to S6030 are the same as those of FIG. 1 , and therefore, repeated descriptions will be omitted.

[0102] In operation S8030, this embodiment corresponds to a case where the AMF directly requests a process for receiving information about the MBS service and delivering it to the terminal from the 5BMSC via the control plane.

[0103] Operation S8040. The AMF sends a request for authentication and information for providing MBS services to the terminal. In this embodiment, if the 5BMSC providing the MBS service is directly linked to the AMF, the AMF directly calls the NF service provided by the 5BMSC to request information. If the terminal provides a separate MBS service identifier at the time of the registration request, or if the subscription information includes information that can identify the MBS service, the AMF takes this into account, otherwise, the AMF uses the subscriber's MBS user identifier (GPSI) to select the 5BMSC as the target of the request. For this process, the AMF can use this information to perform a process for discovering and selecting the 5BMSC together with the NRF or SCP. If the AMF and the 5BMSC are not directly linked, that is, if the request should be made via the NEF, the AMF can include this information in the request message so that the NEF can discover the target 5BMSC. If the request is made via the NEF, the NEF discovers the target 5BMSC by using the received information, and sends a service information request to the 5BMSC in response to the request of the AMF. If location-based service control is required, the AMF can include the location information (user location information) of the terminal in the request message.

[0104] Operation S8050. In response, the 5BMSC that has received the service information request for the MBS service may deliver the information of the MBS service to the AMF, and if location-based service control is required in operation S8040 and the location information of the terminal is received, the 5BMSC may determine whether to allow the service in consideration of the current location of the terminal, or may determine and deliver service parameters in consideration of the location. Information about the MBS service may include an MBS service identifier (e.g., TMGI), an MBS security key, a service session start time, an IP address to be used for multicast transmission, and / or a DNN to be used when unicast transmission is also required. If the request is received via the NEF, the 5BMSC sends a response to the NEF, and the NEF delivers the information about the MBS service to the AMF that has sent the request. Alternatively, the MBS server may operate as an AS to deliver or receive information for providing MBS services to the 5G system in the form of a policy through the PCF. In this case, the MBS server may exchange information directly with the PCF, or may exchange information with the PCF through the NEF, and the PCF may deliver the information again to another NF of the 5GC in the form of a policy.

[0105] Operation S8060 to S8100 with Figure 6 Operations S6070 to S6110 are the same as those of FIG. 1 , and accordingly, repeated descriptions will be omitted.

[0106] Fig. 9 The structure of a terminal according to an embodiment of the present disclosure is shown.

[0107] refer to Fig. 9 , the terminal may include a transceiver 910, a controller 920, and a storage unit 930. In the present disclosure, the controller may be defined as a circuit, an application specific integrated circuit, or at least one processor.

[0108] The transceiver 910 may transmit a signal to another network entity or receive a signal from another network entity. The transceiver 910 may receive, for example, system information from a base station and may receive a synchronization signal or a reference signal.

[0109] According to the embodiments proposed in the present disclosure, the controller 920 may control the overall operation of the terminal. For example, the controller 920 may control the signal flow between the various blocks to Figures 1 to 8 For example, according to an embodiment of the present disclosure, the controller 920 may control the operations proposed in the present disclosure so as to provide an MBS service in a wireless communication system.

[0110] The storage unit 930 may store at least one of information transmitted or received via the transceiver 910 and information generated via the controller 920. For example, according to the aforementioned embodiment of the present disclosure, the storage unit 930 may store information for providing MBS services (eg, MBS identification information, etc.).

[0111] Fig.10 The structure of a base station according to an embodiment of the present disclosure is shown.

[0112] refer to Fig.10 , the base station may include a transceiver 1010, a controller 1020, and a storage unit 1030. In the present disclosure, the controller may be defined as a circuit, an application specific integrated circuit, or at least one processor.

[0113] The transceiver 1010 may transmit a signal to another network entity or receive a signal from another network entity. The transceiver 1010 may transmit, for example, system information to the terminal, and may transmit a synchronization signal or a reference signal.

[0114] According to the embodiments proposed in the present disclosure, the controller 1020 may control the overall operation of the base station. For example, the controller 1020 may control the signal flow between the various blocks to Figures 1 to 8 Specifically, the controller 1020 may control the operations proposed in the present disclosure so as to provide MBS services in a wireless communication system according to an embodiment of the present disclosure.

[0115] The storage unit 1030 may store at least one of information transmitted or received via the transceiver 1010 and information generated via the controller 1020. For example, according to the aforementioned embodiment of the present disclosure, the storage unit 1030 may store information for providing MBS services (eg, MBS identification information, etc.).

[0116] Fig.11 FIG. 2 shows a network entity structure according to an embodiment of the present disclosure. Figure 1 and Figure 2 In addition to the terminals and base stations in Fig.11 The network entity may be, for example, one of the network entities of the 5G core network. For example, the network entity may be AMF, SMF-M, UPF-M, MBSMF, MBUPF, etc.

[0117] refer to Fig.11 , the network entity may include a transceiver 1110, a controller 1120, and a storage unit 1130. In the present disclosure, a controller may be defined as a circuit, an application specific integrated circuit, or at least one processor.

[0118] The transceiver 1110 may transmit a signal to another network entity or receive a signal from another network entity.The transceiver 810 may receive, for example, system information from a base station and may receive a synchronization signal or a reference signal.

[0119] According to the embodiments proposed in the present disclosure, the controller 1120 may control the overall operation of the terminal. For example, the controller 1120 may control the signal flow between the various blocks to Figures 1 to 8 For example, according to an embodiment of the present disclosure, the controller 1120 may control the operations proposed in the present disclosure so as to provide an MBS service in a wireless communication system.

[0120] The storage unit 1130 may store at least one of information transmitted or received via the transceiver 1110 and information generated via the controller 1120. For example, according to the aforementioned embodiment of the present disclosure, the storage unit 1130 may store information for providing MBS services (eg, MBS identification information, etc.).

[0121] The methods according to the embodiments described in the claims or the specification of the present disclosure may be implemented by hardware, software, or a combination of hardware and software.

[0122] When these methods are implemented by software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors in an electronic device. At least one program may include instructions that cause an electronic device to perform methods according to the various embodiments of the present disclosure defined by the attached claims and / or disclosed herein.

[0123] Programs (software modules or software) can be stored in non-volatile memory, including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk storage devices, compact disk-ROM (CD-ROM), digital versatile disk (DVD) or other types of optical storage devices, or cassette tapes. Alternatively, any combination of some or all of them can form a memory for storing programs. In addition, multiple such memories may be included in the electronic device.

[0124] In addition, the program can be stored in an attachable storage device that can access the electronic device through a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WLAN), and a storage area network (SAN) or a combination thereof. Such a storage device can access the electronic device via an external port. In addition, a separate storage device on a communication network can access a portable electronic device.

[0125] In the above detailed embodiments of the present disclosure, the elements included in the present disclosure are expressed in the singular or plural, depending on the detailed embodiments presented. However, for ease of description, the singular form or plural form is appropriately selected for the presented situation, and the present disclosure is not limited to elements expressed in the singular or plural. Therefore, an element expressed in the plural may also include a single element, or an element expressed in the singular may also include multiple elements.

[0126] The embodiments of the present disclosure described and shown in the specification and the drawings are only specific examples, which have been presented to easily explain the technical content of the present disclosure and help understand the present disclosure, and are not intended to limit the scope of the present disclosure. That is to say, it is obvious to those skilled in the art that other variations based on the technical ideas of the present disclosure can be implemented. In addition, as needed, the above-mentioned various embodiments can be adopted in combination. For example, a part of an embodiment of the present disclosure can be combined with a part of another embodiment to operate a base station and a terminal. As an example, parts of multiple embodiments of the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above-mentioned embodiments have been described based on an FDD LTE system, other variations based on the technical ideas of the embodiments can also be implemented in other systems (such as TDD LTE, 5G or NR systems).

[0127] In the above detailed embodiments of the present disclosure, the elements included in the present disclosure are expressed in the singular or plural, depending on the detailed embodiments presented. However, for ease of description, the singular form or plural form is appropriately selected for the presented situation, and the present disclosure is not limited to elements expressed in the singular or plural. Therefore, an element expressed in the plural may also include a single element, or an element expressed in the singular may also include multiple elements.

[0128] Although specific embodiments have been described in the detailed description of the present disclosure, various modifications and changes may be made thereto without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be defined as limited to the embodiments, but should be defined by the appended claims and their equivalents.

Claims

1. A method performed by a session management function SMF in a wireless communication system, the method include: receiving a first message from an access and mobility management function AMF, the first message comprising information about a request to establish a protocol data unit PDU session for a multicast broadcast service MBS, wherein the first message comprises an identifier of the session of the MBS and current location information of the terminal; receiving, from the unified data management (UDM), a second message including subscription information of the terminal, the subscription information of the terminal including information indicating whether the terminal is authorized to use the MBS and an identity of at least one session of the MBS allowed for the terminal; determining an authentication result of the request to establish a PDU session based on the subscription information of the terminal; and sending a third message to the terminal as a response to the first message according to the authentication result, the third message including information about the result of establishing the PDU session, The third message includes at least one of the identifiers of at least one session of the MBS determined based on the current location information of the terminal and the identifier of the session of the MBS.

2. The method according to claim 1, in, Based on the selection made by the AMF based on the data network name DNN of the MBS and the information about the network slice of the MBS, a first message is received.

3. The method according to claim 1, in, The first message includes at least one of a data network name DNN of the MBS and information about a slice of the MBS.

4. The method according to claim 1, in, The identity of at least one session of the MBS allowed for the terminal includes a temporary mobile group identity TMGI of the MBS.

5. A method performed by a terminal in a wireless communication system, the method include: sending a first message to a session management function SMF via an access and mobility management function AMF, the first message comprising information on a request to establish a protocol data unit PDU session for a multicast broadcast service MBS, wherein the first message comprises an identifier of the session of the MBS and current location information of the terminal, and In case that authentication of the PDU session is successfully performed based on the subscription information of the terminal, a second message is received from the SMF as a response to the first message, the second message including information about a result of establishing the PDU session, The subscription information of the terminal includes information indicating whether the terminal is authorized to use the MBS and the identity of at least one session of the MBS allowed by the terminal, and the subscription information of the terminal is obtained from the unified data management UDM, and the authentication of the PDU session is determined by the SMF based on the subscription information of the terminal, The second message includes at least one of the identifiers of at least one session of the MBS determined based on the current location information of the terminal and the identifier of the session of the MBS.

6. The method according to claim 5, in, Based on the selection made by the AMF based on the data network name DNN of the MBS and the information about the network slice of the MBS, the first message is sent.

7. The method according to claim 5, in, The first message includes at least one of a data network name DNN of the MBS and information about a slice of the MBS.

8. The method according to claim 5, in, The identity of at least one session of the MBS allowed for the terminal includes a temporary mobile group identity TMGI of the MBS.

9. A session management function SMF in a communication system, the SMF include: Transceiver; and A controller coupled to the transceiver and configured to: receiving a first message from an access and mobility management function AMF, the first message comprising information about a request to establish a protocol data unit PDU session for a multicast broadcast service MBS, wherein the first message comprises an identifier of the session of the MBS and current location information of the terminal, receiving, from the unified data management (UDM), a second message including subscription information of the terminal, the subscription information of the terminal including information indicating whether the terminal is authorized to use the MBS and an identity of at least one session of the MBS allowed for the terminal, Determining the authentication result of the request to establish a PDU session based on the terminal's subscription information, and sending a third message to the terminal as a response to the first message according to the authentication result, the third message including information about the result of establishing the PDU session, The third message includes at least one of the identifiers of at least one session of the MBS determined based on the current location information of the terminal and the identifier of the session of the MBS.

10. The SMF according to claim 9, in, Based on the selection made by the AMF based on the data network name DNN of the MBS and the information about the network slice of the MBS, a first message is received.

11. The SMF according to claim 9, in, The first message includes at least one of a data network name DNN of the MBS and information about a slice of the MBS.

12. The SMF according to claim 9, in, The identity of at least one session of the MBS allowed for the terminal includes a temporary mobile group identity TMGI of the MBS.

13. A terminal in a wireless communication system, the terminal include: Transceiver; and A controller coupled to the transceiver and configured to: sending a first message to a session management function SMF via an access and mobility management function AMF, the first message comprising information about a request to establish a protocol data unit PDU session for a multicast broadcast service MBS, wherein the first message comprises an identifier of the session of the MBS and current location information of the terminal, and In case that authentication of the PDU session is successfully performed based on the subscription information of the terminal, a second message is received from the SMF as a response to the first message, the second message including information about a result of establishing the PDU session, The subscription information of the terminal includes information indicating whether the terminal is authorized to use the MBS and the identity of at least one session of the MBS allowed by the terminal, and the subscription information of the terminal is obtained from the unified data management UDM, and the authentication of the PDU session is determined by the SMF based on the subscription information of the terminal, The second message includes at least one of the identifiers of at least one session of the MBS determined based on the current location information of the terminal and the identifier of the session of the MBS.

14. The terminal according to claim 13, in, Based on the selection made by the AMF based on the data network name DNN of the MBS and the information about the network slice of the MBS, a first message is sent, and The first message includes at least one of a data network name DNN of the MBS and information about a slice of the MBS.

15. The terminal according to claim 13, in, The identity of at least one session of the MBS allowed for the terminal includes a temporary mobile group identity TMGI of the MBS.

Images