Multicast broadcast service management using assistance information

Abstract

Methods, apparatuses, and systems for wireless communication are described. One method of wireless communication includes receiving, by a wireless device, assistance information related to a multicast-broadcast service (MBS) from a network device, and making, by the wireless device, a decision regarding the MBS service based on the assistance information. In some examples, the decision can use location information of the wireless device.

Description

Technical Field

[0001] This patent document is generally concerned with wireless communication. Background Technology

[0002] Wireless communication technologies are propelling the world towards an increasingly interconnected and networked society. The rapid development and technological advancements in wireless communication have led to greater demands for capacity and connectivity. Other aspects, such as energy consumption, equipment cost, spectrum efficiency, and latency, are also important for meeting the needs of various communication scenarios. Compared to existing wireless networks, next-generation systems and wireless communication technologies need to support a growing number of users and devices, and to support the ever-growing mobile society. Summary of the Invention

[0003] Various technologies that can be implemented by embodiments of mobile communication technologies are disclosed, including fifth-generation (5G), new radio (NR) and other wireless networks.

[0004] In one example aspect, a wireless communication method is disclosed. The method includes: receiving auxiliary information related to a multicast or broadcast service (MBS) from a network device by a wireless device; and making a decision about the MBS service by the wireless device based on the auxiliary information.

[0005] In another example aspect, a different wireless communication method is disclosed. This method includes: a network device sending auxiliary information related to a multicast broadcast service (MBS) to a wireless device, the auxiliary information allowing the wireless device to make decisions regarding the MBS service.

[0006] In yet another exemplary aspect, the methods described above are embodied in the form of a computer-readable medium storing processor-executable code for implementing the methods.

[0007] In yet another exemplary embodiment, an apparatus configured or operable to perform the methods described above is disclosed. The apparatus includes at least one processor configured to implement the methods described above.

[0008] The foregoing and other aspects, as well as their embodiments, will be described in more detail in the accompanying drawings, specification, and claims. Attached Figure Description

[0009] Figure 1 This is a block diagram example of a wireless communication system.

[0010] Figure 2 This is a flowchart of an example method for wireless communication.

[0011] Figure 3 An example of a wireless communication network is shown.

[0012] Figure 4 An example of a signal exchange diagram is shown.

[0013] Figure 5 An example of an uncertain ellipse is shown.

[0014] Figure 6 An example of a polygonal shape is shown.

[0015] Figure 7 An example of a signal exchange diagram is shown.

[0016] Figure 8 An example of message syntax is shown.

[0017] Figure 9 An example of message syntax is shown.

[0018] Figure 10 An example of message syntax is shown.

[0019] Figures 11A to 11B An example of a signal exchange diagram is shown.

[0020] Figure 12 An example of a signal exchange diagram is shown.

[0021] Figure 13 An example of a signal exchange diagram is shown.

[0022] Figure 14 This is a flowchart of an example of a wireless communication method.

[0023] Figure 15 This is a flowchart of an example of a wireless communication method. Detailed Implementation

[0024] The chapter headings used in this document are for readability purposes only and do not limit the scope of the embodiments and techniques disclosed in each chapter to that chapter. Certain features are described using examples of 3GPP and fifth-generation (5G) radio protocol terminology. However, the applicability of the disclosed techniques is not limited to 5G radio systems. Furthermore, in this patent document, the separator “ / ” is used to indicate that the listed options are alternatives equivalent to the conjunction “or”. Additionally, various information elements (IEs) examples disclosed herein include fields marked OPTIONAL to indicate that these fields can optionally be implemented by embodiments using a nomenclature similar to 3GPP protocols.

[0025] 1. Introduction

[0026] MBS service area refers to the area where MBS (multicast / broadcast service) is expected to be provided (including broadcast, multicast, or unicast). In the current MBS mechanism, the Network Open Function (NEF) can obtain precise MBS service area information in a geographic area information format (e.g., a list of one or more city addresses or geographic coverage information) from the MBS service provider. Using this information, the NEF can appropriately convert the received MBS service area information into a cell list or TAI (Tracking Area Identifier) ​​list and forward this information to one or more functional entities. These functional entities include the AMF (Access and Mobility Management Function), Session Management Function (SMF), User Plane Function (UPF), and / or NG-RAN (Next Generation Radio Access Network) for MBS service management. For the issues mentioned above, this type of information may be insufficient on the NW side. A typical use case is when an NTN (non-terrestrial network) cell crosses a national border. For an MBS service intended only for country A, the UE may receive the MBS service in country B. In this case, additional MBS service area information (e.g., country information) can be provided to the UE, enabling the UE to use such information, and / or combine it with other information (e.g., its location) to select the appropriate MBS service.

[0027] To achieve the above objectives, the current mechanism has some limitations, necessitating a new solution. These limitations are summarized as follows:

[0028] Currently, the UE cannot obtain coverage information for the MBS service area; the processing of MBS coverage information is solely handled by the NW (Network). The NW can include at least one of NG-RAN / CN (Core Network) / functional entities, such as NEF (Network Open Function), AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), MBS-AMF, MBS-UPF, MBS-SMF, Operations Management and Maintenance (OAM), etc. NG-RAN nodes can include gNB, ng-eNB, eNB, or other base station types (e.g., 6G base stations). Allowing more information on the UE side to help the UE decide on the appropriate MBS service would be beneficial; this would require enhancing existing signaling procedures or defining new signaling.

[0029] On the NW side, accurate MBS service areas only exist at some functional entities (e.g., NEF) and MBS service providers on the CN side. For other functional entities on the NG-RAN or CN side (e.g., SMF, UPF), the MBS service area can only be obtained in the format of a cell identifier list or a TAI (Tracking Area Identifier) ​​list, which may be insufficient. It may be necessary to enhance existing signaling procedures or define new signaling procedures to allow the NG-RAN or SMF / UPF to obtain more accurate or additional information for MBS session management or other purposes, such as providing MBS auxiliary information to the UE for MBS service selection.

[0030] Furthermore, it can be seen that the limitation lies in the fact that MBS broadcast services are provided at the cell level, and that cell may span different areas, while some MBS services may be area-specific. Enhancements could also be considered to allow MBS services to be provided at a granularity smaller than that of a cell (e.g., at the beam level), which would then allow for more precise handling of MBS service areas for the NW. MBS service refers to broadcast / multicast services.

[0031] For broadcast communication services, the same service and the same specific content data are simultaneously provided to all UEs in the geographic area (i.e., all UEs in the broadcast service area as defined in TS 23.247 are authorized to receive data). As discussed in the previous sections, the current UE is unaware of this geographic coverage area.

[0032] Broadcast communication services are delivered to the UE using a broadcast session. The UE can receive broadcast communication services in the RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states.

[0033] For multicast communication services, the same service and the same specific content data are simultaneously provided to a dedicated group of UEs (i.e., not all UEs in the MBS service area as defined in TS 23.247 are authorized to receive data). Multicast communication services are delivered to UEs using multicast sessions. UEs can receive multicast communication services in the RRC_CONNECTED and RRC_INACTIVE states using mechanisms such as PTP (point-to-point) and / or PTM (point-to-multipoint) delivery. HARQ (Hybrid Automatic Repeat Request) feedback / retransmission can be applied to both PTP and PTM transmission modes.

[0034] For MBS broadcast services, system information SIB20 is used to provide the UE with the information required for MCCH / MTCH configuration to obtain MBS services. The MCCH (MBS Control Channel) is a logical channel carrying downlink messages (from the network NW to the UE) containing control information applicable to MBS services transmitted via broadcast or multicast MRBs. For MBS broadcast services, the MBSBroadcastConfiguration message contains control information applicable to MBS broadcast services transmitted via broadcast MRBs (multicast radio bearers). For MBS multicast services, the MBSMulticastConfiguration message contains control information applicable to MBS multicast services transmitted via multicast MRBs for UEs targeting RRC_INACTIVE. The MTCH (MBS Service Channel) is a logical channel (MBS Service Channel) used for MBS services.

[0035] Figure 1 An example of a wireless communication system (e.g., a Long Term Evolution (LTE), 5G, or NR cellular network) including a BS 120 and one or more user equipments (UEs) 111, 112, and 113 is illustrated. In some embodiments, uplink transmissions (131, 132, 133) may include uplink control information (UCI), higher-layer signaling (e.g., radio link layer messages), or uplink information. In some embodiments, downlink transmissions (141, 142, 143) may include DCI, reference signal configuration, reference signal transmission, or higher-layer signaling or other downlink information. The UE may be, for example, a smartphone, tablet, mobile computer, machine-to-machine (M2M) device, terminal, mobile device, Internet of Things (IoT) device, etc. The disclosed techniques can be implemented by UEs 111, 112, and / or 113.

[0036] Figure 2 This is a block diagram representation of a portion of an apparatus according to some embodiments of the present disclosure. Apparatus 205, such as a network device, base station, or wireless device (or UE), can include processor electronics 210, such as at least one processor or microprocessor implementing one or more technologies presented herein. Apparatus 205 may include transceiver electronics 215 for transmitting and / or receiving wireless signals via one or more communication interfaces, such as antenna 220. Apparatus 205 may include other communication interfaces for transmitting and receiving data. Apparatus 205 may include one or more memories (not explicitly shown) configured to store information such as data and / or instructions. In some embodiments, processor electronics 210 may include at least a portion of transceiver electronics 215. In some embodiments, apparatus 205 is used to implement at least some of the disclosed technologies, modules, or functions.

[0037] Examples of technical problems solved by the embodiments

[0038] MBS functionality provides significant added value to NR NTN (non-terrestrial network) systems, leveraging the larger coverage area of ​​NTN compared to TN. Terrestrial MBS functionality also applies to NR NTN in the 5G specification; however, in some cases, the expected service area may be smaller than the coverage area of ​​the Uu cell, thus requiring enhancements to inform the broadcast service's service area.

[0039] In a TN (Terrestrial Network) MBS system, an MBS service area is the region that provides MBS services, which consists of one or more cells or one or more tracking areas. For location-dependent MBS services, MBS content is intended to be provided only to the corresponding MBS service area. A CN (e.g., SMF) can proactively remove a UE from a location-dependent MBS session (e.g., by rejecting the UE's join request) because its location is outside the MBS service area.

[0040] Because NTN cells have a large coverage area, the typical NTN cell coverage area or NTN tracking area can be several times larger than the typical MBS area, making it difficult to provide MBS services in NTN that are equivalent to the current MBS mechanism in TN. Figure 3 A typical example is given.

[0041] like Figure 3 The depicted MBS service 1 is intended for MBS service on TN cells 2-4 in country A, while MBS service 2 is intended for MBS service on TN cells 8-9 in country B. Furthermore, GEO cells cover TN cells 2-9. In this scenario, based on the current MBS mechanism, GEO cells cannot be used to provide MBS service 1 or 2 because, in the current MBS, the smallest unit of the MBS service area is a single cell. This means that MBS service 1, intended for country A, might be received by a user in country B, and vice versa. To address this issue, enhancements are needed to allow more precise MBS service area information to be provided to the UE and / or NG-RAN and / or CN for MBS service management, particularly for location-related MBS services.

[0042] One approach is to provide the UE with MBS service area information (e.g., geographical coverage information) to help the UE decide whether to receive the corresponding MBS service.

[0043] Another approach is that additional MBS service area information (e.g., geographic coverage information) can help NW perform more precise MBS service management. For example, NW can decide whether to provide MBS service to UE based on UE location and MBS service area information. This includes UE selecting, rejecting / accepting UE's request to join an MBS session, or selecting an appropriate beam (e.g., satellite beam) for broadcasting.

[0044] To address the above problem, at least one of the following enhancements can be considered (where Alt represents an alternative):

[0045] Alt1: Enables the UE to obtain MBS auxiliary information (e.g., information related to the MBS service area), and the UE decides whether / how to select and receive MBS data based on the MBS auxiliary information and / or its location / or registered NW.

[0046] Alt2: Enables the NW to obtain additional MBS service area information (different from the currently defined cell identifier list or TAI list). The NW uses this information, combined with the UE's location, to assist in MBS management (e.g., updating MBS configuration, accepting / rejecting UE requests to establish MBS PDU sessions, modifying / removing MBS PDU sessions). In some examples, if used with Alt1, the NW can convert the received additional MBS service area information into Alt1's MBS auxiliary information (if needed) and provide it to the UE.

[0047] Alt3: Introduces signaling enhancements to allow MBS service to be provided at the beam level. The beam type can be at least one of Synchronization Signal Block (SSB) and Channel State Information Reference Signal (CSI-RS). a. In this alternative, the NW can map each MBS service to one or more beams based on the received geographic coverage of each MBS service, where the coverage of these beams is equal to or less than the geographic coverage of each MBS service. The options for the NW to obtain the geographic coverage of each MBS service are discussed in the detailed section of Alternative 2. b. In this alternative, the NW needs to provide the UE with additional MBS beaming information, including at least a mapping between MBS services and beams, so that the UE can know which beam can be used to receive the MBS service it is interested in. This additional MBS beaming information includes at least one of the following: i. MBS service information, such as the MBS service identifier. ii. The number of beams used for MBS services. iii. Beam type, which indicates the type of beam used for MBS service reception. The beam type can be at least one of Synchronization Block (SSB) or Channel State Information Reference Signal (CSI-RS). iv. Beam index, which indicates the beam used for MBS service reception. v. First beam index, which indicates the first beam used for mapping when beam periodicity is configured. vi. Beam mapping period, which indicates the period during which a beam is used for MBS service. In one example, it can be an integer n, which, when configured, maps MBS service to the first beam indicated by the first beam index and one beam every n beams. vii. The mapping between beams and MBS services, which includes at least one of the following: 1. One or more beams are mapped to the MBS service. 2. A beam is mapped to one or more MBS services.

[0048] NW may include at least one of NG-RAN / CN / functional entities, such as Network Open Function (NEF), AMF, UPF, Session Management Function (SMF), MBS-AMF, MBS-UPF, MBS-SMF, Operations Management and Maintenance (OAM), etc. NG-RAN nodes may include gNB, ng-eNB, eNB, or other base station types (e.g., 6G base stations).

[0049] The aforementioned alternatives can be used independently or in combination. For example, alt1 and alt2 can be used together. The NW obtains MBS service area information for MBS management from the MBS service provider / NEF, and the NW can also convert the received service area information into MBS auxiliary information and pass this MBS auxiliary information to the UE. The UE can decide whether / how to select MBS service and receive MBS service traffic based on at least one of the received MBS auxiliary information, its location, or the NW it uses (e.g., the registered public terrestrial mobile network (PLMN)). In another example, a combination of alt2 and alt3 can be considered. For example, the NW receives MBS service area information from the MBS service provider. Based on this information, the NW can map the MBS service to one or more beams covering the corresponding MBS service area and transmit MBS data through the selected beams, etc.

[0050] In this patent document, the term MBS service is equivalent to the term MBS session. In some examples, each MBS service / session can be identified by an MBS service identifier. In this patent document, the MBS service identifier can be at least an MBS session identifier (e.g., a Temporary Mobile Group Identifier (TMGI)). In some examples, the MBS service identifier identifying an MBS service / session can be both a TMGI and an MBS group RNTI (e.g., a g-RNTI). The MBS group RNTI is used to schedule a group of UEs.

[0051] Other examples of embodiments of ALT1

[0052] Question 0: General Process

[0053] Figure 4 The general steps of alt1 are described. The UE receives MBS assistance information from the network device and decides whether to accept or release MBS service based on the received MBS assistance information.

[0054] This step includes the following.

[0055] Step 1: The UE receives MBS auxiliary information from the NW for MBS service selection.

[0056] In various embodiments, the MBS assistance information may include at least information related to the MBS service area (possible terms may be, but are not limited to, expected / target / permitted MBS service area). To achieve this, the UE decision to select an appropriate MBS service to receive or join may be based on at least one of the MBS assistance information, its interests, its location, or regulations. The MBS assistance information may be associated with one or more MBS services and / or MBS service frequencies.

[0057] Step 2: The UE determines, based on at least one of the received auxiliary information and / or its location and / or the public terrestrial mobile network (PLMN) it uses (e.g., the registered PLMN RPLMN / equivalent PLMN EPLMN), whether the MBS service is available, appropriate, permitted, or qualified for the UE, or whether the MBS service is the target MBS service or the intended MBS service for the UE.

[0058] In the following description, in various embodiments, the phrase “permitted” may be equivalent to: available, appropriate, qualified, or intended or anticipated.

[0059] Step 3: Based on the results of Step 2, different scenarios may exist: ■Scenario 1: Based on the provided MBS auxiliary information, there are no permitted MBS services for the UE: In this situation, the UE can perform at least one of the following actions: ◆Skip the acquisition (or non-acquisition) of MBS configuration, for example, do not monitor or acquire MCCH. ◆Skip monitoring (do not monitor) scheduling information for MBS data reception. ◆Does not receive MBS data. ◆Release MBS sessions that are no longer allowed (if they were previously stored). ◆Release any ongoing MBS sessions that are deemed no longer permitted (if any). ◆If a previously stored or currently active MBS service exists, suspend receiving the MBS service that is no longer allowed. In this case, if the MBS service becomes allowed for the UE again, the suspended MBS service can be resumed in the future. In some examples, the UE releases the MBS session by releasing the broadcast or multicast MRB. ■Scenario 2: At least one MBS service that is permitted for the UE is provided in the cell. For the permitted MBS service, the UE can perform at least one of the following actions: ◆ Obtain configuration information used for MBS reception, for example, initiate MCCH acquisition, or ◆Based on the UE's interests, the UE selects from the permitted MBS services that are about to begin / are currently in operation to receive MBS data, for example, by initiating a broadcast MRB establishment procedure. ◆ Resume receiving previously suspended MBS services / sessions (if any). ■ Considering the mobility of the UE and the satellite, an allowed MBS service may become unallowable. In this case, the UE can release the MBS service it is receiving, for example, by releasing the broadcast / multicast MRB or suspending the MBS service.

[0060] For step 1, the signaling options for transmitting MBS auxiliary information from the NW to the UE include at least one of the following: ● In the system information, at least one of the following system information may be considered: ■SIB1 ■SIB19 ■SIB25 is used to provide TN coverage information to assist UEs in neighbor cell measurements within an NTN cell. In this case, SIB25 can be extended to provide MBS auxiliary information. ■SIB20, which is used to provide the information needed to obtain the MCCH / MTCH configuration for MBS broadcasting. ■SIB21, which will provide a mapping between the current and / or adjacent carrier frequencies and the MBS Frequency Selection Area Identifier (FSAI), which is used only for MBS broadcast services. ■ A new dedicated SIB, namely SIBxx, is used to provide MBS auxiliary information as discussed in this application, where xx is an integer. ● In the MCCH message (which is carried in the Physical Downlink Shared Channel PDSCH), for example, at least one of the MBSBroadcastConfiguration message or MBSMulticastConfiguration message or new messages discussed in this application that are designated to provide MBS auxiliary information.

[0061] In one example, the UE first receives SIB20 to obtain scheduling information for receiving MBS broadcasts. Further, the UE considers its interests, the start time of the MBS service, and the UE's location to select an MBS broadcast service to receive MCCH messages, thereby deciding whether to receive MTCH. For example, if the UE's location is outside the expected MBS service area based on the MBS auxiliary information in the received MCCH message, the UE can decide not to receive (avoid receiving) the MTCH message corresponding to that MBS service. ● In RRC layer signaling to the UE, for example, via NAS (Non-Access Stratum) messages or via RRC messages. ● In the paging message. ●In short messages. ●In the MTCH message. ● In physical layer signaling, for example, through indications included in the DCI. ● In MAC layer signaling, for example, via MAC CE (control unit). ● In group signaling, for example, it could be used to pass MBS auxiliary information to existing or new RRC messages of UEs within the group. ● In the User Service Description (USD) signaling.

[0062] Combinations of at least one of the signaling methods described above are also possible. For example, SIB20 can be used to provide a mapping between MBS broadcast service coverage and current and / or neighboring cells and / or associated frequencies, and this list of neighboring cells can be provided in MCCH signaling.

[0063] Question 1: Contents of MBS auxiliary information

[0064] Depending on the specific content of the MBS auxiliary information, the conditions under which the UE decides whether to allow MBS and how the UE should behave may differ, including the specific signaling to be used, which will be discussed in detail in the various embodiments given.

[0065] The MBS auxiliary information in step 1 may include at least one of the following: information related to the MBS service area (possible terms may be expected / target / permitted MBS service area), satellite information, or information that associates the MBS service area with an MBS session (e.g., broadcast frequency, identifier of the MBS session), including at least one of the following: ● An indication that the MBS service is not restricted by the UE, or in other words, an indication that the MBS service is location-independent. ● An indication that tells the UE whether to use its location information as one of the factors in determining whether to allow MBS service. In one example, this is determined based on the value of the indication; for example, a value of 1 indicates that the UE should use its location information to determine whether to allow MBS service, while a value of zero indicates that the UE is not expected to use its location information to determine whether to allow MBS service, or vice versa. In another example, the presence of this indication can be considered a positive indication, meaning that the UE should use its location information to determine whether to allow MBS service, while the absence of this indication can be considered a negative indication, meaning that the UE is not expected to use its location information to determine whether to allow MBS service. In a third example, a disable indication can be used to prevent the UE from using its location information to determine whether to allow MBS service, meaning that if the disable indication is not present, the UE assumes that it should use its location information to determine whether to allow MBS service. Methods for determining whether to allow MBS service based on the UE's location can refer to the methods discussed in this application. ● An indication that the UE should use its NW information (e.g., RPLMN, selected PLMN, EPLMN, selected independent non-public network SNPN, or others) as one of the factors in determining whether to allow MBS service. In one example, this is determined based on the value of the indication; for example, a value of 1 indicates that the UE should use its NW information to determine whether to allow MBS service, while a value of zero indicates that the UE is not expected to use its NW information to determine whether to allow MBS service, and vice versa. In another example, the presence of this indication can be considered a positive indication, meaning the UE should use its NW information to determine whether to allow MBS service, while the absence of this indication can be considered a negative indication, meaning the UE is not expected to use its NW information to determine whether to allow MBS service. In a third example, a disable indication can be used to prevent the UE from using its NW information to determine whether to allow MBS service, meaning that if the disable indication is absent, the UE assumes it should use its NW information to determine whether to allow MBS service. Methods for determining whether to allow MBS service based on the NW information used by the UE can refer to the methods discussed in this application. ● Country information, indicating one or more countries where MBS service is permitted. MBS type can be at least one of MBS broadcast or MBS multicast. ● Tracking area information, which indicates one or more tracking areas expected to provide MBS services. The MBS type can be at least one of MBS broadcast or MBS multicast. In some examples, each tracking area can be identified by a tracking area code or a tracking area identifier. ● Geographic coverage information, which indicates one or more geographic coverage areas where MBS services are available / allowed. ●TN cell information, which can include at least one of a TN cell identifier or a mapping between a TN cell identifier and MBS service. The TN cell identifier is used similarly to a geographic coverage-dependent approach; the difference is that the UE derives the geographic area of ​​the MBS service from the TN cell coverage area associated with the cell identified by the TN cell identifier. The rest is similar to what was discussed in the examples using geographic area information. In this option, the geographic area of ​​each MBS is equal to the total coverage area of ​​each coverage area of ​​each TN cell associated with the MBS service. In some examples, the provided TN cell is only used to derive the geographic coverage area of ​​the MBS service and does not necessarily indicate that the MBS service is available in that TN cell. ●MBS Region Identifier. Each MBS region identifier identifies the geographical coverage area of ​​the MBS service, which can be overlapping or non-overlapping. In some examples, it can be the MBS region session ID. Or in some examples, it can be a newly defined identifier. ● Mapping between MBS area identifier / MBS service area / MBS geographic coverage and MBS service. Based on the associated MBS area identifier, the UE can derive the geographic coverage of the MBS service. For example, it can be the total coverage of each coverage area identified by the MBS area identifier of the MBS service. The mapping between the MBS area identifier and the MBS service can include at least one of the following options: ■ An MBS geographic coverage area is associated with one or more MBS sessions. This option can also include at least one of the following implementation options: ◆ An MBS region identifier can be used to identify an MBS geographic coverage area and is included in each MBS session configuration to link that MBS geographic coverage area to an MBS service. ◆ An MBS region identifier can be used to identify an MBS geographic coverage area, and an MBS service identifier can be used to identify an MBS session. Then, an MBS region identifier can be associated with a list of MBS service identifiers to associate an MBS geographic coverage area with one or more MBS services. ■ One or more MBS geographic coverage areas are associated with one MBS session. This option can also include at least one of the following implementation options: ◆One or more MBS region identifiers can be included in an MBS session configuration, and each MBS region identifier can identify an MBS geographic coverage area. Based on this, an MBS service can be linked to a set of one or more MBS geographic coverage areas. ◆ An MBS region identifier can be used to identify an MBS geographic coverage area, and an MBS service identifier can be used to identify an MBS session. Then, a list of MBS geographic coverage area identifiers can be associated with an MBS service identifier to associate one or more MBS geographic coverage areas with an MBS service. ● Satellite identifiers, where each satellite identifier identifies a satellite and / or a set of information for a satellite. This set of information includes at least one of the following: satellite ephemeris, satellite epoch time, common TA parameters, and polarization parameters. ● Satellite ephemeris and associated epoch time ● Common TA parameters and associated epoch times ●NTN types, which include geostationary orbit (GEO), low Earth orbit (LEO), geosynchronous orbit (GSO), non-GSO (NGSO), medium Earth orbit (MEO), geostationary orbit (MEO), geostationary orbit (MEO), geostationary orbit (MEO), and quasi-geostationary orbit (MEO). ●Time information associated with MBS auxiliary information, which includes at least one of the following: ■ The start time, which includes when the MBS auxiliary information becomes effective, can be implemented based on at least one of the following options: ◆In one example, the start time can be a past, present, or future time. In some examples, when epochTime is provided, the start time can be the time indicated by epochTime. ◆Time offset information from the start time, which can be at least positive or negative. In one example, the MBS auxiliary information takes effect when the start time is minus the time offset. In another example, the MBS auxiliary information takes effect when the start time is plus the time offset. In one example, the start time can be epochTime, which can be at least positive or negative. In this example, the MBS auxiliary information takes effect when the epochTime is plus the time offset. In another example, the MBS auxiliary information takes effect when the epochTime is minus the time offset. ■ Duration, which indicates how long the MBS auxiliary information is considered valid. The starting time for calculating the duration can be the starting time discussed above. ■ An indication that the UE can provide the NW with the MBS service areas of interest for which the UE wants to receive MBS services. In one example, this is determined based on the value of the indication; for example, a value of 1 indicates that the UE can provide the NW with the MBS service areas of interest for which the UE wants to receive MBS services, while a value of zero indicates that the UE cannot provide the NW with the MBS service areas of interest for which the UE wants to receive MBS services, and vice versa. In another example, the presence of this indication can be considered a positive indication, meaning that the UE can provide the NW with the MBS service areas of interest for which the UE wants to receive MBS services, while the absence of this indication can be considered a negative indication, meaning that the UE cannot provide the NW with the MBS service areas of interest for which the UE wants to receive MBS services. In a third example, a disable indication can be used to prevent the UE from providing the NW with the MBS service areas of interest for which the UE wants to receive MBS services, meaning that if the disable indication does not exist, the UE assumes that it can provide the NW with the MBS service areas of interest for which the UE wants to receive MBS services. In some examples, the indications discussed herein may be included in system information. In some examples, the UE provides the NW with the MBS service areas of interest for which the UE wants to receive MBS services via an MBS interest indication procedure. ●The mapping between MBS auxiliary information and MBS sessions includes at least one of the following options: ■ One MBS auxiliary information is associated with one or more MBS sessions. This option can also include at least one of the following implementation options: ◆ An MBS auxiliary information identifier can be used to identify an MBS auxiliary information set (including one or more MBS auxiliary information) and is included in each MBS session configuration to link the MBS auxiliary information to an MBS service. ◆ An MBS auxiliary information identifier can be used to identify an MBS auxiliary information set (including one or more MBS auxiliary information items), and an MBS service identifier can be used to identify an MBS session. Then, an MBS auxiliary information identifier can be associated with a list of MBS service identifiers to realize the association between MBS auxiliary information and one or more MBS services. ◆ An MBS ancillary information set (including one or more MBS ancillary information sets) can be included in each MBS session configuration to link the MBS ancillary information set to an MBS service. ◆ An MBS ancillary information set (including one or more MBS ancillary information items) can include one or more MBS service identifiers (e.g., TMGI) to link the MBS ancillary information to one or more MBS services. ■ One or more MBS auxiliary information items are associated with an MBS session. These options can also include at least one of the following implementation options: ◆One or more MBS auxiliary information identifiers can be included in an MBS session configuration, and each MBS auxiliary information identifier can identify an MBS auxiliary information set (including one or more MBS auxiliary information sets). Based on this, an MBS service can be linked to one or more MBS auxiliary information sets. ◆ An MBS auxiliary information identifier can be used to identify an MBS auxiliary information set (including one or more MBS auxiliary information items), and an MBS service identifier can be used to identify an MBS session. Then, a list of MBS auxiliary information identifiers can be associated with an MBS service identifier to realize the association between one or more MBS auxiliary information items and an MBS service. ◆ Each MBS session configuration includes a list of MBS auxiliary information sets (each MBS auxiliary information set includes one or more MBS auxiliary information sets) to link one or more MBS auxiliary information sets to an MBS service. ◆ For an MBS service identifier (e.g., TMGI), a list of MBS ancillary information sets (each MBS ancillary information set includes one or more MBS ancillary information items) is included to link one or more MBS ancillary information items to an MBS service. In this application, there are several references to the ability of MBS services to be identified by an MBS service identifier. In some examples, an MBS service can be identified by a single MBS service identifier (e.g., TMGI). In other examples, an MBS service can be identified by a combination of multiple MBS service identifiers (e.g., by TMGI and g-RNTI (Group Radio Network Temporary Identifier)). g-RNTI is a group RNTI assigned to an MBS service identified by TMGI. In the above description of the mapping between MBS auxiliary information and MBS services, MBS auxiliary information may be at least one of the MBS auxiliary information discussed in this application, such as country information, tracking area information, geographic coverage information, TN cell information, satellite information, ephemeris information, NTN type, public TA, time information, etc.

[0066] The following will discuss in detail some examples of the MBS auxiliary information content mentioned above:

[0067] Example 0: Instructions for canceling / enabling restrictions

[0068] An indication that the MBS service has no restrictions on the UE, or in other words, an indication that the MBS service is location-independent. Alternatively, an indication that MBS auxiliary information is used by the UE for MBS service management (e.g., selecting / releasing / suspending the MBS service).

[0069] In one implementation, this indication is a one-bit indicator with a value of 1 or 0, where a value of 1 indicates that the MBS service allows all UEs capable of receiving MBS data without restriction; otherwise, the value is set to zero, and vice versa. In another implementation, the presence of this indication can be used for similar purposes, such as indicating that the MBS service allows all UEs capable of receiving MBS data without restriction; otherwise, the indication does not exist. In one implementation, this indication is a one-bit indicator with a value of 1 or 0, where a value of 1 indicates that the MBS auxiliary information is used by the UE for MBS service management (e.g., selecting / releasing / suspending the MBS service); otherwise, it is set to zero to indicate that the MBS auxiliary information is not used by the UE, and vice versa. In another implementation, the presence of this indication can be used for similar purposes, such as indicating that the MBS auxiliary information is used by the UE; otherwise, the indication does not exist to indicate that the MBS auxiliary information is not used by the UE. In some examples, this indication can be common to all provided MBS auxiliary information, or in another example, the indication can be introduced and set separately for each type of MBS auxiliary information. Alternatively, in another example, the UE learns, based on the existence of other MBS auxiliary information (e.g., country information, tracking area information), that the MBS service associated with the provided MBS auxiliary information is applicable to the area / frequency / satellite indicated by the auxiliary information, and the UE needs to consider the auxiliary information when selecting an MBS service.

[0070] Example 1: MBS auxiliary information including country information

[0071] Sub-question 1: Content details

[0072] Country information, indicating the countries where MBS service is available. The MBS type can be at least one of MBS broadcast or MBS multicast. This country information includes at least one of the following:

[0073] A country identifier (e.g., country code) is used to identify the country in which MBS services are permitted / available.

[0074] Mapping between national information and MBS services

[0075] MBS service is permitted / available in one or more geographic regions within a country.

[0076] The largest number of countries associated with MBS services.

[0077] For the country identifier, in one implementation, the country information passed to the UE can be one or more country codes, where each country code is associated with a country. The country code can be fixed or configurable. At least one of the following options can be considered in the implementation:

[0078] - Mobile Country Code (MCC), as defined in 3GPP standard TS 23.003, uniquely identifies a country. It consists of three integer digits.

[0079] - A two- or three-digit Mobile Network Code (MNC) used for 3GPP network applications. The MNC identifies the home PLMN of the mobile contract within its country of registration, or it is identified together with the MCC and the NID (Network Identifier) ​​of the SNPN (Standard Non-Public Network). The length of the MNC (two or three digits) depends on the value of the MCC. Mixing two- and three-digit MNC codes within a single MCC area is not recommended and is beyond the scope of this specification.

[0080] - Country name abbreviations, where each abbreviation uniquely identifies a country.

[0081] - Country codes as defined by ISO 3166.

[0082] In some examples, combinations of some of the above can be considered; for example, the combination of MCC and MNC can be used to indicate areas where MBS services are available / allowed.

[0083] To map country information to MBS services, each country information can be associated with one or more MBS services. To achieve this, at least one of the following signaling options can be considered:

[0084] Each MBS service can be associated with one or more countries (e.g., a list of country codes). For example, an MBS service can be identified by an identifier (e.g., TMGI or TMGI+g-RNTI), and each MBS service identified by the identifier can be linked to one or more country codes, where each country code identifies a country.

[0085] In one implementation, a list of one or more allowed countries for MBS service can be provided for the cell, and a bitmap is introduced to indicate the allowed countries for the MBS service, wherein each bit of the bitmap indicates whether a country indicated in the list of allowed countries is allowed / available for the MBS service. The bit is set to 1 to indicate that the MBS service is allowed / available in that country, or set to zero to indicate that the MBS service is not allowed / unavailable in that country, and vice versa.

[0086] Each country can be associated with one or more MBS services. For example, for each country provided, it can be associated with one or more identifiers that identify an MBS session. For example, each country can be associated with one or more TMGIs. The TMGI is used to identify the MBS session.

[0087] MBS services are permitted to be provided for one or more geographic regions within a country, allowing for a finer granularity in indicating the MBS service area than the country itself. In some examples, to allow for further indication of geographic regions within a country, country information can be used in conjunction with additional geographic coverage information, which includes at least one of the following:

[0088] National information is used in conjunction with one or more tracking information as discussed in Example 2.

[0089] The country information is used in conjunction with one or more geographic coverage information as discussed in Example 3 or Example 4.

[0090] Country information is used in conjunction with one or more Mobile Network Codes (MNCs). The MNC is used to identify a list of network operators within the country.

[0091] When used in conjunction with the additional information discussed above, the following rules may be considered to allow the UE to determine the availability of MBS services based on country information:

[0092] In one example, the UE considers MBS to be allowed to receive / join when all conditions are met. For instance, when the MNC is provided along with country information, the UE considers the MBS service available / allowed when its geographic location is within the country associated with the MBS service and it is served by the operator identified by the MNC associated with the MBS, or by an equivalent operator identified by the MNC associated with the MBS service. Here, an equivalent operator means that the operator identified by the MNC associated with the MBS service is considered equivalent to the operator currently serving the UE.

[0093] In another example, the UE considers MBS to be allowed to receive / join when any of the following conditions are met. For example, when the MNC is provided along with country information, the UE considers the MBS service available / allowed when its geographic location is within the country associated with the MBS service, or when the UE is served by the operator identified by the MNC associated with the MBS service, or by an equivalent operator identified by the MNC associated with the MBS service. Here, an equivalent operator means that the operator identified by the MNC associated with the MBS service is considered equivalent to the operator currently serving the UE.

[0094] The maximum number of countries associated with MBS service can be represented as an integer. In one implementation, the maximum number of countries associated with MBS service can be defined for a cell. In another implementation, the maximum number of countries associated with MBS service can be defined for a cell. In yet another implementation, the maximum number of countries associated with MBS service can be defined for a UE. In yet another implementation, the maximum number of countries associated with MBS service can be defined for a UE.

[0095] Sub-question 2: UE determines whether MBS service is allowed.

[0096] When providing country information for MBS services, the UE can decide whether MBS services are permitted based on at least one of the following options: ● Option 1: Based on UE's geographic location. In this option, MBS service is considered permitted for the UE when the UE's location is within a country included in the country information associated with MBS (e.g., a country list). When MBS is considered permitted / available for the UE, the UE can receive MBS broadcast data, or the UE can request to receive multicast data. ● Option 2: Based on the NW registered or selected by the UE and the UE's location. Different implementations can be considered in the following example: ◆ In one example, the UE is registered in a PLMN of country A identified by the MCC. In this option, the MBS service is considered permitted for the UE when the country identified by the MCC of the UE's RPLMN is included in the country information associated with MBS (e.g., a country list) and the UE's location is within a country included in the country information associated with MBS. The country information derived based on the MCC can be the same as or different from the country information derived through the UE's location. A typical use case could be in the EU, for example, a Spanish user roaming to France while still being served by a Spanish operator. When the MBS service provider offers MBS service at least in Spain and France, the Spanish user terminal is allowed to receive the MBS service while roaming in France. In this example, the country information associated with the MBS service could include Spain and France, the UE's RPLMN's MCC is Spain, and its location is in France, which satisfies the specified rule, therefore the UE considers the MBS service available / allowed to join. ◆In another example, an EPLMN can be considered. The MBS service is considered permitted for the UE when at least one of the countries identified by the MCC of the EPLMN stored by the UE is part of the country associated with the MBS, and the UE's location is within a country that is part of the country associated with the MBS. The country information derived based on the MCC can be the same as or different from the country information derived from the UE's location. ◆In yet another example, MBS service is considered permitted for the UE when any of the following conditions are met: ■Condition 1: The UE's location is within the country associated with the MBS. ■Condition 2: The country information derived from the MCC of the PLMN registered or selected by the UE is one of the countries associated with the MBS. ◆In the fourth example, MBS service is considered permitted for the UE when any of the following conditions are met: ■Condition 1: The UE's location is within the country associated with the MBS. ■Condition 2: The country information derived from the MCC of at least one of the UE's EPLMNs is one of the countries associated with the MBS. ●Option 3: Based on the NW type registered or selected by the UE. Different implementation methods can be considered as shown in the following examples: ◆In one example, the UE registers in a PLMN for country A, which is identified by the MCC included in the RPLMN. In this option, the MBS service is considered permitted for the UE when the country identified by the MCC of the UE's RPLMN is included in the country information (e.g., a country list) associated with the MBS. ◆In another example, EPLMN can be considered. The MBS service is considered permitted for the UE when at least one of the countries identified by the MCC of the EPLMN stored by the UE is part of the country associated with the MBS.

[0097] In another example, the selected PLMN can be considered. The MBS service is considered permitted for the UE when the country identified by the MCC of the UE's selected PLMN is included in the country information associated with the MBS (e.g., a country list). In some examples, when the UE operates in a non-public network (e.g., an NPN), the registered PLMN can be replaced with either the registered SNPN identifier or the selected SNPN identifier, and the same rules discussed above apply.

[0098] Sub-question 3: Signaling options and example ASN.1

[0099] As discussed in Question 0 of the General Procedures section, country information can be passed to the UE through at least one of the following methods: system information, dedicated RRC messages, NAS messages, MCCH messages, MTCH messages, in MAC layer signaling, in physical layer signaling, in paging messages, or in group signaling. Some examples of how this information can be passed to the UE are given below, assuming the country code used to identify the country is the MCC code and the identifier used to identify the MBS session is TMGI. However, note that other country codes or identifiers used to identify the MBS service are also possible, such as country abbreviations defined in ISO standards, or the MBS service identifier could be TMGI+g-RNTI.

[0100] An example of ASN.1 used to indicate country information. An example using a list is as follows.

[0101] In one example, an MBS country list (e.g., mbs-AllowedCountryList) can be defined, which contains multiple entries, each including a country identifier that identifies the country.

[0102] Example ASN.1 is shown below:

[0103] In this example, the MBS country list is defined as mbs-AllowedCountryList, and maxAllowedCountry is the maximum number of defined entries, which is an integer. For the example above, country information can be at least one of MCC, country abbreviation, or other defined identifiers. When using MCC, MCC consists of three integers, each selected from zero to 9. An example is given below:

[0104] Example when MBS service is associated with one or more country codes

[0105] Example a when the country code is provided within the MCCH message MBSBroadcastConfiguration message A. Example when MBS service is associated with one or more country codes

[0106] Example a when the country code is provided within the MCCH message MBSBroadcastConfiguration message --

[0107] In this example, the MBSBroadcastConfiguration message carried in the MCCH logical channel provides a list of allowed countries identified by the MCC code list for each MBS session. In this signaling structure, the traditional MBS session list (mbs-SessionInfoList-r17) included in the UE contains MBS identifiers, and entries in mbs-SessionInfoList-r19 are mapped sequentially to entries in mbs-SessionInfoList-r17. Therefore, the UE can map the list of allowed countries to each MBS service and derive the mapping between each MBS session and the list of allowed countries. Thus, the UE can determine whether an MBS service is allowed / available based on this MBS auxiliary information and / or the UE's location / NW used by the UE (as discussed in the preceding sections).

[0108] Here, maxAllowedCountryMBS is the maximum number of countries associated with the MBS service provided in the cell. It is an integer value.

[0109] Example b when the country code is provided in the system information block

[0110] In the following example, SIBxx containing MBS auxiliary information is introduced to assist in MBS service selection. In this example, the MBS auxiliary information is a list of countries where MBS services are permitted / available. In other examples, other SIBs may be considered, such as SIB1, SIB19, SIB20, SIB21, SIB25, etc.

[0111] In this example, the list of allowed countries for MBS services can be optionally provided. In another example, it can be mandatory. In this signaling design, the list of countries associated with one or more MBS services contains multiple entries, and for each entry, the MBS service identified by TMGI is associated with the list of countries identified by MCC. maxAllowedCountryMBS is the maximum number of countries associated with MBS services provided in this cell.

[0112] Note that although this example is given for a new SIB (System Information Block), the list of allowed countries for one or more MBS services given in the example above can be carried in other SIBs (e.g., SIB1, SIB19, SIB20, SIB21, SIB25, etc.).

[0113] Examples of country codes associated with one or more MBS services

[0114] Example a when the country code is provided in the system information block

[0115] In the following example, SIBxx is a new SIB used to provide MBS ancillary information. In other examples, other SIBs may be considered, such as SIB1, SIB19, SIB20, SIB21, SIB25, etc. SIBxx contains MBS ancillary information to assist in MBS service selection. In this example, the MBS ancillary information is a list of countries where MBS services are permitted / available.

[0116] In this example, a list of allowed countries for the MBS service may be provided optionally. In another example, it may be mandatory. In this signaling design, the list of countries associated with one or more MBS services contains multiple entries, for each entry, a country identified by the MCC is associated with a list of MBS services identified by the TMGI. Each country is identified by an MCC code, and each MBS session is identified by a TMGI.

[0117] `maxAllowedCountryMBS` is the maximum number of countries associated with MBS services provided in the cell. `maxNrofMBS-Session` indicates the maximum number of MBS sessions supported in the cell. It should be noted that although the examples are given for a new SIB, the list of allowed countries for one or more MBS services given in the examples above can be carried in other SIBs (e.g., SIB1, SIB19, SIB20, SIB21, SIB25, etc.).

[0118] Example based on the list of allowed countries for MBS service and a bitmap of the allowed countries.

[0119] In some examples, combinations of the signaling options discussed in the general procedures section can be considered, which can allow for further UE power saving and flexible management relative to the actually deployed MBS services. For example, NTN can cover multiple country information and provide different MBS services at different frequencies for different countries.

[0120] In some examples, a list of permitted countries for MBS services for each cell (serving cell or neighboring cell) can be provided via system information (e.g., SIB20 or a newer SIB). Furthermore, in the MCCH message (whether for MBS broadcast or MBS multicast), a bitmap of country information can be provided to each MBS service, indicating the country associated with the MBS service. In this example, each bit of the bitmap corresponds sequentially to the list of countries in the system information, whether the bit is set to 1 to indicate that the country is associated with the MBS service, or set to zero to indicate that the country is not associated with the MBS service, or vice versa. In the case where a country is associated with the MBS service, this indicates that the MBS service is permitted / available in that country. The advantage of this approach is that when the UE decodes the system information (e.g., SIB20) carrying MBS auxiliary information and finds that it is not permitted to receive MBS services in the current cell based on this list, the UE will skip further decoding of the scheduling information for the received corresponding MBS service, which can save some UE power consumption.

[0121] For simplicity, in the following examples, the interpretation of allowed countries information for MBS service of the serving cell is based on the existence of a list of allowed countries (e.g., mbs-AllowedCountryList) and a bitmap of allowed countries (e.g., mtch-AllowedCountry). The terminology used is merely illustrative; other terms are possible. Furthermore, the bitmap of allowed countries associated with the MBS session is presented as mtch-AllowedCountry, but the terminology used is also illustrative; other terms are possible. Different options exist for signaling this information to the UE, which are summarized in the table below.

[0122] The following is an example of ASN.1 for Example Case 1, assuming that the system information used to provide a list of countries where MBS services are available / permitted in the cell is SIB20, but it can also be a new SIB or other SIB defined in the standard (e.g., SIB1, SIB19, SIB21, etc.). –SIB20 SIB20 contains the information needed to obtain the MCCH / MTCH configuration for MBS broadcasts. SIB20 Information Elements

[0123] `maxAllowedCountryMBS` is the maximum number of countries associated with the MBS service provided in the cell. It is an integer.

[0124] –MBSBroadcastConfiguration

[0125] The MBSBroadcastConfiguration message contains control information applicable to MBS broadcast services transmitted via broadcast MRB. Signaling radio bearer: N / A RLC-SAP: UM Logical Channel: MCCH Direction: Network to UE MBSBroadcastConfiguration message -- ASN1START

[0126] Example 2: MBS auxiliary information includes tracking area information

[0127] Sub-question 1: Content details

[0128] Tracking area information indicates one or more tracking areas where MBS service is available / allowed. The MBS type can be at least one of MBS broadcast or MBS multicast. Specifically for NTN, TAC can be used to identify fixed geographic areas. The mapping between the TAC and this fixed geographic area is handled by NW. In different implementations, this mapping can be determined by CN or NG-RAN. Currently, the UE is unaware of this mapping relationship. Therefore, tracking area information can be used to assist the UE in selecting MBS service. To achieve this, at least one of the following options can be considered: ●Opt1: Provides the UE with one or more permitted tracking areas associated with the MBS service, and / or a mapping between geographic areas and tracking areas. Based on the received information, the UE can deduce that the geographic coverage area where the MBS service is available is available. In one example, the UE considers the MBS to be available in the geographic area identified by the TA associated with the MBS. For example, the UE knows from the mapping between geographic areas and tracking areas that TA1 corresponds to geographic area 1, TA2 corresponds to geographic area 2, and TA3 corresponds to geographic area 3, and that the MBS is associated with TA1 and TA3, then the UE can determine that the MBS service is available in geographic areas 1 and 3.

[0129] In addition, the UE determines whether the MBS is available or allowed for the UE based on a comparison between the coverage area available for the MBS service and the UE's location / UE's NW. ●Opt2: One or more permitted tracking areas associated with MBS service for a cell are provided together with a list of permitted tracking areas for the UE. The UE determines whether the MBS is available / permitted for the UE based on a comparison of the two received tracking area information.

[0130] For the above options (opt1 / 2), at least one or more of the following options can be used to identify the tracking area: ■Option 1: The tracking area can be identified by one or more tracking area codes (TACs). ■Option 2: The tracking area can be identified by one or more Tracking Area Identifiers (TAIs). Each TAI consists of a PLMN identifier and a TAC.

[0131] For both options, in order for the UE to understand the permitted tracking area associated with the MBS service, a mapping between the MBS service and the tracking area needs to be defined and signaled to the UE. This mapping can be passed to the UE through at least one of the following options: ■ Option 1: One or more TACs can be configured for the MBS service. The MBS service can be identified by an identifier (e.g., TMGI). ■ Option 2: One or more TAIs can be configured for the MBS service. The MBS service can be identified by an identifier (e.g., TMGI). ■ Option 3: Each tracing region identified by a TAC can be configured with one or more MBS services / sessions. For example, if the MBS service / session is identified by a TMGI, each tracing region can be configured with one or more TMGIs. ■ Option 4: Each tracking region identified by a TAI can be configured with one or more MBS services / sessions. For example, if the MBS service / session is identified by a TMGI, each tracking region can be configured with one or more TMGIs.

[0132] For option 1, the mapping relationship between the geographic area and the tracking area needs to be notified to the UE via signaling. This mapping relationship can be transmitted through at least one of the following options: ■Option 1: One or more TACs can be configured for this geographic area. ■Option 2: One or more TAIs can be configured for this geographic area. ■Option 3: Each tracking region identified by a TAC can be configured with one or more geographic regions. ■Option 4: Each tracking region identified by a TAI can be configured with one or more geographic regions.

[0133] For the options discussed above, each geographic region can be presented through at least one of the following options: ◆Option 1: A circular area defined by the coordinates of the center (origin) and the radius. ◆Option 2: An elliptical region defined by the coordinates of the origin, a major semi-axis of length r1, and a minor semi-axis of length r2, wherein the direction of the major semi-axis is an angle A (0 to r2) measured clockwise from north. An example of an uncertain ellipse is shown in... Figure 5 It was described in the text. ◆Option 3: Polygon shape, with a minimum allowed number of points of 3. A maximum number of points can be defined; for example, in some examples, the maximum allowed number of points is 15. These points should be connected in the order they are given (e.g., ...). Figure 6 (A to E in the diagram). A connecting line is defined as the line (geodesic line) that connects two points on the ellipsoid with the shortest distance. The last point is connected to the first point. The list of points is based on the following conditions: - A connecting line must not cross another connecting line; - Two consecutive points on the ellipsoid must not be in positions opposite each other by diameter. The area described lies to the right of the straight line, with the downward direction pointing towards the center of the Earth and the forward direction pointing from one point to the next. ◆Option 4: Regional identifiers used to identify geographic areas. In some examples, geographic areas can be represented by the geometric shapes discussed in the options above.

[0134] Sub-question 2: UE determines whether MBS service is allowed.

[0135] Based on Opt 1 (paragraph

[0129] )

[0136] For option 1, when providing tracking area information associated with MBS service, the UE implementation may determine whether MBS service is permitted based on at least one of the following options:

[0137] Option 1: Based on the UE's geographic location (e.g., location conditions)

[0138] In this option, the UE first determines the geographic coverage of each MBS service based on the TA associated with each MBS service and the mapping between the TA and geographic regions. Then, the UE compares its geographic location with the derived geographic coverage of the MBS service. If its location is within the geographic coverage of the MBS service, the UE considers the MBS service permitted / available for that UE; otherwise, the UE considers the MBS service not permitted / available.

[0139] Option 2: Based on the UE's RPLMN / selected PLMN or EPLMN (if available), e.g., NW conditions

[0140] In this option, if the TA (TAI or TAC) included in the UE's PLMN is included in the TA (TAI or TAC) associated with the MBS service, the UE considers the MBS service permitted / available for the UE; otherwise, the UE considers the MBS service not permitted / available. Here, the UE's PLMN can be at least one of RPLMN, the selected PLMN, or EPLMN. In some examples, when the UE uses other NW types (e.g., when the UE uses an NPN), the PLMN identifier discussed above can be replaced with the registered SNPN identifier or an equivalent SNPN, using the same rules discussed above.

[0141] Option 3: Based on the UE's PLMN and / or the UE's geographic location

[0142] In this option, the UE determines MBS service availability based on a comparison of the UE's PLMN and / or the UE's geographic location. In one implementation, the UE considers MBS service available / allowed when both the location condition and NW condition discussed in options 1 / 2 above are met; otherwise, the UE considers MBS service unavailable. The PLMN can be a registered PLMN, a selected PLMN, or an EPLMN. In some examples, when the UE uses other NW types (e.g., when the UE uses an NPN), the same rules as discussed above apply, and the PLMN identifier discussed above can be replaced with a registered SNPN identifier or an equivalent SNPN.

[0143] In another implementation, the UE considers the MBS service to be available / allowed when either the location condition or the NW condition discussed in options 1 / 2 above is met; otherwise, the UE considers the MBS service to be unavailable (i.e., when neither condition is met).

[0144] Based on Opt2 (paragraph

[0130] )

[0145] For option 2, a list of tracking areas associated with the MBS service of a cell can be provided in the system information. This list indicates one or more MBS services available in the cell, where each MBS service can be associated with one or more tracking areas using the options discussed above. Furthermore, a UE or (a group of UEs) can be assigned one or more tracking areas where it is permitted to receive MBS services (e.g., a list of permitted TAs for MBS). When the list of permitted TAs for MBS is received in dedicated signaling and / or group signaling, the UE will use both the information received in the system information and the dedicated / group signaling to determine whether the MBS is permitted / available for that UE. For example, if at least one of the TAs associated with the MBS is included in the list of permitted TAs for MBS received by the UE, the UE considers the MBS permitted / available; otherwise, the UE considers the MBS not permitted / available. That is, if the MBS service is not associated with any TA included in the UE's list of permitted TAs for MBS, the UE considers the MBS service not permitted for that UE.

[0146] When it is determined that MBS service is available, the UE may perform actions discussed in the General Procedure section, such as obtaining MBS service scheduling information, receiving MBS data, or requesting to receive MBS data. When it is determined that MBS service is not allowed, the UE may perform actions discussed in the General Procedure section, such as releasing the MBS session. Figure 7 An example is shown below. In signaling exchange diagram 700, the UE receives the tracking area associated with MBS in the cell in a system information message sent by the NW. The UE also receives a list of permitted tracking areas for MBS for that UE in a dedicated or group signaling message sent by the NW. Based on this information, the UE decides whether to accept or release MBS service.

[0147] Sub-question 3: Signaling options and example ASN.1

[0148] As discussed in Question 0 of the General Procedures section, tracking area information can be transmitted to the UE through at least one of the following methods: system information, dedicated RRC messages, NAS messages, MCCH messages, MTCH messages, in MAC layer signaling, in physical layer signaling, in paging messages, or in group signaling. Some examples of how this information can be transmitted to the UE are given below, assuming that the MBS identifier used to identify the MBS service is TMGI. However, note that other identifiers for identifying MBS services are also possible, such as those based on TMGI and g-RNTI.

[0149] Based on Opt 1

[0150] In this option, the TA of the MBS and the mapping between the TA and the geographic region are provided to the UE.

[0151] Example of a TA providing MBS information a. One or more TAs are included in the MBS session information.

[0152] In this example, the MBS session can include a list of identifiers that identify the TA, indicating that the TA of the MBS service identified by the MBS service identifier is available.

[0153] The identifier for the tracking area can be either TAC or TAI. b. Examples for TAI

[0154] In the example below, the allowed TA associated with the MBS service is provided in the MBSBroadcastConfiguration message. The same content can be included in other messages, such as the MBSMulticastConfiguration message, or messages used to transmit MBS auxiliary information from the NW to the UE. For example, it could be a NAS message when the NW is a CN; and an RRC message when the NW is an NG-RAN node. MBSBroadcastConfiguration message -- ASN

[0155] Here, maxTAMBS is the maximum number of tracking regions used for MBS services.

[0156] When a TAI is used, each TAI will include a TAC and a PLMN identifier. In some examples, to further reduce signaling overhead, one possible implementation is to make the presence of the PLMN identifier in the TAI list optional. In this implementation, if the PLMN identifier of an entry is the same as the PLMN included in a previous entry, then the PLMN identifier is not included in that entry to save signaling overhead, and so on. With this implementation, when all TAIs included in the list share the same PLMN, the network can include the PLMN only in the first entry. From the UE side, if the PLMN identifier is missing in an entry of the received TAI list, the UE assumes that the PLMN identifier has the same value as the PLMN identifier included in the nearest previous entry. This implementation can be used for all examples of Tracking Area Identifiers (TAIs) discussed in this application. ●Example for TAC

[0157] When the tracking area is identified by a TAC, the ASN.1 encoding for mbs-TAList can be as follows. In this example, the TA information associated with the MBS service is included in the MBSBroadcastConfiguration message. The same content can be included in other messages, such as the MBSMulticastConfiguration message, or messages used to transmit MBS auxiliary information from the NW to the UE. For example, when the NW is a CN, it could be a NAS message; when the NW is an NG-RAN node, it could be an RRC message. MBSBroadcastConfiguration message -- ASN1ST

[0158] Here, maxTAMBS is the maximum number of tracking regions used for MBS services. c. A TAC is associated with one or more MBS service identifiers, and each MBS session identifier identifies an MBS session.

[0159] In the following example, SIBxx is a new SIB used to provide MBS auxiliary information. In other examples, other SIBs may be considered, such as SIB1, SIB19, SIB20, SIB21, SIB25, etc. SIBxx contains MBS auxiliary information to assist in MBS service selection. In this example, the MBS auxiliary information is a list of tracking areas where MBS services are allowed / available.

[0160] In this example, an optional list of allowed tracking areas for MBS services is provided. In another example, it can be mandatory. In this signaling design, the list of tracking areas associated with one or more MBS services contains multiple entries, for each entry, the MBS service identified by the TMGI is associated with a list of TAs identified by the tracking area identifier. maxAllowedTAMBS is the maximum number of tracking areas associated with MBS services provided in the cell.

[0161] Note that although this example is given for a new SIB, the list of allowed countries for one or more MBS services given in the above example can be carried in other SIBs (e.g., SIB1, SIB19, SIB20, SIB21, SIB25, etc.). Similar to the previous example, in some examples, the PLMN identifier in the TAI can be optionally included, and when it is not present, the UE will treat the PLMN identifier of the TAI as the PLMN identifier included in the nearest preceding entry.

[0162] In some examples, the TAIdentity included in each entry of mbs-AllowedTAList can be the Tracking Region Code (TAC).

[0163] Provide an example of mapping between TAs and geographic regions.

[0164] In one implementation, for security reasons, the mapping between the TA and the geographic area is passed to the UE in a NAS message. In another implementation, this mapping may be provided to the UE in an RRC message or via system information.

[0165] Based on Opt 2

[0166] In this option, the UE is provided with a first list of tracking areas associated with the MBS used for the cell, where this information is public to all UEs in the cell. The list associated with the MBS used for the cell includes tracking area information and a mapping between the MBS and the tracking areas. This information may be passed to the UE in at least one message in system information or MCCH messages. The signaling example discussed in option 1 above can be considered.

[0167] In addition, the UE can receive a second list of tracking areas permitted for MBS from the NW, indicating the tracking areas where the UE is allowed to receive MBS. This second list may only include tracking area information. Based on this, the UE can determine whether MBS service is available / permitted for UE reception. This second TA list can be provided to the UE from the NW in at least one of the following messages: RRC messages, MAC layer signaling, paging messages, and group messages (e.g., group paging or multicast messages). For the signaling options discussed above, they can be provided to the UE in a dedicated method or a group-based method. When using a dedicated method, the UE can use a UE-specific RNTI (e.g., C-RNTI) to monitor scheduling information (e.g., Physical Downlink Control Channel PDCCH) for receiving RRC messages. When using group signaling, the UE can use a group RNTI to monitor scheduling information (e.g., PDCCH) for receiving dedicated messages. This group RNTI can be a G-RNTI for multicast or a newly defined group RNTI. In some examples, the NW considers the UE location information available on the NW side when allocating group RNTIs.

[0168] Below are some signaling examples:

[0169] Example of using RRC messages

[0170] At least an RRCReconfiguration message or a new RRC message for MBS auxiliary information can be used to provide the UE with a second tracking area list. When using an RRC message, an Information Element (IE) can be used to indicate a second list of tracking areas permitted for MBS, which indicates the tracking areas in which the UE is allowed to receive MBS.

[0171] The following is an example of IE using TAI and TAC:

[0172] Example information elements based on TAI:

[0173] Example information element based on TAC:

[0174] Example of using MAC layer signaling

[0175] In this example, a MAC CE can be defined to provide the UE with a list of tracking areas available to the UE for the MBS service. When this list is provided, the UE considers the MBS service available / allowed to be received only if at least one TA indicated by the received MAC CE for that UE is associated with the MBS. The MAC CE used to provide the UE with the list of tracking areas can be at least one of the following: - MAC subheader only; - MAC subheader and MAC CE;

[0176] The MAC subheader includes at least information to identify the MAC CE. The MAC CE and MAC subheader are octet aligned. The MAC CE can be fixed-size or variable-size. The MAC subheader and MAC CE include at least one of the following fields: -LCID or eLCID: The logical channel identifier field or extended logical channel identifier field identifies the type of the corresponding MAC CE.

[0177] The LCID / eLCID can have a reserved value from at least one of the following: ✧ Reserved LCID values ​​in the LCID used for MBS multicast MCCH and MBS broadcast on DL-SCH. ✧ Reserved LCID value in an octet eLCID used for DL-SCH. ✧ Reserved LCID values ​​in the two octets eLCID used for DL-SCH. ✧ Reserved LCID value in LCID used for DL-SCH.

[0178] Regardless of the LCID type used, the (e)LCID discussed in this document has a value derived from the reserved (e)LCID value, indicating that it is for the MAC CE of the permitted tracking area for the UE.

[0179] For MBS broadcasts, if the same LCID is assigned to logical channels corresponding to different G-RNTIs, then the logical channel is identified based on the G-RNTI and LCID. -L: The length field indicates the length of the variable-sized MAC CE in bytes. -F: The format field indicates the size of the length field. The F field is 1 bit in size. A value of 0 indicates an 8-bit length field. A value of 1 indicates a 16-bit length field. -LX: The LCID extension field indicates the use of the extended LCID space. The LX field is 1 bit in size. Setting the LX field to 1 indicates the use of Table 6.2.1-2c; otherwise, the R bits are present (i.e., set to 0). -R: Reserved bits, set to 0. - The Tracking Area (TA) field indicates whether the tracking area provided in the list of allowed TAs for MBS in the cell is used by the UE. Each bit indicates, sequentially (from first to last, or from last to first), whether each TA entry provided in the TA list (e.g., in system information) is used by the UE. Each bit is set to 1 when the TA is used by the UE, and set to zero otherwise, or vice versa. For example, a list of allowed TAs for MBS in the cell is provided, containing eight entries. Each entry includes a list of TA identifiers (e.g., TAI or TAC) associated with the tracking area and MBS service identifiers (e.g., TMGI). The first entry indicates TA1, the second indicates TA2, and so on. The UE receives a MAC CE with the RA field set to 10110000, meaning that TA1, TA3, and TA4 are for the UE, and the UE considers MBS associated with at least TA1, TA3, and TA4 to be available / allowed for the UE. Because MAC is octet aligned, if the number of entries in the list of allowed TAs for MBS in the cell is less than the number of entries in the TA field, the UE sets the remaining TA fields to zero. Figure 8 The TA field used here is for illustrative purposes only; other terms may also be used (e.g., tracking area indication, tracking area code, tracking area identifier / identifier).

[0180] Example of a MAC CE with only a subheader

[0181] In one example (refer to) Figure 8 (Top syntax structure), the LCID has a value from the reserved LCID value from the LCID used for DL-SCH or from the reserved LCID value from the LCID used for MBS multicast MCCH and MBS broadcast on DL-SCH, which indicates that it is the MAC CE of the allowed tracking area for the UE.

[0182] In one example (refer to) Figure 8(bottom syntax structure), the eLCID has a value from the reserved eLCID value of an octet eLCID used for DL-SCH, which indicates that it is the MAC CE of the allowed tracking area for the UE.

[0183] MAC CE example with MAC subheader and fixed-size MAC CE

[0184] In one example (refer to) Figure 9 (Top syntax structure), the TA field is carried in the MAC CE payload. The following is just one example; the actual number of bits may vary. Depending on the number of bits used in the TA field, one or more R bits may be included to ensure that the MAC CE payload is octet aligned.

[0185] The subheader used to identify a fixed-size MAC CE can be as follows: Figure 9 Examples are given in (bottom syntax structure). In one example (see...) Figure 9 (bottom syntax structure), the LCID has a value from the reserved LCID value from the LCID used for DL-SCH or from the reserved LCID value from the LCID used for MBS multicast MCCH and MBS broadcast on DL-SCH, which indicates that it is the MAC CE of the allowed tracking area for the UE.

[0186] MAC CE example with MAC subheader and variable-size MAC CE

[0187] In one example (refer to) Figure 10 (Top syntax structure) The TA field is carried in the MAC CE payload, which consists of N TA fields and can indicate 8*N identifiers of the tracking area, where N is an integer. The following is just an example; the actual number of bits may vary. Depending on the number of bits used in the TA field, one or more R bits may be included to ensure that the MAC CE payload is octet aligned.

[0188] The subheader given above for identifying variable-size MAC CEs can be as follows: Figure 10 (See the syntax structure at the bottom).

[0189] In this example, the LCID has a value from the reserved LCID value in the LCID used for DL-SCH or a value from the reserved LCID value in the LCID used for MBS multicast MCCH and MBS broadcast on DL-SCH, which indicates that it is the MAC CE of the allowed tracking area for the UE.

[0190] Example 3 based on geographic coverage information

[0191] Sub-question 1: Content details

[0192] Geographic coverage information, which identifies one or more geographic areas where MBS services are available / permitted. This geographic coverage information may include at least one of the following: ●Area Identifier. Each area identifier is used to identify a geographic area. The area identifier can be at least one of the following: TN-AreaId-r18 (an identifier defined in SIB25 to indicate TN coverage), MBS area session ID, or a newly defined identifier for identifying a geographic area. ● A geographic area indicated by a geometric shape, which may include at least one of the following: ■Opt 1: A circular area defined by the coordinates of the center (origin) and the radius. ■Opt 2: An elliptical region defined by the coordinates of the origin, a major semi-axis of length r1, and a minor semi-axis of length r2, the direction of which is angle A (0 to 180 degrees) measured clockwise from north. ■Opt 3: A polygonal shape indicated by multiple points. The minimum number of points allowed is 3. A maximum number of points can be defined; for example, in some examples, the maximum allowed number of points is 15. The points should be connected in the given order. The connecting line is defined as the line (geodetic line) that connects two points on the ellipsoid with the shortest distance. The last point is connected to the first point. The list of points should follow several conditions: - A connecting line must not cross another connecting line; - Two consecutive points on the ellipsoid must not be in positions opposite each other by diameter.

[0193] The area described lies to the right of the straight line, with the downward direction pointing towards the center of the Earth and the forward direction pointing from one point to the next. ● The mapping between geographic regions and MBS services can include at least one of the following mapping relationships: ■ A geographic region is mapped to one or more MBS services ◆A region identifier is associated with one or more MBS identifiers, where each MBS service identifier is used to identify an MBS service. The MBS service identifier can be a TMGI. ◆A geographic region is associated with one or more MBS identifiers, where each MBS service identifier is used to identify an MBS service. This MBS service identifier can be a TMGI. Each geographic region can be indicated by the geometry discussed in the options above. ■ An MBS service is mapped to one or more geographic regions. ◆ An MBS service identifier is associated with one or more region identifiers. Each region identifier identifies a geographic region, and each MBS service identifier identifies an MBS service. In one example, the MBS service identifier could be TMGI. ◆ An MBS service identifier is associated with one or more geographic regions. Each geographic region can be indicated by the geometry discussed in the options above.

[0194] For the options discussed above, the geographic regions identified by different region identifiers may be non-overlapping or overlapping. For the options discussed above, the MBS service identifier may be other defined identifiers, such as TMGI and group-RNTI.

[0195] Sub-question 2: UE determines whether MBS service is allowed. ●Option 1: Based on the UE's geographic location, for example, location conditions

[0196] In this option, the UE first determines the geographic coverage of each MBS service based on the received geographic area information. For example, when an area identifier is provided and an MBS service is associated with one or more area identifiers, the UE considers the MBS service area to be the total geographic area identified by the area identifiers associated with that MBS service. For example, MBS1 is associated with area identifiers 1, 2, and 3, and area identifiers 1, 2, and 3 correspond to areas 1, 2, and 3. Then the geographic coverage of the MBS service is area 1 + area 2 + area 3.

[0197] Subsequently, the UE compares its geographic location with the geographic coverage of the derived MBS service. When the UE's location is within the geographic coverage of the MBS service, the UE considers the MBS service to be permitted / available for the UE; otherwise, the UE considers the MBS service to be not permitted / available.

[0198] Sub-question 3: Signaling options and example ASN.1

[0199] As discussed in the General section, various options can be considered to provide the UE with the MBS assistance information discussed above. Some example implementations are given below, but other possibilities discussed in the General section are not excluded.

[0200] Example using SIB25

[0201] Example 1 when a TN coverage area is associated with multiple MBS services

[0202] In this example, SIB25 is used to provide geographic coverage for MBS services, and some existing IEs are reused to indicate TN coverage. SIB25 Information Elements

[0203] Example 1: When one or more TN coverage areas are associated with an MBS service

[0204] In this example, SIB25 is used to provide geographic coverage for MBS services, and some existing IEs are reused to indicate TN coverage. SIB25 Information Elements

[0205] Example using the new IE MBS-SessionInfoListAssistingInfo

[0206] The IE MBS-SessionInfoListAssistingInfo provides a list of MBS assistance information. This IE can be included in at least one of the following messages: an existing SIB (e.g., SIB20 / SIB21 / SIB25 / SIB19 or a new SIB defined to provide MBS assistance information), an MCCH / MTCH message, an RRC message, a NAS message, or a paging message. MBS-AssistingInfoList Information Element

[0207] This mbs-assistintInfoList contains one to a maximum of maxAllowedAssistingInfoMBS entries, each containing a set of MBS assistance information indicated by mbs-assistingInfo. maxAllowedAssistingInfoMBS is an integer that specifies the maximum number of MBS assistance information that can be supported.

[0208] In this example, mbs-assistingInfo includes geographic coverage information for MBS.

[0209] For example, if the country information is an MCC code, then mbs-assistingInfo in the example above will be the MCC. In this example, mbs-SessionId-r19 is optional. In some examples, mbs-SessionId-r19 in the example above is mandatory. In this example, g-RNTI-r19 is optional. In some examples, g-RNTI-r19 in the example above is conditionally present; for example, for MBS multicast services, it is mandatory, otherwise it does not exist.

[0210] In this example, each MBS service includes an mbs-CoverageList containing one or more geographic coverage areas. Alternatively, the geographic coverage area might be the TN coverage area provided in SIB25, where each TN coverage area can be identified by an identifier (i.e., TN-AreaId-r18), and only the TN-AreaId-r18 needs to be included for each MBS service. The UE can derive the geographic coverage area of ​​the MBS service by referring to both SIB25 and the message carrying the MBS-AssistingInfoList IE. A signaling example is shown below:

[0211] The only update in this example is that mbs-CoverageList IE includes a TN identifier (e.g., TN-AreaId-r18) for identifying TN coverage areas that are signaled as in SIB25, while the rest is the same as given in the previous example.

[0212] Example 4, based on the combination of the above-discussed content.

[0213] Considering that different MBS services can have different granularities (e.g., national, tracking area, cell, etc.), and to allow for flexible configuration and implementation methods, different signaling can be considered to support the combined use of one or more MBS auxiliary information as discussed above, including at least one of the following implementation options: ● Option 1: A public information element (IE) is used to indicate ancillary information related to MBS service, which can be a selection of at least one of the MBS ancillary information discussed in this application (e.g., country information, tracking area information, TN coverage information, etc.). In this option, only one type of MBS ancillary information is provided to the UE, and the UE will determine whether MBS is available / permitted based on the rules discussed in this application for each type of MBS ancillary information. ● Option 2: A public information element (IE) is used to indicate auxiliary information related to MBS service, which may be a sequence of at least one of the MBS auxiliary information discussed in this application (e.g., country information, tracking area information, TN coverage information, etc.). In this option, one or more types of MBS auxiliary information are provided to the UE, and the UE determines whether MBS service is permitted / available by at least one of the following methods: ■ The UE considers the MBS service available / permitted when all conditions for the provided MBS auxiliary information associated with the MBS service are met. In this method, the UE determines whether the MBS is available / permitted for each type of MBS auxiliary information based on the rules discussed in this application for each type of MBS auxiliary information. ■ The UE considers the MBS service available / permitted when at least one condition of provided MBS auxiliary information associated with the MBS service is met. In this method, the UE determines whether the MBS is available / permitted for each type of MBS auxiliary information based on the rules discussed in this application for each type of MBS auxiliary information.

[0214] The public IE discussed above can be provided to the UE from the NW via at least one of the following signaling options: system information, MCCH message, NAS message, RRC message, paging message, short message, MTCH message, physical layer signaling (e.g., via indications included in DCI), MAC layer signaling (e.g., via MAC CE), group signaling (e.g., based on existing or new RRC messages, used to deliver MBS auxiliary information to UEs within a group), or User Service Description (USD) signaling.

[0215] Example 5 based on public information elements

[0216] In this example, a common IE for providing MBS auxiliary information can be introduced. This common IE can be included in multiple locations / messages, such as at least one of the following: SIBx (e.g., SIB19, SIB20, SIB21, SIB25 or a new SIB for delivering MBS auxiliary information as discussed in this application), or MBSBroadcastConfiguration, or MBSMulticastConfiguration message, a new message for delivering MBS auxiliary information, or RRC message (e.g., RRCReconfiguration), to allow information to be delivered to the UE in different ways to meet different needs.

[0217] Below is an example of MBS auxiliary information for each MBS session.

[0218] Example a: The MBS service identifier is included.

[0219] Example a: MBS auxiliary information includes an MBS service identifier used to identify the MBS session, and the MBS service type can be at least one of broadcast or multicast. –MBS-SessionInfoListAssistingInfo

[0220] The IE MBS-SessionInfoListAssistingInfo provides a list of MBS assistance information. MBS-SessionInfoListAssistingInfo information element

[0221] This mbs-assistintInfoList contains one to a maximum of maxAllowedAssistingInfoMBS entries, each containing a set of MBS assistance information indicated by mbs-assistingInfo. maxAllowedAssistingInfoMBS is an integer that specifies the maximum number of MBS assistance information that can be supported.

[0222] For different implementations, mbs-assistingInfo may include one or more auxiliary information as discussed in this application, such as country information discussed in this application.

[0223] For example, if the country information is an MCC code, then mbs-assistingInfo in the example above would be an MCC.

[0224] In this example, mbs-SessionId-r19 in the examples above is optional. In some examples, mbs-SessionId-r19 in the examples above is mandatory. In some examples, g-RNTI-r19 in the examples above is conditionally present; for example, for MBS multicast services, it is mandatory, otherwise it does not exist.

[0225] Example A: The MBS service identifier is not included. –MBS-SessionInfoListAssistingInfo

[0226] The IE MBS-SessionInfoListAssistingInfo provides a list of MBS assistance information. MBS-SessionInfoListAssistingInfo information element

[0227] This mbs-assistintInfoList contains one to a maximum of maxAllowedAssistingInfoMBS entries, each containing a set of MBS assistance information indicated by mbs-assistingInfo. maxAllowedAssistingInfoMBS is an integer that specifies the maximum number of MBS assistance information that can be supported.

[0228] For different implementations, mbs-assistingInfo may include one or more auxiliary information as discussed in this application, such as country information discussed in this application.

[0229] For example, if the country information is an MCC code, then mbs-assistingInfo in the example above would be an MCC.

[0230] In some examples, mbs-SessionId-r19 and g-RNTI-r19 are not included in the MBS auxiliary information element. In such examples, entries in the MBS auxiliary information list (e.g., MBS-AssistingInfoList) are mapped one-to-one with entries in the MBS session information list (e.g., MBS-SessionInfoList or MBS SessionInfoListMulticas) to ensure a mapping between MBS auxiliary information and MBS services.

[0231] In some examples, such as those discussed above in Example 4, the MBS auxiliary information may be a selection of the MBS auxiliary information discussed in this document to allow for more flexible selection of appropriate MBS auxiliary information to assist the UE in deciding how to correctly select MBS services.

[0232] More details about the information elements mentioned above are provided in the previous example description.

[0233] In some examples, as discussed above in Embodiment 4, the MBS auxiliary information may be one or more MBS auxiliary information as discussed in this application, to allow for more flexible selection of appropriate MBS auxiliary information to assist the UE in deciding how to correctly select MBS services.

[0234] More details about the information elements mentioned above are provided in the previous example description.

[0235] Example 6 based on User Service Description (USD)

[0236] An example of this embodiment is... Figure 11A It was described in the text.

[0237] Sub-question 1: Content details

[0238] The UE can at least obtain the geographical coverage area of ​​the MBS service and / or the MBS area identifier associated with the MBS service from the USD. The USD may include other parameters necessary or beneficial for MBS service reception, which will not be elaborated here. The geographical coverage area can be indicated by at least one of the options discussed in this application for describing the geographical coverage area. Each MBS area identifier can be used to identify a geographical coverage area of ​​the MBS service, and the geographical coverage areas of each MBS service may overlap or not overlap. NW may include at least one of NG-RAN / CN / functional entity, such as NEF, AMF, UPF, SMF, MBS-AMF, MBS-UPF, MBS-SMF, OAM, etc. NG-RAN nodes may include gNB, eNB, ng-eNB, or other base stations (e.g., 6G base stations).

[0239] In addition, the UE can obtain MBS information for MBS service reception from the NW. This MBS information includes at least the MBS area identifier and the associated MBS service. This MBS information may include other parameters necessary or beneficial for MBS service reception, which will not be elaborated here.

[0240] The information in the MBS may include at least one of the following: ●MBS area identification ●Mapping between MBS area identifiers and MBS services

[0241] For details, please refer to the discussion in the previous chapters of Question 1.

[0242] Based on the MBS area identifier and associated geographic coverage in the USD, and the association between the MBS area identifier and MBS services, the UE can derive the geographic coverage of each MBS service. In one example, the MBS area identifier discussed here could be the MBS area session identifier.

[0243] Sub-question 2: How does the UE determine whether MBS service is permitted?

[0244] After knowing the geographic coverage area of ​​each MBS service, the UE can determine whether the MBS service is available based on its geographic location. For example, if the UE is within the geographic coverage area of ​​an MBS service, the MBS service is considered available / allowed for that UE; if the UE is outside the geographic coverage area of ​​an MBS service, the MBS service is considered unavailable / disallowed for that UE.

[0245] Sub-question 3: Signaling options and example ASN.1

[0246] As discussed in Question 0 of the General Procedures section, MBS information received for MBS service reception (which includes at least the MBS area identifier and the associated MBS service) can be transmitted to the UE through at least one of the following methods: system information, dedicated RRC messages, NAS messages, MCCH messages, MTCH messages, MAC layer signaling, physical layer signaling, paging messages, or group signaling. Some examples of how this information can be transmitted to the UE are given below, assuming that the MBS identifier used to identify the MBS service is TMGI, or TMGI+g-RNTI (throughout this document). In various embodiments, other identifiers that can sufficiently uniquely identify the MBS service are also possible.

[0247] An example of how an MBS session identified by an MBS service identifier is mapped to one or more MBS geographic coverage areas identified by an MBS region identifier.

[0248] This `mbs-AreaIdentityList` contains one to a maximum of `maxAreaIdentity-MBS` entries, each containing a set of MBS area identifiers used for an MBS session. `maxAreaIdentity-MBS` is an integer specifying the maximum number of supported MBS area identifiers. In some examples, `MBS-AreaIdentity` can be an octet string, referring to MBS area identifiers defined in other standards. In some examples, `MBS-AreaIdentity` can be an MBS session area identifier.

[0249] For alternative option 1 discussed above, in order to correctly configure MBS auxiliary information (e.g., information related to the MBS service area) to the UE, the NG-RAN and / or CN need to know the geographical coverage of the provided MBS service. And as described in the background section, currently such information is only available from the NEF and MBS service providers. Therefore, an enhancement scheme needs to be considered to allow the geographical coverage of the MBS service to be transmitted to the MBS auxiliary information provided to the UE. Detailed solutions are discussed in the following sections on some additional details for Alt2.

[0250] Example 7: UE reports MBS of interest

[0251] In one example, when MBS auxiliary information has been provided to the UE, the UE may also indicate the MBS service areas of interest on which it wishes to receive MBS services. Based on this and / or its interests and / or its mobility, the UE may report the MBS service areas of interest to the NW by including the MBS service area information in the MBS interest indication. In some examples, this behavior is controlled by NW indication; for example, the UE is allowed to report the MBS service areas of interest when the NW has indicated that this behavior is permitted, for example, by indicating whether the UE can provide the NW with an indication of the MBS service areas of interest on which the UE wants to receive MBS services, as discussed in the MBS auxiliary information section. In some examples, the indication allowing the UE to report the MBS service areas of interest may be included in the system information (e.g., SIB1).

[0252] The following is an example when a list of MBS area identifiers has been provided to the UE, where each MBS service area identifier indicates the geographic area where the MBS service is available. Based on this message and / or its interests and / or its mobility, the UE can report to the NW the MBS service areas on which it intends to receive MBS services by including the MBS service area identifiers of interest in its MBS interest indication. The UE sends an MBSInterestIndication to the NW. MBSInterestIndication Message

[0253] Example of implementation methods related to UE capabilities

[0254] For the examples discussed above regarding receiving MBS auxiliary information and selecting an MBS service based on the provided MBS auxiliary information, there may be additional requirements for the UE. Allowing the UE to inform the NW of its ability to support features as discussed above may be beneficial for the NW in deciding how to appropriately provide MBS auxiliary information. In some examples, it is optional for the UE to support obtaining MBS auxiliary information (e.g., country information) and selecting an MBS service based on that MBS auxiliary information. The UE can send an indication to the NW via a UE capability query / reporting procedure to indicate its ability to support this feature.

[0255] Given that different types of MBS auxiliary information have been discussed in this document, various embodiments are possible. For example, in one approach, only one UE capability is used to indicate the UE's ability to use MBS auxiliary information; when the UE indicates support for MBS service selection using MBS auxiliary information, it supports all MBS auxiliary information introduced for this purpose.

[0256] In another approach, a separate UE capability indication can be used to indicate which MBS auxiliary information the UE supports for MBS service selection. That is, for each type of MBS auxiliary information introduced for this purpose, there will be a different UE capability indication to allow the UE to indicate whether it supports using that MBS auxiliary information for MBS service selection.

[0257] Figure 11B The process 1102 for UE capability information reporting is described. In the first step, the NW can query the UE using a UE capability query. In the subsequent response, the UE can provide its capabilities to the NW in a UECapabilityInformation message. In some examples, such as... Figure 11B As shown, the UE capabilities discussed in this article can be reported to the NG-RAN via RRC messages. In some examples, the UE capabilities discussed in this article can be reported to the CN via NAS messages.

[0258] In some examples, it is optional for the UE to indicate its MBS reception area of ​​interest to the NW, as discussed in this application. The UE can send an indication to the NW via a UE capability query / reporting procedure to indicate its capability to support that feature. In another example, the UE capability discussed herein can be reported to the CN via a NAS message.

[0259] Some additional details regarding Alt2

[0260] As discussed in the General Procedures section, the NW providing MBS auxiliary information to the UE can be at least one NW, which may include at least one of the NG-RAN / CN / functional entities, such as NEF, AMF, UPF, SMF, MBS-AMF, MBS-UPF, MBS-SMF, OAM, etc. NG-RAN nodes may include gNB, eNB, ng-eNB, or other base stations (e.g., 6G base stations).

[0261] In existing systems, the NEF / AF can obtain the geographic coverage area of ​​the MBS service region from the MBS service provider. This coverage area can be a list of cell identifiers, a list of TAIs, a list of geographic areas represented by geometric shapes, or a list of city addresses. When the received MBS service region is a list of geographic areas represented by geometric shapes or a list of city addresses, the NEF will convert it into a list of cell identifiers or TAIs covering the same or substantially the same geographic coverage area. For simplicity, we will use "external MBS service region information" to refer to the geographic coverage information of the MBS service region received from the MBS service provider / AF.

[0262] To allow the conversion of external MBS service area information into MBS auxiliary information as discussed in this application, at least one of the following options may be considered: ● In the first option, the CN converts the received external MBS service area information into MBS auxiliary information and transmits this information to the NG-RAN. ● In the second option, the CN can forward the received external MBS service area information to the NG-RAN node, and then the NG-RAN node converts the external MBS service area information into MBS auxiliary information. ● In the third option, the CN can forward the received external MBS service area information to the UE. ● In the fourth option, the CN converts the received external MBS service area information into MBS auxiliary information and transmits this information to the UE.

[0263] All of the above options are possible, depending on the specific NW implementation.

[0264] As discussed in the preceding chapters of this document, MBS auxiliary information can be at least one of the following: ● One or more country information associated with the MBS service, indicating the countries where the MBS service is intended to be offered. ■ For example, if the received MBS service area indication covers a geographic area of ​​the USA and Canada, then NEF can include: ● One or more tracking regions for MBS services, which indicate the tracking regions that the MBS service intends to provide. ● One or more geographic regions used for MBS services, indicating the geographic regions that the MBS service intends to provide. ● One or more TN cells used for MBS service, indicating TN cells covering the geographic area where MBS service is intended to be provided. It does not indicate that MBS service is provided within that TN cell, but only that the geographic coverage area of ​​that TN cell is the same as or included within the geographic coverage area of ​​MBS service.

[0265] The details of the above information are as discussed in the previous chapters.

[0266] Once additional MBS service area information and / or MBS auxiliary information are available on the NW side, the NW can perform at least one of the following actions in conjunction with the available UE locations:

[0267] When the UE is located outside the MBS service area, the NW rejects the UE's request to join the MBS service.

[0268] When the UE is outside the MBS service area, the NW will remove / release the UE from the MBS session.

[0269] The NW determines the multicast group and the assigned group RNTI based on the UE's location, which is used for monitoring and receiving multicast and for group notifications.

[0270] NW determines whether to use PTP or PTM transmission mode based on the UE's location.

[0271] Reference Figure 12 Here are some examples of possible signaling options.

[0272] Example 7: Transmitting MBS auxiliary information in NEF.

[0273] In this example, the NEF is responsible for converting external MBS service area information received from the AF into MBS auxiliary information. Here, external MBS service area information refers to the MBS service area received from the application provider (AF) (e.g., in the format of a municipal or postal address or geographic area). The AF can be an MBS service provider. Details of the MBS auxiliary information are discussed in this application.

[0274] In some examples, when transmitting received MBS service area information, NEF may combine it with MBS ancillary information discussed in this document to include cell identifiers and / or tracking areas. Alternatively, in another example, the inclusion of MBS ancillary information is mutually exclusive with traditional MBS service area information (i.e., cell identifier lists / TAI lists).

[0275] Subsequently, NEF can transmit MBS auxiliary information to at least one functional entity of CN (e.g., / UPF / SMF / MBS-UPF / MBS-AMF / MBS-SMF), NG-RAN node, or OAM.

[0276] Furthermore, if the NEF does not directly provide MBS auxiliary information to the NG-RAN node, the NG-RAN node can obtain auxiliary information from at least one of the aforementioned CN functional entities (e.g., AMF) or OAM. In the first option, it obtains it from a functional entity other than the NEF (e.g., AMF). In the second option, the NG-RAN node obtains MBS auxiliary information directly from the NEF.

[0277] In another example, the NEF or AF can directly provide external MBS service area information to other functional entities of the CN. Furthermore, the CN functional entity receiving this information can convert the external MBS service area information received from the AF into the MBS auxiliary information discussed in this application. The CN or CN functional entity can also provide MBS auxiliary information to NG-RAN nodes or OAM.

[0278] In another example, the NEF or AF can directly provide external MBS service area information to the NG-RAN node. Furthermore, the NG-RAN node receiving this information can convert the external MBS service area information received from the AF into the MBS auxiliary information discussed in this application.

[0279] Other functional entities of CN include at least one of AMF / UPF / SMF / MBS-UPF / MBS-AMF / MBS-SMF.

[0280] Example 8: CN provides MBS service area to NG-RAN

[0281] Reference Figure 13 In some examples, the CN (including its functional entities, such as the AMF) can provide additional MBS information to the NG-RAN. This additional MBS information may include at least the content of MBS auxiliary information as discussed in this document, such as country information or external MBS service area information discussed in this application. This additional MBS information is optional. Based on this additional MBS information, the NG-RAN node can provide the UE with appropriate MBS auxiliary information.

[0282] In another example, the CN can provide external MBS service area information to the NG-RAN in the format of a list of geographic coverage areas or a list of city addresses. The NG-RAN can then determine the MBS auxiliary information to be provided to the UE based on the received external MBS service area information. This MBS auxiliary information is as discussed in previous sections. For the above example, the NG message includes at least a broadcast session establishment request, a broadcast session modification request, a multicast session update request, a multicast group paging, or a new NGAP message defined to provide MBS auxiliary information related to the MBS service area.

[0283] Some preferred embodiments may implement the following technical solutions.

[0284] 1. A method for wireless communication (e.g., in...) Figure 14 The method 1400 described herein includes: receiving auxiliary information related to a multicast or broadcast service (MBS) from a network device by a wireless device (1402); and making a decision regarding the MBS service by the wireless device based on the auxiliary information (1404). As disclosed herein, in some embodiments, the wireless device may also use its location information when making the decision regarding the MBS service. Various decision examples are disclosed throughout this document, including, for example, joining an MBS service, releasing an MBS service, etc.

[0285] 2. A wireless communication method (e.g., in...) Figure 15 The method 1500 described herein includes: sending auxiliary information (1502) from a network device to a wireless device in relation to a multicast or broadcast service (MBS), the auxiliary information allowing the wireless device to make a decision regarding the MBS service.

[0286] 3. The method according to any one of Schemes 1 to 2, wherein the decision includes determining whether the MBS service is available, appropriate, permitted, qualified, targeted, or anticipated for the wireless device.

[0287] 4. The method according to any one of Schemes 1 to 3, wherein the auxiliary information includes service area information.

[0288] 5. According to the method described in Scheme 4, the service area information includes country information.

[0289] 6. The method according to Scheme 4, wherein the service area information includes tracking area information.

[0290] 7. The method according to claim 5, wherein the decision includes: determining whether the MBS service is available in response to location information indicated by the auxiliary information, which indicates the country in which the wireless device is operating.

[0291] 8. The method according to any one of claims 1 to 7, wherein the location information indicates that the wireless device is associated with more than one country.

[0292] 9. The method according to any one of Schemes 1 to 8, wherein the auxiliary information is carried in a system information block.

[0293] 10. The method according to any one of schemes 1 to 9, wherein the auxiliary information includes a list of allowed countries and / or a bitmap indicating the countries allowed for the MBS service.

[0294] 11. The method according to any one of claims 1 to 10, wherein the decision regarding MBS service includes: in response to determining based on the auxiliary information that an unauthorized MBS service is available: the wireless device skips the acquisition of MBS configuration, or the wireless device skips the monitoring of scheduling information for receiving MBS data; or the wireless device avoids receiving MBS data.

[0295] 12. The method according to any one of Schemes 1 to 10, wherein the decision regarding the MBS service comprises: in response to determining that at least one MBS service is available based on the auxiliary information: the radio device initiates the acquisition of the multicast control channel (MCCH); or selects one or more of the available at least one MBS services and initiates a multicast radio bearer establishment process.

[0296] 13. The method according to any one of claims 1 to 10, wherein the decision regarding MBS service includes: in response to determining, based on the auxiliary information, that the MBS service currently being received by the wireless device is now unavailable: releasing the MBS service.

[0297] 14. An apparatus for wireless communication, the apparatus comprising at least one processor configured to implement the method described in any of the above solutions.

[0298] 15. A computer storage medium having code stored thereon, wherein, when executed by at least one processor, the code causes at least one processor to perform the method described in any of the above solutions.

[0299] Some embodiments described herein are described in the general context of methods or processes that may be implemented in one embodiment by a computer program product embodied in a computer-readable medium, including computer-executable instructions such as program code executed by a computer in a networked environment. The computer-readable medium may include removable and non-removable storage devices, including but not limited to read-only memory (ROM), random access memory (RAM), optical disc (CD), digital versatile optical disc (DVD), etc. Therefore, the computer-readable medium can include non-transitory storage media. Typically, program modules may include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. Computer or processor-executable instructions, associated data structures, and program modules represent examples of program code for performing steps of the methods disclosed herein. A particular sequence of executable instructions or associated data structures represents examples of corresponding behaviors for implementing the functions described in these steps or processes.

[0300] Some of the disclosed embodiments can be implemented as devices or modules using hardware circuitry, software, or combinations thereof. For example, hardware circuitry implementations can include discrete analog and / or digital components, which may be integrated, for example, as part of a printed circuit board. Alternatively or additionally, the disclosed components or modules can be implemented as application-specific integrated circuits (ASICs) and / or field-programmable gate arrays (FPGAs) devices. Some implementations additionally or alternatively include a digital signal processor (DSP), which is a dedicated microprocessor with an architecture optimized for the operational requirements of digital signal processing associated with the functions disclosed herein. Similarly, the various components or sub-components within each module can be implemented in software, hardware, or firmware. Connections between modules and / or components within modules can be provided using any connection methods and media known in the art, including but not limited to communication via the Internet, wired or wireless networks using appropriate protocols.

[0301] Although this document contains numerous details, these details should not be construed as limiting the scope of the claimed invention or the claimed content, but rather as descriptions of specific features of particular embodiments. Some features described herein in the context of individual embodiments can also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment can also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, although the foregoing features may be described as operating in a particular combination, and even initially claimed, one or more features from the claimed combination can be removed from the claimed combination in certain circumstances, and the claimed combination may be for sub-combinations or variations thereof. Similarly, although operations are depicted in a specific order in the drawings, this should not be construed as requiring these operations to be performed in the specific order or sequence shown, or requiring the performance of all illustrated operations to achieve the desired result.

[0302] This document describes only some implementation methods and examples. Other implementation methods, improvements and variations can be made based on the content described and explained in this document.

Claims

1. A method for wireless communication, the method comprising: The wireless device receives auxiliary information related to multicast or broadcast services (MBS) from the network device; as well as The wireless device makes a decision regarding MBS services based on the auxiliary information.

2. A method for wireless communication, the method comprising: The network device sends auxiliary information related to multicast or broadcast services (MBS) to the wireless device, which allows the wireless device to make decisions about the MBS service.

3. The method according to any one of claims 1 to 2, wherein, The decision includes determining whether the MBS service is available, appropriate, permitted, qualified, targeted, or anticipated for the wireless device.

4. The method according to any one of claims 1 to 3, wherein, The auxiliary information includes service area information.

5. The method according to claim 4, wherein, The service area information includes country information.

6. The method according to claim 4, wherein, The service area information includes tracking area information.

7. The method according to claim 5, wherein, The decision includes determining whether the MBS service is available in response to location information indicated by the auxiliary information, which indicates the country in which the wireless device is operating.

8. The method according to any one of claims 1 to 7, wherein, The location information indicates that the wireless device is associated with more than one country.

9. The method according to any one of claims 1 to 8, wherein, The auxiliary information is carried in the system information block.

10. The method according to any one of claims 1 to 9, wherein, The auxiliary information includes a list of allowed countries and / or a bitmap indicating the countries allowed for the MBS service.

11. The method according to any one of claims 1 to 10, wherein, The decision regarding the MBS service includes: In response to determining, based on the auxiliary information, that no authorized MBS service is available: The wireless device skips the acquisition of MBS configuration, or The wireless device skips the monitoring of scheduling information used to receive MBS data; or The wireless device avoids receiving MBS data.

12. The method according to any one of claims 1 to 10, wherein, The decision regarding the MBS service includes: In response to determining that at least one MBS service is available based on the auxiliary information: The wireless device initiates the acquisition of the MBS control channel (MCCH); or Select one or more of the at least one available MBS service and initiate a multicast radio bearer establishment process.

13. The method according to any one of claims 1 to 10, wherein, The decision regarding the MBS service includes: In response to determining, based on the auxiliary information, that the MBS service currently being received by the wireless device is now unavailable: Release the MBS service.

14. An apparatus for wireless communication, the apparatus comprising at least one processor configured to perform the method of any one of the preceding claims.

15. A computer storage medium having code stored thereon, wherein, When the code is executed by at least one processor, it causes the at least one processor to perform the method according to any one of the preceding claims.

Images