WO2025251997A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置

Info

Publication number
WO2025251997A1
WO2025251997A1 PCT/CN2025/098036 CN2025098036W WO2025251997A1 WO 2025251997 A1 WO2025251997 A1 WO 2025251997A1 CN 2025098036 W CN2025098036 W CN 2025098036W WO 2025251997 A1 WO2025251997 A1 WO 2025251997A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
area
mbs
region
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2025/098036
Other languages
English (en)
French (fr)
Inventor
李濛
潘奇
张海森
陈磊
杨艳梅
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2025251997A1 publication Critical patent/WO2025251997A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

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

Definitions

  • This application relates to the field of wireless communication technology, and in particular to a communication method and apparatus.
  • Multicast and broadcast service was introduced by the 3rd generation partnership project (3GPP) to effectively utilize mobile communication network resources. It is a point-to-multipoint service in mobile communication networks that provides a data source to send data to multiple users, thereby achieving network resource sharing and improving resource (especially air interface resources) utilization.
  • 3GPP 3rd generation partnership project
  • Location-dependent MBS is a type of MBS service that allows the transmission of different data for the same MBS service in different regions.
  • This application provides a communication method and apparatus that offers a solution for location-related MBS services, addressing the service requirement of sending different data of the same MBS service within the same area.
  • a communication method is provided, which can be applied to the network side, such as to an access network device, or a module (e.g., circuit, chip, or chip system) within the access network device, or a logical node, logical module, or software capable of implementing all or part of the functions of the access network device.
  • the access network device receives a request message for requesting the establishment of a first area session.
  • the request message includes information about the first area, wherein the first area overlaps with a second area corresponding to an established second area session, and the second area session is used to send second data of a first MBS service.
  • the access network device establishes a first area session, which corresponds to other areas within the first area besides the area overlapping with the second area.
  • the first area session is used to send first data of the first MBS service.
  • the first MBS session is used to transmit the first MBS service
  • the first regional session and the second regional session are different regional sessions associated with the first MBS session.
  • the identifier of the first regional session is a unique identifier used to identify location-related content.
  • the overlapping region can be excluded from the MBS service region corresponding to the first region session when establishing the first region session. This can prevent the newly established first region session from affecting the already established second region session, so as to ensure that the terminal devices in the second region (including the overlapping region) can still receive the second data.
  • the request message for requesting the establishment of a first area session may further include the identifier of the first MBS session and the identifier of the first area session.
  • the information in the first area includes one or more of the following: cell identifier and tracking area identifier.
  • the cell identifier is the identifier of the mapped cell corresponding to the NTN cell
  • the tracking area identifier is the identifier of the mapped tracking area corresponding to the NTN tracking area.
  • the method further includes sending a first message indicating that no regional session has been established for the overlapping region.
  • the first information includes information about the overlapping area and first indication information; wherein, the first indication information indicates that the overlapping area is not included in the area corresponding to the first area session, or the first indication information indicates that the area corresponding to the first area session to be established overlaps with the area corresponding to another area session.
  • the first information may be included in a response message, which may also include the identifier of the first MBS session and the identifier of the first regional session.
  • the access network device can notify the application function (AF) or MBS server that the overlapping area is not included in the area corresponding to the first area session, and notify the AF (or MBS server) of the overlapping area. This allows the AF (or MBS server) to obtain the MBS service area corresponding to the first area session and initiate a new session establishment process for the overlapping area.
  • AF application function
  • MBS server MBS service area
  • the method further includes: an access network device receiving a request message for requesting the establishment of a new session, the request message including information about the overlapping area, the new session being used to send the first data.
  • new sessions can also be established for the overlapping regions to transmit the first data, thereby ensuring that terminal devices in the overlapping regions can receive both the second and first data, thus meeting business requirements.
  • the new session is a second MBS session, which is different from the first MBS session.
  • the first MBS session is a session of location-related MBS services; the second MBS session is a session of non-location-related MBS services, or the second MBS session is a session of location-related MBS services.
  • a communication method is provided, which can be applied to the network side, such as an AF or MBS server applied to the network side, or a module (e.g., circuit, chip, or chip system) in the AF or MBS server, or a logical node, logical module, or software that can implement all or part of the functions of the AF or MBS server.
  • a module e.g., circuit, chip, or chip system
  • AF sends a request message for requesting the establishment of a first area session, the request message including information about the first area, wherein the first area overlaps with a second area corresponding to an established second area session, and the second area session is used to send second data of the first MBS service; AF receives first information, the first information indicating that no area session has been established for the overlapping area; AF sends a request message for requesting the establishment of a new session, the request message for requesting the establishment of a new session including information about the overlapping area, and the new session is used to send the first data.
  • the first information includes information about the overlapping region and first indication information; wherein the first indication information indicates that the overlapping region is not included in the region corresponding to the first region session, or the first indication information indicates that the region corresponding to the first region session to be established overlaps with the region corresponding to another region session.
  • the new session is a second MBS session, which is different from the first MBS session.
  • the first MBS session is a session of location-related MBS services; the second MBS session is a session of non-location-related MBS services, or the second MBS session is a session of location-related MBS services.
  • the method further includes: the AF sending an announcement message to a terminal device in the overlapping area, the announcement message including an identifier of the first MBS session and an identifier of the second MBS session, the announcement message being used to instruct the terminal device to receive data from the first MBS session and data from the second MBS session, the data from the first MBS session including the second data, and the data from the second MBS session including the first data.
  • a communication method is provided, which can be applied to the network side, such as to access network devices or network exposure functions (NEFs) on the network side, or modules (e.g., circuits, chips, or chip systems) in access network devices or NEFs, or logical nodes, logical modules, or software that can implement all or part of the functions of access network devices or NEFs.
  • NEFs network exposure functions
  • modules e.g., circuits, chips, or chip systems
  • the access network device receives a request message for requesting the establishment of a first area session, the request message including information about the first area, the first area session being used to send first data of a first MBS service; if the first area overlaps with the second area corresponding to a second area session, a response message is sent, the response message indicating that the establishment of the first area session has failed, wherein the second area session is used to send second data of the first MBS service.
  • the access network device can refuse to establish the first area session. This can avoid affecting the already established second area session and ensure that the terminal device in the second area (including the overlapping area) can still receive the second data.
  • the method further includes: obtaining context information of the second region session, the context information including information of the second region; and determining, based on the information of the second region and the information of the first region, that the first region and the second region overlap.
  • the response message includes one or more of the following: the reason for the failure to establish the first regional session, or a handling suggestion.
  • the access network device can feed back the reason for the failure of the first area session establishment and/or the handling suggestions to the AF or MBS server, so that the AF or MBS server can perform corresponding processing.
  • the response message includes failure reason indication information for indicating the reason why the establishment of the first area session failed.
  • the failure reason indication information indicates one or more of the following: a session for location-related MBS services cannot be established; or, the first area corresponding to the first area session to be established includes a non-terrestrial network NTN type area; or, for the first MBS session, the first area corresponding to the first area session to be established overlaps with the area corresponding to another area session.
  • the response message includes processing suggestion indication information for indicating processing suggestions.
  • the processing suggestion indication information indicates one or more of the following: establishing a non-location-related MBS service session, wherein the MBS service area of the non-location-related MBS service session is the first area; or establishing a location-related MBS service session, wherein the MBS service area of the location-related MBS service session is the first area; or establishing unicast sessions for terminal devices within the first area, wherein the unicast sessions are used to transmit the first data.
  • the method further includes: receiving a request message for requesting the establishment of a new session, the request message for requesting the establishment of a new session including information about the overlapping area, the new session being used to send the first data; and in response to the request message for requesting the establishment of a new session, establishing the new session, or sending a session establishment request message for requesting the establishment of the new session to a session management function network element.
  • a new session can be established for the first region to transmit the first data, so as to ensure that the terminal device in the overlapping region can receive both the second data and the first data, thereby meeting the business requirements.
  • the new session is a second MBS session, which is different from the first MBS session.
  • the first MBS session is a session of location-related MBS services; the second MBS session is a session of non-location-related MBS services, or the second MBS session is a session of location-related MBS services.
  • a communication method is provided, which can be applied to the network side, such as an AF or MBS server applied to the network side, or a module (e.g., circuit, chip, or chip system) in the AF or MBS server, or a logical node, logical module, or software that can implement all or part of the functions of the AF or MBS server.
  • a module e.g., circuit, chip, or chip system
  • AF sends a request message for requesting the establishment of a first area session, the request message including information about the first area; wherein, the first area overlaps with a second area corresponding to an established second area session, the second area session is used to send second data of the first MBS service, and the first area session is used to send first data of the first MBS service; AF receives a response message corresponding to the request message, the response message indicating that the establishment of the first area session failed; AF sends a request message for requesting the establishment of a new session, the request message for requesting the establishment of a new session including information about the overlapping area, the new session being used to send the first data.
  • the response message includes one or more of the following: the reason for the failure to establish the first regional session, or a handling suggestion.
  • the response message includes failure reason indication information for indicating the reason why the establishment of the first area session failed.
  • the failure reason indication information indicates one or more of the following: a session for location-related MBS services cannot be established; or, the first area corresponding to the first area session to be established includes a non-terrestrial network NTN type area; or, for the first MBS session, the first area corresponding to the first area session to be established overlaps with the area corresponding to another area session.
  • the response message includes processing suggestion indication information for indicating processing suggestions.
  • the processing suggestion indication information indicates one or more of the following: establishing a non-location-related MBS service session, wherein the MBS service area of the non-location-related MBS service session is the first area; or establishing a location-related MBS service session, wherein the MBS service area of the location-related MBS service session is the first area; or establishing unicast sessions for terminal devices within the first area, wherein the unicast sessions are used to transmit the first data.
  • the new session is a second MBS session, which is different from the first MBS session.
  • the first MBS session is a session of location-related MBS services; the second MBS session is a session of non-location-related MBS services, or the second MBS session is a session of location-related MBS services.
  • a communication method is provided, which can be applied to the network side, such as a NEF applied to the network side, or a module (e.g., circuit, chip, or chip system) in the NEF, or a logical node, logical module, or software that can implement all or part of the NEF's functions.
  • a NEF applied to the network side
  • a module e.g., circuit, chip, or chip system
  • a logical node e.g., circuit, chip, or chip system
  • the NEF receives a request message for requesting the establishment of a first area session, the request message including information about the first area, the first area session being used to send first data of a first MBS service; the NEF determines that the first area includes an NTN cell based on the cell identifier and corresponding relationship information contained in the information of the first area, and/or determines that the first area includes an NTN tracking area based on the tracking area identifier and the corresponding relationship information contained in the information of the first area, then sends a response message in response to the first request message, the response message indicating that the establishment of the first area session has failed.
  • the corresponding relationship information includes one of a first corresponding relationship information and a second corresponding relationship information.
  • the first corresponding relationship information includes the corresponding relationship information between cell identifier and cell type, and/or the corresponding relationship information between tracking area identifier and tracking area type.
  • the second corresponding relationship information includes the corresponding relationship information between mapped cell identifier and NTN cell identifier, and/or the corresponding relationship information between mapped tracking area identifier and NTN tracking area identifier.
  • a communication method is provided, which can be applied to the network side, such as a NEF applied to the network side, or a module (e.g., circuit, chip, or chip system) in the NEF, or a logical node, logical module, or software that can implement all or part of the NEF's functions.
  • a NEF applied to the network side
  • a module e.g., circuit, chip, or chip system
  • a logical node, logical module e.g., software that can implement all or part of the NEF's functions.
  • the NEF receives a request message for requesting the establishment of a first area session, the request message including information about the first area, the first area session being used to send first data of a first MBS service; the NEF sends a first message, the first message being used to request feedback from a network element storing corresponding relationship information whether the establishment of a first area session for the first area is permitted, the first message including information about the first area; the NEF receives a second message from the network element storing the corresponding relationship, the second message indicating that the establishment of a first area session for the first area is not possible, and the NEF sends a response message according to the second message, the response message being used to indicate that the establishment of the first area session has failed.
  • the network element storing the correspondence information is used to determine whether the first region includes an NTN cell and/or an NTN tracking area based on the information of the first region and the correspondence information.
  • the correspondence information includes one of a first correspondence information and a second correspondence information, wherein the first correspondence information includes correspondence information between cell identifier and cell type, and/or correspondence information between tracking area identifier and tracking area type, and the second correspondence information includes correspondence information between mapped cell identifier and NTN cell identifier, and/or correspondence information between mapped tracking area identifier and NTN tracking area identifier.
  • the response message includes one or more of the following: the reason for the failure of the first regional session establishment, or a processing suggestion.
  • the response message includes failure reason indication information for indicating the reason why the establishment of the first regional session failed.
  • the failure reason indication information indicates one or more of the following: a session for location-related MBS services cannot be established; or, the first region corresponding to the first regional session to be established includes a non-terrestrial network NTN type region; or, for the first MBS session, the first region corresponding to the first regional session to be established overlaps with the region corresponding to another regional session.
  • the response message includes processing suggestion indication information for indicating processing suggestions, the processing suggestion indication information indicating one or more of the following: establishing a non-location-related MBS service session, the MBS service area of the non-location-related MBS service session being the first area; or establishing a location-related MBS service session, the MBS service area of the location-related MBS service session being the first area; or establishing unicast sessions for terminal devices within the first area respectively, the unicast sessions being used to transmit the first data.
  • it further includes: receiving a request message for requesting the establishment of a new session, the request message for requesting the establishment of a new session including information about the overlapping area, the new session being used to send the first data; and in response to the request message for requesting the establishment of a new session, establishing the new session, or sending a session establishment request message for requesting the establishment of the new session to a session management function network element.
  • the new session is a second MBS session
  • the first MBS session is different from the second MBS session.
  • the first MBS session is a session of location-related MBS services; the second MBS session is a session of non-location-related MBS services, or the second MBS session is a session of location-related MBS services.
  • a seventh aspect provides a communication apparatus comprising a unit or module for performing the method as described in any of the first aspects above, or comprising a unit or module for performing the method as described in any of the second aspects above, or comprising a unit or module for performing the method as described in any of the third aspects above, or comprising a unit or module for performing the method as described in any of the fourth aspects above, or comprising a unit or module for performing the method as described in any of the fifth aspects above, or comprising a unit or module for performing the method as described in any of the sixth aspects above.
  • a communication device comprising: one or more processors configured to perform the method as described in any one of the first aspects, or to perform the method as described in any one of the second aspects, or to perform the method as described in any one of the third aspects, or to perform the method as described in any one of the fourth aspects, or to perform the method as described in any one of the fifth aspects, or to perform the method as described in any one of the sixth aspects.
  • a communication system which may include an access network device and an AF; wherein the access network device can implement the method as described in any one of the first aspects, and the AF can implement the method as described in any one of the second aspects; or, the access network device can implement the method as described in any one of the third aspects, and the AF can implement the method as described in any one of the fourth aspects.
  • a communication system which may include a NEF and an AF; wherein the NEF can implement the method as described in any one of the fifth or sixth aspects, and the AF can implement the method as described in any one of the fourth aspects.
  • a readable storage medium storing a program or instructions that, when the program or instructions are executed on a device, cause the device to perform the method as described in any one of the first aspects, or the method as described in any one of the second aspects, or the method as described in any one of the third aspects, or the method as described in any one of the fourth aspects, or the method as described in any one of the fifth aspects, or the method as described in any one of the sixth aspects.
  • a chip system for supporting a computer device to implement the method as described in any one of the first aspects, or the method as described in any one of the second aspects, or the method as described in any one of the third aspects, or the method as described in any one of the fourth aspects, or the method as described in any one of the fifth aspects, or the method as described in any one of the sixth aspects.
  • a program product comprising a program; when the program is run on a computer, the computer performs the method as described in any one of the first aspects, or performs the method as described in any one of the second aspects, or performs the method as described in any one of the third aspects, or performs the method as described in any one of the fourth aspects, or performs the method as described in any one of the fifth aspects, or performs the method as described in any one of the sixth aspects.
  • Figure 1 is a schematic diagram of a 5G network architecture based on service-oriented interfaces applicable to the embodiments of this application;
  • Figure 2 is a schematic diagram of a 5G network architecture based on a point-to-point interface applicable to the embodiments of this application;
  • FIG. 3 is a schematic diagram of the NTN network applicable to the embodiments of this application.
  • FIG. 4 is a schematic diagram of the MBS transmission method applicable to the embodiments of this application.
  • Figure 5 is a schematic diagram of a session establishment process for a broadcast service applicable to an embodiment of this application
  • Figure 6 is a schematic diagram of the transmission of location-related MBS services
  • Figure 7 is a flowchart illustrating a communication method provided in an embodiment of this application.
  • Figure 8 is a schematic diagram of location-related MBS transmitting different data in the same area in an embodiment of this application.
  • Figure 9 is a flowchart illustrating another communication method provided in an embodiment of this application.
  • Figure 10 is a schematic diagram of location-related MBS transmitting different data in the same area in an embodiment of this application;
  • FIG 11 is a flowchart illustrating another communication method provided in an embodiment of this application.
  • Figure 12 is a flowchart illustrating another communication method provided in an embodiment of this application.
  • Figure 13 is a schematic diagram of the structure of a communication device provided in an embodiment of this application.
  • Figure 14 is a schematic diagram of another communication device provided in an embodiment of this application.
  • Figure 15 is a schematic diagram of another communication device provided in an embodiment of this application.
  • NTN Non-terrestrial networks
  • TN terrestrial networks
  • Non-terrestrial networks refer to networks where at least some network equipment is deployed on land. Examples include communication networks that incorporate aircraft (such as airplanes or drones) or satellites as relay nodes or base stations. Conversely, terrestrial networks, abbreviated as TN or TN network, are networks where all network equipment is deployed on land.
  • the terminal device sends data to the base station via satellite
  • the base station sends data to the terminal device via satellite. Because the distance from the satellite to the ground is very long, the coverage area of a single satellite is large, meaning the coverage radius of an air interface cell is also large.
  • the network architectures of NTN and TN can follow the Next Generation System architecture defined by the 3GPP standards group, which can also be called the 5G network architecture.
  • This architecture supports radio access technologies defined by the 3GPP standards group (such as Long Term Evolution (LTE) access technology, 5G radio access network (RAN) access technology, etc.) to access the 5G core network (CN). It also supports access to the core network using non-3GPP access technologies through non-3GPP interworking functions (N3IWF) or next generation packet data gateways (ngPDG).
  • LTE Long Term Evolution
  • RAN radio access network
  • CN 5G core network
  • N3IWF non-3GPP interworking functions
  • ngPDG next generation packet data gateways
  • FIG. 1 is a schematic diagram of a service-oriented architecture-based 5G network.
  • the 5G network architecture shown in Figure 1 may include access network equipment and core network equipment. Terminal devices access the data network (DN) through access network equipment and core network equipment.
  • the core network equipment includes, but is not limited to, some or all of the following network elements: authentication server function (AUSF) network element, unified data management (UDM) network element, unified data repository (UDR) network element (not shown in the figure), network repository function (NRF) network element, network exposure function (NEF) network element, network slice selection function (NSSF) network element, and network slice-specific authentication and authorization function.
  • AUSF authentication server function
  • UDM unified data management
  • UDR unified data repository
  • NEF network exposure function
  • NSSF network slice selection function
  • the network elements include: authorization function (NSSAAF), network slice admission control function (NSACF), application function (AF), policy control function (PCF), access and mobility management function (AMF), session management function (SMF), user plane function (UPF), and binding support function (BSF) (not shown in the figure).
  • NSSAAF authorization function
  • NSACF network slice admission control function
  • AF application function
  • PCF policy control function
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • BSF binding support function
  • Terminal devices can be user equipment (UE), mobile stations, mobile terminal devices, etc. They can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc.
  • Terminal devices can include mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, urban air mobility vehicles (such as drones, helicopters, etc.), ships, robots, robotic arms, smart home devices, etc.
  • Access network equipment is a device with wireless transceiver capabilities used to communicate with the terminal device.
  • the access network equipment includes, but is not limited to, base stations (base transceiver stations, BTS, Node B, eNodeB/eNB, or gNodeB/gNB), transmission reception points (TRPs), base stations evolved from the 3rd Generation Partnership Project (3GPP), access nodes in Wi-Fi systems, wireless relay nodes, and wireless backhaul nodes.
  • the base station can be a macro base station, micro base station, pico base station, small cell, relay station, etc. Multiple base stations can support networks using the same access technology or networks using different access technologies.
  • a base station can contain one or more co-located or non-co-located transmission and reception points.
  • the access network equipment can also be a radio controller, centralized unit (CU), and/or distributed unit (DU) in a cloud radio access network (CRAN) scenario.
  • the access network equipment can also be a server, etc.
  • Access network equipment and terminal equipment can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the access network equipment and terminal equipment.
  • the AMF network element is responsible for the mobility management of the UE, including mobility state management, assigning temporary identity identifiers to the UE, and authenticating and authorizing the UE.
  • the SMF network element is responsible for the selection of UPF network elements, the reselection of UPF network elements, IP address allocation, the establishment, modification and release of bearers, and quality of service (QoS) control.
  • QoS quality of service
  • UPF network elements support all or some of the following functions: interconnecting Protocol Data Unit (PDU) sessions with the data network; packet routing and forwarding (e.g., supporting uplink classification of traffic before forwarding to the data network); and packet inspection.
  • PDU Protocol Data Unit
  • packet routing and forwarding e.g., supporting uplink classification of traffic before forwarding to the data network
  • packet inspection e.g., packet inspection.
  • the UDM network element is responsible for managing the contract data and notifying the relevant network element when the contract data is modified.
  • Nnssf, Nnef, Nnrf, Npcf, Nudm, Naf, Nnssaaf, Nausf, Namf, Nsmf, and Nnsacf are the service interfaces provided by NSSF, NEF, NRF, PCF, UDM, AF, NSSAAF, AUSF, AMF, SMF, and NSACF, respectively, used to invoke the corresponding service operations.
  • N1, N2, N3, N4, N6, and N9 are interface sequence numbers, and the meanings of these interface sequence numbers are as follows:
  • N1 The interface between the AMF and the terminal device, which can be used to transmit non-access stratum (NAS) signaling (such as QoS rules from the AMF) to the terminal device.
  • NAS non-access stratum
  • N2 The interface between the AMF and the access network equipment, which can be used to transmit radio bearer control information from the core network side to the access network equipment.
  • N3 The interface between the access network device and the UPF, mainly used to transmit uplink and downlink user plane data between the access network device and the UPF.
  • N4 The interface between SMF and UPF, which can be used to transmit information between the control plane and the user plane, including the distribution of forwarding rules, QoS rules, traffic statistics rules, etc. from the control plane to the user plane, as well as the reporting of information from the user plane.
  • N6 The interface between UPF and DN, used to transmit uplink and downlink user data streams between UPF and DN.
  • N9 User plane interface between UPF network elements, used to transmit uplink and downlink user data streams between UPF network elements.
  • Figure 2 is a schematic diagram of a 5G network architecture based on point-to-point interfaces. The functions of the network elements are described in Figure 1, and will not be repeated here. The main difference between Figure 2 and Figure 1 is that the interfaces between the control plane network elements in Figure 1 are service-oriented interfaces, while the interfaces between the control plane network elements in Figure 2 are point-to-point interfaces.
  • the aforementioned network element or function can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform).
  • a platform e.g., a cloud platform
  • the aforementioned network element or function can be implemented by one device, multiple devices working together, or a functional module within a single device; this application embodiment does not specifically limit this.
  • the mobility management network element, session management network element, data management network element, and network storage function network element in this application can be the AMF network element, SMF network element, and NEF network element in a 5G system, respectively, or they can be network elements in future communications such as 6G networks that have the functions of the aforementioned AMF network element, SMF network element, and NEF network element.
  • This application does not limit them in this way.
  • the AMF network element, SMF network element, and NEF network element are described as examples of the mobility management network element, session management network element, data management network element, and network storage function network element, respectively.
  • the AMF network element, SMF network element, and NEF network element are abbreviated as AMF, SMF, and NEF, respectively.
  • this application uses a base station and a UE as specific examples of access network equipment and terminal equipment, respectively.
  • the base station and UE appearing in any subsequent position can be replaced with access network equipment and terminal equipment, respectively.
  • Figure 3 shows a schematic diagram of an NTN network, in which satellites can serve as relay nodes between terminal devices and ground base stations, or as base stations.
  • the air interface cell identifier is the identifier of an air interface cell.
  • the air interface cell identifier includes the physical cell identifier (PCI), carrier frequency (such as the absolute radio frequency channel number (ARFCN)), and cell global identifier (GCI).
  • PCI physical cell identifier
  • ARFCN absolute radio frequency channel number
  • GCI cell global identifier
  • the CGI is typically used to identify cells.
  • some core network elements such as NEF (New Network Frame) and AMF (Active Network Frame), can map their corresponding geographical locations based on the CGI.
  • An air interface cell can be associated with multiple mapped cell IDs, each corresponding to a fixed geographical area.
  • the satellite is stationary relative to the ground, making the mapped cell ID of an NTN cell unchanged over time; in other NTN scenarios, the satellite moves relative to the ground, causing the mapped cell ID of an NTN cell to change over time.
  • the NR CGI field in the exchanged messages is filled with the mapped cell ID, allowing the base station and the core network to clearly identify the current geographical location of the terminal device.
  • the mapped air interface cell ID or the mapped cell ID can be exchanged.
  • the purpose of the mapped cell identifier is to map a geographical location area, and it does not represent the air interface cell coverage of that geographical location area, nor does it mean that there is definitely signal coverage in that geographical location area.
  • a tracking area can include one or more cells, and different tracking areas can be distinguished using a tracking area identity (TAI). Similarly, there are also NTN tracking areas.
  • An NTN tracking area's TAI can correspond to one or more mapped tracking area identities (TAIs).
  • a mapped TAI can correspond to one or more mapped cell IDs.
  • MBS Mobile Broadcast Service
  • MBS service data originates from an MBS server, also known as a data server, which provides MBS data.
  • MBS server also known as a data server, which provides MBS data.
  • AF Automatic Firewall
  • MBS server can act as an MBS server.
  • the MBS server sends the MBS data to the core network equipment.
  • the core network equipment sends the MBS data to the access network equipment.
  • the access network equipment sends the MBS data to one or more terminal devices that received the MBS.
  • the core network equipment sends the MBS data to the access network equipment through a common transmission channel, namely the MBS session.
  • the access network equipment can send the MBS data to the terminal devices in two ways: Method 1) using point-to-multipoint (PTM) transmission; Method 2) using point-to-point (PTP) transmission.
  • Figure 4 shows a schematic diagram of PTP and PTM transmission.
  • MBS is merely an exemplary name.
  • the name of multicast service may differ under different communication standards. For example, in Long Term Evolution (LTE), multicast service may be called Multimedia Broadcast Multicast Service (MBMS), while in New Radio (NR), multicast service may be called MBS. In the future development of communications, multicast service may also be named other names. This application does not impose any specific limitations.
  • MBS can also be referred to as "MBS service”, “MBS business”, “MBS broadcast service”, “MBS session” or “MBS broadcast business”, etc.
  • the area that provides MBS can be called “MBS service area”, "MBS business area”, “MBS broadcast service area”, “MBS session area”, “MBS broadcast business area”, “MBS area”, “MBS service area”, “MBS service area” or “service area”, etc.
  • MBS services can include multicast and broadcast services.
  • MBS can be replaced with multicast or broadcast.
  • Multicast services are designed for services with high Quality of Service (QoS) requirements. Group management is available for multicast services, providing the same QoS level as unicast services.
  • the core network CN
  • the core network For the radio access network (RAN), it supports sending data to terminal devices via PTP or PTM transmission, and supports dynamic switching between PTP and PTM controlled by the RAN.
  • Multicast services are provided to connected terminal devices in Radio Resource Control (RRC) mode, and the RAN and CN can maintain the terminal device information corresponding to MBS groups. Multicast services also support MBS session deactivation/activation triggered by the core network, without the terminal devices being aware of the service status.
  • RRC Radio Resource Control
  • Broadcast services are designed for services with relatively low QoS requirements, aiming to guarantee QoS to the best of our ability.
  • Broadcast services support terminal devices in any RRC state.
  • the RAN and CN do not need to maintain groups of terminal devices receiving broadcast services; when a service is being provided, the terminal device group receives it autonomously based on its configuration information.
  • broadcast data transmission is designed only for downlink transmission.
  • broadcast services only support PTM transmission mode. For terminal devices, the configuration for broadcast services is completely independent of that for multicast services.
  • Broadcast services are limited to a specific area.
  • a single broadcast service can provide different data content in different areas (i.e., local broadcast services).
  • broadcast services involve a top-down session establishment process.
  • the content provider such as an application function (AF) or MBS server
  • AF application function
  • MBS server provides the relevant information needed to establish a broadcast service session (such as the broadcast area, QoS information required for data transmission, etc.) to the SMF (MB-SMF in the figure).
  • MB-SMF is an abbreviation for multicast/broadcast session management function.
  • the core network equipment determines the corresponding policy based on the QoS information, establishes the corresponding QoS flow, and establishes the broadcast session context at the corresponding base station (gNB) and UPF (MB-UPF in the figure).
  • the characteristic of local MBS service is that the service content is area-dependent; only terminal devices within the service area can receive the content data, while terminal devices outside the MBS service area are not allowed to receive location-specific content.
  • the multicast service area (MBS service area) corresponding to a location-dependent MBS service can consist of a set of tracking areas and/or a set of cells, used to indicate a specific range.
  • each MBS session is identified by a unique session identifier, which can be an MBS Session ID or a Temporary Mobile Group Identity (TMGI).
  • An MBS session can be associated with multiple MBS service areas, each identified by an area session ID.
  • an MBS session can be associated with one or more MBS area sessions, or an MBS session ID can be associated with one or more area session IDs.
  • Different area session IDs within the same MBS session correspond to different data contents and may originate from different sources.
  • the area session ID e.g., area session ID
  • the MBS session identifier e.g., TMGI
  • Terminal devices are unaware of the area session ID, only the MBS session identifier.
  • Examples of location-related MBS services include weather forecasts and map updates.
  • the MBS session corresponding to TMGI#A is associated with Area 1 in cell #1 and Area 2 in cell #2.
  • Area Session 1 (Area session #1) is established for Area 1
  • Area Session 2 (Area session #1) is established for Area 2.
  • the base station broadcasts weather data for Area 1 through Area Session 1 and weather data for Area 2 through Area Session 2.
  • an air interface cell is mapped to multiple mapped cells in the core network.
  • a base station can only transmit data corresponding to the area session within a single area of an air interface cell.
  • the base station can only broadcast weather data for area 1 in cell #1 through area session #1. If an area session already exists within an area of an air interface cell, when a content provider (e.g., AF) requests to establish a new area session for that area to broadcast new data, one of the following situations may occur:
  • a content provider e.g., AF
  • Scenario 1 The network side (e.g., core network equipment or base station) determines that a regional session already exists in the region for which a regional session is requested (referred to as an old regional session), and therefore refuses to establish a new regional session for that region, resulting in the inability to fulfill the service requirement of broadcasting the data corresponding to the old regional session and the new data in that region;
  • the network side e.g., core network equipment or base station
  • Scenario 2 The network side (e.g., core network equipment or base station) determines that a regional session already exists in the area where this request for establishing a regional session (referred to as the old regional session). Therefore, it no longer broadcasts the data corresponding to the old regional session in that area, but instead broadcasts the data corresponding to the new regional session. In other words, the new regional session will overwrite the old regional session, making it impossible to meet the service requirement of simultaneously broadcasting the data corresponding to both the old and new regional sessions in that area.
  • the network side e.g., core network equipment or base station
  • this application provides a communication method and related apparatus for implementing the method, which provides a solution for sending different data in the same area for location-related MBS services, thereby enabling the sending of different data in the same area for location-related MBS services.
  • the access network device can establish the first area session.
  • the area corresponding to the first area session does not include the aforementioned overlapping area, thereby reducing or avoiding the impact of the newly established first area session on the original second area session.
  • the access network device can also indicate the overlapping area to the content provider (i.e., MBS server, such as AF), so that the content provider can establish a new session in the overlapping area, thereby transmitting the same data as the data corresponding to the first area session in the overlapping area, and thus enabling the transmission of different data of the same MBS session in the overlapping area.
  • the content provider i.e., MBS server, such as AF
  • the first area session and the second area session are area sessions associated with the first MBS session, or in other words, the first area session and the second area session belong to the first MBS session.
  • Figure 7 illustrates the process using AF as the content provider as an example. It should be understood that this process is described with AF as the content provider for the MBS service; however, the content provider for the MBS service can also be other devices, and this application does not impose any restrictions.
  • the process may include the following steps:
  • Step 701 AF sends a session establishment request message to NEF, which is used to request the establishment of a first area session.
  • the first area session is the user plane channel between the access network equipment and the user plane function network element (such as UPF) in the core network.
  • the first area session is used to transmit the first data of the first MBS session. That is, the user plane network element can send the first data in multicast, broadcast or other methods based on the first area session.
  • the session establishment request message may include an identifier of the first MBS session, indicating that the requested first area session belongs to the first MBS session, or that the first area session is an area session associated with the first MBS.
  • the session establishment request message may not contain an identifier of the first MBS session; in this case, the identifier of the MBS session will be assigned by the MB-SMF network element in step 703.
  • the session establishment request message also includes information about the first region, which indicates the MBS service region corresponding to the requested regional session.
  • the information of the first area may include information about one or more cells, such as identifiers of one or more cells.
  • the information of the first area may include a cell list that includes identifiers of one or more cells.
  • the above cell identifier is the mapped cell ID.
  • the above cell is identified by the air interface cell ID (Uu cell ID), such as CGI or PCI.
  • Uu cell ID such as CGI or PCI.
  • the information of the first region may include information about one or more tracking regions, such as identifiers of one or more tracking regions.
  • the information of the first region may include a list of tracking regions, which includes identifiers of one or more tracking regions.
  • the identifier of the tracking area mentioned above is the mapped tracking area identifier (TAI).
  • TAI mapped tracking area identifier
  • One mapped TAI can correspond to one or more mapped cell IDs.
  • the aforementioned tracking area is identified as a TAI.
  • One TAI can correspond to one or more air interface cell identifiers.
  • the information of the first region may include geographic region information.
  • the geographic region information may be positioning system coordinates, address information (e.g., street name), postal code (zip code), or other information that can be used to describe the geographic region, which is not limited in this application.
  • the information for the first area may include one or more of the following: cell identifier, tracking area identifier, and geographic area information.
  • the session establishment request message may also include first indication information, which indicates that the first regional session to be established is a location-related MBS service session, or in other words, the first indication information indicates that the type of the first regional session is a location-related MBS service session type.
  • AF can call the Nnef_MBSSession_Create request service provided by NEF to trigger the establishment process of the first zone session.
  • Step 702 After receiving the session establishment request message from the AF, the NEF sends a session establishment request message to the MB-SMF. This session establishment request message is used to request the establishment of a first area session.
  • the NEF can select an MB-SMF that matches the location of the first region based on the information of the first region contained in the received session establishment request message, and send a session establishment request message to that MB-SMF.
  • the NEF selects an MB-SMF based on the association between the identifier of the first MBS session stored locally and the MB-SMF, and then sends a session establishment request message to that MB-SMF.
  • the session establishment request message sent by NEF may include the identifier of the first MBS session, which indicates that the first area session to be established belongs to the first MBS session, or that the first area session is an area session associated with the first MBS.
  • the session establishment request message sent by NEF may also include information about a first region, which may be the same as the first region indicated by the information about a first region received by NEF from AF.
  • the NEF can obtain the corresponding cell identifier and/or tracking area identifier based on the geographic region information, and replace the geographic region information in the information of the first region with the obtained cell identifier and/or tracking area identifier, thereby carrying the replaced information of the first region in the session establishment request message sent to the MB-SMF.
  • NEF can call the Nmbsmf_MBSSession_Create Request service provided by MB-SMF to send a session establishment request message to MB-SMF.
  • Step 703 After receiving the session establishment request message from the NEF, the MB-SMF sends a session establishment request message to the AMF. This session establishment request message is used to request the establishment of a first area session.
  • the MB-SMF can select the AMF that matches the location of the first region based on the information of the first region contained in the received session establishment request message, and send the session establishment request message to that AMF.
  • the MB-SMF assigns a first MBS session identifier, for example, when the session establishment request message received from the NEF does not contain an identifier for the first MBS session.
  • the session establishment request message sent by MB-SMF may include the identifier of the first MBS session, which indicates that the first area session to be established belongs to the first MBS session, or that the first area session is an area session associated with the first MBS.
  • the session establishment request message sent by MB-SMF may also include information about the first region, which may be the same as the information about the first region received by MB-SMF from NEF.
  • the session establishment request message sent by the MB-SMF may also include an identifier for the first area session. Since the first area session is used to send first data in the first area, and the first area session belongs to the first MBS session, the identifier of the first area session can be understood as identifying the first data of the first MBS session. The identifier of the first area session can be assigned by the MB-SMF.
  • the MB-SMF can call the Namf_MBSBroadcast_ContextCreate service provided by the AMF to send a session establishment request message to the AMF.
  • Step 704 After receiving the session establishment request message from the MB-SMF, the AMF sends a session establishment request message to the access network device. This session establishment request message is used to request the establishment of a first area session.
  • the session establishment request message sent by AMF may include the identifier of the first MBS session, which indicates that the first area session to be established belongs to the first MBS session, or that the first area session is an area session associated with the first MBS.
  • the session establishment request message sent by the AMF may also include information about a first region, which may be the same as the first region information received by the AMF from the MB-SMF.
  • the session establishment request message sent by the AMF includes information about a third region, which indicates that the third region belongs to or is included in the first region indicated by the first region information received by the AMF from the MB-SMF.
  • the AMF may send messages to multiple access network devices based on the regions supported by the access network devices, with the region in each message appropriately narrowed to fit the regions supported by the access network devices.
  • the session establishment request message sent by AMF may also include the identifier of the first area session.
  • the session setup request message sent by the AMF is a Broadcast Session Setup Request message.
  • Step 705 After receiving the session establishment request message from the AMF, the access network device determines that there is an overlapping area between the first area and the second area based on the information of the first area included in the session establishment request message.
  • the second region is the MBS service region corresponding to the second region session associated with the first MBS session.
  • the second region session is used to send the second data of the first MBS service to terminal devices within the second region.
  • the first data sent through the first region session is different from the second data sent through the second region session.
  • the first region corresponding to the currently requested first region session overlaps with the MBS service region corresponding to the other region session associated with the same MBS session.
  • the access network device Since the second area session is an established area session, the access network device stores the context information of the second area session, which includes information about the second area corresponding to the second area session. The access network device can determine whether the first area and the second area overlap based on the information about the first area contained in the received session establishment request message and the information about the second area contained in the context information of the second area session stored by the access network device.
  • the overlapping area between the first region and the second region can be understood as: the first region includes both the part that overlaps with the second region and the part that does not overlap with the second region.
  • the overlapping area between the first region and the second region can specifically include the following situations:
  • Scenario 1 Parts of the first region and parts of the second region overlap. For example, if the first region includes cell A and cell B, and the second region includes cell A and cell C, then the overlapping area of the first region and the second region is cell A.
  • the first region is larger than the second region, and the second region is completely within the first region. For example, if the first region includes cell A and cell B, and the second region includes cell A, then the overlapping area of the first and second regions is cell A.
  • Step 706 The access network device establishes a first area session.
  • the area corresponding to the first area session is the area in the first area other than the area that overlaps with the second area.
  • the access network device can establish a first region session and save the context information of the first region session.
  • the context information of the first region session may include information about the MBS service area corresponding to the first region session.
  • This MBS service area is the area in the first region other than the overlapping areas mentioned above.
  • the area corresponding to the first region session is the area in the first region other than the area that overlaps with the second region.
  • the access network device can receive the first data of the first MBS service from the core network and, based on the MBS service area information contained in the context information of the first region session, send the first data to terminal devices in the area other than the overlapping areas in the first region.
  • Access network equipment can still receive the second data of the first MBS service from the core network through the second area session, and send the second data to the terminal equipment in the second area (including overlapping areas).
  • the overlapping region can be excluded from the MBS service region corresponding to the first region session when establishing the first region session. This can prevent the newly established first region session from affecting the already established second region session, so as to ensure that the terminal devices in the second region (including the overlapping region) can still receive the second data.
  • some embodiments of this application may also establish new sessions for the overlapping regions to transmit first data, so as to ensure that terminal devices in the overlapping regions can receive both second data and first data, thereby meeting service requirements.
  • the process shown in Figure 7 may also include the following steps:
  • Step 707 The access network device sends a first message (e.g., a session establishment response message) to the AMF, indicating that no area session has been established for the aforementioned overlapping area.
  • a first message e.g., a session establishment response message
  • the first information may include information about the overlapping area and first indication information.
  • the first indication information may be used to indicate that the overlapping area is not included in the area corresponding to the first area session, or in other words, the first indication information may be used to indicate that the area corresponding to the requested first area session overlaps with the area corresponding to another area session.
  • the first information may be included in the session establishment response message, or the first information may be understood as the session establishment response message. This process will be described using the sending of a session establishment response message as an example.
  • the information of the overlapping area may include the identifiers of one or more cells, where the first area and the second area overlap.
  • the information includes the identifier of cell A.
  • the information may include the identifiers of one or more tracking areas, where the first area and the second area overlap.
  • the information used to indicate the overlapping area of the first and second regions may include one or more of the following: cell identifier, tracking area identifier, etc.
  • the access network device cannot send another data of the first MBS service (i.e., the first data here) in the aforementioned overlapping area.
  • the overlapping area can also be called the area not accepted by the requested area session (i.e., the first area session), or simply the unaccepted area.
  • the area of the first area other than the overlapping area can be called the area accepted by the requested area session (i.e., the first area session), or simply the accepted area.
  • the first indication information can indicate the areas in the first area that are accepted and/or not accepted by the first area session.
  • the reason why the overlapping area is not included in the area corresponding to the first area session is that the area corresponding to the first area session to be established overlaps with the area corresponding to another area session.
  • the reason why the overlapping area is not included in the area corresponding to the first area session can also be indicated by the second indication information.
  • the first information may include the second indication information in addition to the first indication information.
  • the session establishment response message sent by the access network device may also include the second indication information, which is used to indicate the reason why the overlapping area is not accepted by the first area session, or in other words, the second indication information is used to indicate the reason why the overlapping area is not included in the area corresponding to the first area session.
  • the reason may be: for the same MBS session (i.e., the first MBS session mentioned above), the area corresponding to the first area session to be established overlaps with the area corresponding to the already established area session.
  • the reason may be: there is an area in the area corresponding to the first area session to be established that overlaps with the MBS service area corresponding to the already established area session.
  • the second indication information can also be called reason information or reason value.
  • the session establishment response message sent by the access network device also includes an identifier of the first area session, indicating that the session establishment response message is a session establishment response message for the first area session.
  • the session establishment response message sent by the access network device also includes an identifier of the first MBS session, indicating that the first area session to be established belongs to the first MBS session, or that the first area session is an area session associated with the first MBS.
  • the session establishment response message sent by the access network device can be a Namf_MBSBroadcast_ContextCreate Response message.
  • Step 708 After receiving the session establishment response message from the access network device, the AMF sends a session establishment response message to the MB-SMF.
  • the session establishment response message sent by the AMF includes the aforementioned first information.
  • the session establishment response message sent by the AMF also includes an identifier of the first area session, indicating that the session establishment response message is for the first area session.
  • the session establishment response message sent by the AMF also includes the identifier of the first MBS session, to indicate that the first area session to be established belongs to the first MBS session, or that the first area session is an area session associated with the first MBS.
  • the session establishment response message sent by AMF can be a Namf_MBSBroadcast_ContextCreate Response message.
  • Step 709 After receiving the session establishment response message from the AMF, the MB-SMF sends a session establishment response message to the NEF.
  • the session establishment response message sent by MB-SMF includes the aforementioned first information.
  • the session establishment response message sent by MB-SMF also includes an identifier of the first area session, indicating that the session establishment response message is for the first area session.
  • the session establishment response message sent by MB-SMF also includes the identifier of the first MBS session, to indicate that the first area session to be established belongs to the first MBS session, or that the first area session is an area session associated with the first MBS.
  • the session establishment response message sent by MB-SMF can be the Nmbsmf_MBSSession_StatusNotify message.
  • Step 710 After receiving the session establishment response message from the MB-SMF, the NEF sends a session establishment response message to the AF.
  • the session establishment response message sent by NEF includes information about the overlapping area and first indication information. Optionally, it may also include second indication information.
  • the information of the overlapping region in the session establishment response message sent by NEF is the same as the information of the overlapping region contained in the session establishment response message received by NEF.
  • NEF obtains the corresponding geographic location information based on the cell identifier and/or tracking area identifier of the overlapping area received from MB-SMF, and sends the geographic location information as the information of the overlapping area to AF in the session establishment response message.
  • the session establishment response message sent by NEF also includes an identifier of the first area session, indicating that the session establishment response message is for the first area session.
  • the session establishment response message sent by NEF also includes the identifier of the first MBS session, to indicate that the first area session to be established belongs to the first MBS session, or that the first area session is an area session associated with the first MBS.
  • the session establishment response message sent by NEF can be an Nnef_MBSSession_StatusNotify message.
  • Step 711 After receiving the session establishment response message from the NEF, the AF sends a session establishment request message for the overlapping area based on the information in the message, requesting the establishment of a new session. This request message initiates the process of establishing a new session, through which the first data can be transmitted.
  • the AF can initiate the establishment process of a second MBS session.
  • This second MBS session is a regular MBS session, or in other words, a session for non-location-related MBS services.
  • the AF sends a session establishment request message, which includes information about the overlapping area.
  • This message requests the establishment of a second MBS session, which is used to send the first data to terminal devices within the overlapping area.
  • the identifier of the second MBS session differs from that of the first MBS session, and the MBS service area corresponding to the second MBS session includes the overlapping area.
  • the AF can initiate the establishment process of a regional session associated with a second MBS session, which is a session for location-related MBS services.
  • the second MBS session can be associated only with the first region, or in other words, the second MBS session can be associated with only one regional session, the MBS service area corresponding to which is the aforementioned overlapping region.
  • the AF sends a session establishment request message, which includes information about the aforementioned overlapping region. This session establishment request message is used to request the establishment of a regional session (to distinguish it from the aforementioned first and second regional sessions, it can be referred to here as a third regional session).
  • This third regional session is the only regional session associated with the second MBS session, and the MBS service area corresponding to this regional session is the aforementioned overlapping region.
  • This regional session is used to send the aforementioned first data to terminal devices within the overlapping region.
  • the identifier of the second MBS session is different from the identifier of the first MBS session.
  • the AF can also send service announcement messages (e.g., service announcements) to terminal devices within the MBS service area of the second MBS session to notify the terminal devices at the application layer to receive data (i.e., first data) of the second MBS session within the MBS service area of the second MBS session.
  • service announcement messages e.g., service announcements
  • the service notification message may include the identifier of the second MBS session and information about the MBS service area (the MBS service area is the aforementioned overlapping area), thereby enabling the terminal device to receive data from the second MBS session.
  • the service notification message may also include the identifier of the first MBS session and information about the MBS service area (which includes the aforementioned overlapping area), thereby enabling the terminal device to receive data from the first MBS session.
  • the service may also include service identification information in the message, such as the IP address information corresponding to the service, such as the IP 5-tuple, or the application identifier (APP ID) corresponding to the service.
  • service identification information such as the IP address information corresponding to the service, such as the IP 5-tuple, or the application identifier (APP ID) corresponding to the service.
  • the terminal device located in the overlapping area can receive data from the first MBS session (i.e., the second data) and data from the second MBS session (i.e., the first data) according to the service pass message.
  • the AF can initiate a session establishment process for each terminal device in the overlapping area of the first area and the second area, thereby establishing a unicast session with each of these terminal devices and sending the data corresponding to the first area session to the terminal devices in the overlapping area via unicast.
  • a session establishment request message can be replaced by "first request message”
  • a session establishment response message can be replaced by "first response message”.
  • the method of sending the first information in the process shown in Figure 7 above is only one possible example, and this application does not limit it.
  • the first information may be included in the session establishment response message, and the session establishment response message may also be regarded as the first information.
  • the access network device establishes a first region session, and the region corresponding to the first region session is the first region. Based on the first region session, the access network device obtains the first data of the first MBS service from the core network and sends the first data to the terminal devices in the first region via broadcast or multicast. Based on the second region session, the access network device obtains the second data of the first MBS service from the core network and sends the second data to the terminal devices in the second region via broadcast or multicast.
  • the first area session and the second area session are two different area sessions associated with the first MBS session.
  • the second area session is an established area session, and its corresponding MBS service area is the second area 802 shown in the figure. If a second area session has already been established for the second area 802 to transmit the second data of the first MBS session, and a request is made to establish a first area session for the first area 801 to transmit the first data of the first MBS session, then the area corresponding to the first area session does not include the overlapping area 803 of the first area 801 and the second area 802. A second MBS session can be established for the overlapping area 803 to transmit the first data.
  • the terminal device within the overlapping area 803 can receive both the first and second data, thereby meeting service requirements.
  • the access network device can report area session establishment failure information and indicate the reason for failure so that the content provider (i.e., MBS server, such as AF, etc.) can perform corresponding processing according to the reason for failure, such as establishing a new session for the overlapping area, so that the same data as the data corresponding to the first area session can be transmitted in the overlapping area, thereby enabling the transmission of different data of the same MBS session in the overlapping area.
  • MBS server such as AF, etc.
  • the first MBS session can be associated with multiple regional sessions.
  • the first regional session and the second regional session are regional sessions associated with the first MBS, or in other words, the first regional session and the second regional session belong to the first MBS session.
  • the service area corresponding to the first regional session and the service area corresponding to the second regional session are within the service area corresponding to the first MBS session.
  • Step 901 AF sends a session establishment request message to NEF, which is used to request the establishment of a first area session.
  • Step 902 After receiving the session establishment request message from the AF, the NEF sends a session establishment request message to the MB-SMF. This session establishment request message is used to request the establishment of a first area session.
  • Step 903 After receiving the session establishment request message from the NEF, the MB-SMF sends a session establishment request message to the AMF. This session establishment request message is used to request the establishment of a first area session.
  • Step 904 After receiving the session establishment request message from the MB-SMF, the AMF sends a session establishment request message to the access network device. This session establishment request message is used to request the establishment of a first area session.
  • Step 905 After receiving the session establishment request message from the AMF, the access network device determines that the first area and the second area overlap based on the information of the first area included in the session establishment request message.
  • the second region is the service region corresponding to the second region session associated with the first MBS session.
  • the second region session is used to send the second data of the first MBS service to terminal devices within the second region.
  • the first data sent through the first region session is different from the second data sent through the second region session.
  • the first region corresponding to the currently requested first region session overlaps with the second region corresponding to the already established second region session.
  • the access network device Since the second area session is an established area session, the access network device stores the context information of the second area session, which includes information about the second area corresponding to the second area session. The access network device can determine whether the first area and the second area overlap based on the information about the first area contained in the received session establishment request message and the information about the second area contained in the context information of the second area session stored by the access network device.
  • the first region and the second region overlap, which can be understood as: the first region and the second region partially overlap, or the first region and the second region coincide.
  • first region and the second region overlap can specifically include the following situations:
  • Scenario 1 Parts of the first region and parts of the second region overlap. For example, if the first region includes cell A and cell B, and the second region includes cell A and cell C, then the overlapping area of the first region and the second region is cell A.
  • the first region is larger than the second region, and the second region is completely within the first region. For example, if the first region includes cell A and cell B, and the second region includes cell A, then the overlapping area of the first and second regions is cell A.
  • the first region is smaller than the second region, and the first region completely falls within the second region. For example, if the first region includes cell A, and the second region includes cell A and cell B, then the overlapping area of the first and second regions is cell A.
  • Scenario 4 The first and second regions completely overlap. For example, if the first region includes cell A and cell B, and the second region also includes cell A and cell B, then the overlapping area of the first and second regions is cell A and cell B.
  • Step 906 The access network device sends a session establishment response message to the AMF, which indicates that the session establishment in the first area has failed.
  • the session establishment response message includes the reason for the failure of the first area session establishment and/or handling suggestions.
  • the reason for the failure to establish the first area session can be indicated by indication information (or reason value).
  • the above processing suggestions can be indicated by corresponding instruction information.
  • the indication information of the reason for the session establishment failure and the indication information of the processing suggestion can be jointly encoded. That is, the reason for the session establishment failure in the first area and the processing suggestion can be indicated by a single indication information.
  • the failure reason indicated by the failure reason information is: unable to establish a session for location-related MBS services. Because the first and second areas overlap, the access network device refuses to establish a first area session for the first area.
  • the failure reason indicated by the failure reason information is: the first area corresponding to the first area session to be established includes an NTN type area, such as an NTN cell and/or an NTN tracking area.
  • a mapping relationship between cell identifiers and cell types can be pre-set.
  • this mapping relationship information can indicate whether a cell is an NTN type cell for a single cell.
  • the access network device can query this mapping relationship information based on the cell identifier contained in the first area information in the received session establishment request message, thereby determining whether the first area corresponding to the first area session includes an NTN cell.
  • a mapping relationship between tracking area identifiers and tracking area types can be pre-set, allowing the access network device to query this mapping relationship information based on the tracking area identifier contained in the first area information in the received session establishment request message, thereby determining whether the first area corresponding to the first area session includes an NTN tracking area.
  • a mapping relationship between the mapped cell ID and the air interface cell ID can be pre-set. This allows the access network device to query this mapping relationship based on the mapped cell ID contained in the first area information of the received session establishment request message, thereby determining whether the first area corresponding to the first area session includes an NTN cell.
  • a mapping relationship between the mapped tracking area identifier (Mapped TAI) and the NTN tracking area identifier can be pre-set. This allows the access network device to query this mapping relationship based on the mapped TAI contained in the first area information of the received session establishment request message, thereby determining whether the first area corresponding to the first area session includes an NTN tracking area.
  • the above-mentioned correspondence information can be configured on the access network device; or the above-mentioned correspondence information can be configured on other devices that the access network device can access.
  • the access network device can obtain the above-mentioned correspondence information from the other devices, or the access network device can request the other devices to determine, based on the correspondence information, that the first area corresponding to the first area session currently requested to be established includes NTN cells.
  • the failure reason indicated by the failure reason information is: for the first MBS session, the first region corresponding to the first region session to be established overlaps with the region corresponding to another region session.
  • the processing suggestion information indicates the following processing method: for overlapping areas, it is suggested to establish a session of non-location-related MBS service, wherein the MBS service area of the session of non-location-related MBS service is the first area.
  • the processing suggestion indicates the following processing method: establishing a location-related MBS service session, wherein the MBS service area of the location-related MBS service session is the first area.
  • the location-related MBS service session is only associated with the first area, or in other words, the location-related MBS session is only associated with one area session, and the MBS service area corresponding to that area session is the first area.
  • the processing suggestion indicated by the processing suggestion information is: to establish unicast sessions for each terminal device in the first area, wherein the unicast sessions are used to transmit the first data. That is, to initiate a session establishment process for each terminal device in the first area, thereby sending the first data to the terminal device via unicast.
  • the session establishment response message sent by the access network device includes information about a first region.
  • the information about the first region may include the identifier of the NTN cell and/or the identifier of the NTN tracking area.
  • the access network device can obtain the identifier of the corresponding NTN cell based on the cell identifier of the mapped cell in the first region information of the session establishment request message, and carry the identifier of the NTN cell in the session establishment response message.
  • the access network device can obtain the identifier of the corresponding NTN tracking area based on the identifier of the mapped tracking area in the first region information of the session establishment request message, and carry the identifier of the NTN tracking area in the session establishment response message.
  • the session establishment response message may also include the reason for the session establishment failure in the first region and/or handling suggestions.
  • the session establishment response message sent by the access network device also includes an identifier of the first area session, indicating that the session establishment response message is a session establishment response message for the first area session.
  • the session establishment response message sent by the access network device also includes an identifier of the first MBS session, indicating that the first area session to be established belongs to the first MBS session, or that the first area session is an area session associated with the first MBS.
  • the session establishment response message sent by the access network device can be a Namf_MBSBroadcast_ContextCreate Response message.
  • Step 907 After receiving the session establishment response message from the access network device, the AMF sends a session establishment response message to the MB-SMF.
  • the session establishment response message may include the reason for the failure of the first area session establishment and/or handling suggestions.
  • the session establishment response message sent by the AMF also includes information about the first region mentioned above.
  • the information about the first region may include the identifier of the NTN cell and/or the identifier of the NTN tracking area.
  • the session establishment response message sent by the AMF also includes an identifier of the first area session, indicating that the session establishment response message is for the first area session.
  • the session establishment response message sent by the AMF also includes the identifier of the first MBS session, to indicate that the first area session to be established belongs to the first MBS session, or that the first area session is an area session associated with the first MBS.
  • the session establishment response message sent by AMF can be a Namf_MBSBroadcast_ContextCreate Response message.
  • Step 908 After receiving the session establishment response message from the AMF, the MB-SMF sends a session establishment response message to the NEF.
  • the session establishment response message may include the reason for the failure of the first area session establishment and/or handling suggestions.
  • the session establishment response message sent by the MB-SMF also includes information about the first region mentioned above.
  • the information about the first region may include the identifier of the NTN cell and/or the identifier of the NTN tracking area.
  • the session establishment response message sent by MB-SMF also includes an identifier of the first area session, indicating that the session establishment response message is for the first area session.
  • the session establishment response message sent by MB-SMF also includes the identifier of the first MBS session, to indicate that the first area session to be established belongs to the first MBS session, or that the first area session is an area session associated with the first MBS.
  • the session establishment response message sent by MB-SMF can be the Nmbsmf_MBSSession_StatusNotify message.
  • Step 909 After receiving the session establishment response message from the MB-SMF, the NEF sends a session establishment response message to the AF.
  • the session establishment response message may include the reason for the failure of the first area session establishment and/or handling suggestions.
  • the session establishment response message sent by NEF also includes information about the first region mentioned above.
  • the information about the first region may include the identifier of the NTN cell and/or the identifier of the NTN tracking area.
  • NEF obtains the corresponding geographic location information based on the identifier of the NTN cell and/or the identifier of the NTN tracking area, and sends the geographic location information as the information of the first area to AF in the session establishment response message.
  • the session establishment response message sent by NEF also includes an identifier of the first area session, indicating that the session establishment response message is for the first area session.
  • the session establishment response message sent by NEF also includes the identifier of the first MBS session, to indicate that the first area session to be established belongs to the first MBS session, or that the first area session is an area session associated with the first MBS.
  • the session establishment response message sent by NEF can be an Nnef_MBSSession_StatusNotify message.
  • the access network device can refuse to establish a session in the first area. This can avoid affecting the established session in the second area, so as to ensure that the terminal device in the second area (including the overlapping area) can still receive the second data.
  • the access network device may feed back the reason and/or handling suggestions for the failure of the first area session establishment to the AF or MBS server, so that the AF or MBS server can perform corresponding processing.
  • a new session can also be established for the first region to transmit the first data, so as to ensure that the terminal device in the overlapping region can receive both the second data and the first data, thereby meeting the service requirements.
  • the process shown in Figure 9 may also include the following steps:
  • Step 910 After receiving the session establishment response message from the NEF, the AF initiates a new session establishment process for the first region based on the information included in the session establishment response message (e.g., the reason for the failure of the first region session establishment and/or the processing suggestion, and/or the information of the first region mentioned above), and transmits the first data through the new session.
  • the information included in the session establishment response message e.g., the reason for the failure of the first region session establishment and/or the processing suggestion, and/or the information of the first region mentioned above
  • the AF can initiate the establishment process of a second MBS session.
  • This second MBS session is a regular MBS session, or in other words, a session for non-location-dependent MBS services.
  • the AF sends a session establishment request message, which includes information about the first area.
  • This message requests the establishment of a second MBS session, which is used to send the first data to terminal devices within the first area.
  • the identifier of the second MBS session differs from that of the first MBS session, and the MBS service area corresponding to the second MBS session includes the first area.
  • the access network device receives the session establishment request message requesting the establishment of the second MBS session, it can establish the second MBS session and send the first data within the MBS service area (i.e., the first area) of the second MBS session.
  • the AF can initiate the establishment process of a regional session associated with a second MBS session.
  • This second MBS session is a location-related MBS service session, and the MBS service area corresponding to this regional session is the first area.
  • the second MBS session is only associated with the first area, or in other words, the second MBS session is only associated with one regional session.
  • the AF sends a session establishment request message, which includes information about the first area.
  • This session establishment request message is used to request the establishment of a regional session (to distinguish it from the first and second regional sessions, it can be referred to as a third regional session).
  • This regional session is the only regional session associated with the second MBS session, and the MBS service area corresponding to this regional session is the first area.
  • This regional session is used to send the first data to terminal devices within the first area.
  • the identifier of the second MBS session is different from the identifier of the first MBS session.
  • the AF can also send service announcement messages (e.g., service announcements) to terminal devices within the MBS service area of the second MBS session.
  • service announcement messages e.g., service announcements
  • This is to notify the terminal devices at the application layer to receive data (i.e., first data) of the second MBS session within the MBS service area of the second MBS session, and to receive data of the first MBS session within the MBS service area of the first MBS session.
  • the service announcement message may include the identifier of the second MBS session and information about the MBS service area, as well as the identifier of the first MBS session and information about the MBS service area, thereby enabling the terminal devices to receive data from both the second and first MBS sessions.
  • the implementation methods for initiating a new session establishment process for the first region based on the information included in the session establishment response message may include the following:
  • the session establishment response message includes a first reason value indicating the reason for the failure of session establishment in the first area.
  • the reason for failure indicated by the first reason value is: unable to establish a session for location-related MBS services.
  • AF can attempt to establish a non-location-dependent MBS service session for the first area.
  • the specific implementation method can be found in the previous description.
  • the AF before establishing a non-location-related MBS service session for the first region, the AF can analyze the failure reasons and determine the corresponding processing method based on the failure reasons. For example, the AF can obtain the MBS service areas corresponding to other region sessions associated with the first MBS session and determine whether there is any overlap between the first region and the MBS service areas corresponding to the other region sessions. If there is an overlap, it can be determined that a non-location-related MBS service session should be established for the first region.
  • the session establishment response message includes a second reason value to indicate the reason for the failure of the first area session establishment.
  • the reason for failure indicated by the second reason value is: the first area corresponding to the first area session to be established includes an NTN type area.
  • the AF can attempt to establish a session for a non-location-related MBS service.
  • the AF can also establish a session for a location-related MBS service.
  • this location-related MBS service session is only associated with the first region, or in other words, this location-related MBS session is only associated with one region session.
  • the MBS service region corresponding to this region session is the first region.
  • the AF can determine that the failure of the first region session may be due to the overlap between the first region and other region sessions associated with the same MBS session in the NTN scenario. Therefore, it can be determined that a non-location-related MBS service session should be established for the first region, or a location-related MBS service session should be established.
  • Method 2 provides more information about the failure reason indicated by the reason value, or in other words, the failure reason given is more specific. This can reduce the processing logic of AF, provide the processing flexibility of AF, and help AF to adopt appropriate methods for processing.
  • the session establishment response message includes a second reason value indicating the reason for the failure of session establishment in the first area, as well as information about the first area.
  • the AF can attempt to establish a session for a non-location-related MBS service.
  • the AF can establish a session for a location-related MBS service, where the location-related MBS service session is only associated with the first region, or in other words, the location-related MBS session is only associated with one region session, and the MBS service region corresponding to this region session is the first region.
  • AF can determine that the failure of the first region session may be due to the overlap between the first region and the MBS service regions corresponding to other region sessions associated with the same MBS session in the NTN scenario. Therefore, it can be determined that a non-location-related MBS service session or a location-related MBS service session should be established for the first region.
  • the session establishment response message includes a third reason value indicating the reason for the failure of the first region session establishment.
  • the reason for failure indicated by the third reason value is: the first region corresponding to the first region session currently requested to be established overlaps with the MBS service region corresponding to another region session associated with the same MBS session.
  • the AF can attempt to establish a session for a non-location-related MBS service.
  • the AF can establish a session for a location-related MBS service, where the location-related MBS service session is only associated with the first region, or in other words, the location-related MBS session is only associated with one region session, and the MBS service region corresponding to this region session is the first region.
  • AF can determine whether to establish a non-location-related MBS service session or a location-related MBS service session for the first region without performing failure reason analysis.
  • Method 4 provides more information about the failure cause indicated by the cause value, or in other words, the failure cause given is more specific. This reduces the processing logic of AF, provides processing flexibility for AF, and helps AF to adopt appropriate methods for processing.
  • the session establishment response message includes instructions on processing recommendations, which suggest establishing a regular MBS session, i.e., establishing a session for non-location-related MBS services.
  • AF can establish sessions for non-location-related MBS services.
  • the AF can perform corresponding processing based on these suggestions, thereby reducing the processing logic of the AF.
  • the session establishment response message includes information about the first region.
  • the AF can attempt to establish a session for a non-location-related MBS service.
  • the AF can establish a session for a location-related MBS service, where the location-related MBS service session is only associated with the first region, or in other words, the location-related MBS session is only associated with one region session, and the MBS service region corresponding to this region session is the first region.
  • the AF can determine that the failure of the first region session may be due to the overlap between the first region and the MBS service regions corresponding to other regions associated with the same MBS session in the NTN scenario. Therefore, it can be determined whether to establish a non-location-related MBS service session for the first region or to establish a location-related MBS service session.
  • method 6 contains more information in the session establishment response message, which reduces the processing logic of AF, provides processing flexibility for AF, and helps AF to adopt appropriate methods for processing.
  • the access network device can still receive the second data of the first MBS service from the core network through the second area session, and send the second data to the terminal device in the second area (including the overlapping area).
  • the access network device establishes a first region session, and the region corresponding to the first region session is the first region. Based on the first region session, the access network device obtains the first data of the first MBS service from the core network and sends the first data to the terminal devices in the first region via broadcast or multicast. Based on the second region session, the access network device obtains the second data of the first MBS service from the core network and sends the second data to the terminal devices in the second region via broadcast or multicast.
  • a new session can be established for that area.
  • the MB-SMF sends a session establishment request message to the AMF, and the AMF sends a session establishment request message to the access network device to transmit the requested first data.
  • both the second data corresponding to the original area session and the first data corresponding to the new session can be transmitted, thereby enabling the transmission of different data in the same area.
  • the first area session and the second area session are two different area sessions associated with the first MBS session.
  • the second area session is an established area session, and its corresponding MBS service area is the second area 1002 shown in the figure. If an AF requests the establishment of a first area session for the first MBS session in the first area 1001 to transmit the first data of the first MBS session, the access network device will refuse to establish the first area session because the first area 1001 and the second area 1002 overlap.
  • the AF can initiate the establishment process of the second MBS session for the first area 1001, thereby establishing the second MBS session, and the area corresponding to the second MBS session is the first area 1001.
  • terminal devices in the overlapping area 1003 can receive the second data based on the second area session and can also receive the first data based on the second MBS session, thus meeting service requirements.
  • the NEF can report the region session establishment failure information and indicate the reason for the failure so that the content provider (i.e., the MBS server, such as AF, etc.) can take corresponding actions based on the reason for the failure, such as establishing a new session for the overlapping region, so that the same data as the data corresponding to the first region session can be transmitted in the overlapping region, thereby enabling the transmission of different data of the same MBS session in the overlapping region.
  • the content provider i.e., the MBS server, such as AF, etc.
  • the first MBS session can be associated with multiple regional sessions.
  • the first regional session and the second regional session are regional sessions associated with the first MBS, or in other words, the first regional session and the second regional session belong to the first MBS session.
  • the service area corresponding to the first regional session and the service area corresponding to the second regional session are within the service area corresponding to the first MBS session.
  • Step 1101 AF sends a session establishment request message to NEF, which is used to request the establishment of a first area session.
  • Step 1102 After receiving the session establishment request message from the AF, the NEF determines that the first region includes an area of type NTN, for example, the first region includes NTN cells and/or NTN tracking areas.
  • a first correspondence information can be pre-set, which includes a correspondence between cell identifiers and cell types.
  • this correspondence information can indicate whether a cell is an NTN type cell for a single cell.
  • the NEF can query this correspondence information based on the cell identifier contained in the first area information in the received session establishment request message, thereby determining whether the first area corresponding to the first area session includes NTN cells.
  • the first correspondence information can also include the correspondence information between the tracking area identifier and the tracking area type. That is, the correspondence information between the tracking area identifier and the tracking area type can be preset, so that NEF can query the correspondence information based on the tracking area identifier contained in the first area information in the received session establishment request message, thereby determining whether the first area corresponding to the first area session includes an NTN tracking area.
  • a second correspondence information can be pre-set.
  • the second correspondence information includes the correspondence information between the mapped cell ID and the air interface cell ID.
  • NEF can query the correspondence information based on the mapped cell ID contained in the first area information in the received session establishment request message, thereby determining whether the first area corresponding to the first area session includes an NTN cell.
  • the second mapping information may also include the mapping information between the mapped tracking area identifier (TAI) and the NTN tracking area identifier. That is, the mapping information between the mapped tracking area identifier (TAI) and the NTN tracking area identifier can be pre-set. This allows NEF to query this mapping information based on the mapped TAI contained in the first area information of the received session establishment request message, thereby determining whether the first area corresponding to the first area session includes an NTN tracking area.
  • TAI mapped tracking area identifier
  • the aforementioned correspondence information can be configured on NEF.
  • the above correspondence information can be configured in the NRF or UDM.
  • the NEF can query the NRF to obtain the correspondence or to obtain information on whether the first region includes NTN cells.
  • Step 1103 NEF sends a session establishment response message to AF, which indicates that the session establishment in the first area has failed.
  • the session establishment response message includes the reason for the failure of the first area session establishment and/or a handling suggestion.
  • a description of the failure reason and handling suggestion can be found in step 906 of Figure 9.
  • the session establishment response message sent by the NEF includes information about a first region.
  • the information about the first region may include the identifier of the NTN cell and/or the identifier of the NTN tracking area.
  • the NEF can obtain the identifier of the corresponding NTN cell based on the cell identifier of the mapped cell in the first region information of the session establishment request message, and carry the identifier of the NTN cell in the session establishment response message.
  • the NEF can obtain the identifier of the corresponding NTN tracking area based on the identifier of the mapped tracking area in the first region information of the session establishment request message, and carry the identifier of the NTN tracking area in the session establishment response message.
  • the session establishment response message may also include the reason for the session establishment failure in the first region and/or handling suggestions.
  • the session establishment response message sent by NEF also includes an identifier of the first area session, indicating that the session establishment response message is for the first area session.
  • the session establishment response message sent by NEF also includes the identifier of the first MBS session, to indicate that the first area session to be established belongs to the first MBS session, or that the first area session is an area session associated with the first MBS.
  • the session establishment response message sent by NEF can be either an Nnef_MBSSession_Create response message or an Nnef_MBSSession_StatusNotify message.
  • Step 1104 After receiving the session establishment response message from the NEF, the AF initiates a new session establishment process for the first region based on the information included in the session establishment response message (e.g., the reason for the failure of the first region session establishment and/or the processing suggestion, and/or the information of the first region mentioned above), and transmits the first data through the new session.
  • the information included in the session establishment response message e.g., the reason for the failure of the first region session establishment and/or the processing suggestion, and/or the information of the first region mentioned above
  • step 910 in Figure 9.
  • the NEF determines that the first area does not include an NTN type area, it can continue with the subsequent session establishment process, such as sending a session establishment request message to the MB-SMF to enable the access network device to establish a first area session.
  • the area corresponding to the first area session is the first area.
  • the access network device obtains the first data of the first MBS service from the core network and sends the first data to the terminal devices in the first area via broadcast or multicast.
  • the access network device obtains the second data of the first MBS service from the core network and sends the second data to the terminal devices in the second area via broadcast or multicast.
  • the first area corresponding to the first area session currently requested to be established includes an NTN type area
  • the MBS service area corresponding to the requested area session may cause the establishment of the current requested area session to fail. Therefore, AF can establish a new session for this area to transmit the requested first data.
  • the overlapping area it can transmit both the second data corresponding to the original area session and the first data corresponding to the new session, thereby enabling the transmission of different data in the same area.
  • the method shown in Figure 11 can reduce signaling interaction, enabling AF to respond to session establishment failure information and perform corresponding processing more quickly, thereby reducing the processing latency of MBS services.
  • the NEF can report the region session establishment failure information and indicate the reason for the failure so that the content provider (i.e., the MBS server, such as AF, etc.) can take corresponding actions based on the reason for the failure, such as establishing a new session for the overlapping region, so that the same data as the data corresponding to the first region session can be transmitted in the overlapping region, thereby enabling the transmission of different data of the same MBS session in the overlapping region.
  • the content provider i.e., the MBS server, such as AF, etc.
  • the first MBS session can be associated with multiple regional sessions.
  • the first regional session and the second regional session are regional sessions associated with the first MBS, or in other words, the first regional session and the second regional session belong to the first MBS session.
  • the service area corresponding to the first regional session and the service area corresponding to the second regional session are within the service area corresponding to the first MBS session.
  • NEF obtains regional session establishment failure information by interacting with other network elements, and optionally, it can also obtain the cause of failure and/or handling suggestions.
  • the process may include the following steps:
  • Step 1201 AF sends a session establishment request message to NEF, which is used to request the establishment of a first area session.
  • Step 1202 After receiving the session establishment request message from the AF, the NEF sends a first message to the NRF, which requests feedback on whether to allow the establishment of a first area session for the first area.
  • the first message may include information about the first region.
  • NEF can send the first message to NRF by calling NRF's Nnrf_NFDiscovery_Request Request service.
  • Step 1203 NRF sends a second message to NEF, indicating that a first-area session cannot be established for the first area.
  • the NRF determines that the first region includes an NTN-type region (e.g., an NTN cell and/or an NTN tracking area), then it determines that a first region session cannot be established for the first region.
  • an NTN-type region e.g., an NTN cell and/or an NTN tracking area
  • the NRF determines that the first region corresponding to the first region session currently requested to be established overlaps with the MBS service region corresponding to another region session associated with the same MBS session, then it is determined that the first region session cannot be established for the first region.
  • the NRF can determine whether the first region contains an NTN type region in the following ways:
  • the first method involves setting a mapping between cell identifiers and cell types on the NRF.
  • this mapping information can indicate whether a cell is an NTN type cell for a single cell.
  • the NRF can then query this mapping information based on the cell identifiers contained in the received information for the first area, thereby determining whether the first area includes NTN cells.
  • mapping information between tracking area identifiers and tracking area types can be set on the NRF.
  • the NRF can query the mapping information based on the tracking area identifier contained in the information of the first region, thereby determining whether the first region includes an NTN tracking area.
  • the above correspondence information is independent of the configuration information of MB-SMF and AMF.
  • the second method is to set the mapping relationship between the mapped cell ID and the air interface cell ID on the NRF.
  • the NRF can query the mapping relationship information based on the mapped cell ID contained in the information of the first area, thereby determining whether the first area includes an NTN cell.
  • mapping relationship between the mapped tracking area identifier (TAI) and the NTN tracking area identifier can be set on the NRF.
  • the NRF can query the mapping relationship information based on the mapped TAI contained in the information of the first region, thereby determining whether the first region includes the NTN tracking area.
  • the above correspondence information is independent of the configuration information of MB-SMF and AMF.
  • the third method The mapping relationship between the identifiers of the mapped cells and the identifiers of the NTN cells can be set in the MB-SMF configuration information (or NF profile) stored on the NRF.
  • the NRF can query this mapping relationship information based on the identifiers of the mapped cells contained in the information of the first area, thereby determining whether the first area includes an NTN cell.
  • mapping relationship between the mapped tracking area identifier (mapped cell ID) and the air interface cell identifier (Uu cell ID) can be set in the MB-SMF configuration information (or NF profile) stored on the NRF.
  • the NRF can query the mapping relationship information based on the mapped cell ID contained in the information of the first area, thereby determining whether the first area includes an NTN cell.
  • the mapping relationship between the identifiers of mapped cells and NTN cells can be set in the AMF configuration information (or NF profile) stored on the NRF.
  • the NRF can query this mapping relationship information based on the identifiers of mapped cells contained in the information of the first area, thereby determining whether the first area includes NTN cells.
  • mapping relationship between the mapped tracking area identifier (mapped cell ID) and the air interface cell identifier (Uu cell ID) can be set in the AMF configuration information (or NF profile) stored on the NRF.
  • the NRF can query the mapping relationship information based on the mapped cell ID contained in the information of the first area, thereby determining whether the first area includes an NTN cell.
  • the second message may also include the reason why a first-area session could not be established for the first area.
  • the NRF can determine the reason why a first-area session could not be established for the first area and carry the indication information (or reason value) of the reason in the second message.
  • the failure reason indicated by the failure reason information is: Unable to establish a session for location-related MBS services. Because the first region includes an NTN type region, or because the MBS service regions corresponding to the first region and other region sessions associated with the same MBS session overlap, the NRF determines that a first region session cannot be established for the first region.
  • the failure reason indicated by the failure reason indication information is: the first area corresponding to the first area session currently requested to be established includes an NTN type area, such as an NTN cell and/or an NTN tracking area.
  • the failure reason indicated by the failure reason information is: the first region corresponding to the first region session currently requested to be established overlaps with the MBS service region corresponding to another region session associated with the same MBS session.
  • the second message may also include a processing suggestion. If the NRF determines that a first-area session cannot be established for the first area, it may determine a suggested processing method (i.e., a processing suggestion) and carry indication information for the processing suggestion in the second message.
  • a suggested processing method i.e., a processing suggestion
  • the processing suggestion instruction information indicates the following processing method: for overlapping areas, it is recommended to establish a session for non-location-related MBS services.
  • the processing suggestion indicates the following processing method: establishing a location-related MBS service session, where the MBS service area corresponding to this regional session is the first region.
  • the location-related MBS service session is only associated with the first region, or in other words, the location-related MBS session is only associated with one regional session.
  • the processing suggestion indicated by the processing suggestion instruction information is: to initiate a session establishment process for each terminal device in the first area, thereby sending the first data to the terminal device via unicast.
  • the second message may include the reason for the failure, or a handling suggestion, or both the reason for the failure and a handling suggestion.
  • the second message includes an indication message indicating that a first-zone session cannot be established for the first zone.
  • the second message includes information about the first region.
  • the information about the first region may include the identifier of the NTN cell and/or the identifier of the NTN tracking area. If the NRF determines that a first region session cannot be established for the first region, it can obtain the identifier of the corresponding NTN cell based on the cell identifier of the mapped cell in the first region information and carry that NTN cell identifier in the second message.
  • the NEF determines that a first region session cannot be established for the first region, it can obtain the identifier of the corresponding NTN tracking area based on the identifier of the mapped tracking area in the first region information and carry that NTN tracking area identifier in the second message.
  • the second message also includes an identifier for the first area session.
  • the second message also includes an identifier of the first MBS session.
  • the second message is an Nnrf_NFDiscovery_Request Response message.
  • Step 1204 Based on the received second message, NEF sends a session establishment response message to AF, which indicates that the session establishment in the first area has failed.
  • step 1103 For details on how to implement this step, please refer to step 1103 in Figure 11.
  • Step 1205 After receiving the session establishment response message from the NEF, the AF initiates a new session establishment process for the first region based on the information included in the session establishment response message (e.g., the reason for the failure of the first region session establishment and/or the processing suggestion, and/or the information of the first region mentioned above), and transmits the first data through the new session.
  • the information included in the session establishment response message e.g., the reason for the failure of the first region session establishment and/or the processing suggestion, and/or the information of the first region mentioned above
  • step 1104 For details on how to implement this step, please refer to step 1104 in Figure 11.
  • NRF can be replaced by other network elements, and NEF can obtain area session establishment failure information by interacting with these other network elements. Optionally, it can also obtain the cause of failure and/or handling suggestions.
  • the subsequent session establishment process can continue. For example, a session establishment request message is sent to the MB-SMF, which in turn sends a session establishment request message to the AMF, which then sends a session establishment request message to the access network device.
  • a session establishment request message is sent to the MB-SMF, which in turn sends a session establishment request message to the AMF, which then sends a session establishment request message to the access network device.
  • This allows the access network device to establish a first-area session, with the area corresponding to the first-area session being the first area.
  • the access network device obtains the first data of the first MBS service from the core network and sends this first data to terminal devices within the first area via broadcast or multicast.
  • the access network device obtains the second data of the first MBS service from the core network and sends this second data to terminal devices within the second area via broadcast or multicast.
  • the first area corresponding to the first area session currently requested to be established includes an NTN type area
  • the MBS service area corresponding to the requested area session may cause the establishment of the current requested area session to fail. Therefore, AF can establish a new session for this area to transmit the requested first data.
  • the overlapping area it can transmit both the second data corresponding to the original area session and the first data corresponding to the new session, thereby enabling the transmission of different data in the same area.
  • the method shown in Figure 12 can reduce signaling interaction, enabling AF to respond to session establishment failure information and perform corresponding processing more quickly, thereby reducing the processing latency of MBS services.
  • the network device and terminal device include hardware structures and/or software modules corresponding to perform each function.
  • Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.
  • Figures 13 and 14 are schematic diagrams illustrating possible communication devices provided in embodiments of this application. These communication devices can be used to implement the functions of related devices (e.g., access network devices, NEF, or AF) in the above method embodiments, and thus also achieve the beneficial effects of the above method embodiments.
  • the communication device can be the above-mentioned device or a module (such as a chip) within the above-mentioned device.
  • the communication device 1300 includes a processing unit 1310 and a transceiver unit 1320.
  • the communication device 1300 is used to implement the functions of the related devices in the method embodiments shown in any of the figures 7, 9, 11 or 12 above.
  • the transceiver unit 1320 is used to receive a request message for requesting the establishment of a first area session, the request message including information of the first area, wherein the first area overlaps with the second area corresponding to the established second area session, and the second area session is used to send the second data of the first MBS service;
  • the processing unit 1310 is used to respond to the request message to establish a first area session, the first area session corresponding to the other areas in the first area except the area that overlaps with the second area, and the first area session is used to send the first data of the first MBS service.
  • the processing unit 1310 is used to send a request message for requesting the establishment of a first area session through the transceiver unit 1320, the request message including information of the first area, wherein the first area overlaps with the second area corresponding to the established second area session, and the second area session is used to send the second data of the first MBS service;
  • the transceiver unit 1320 is used to receive first information, the first information indicating that no area session has been established for the overlapping area;
  • the processing unit 1310 is used to send a request message for requesting the establishment of a new session through the transceiver unit 1320, the request message for requesting the establishment of a new session including information of the overlapping area, and the new session is used to send the first data.
  • the transceiver unit 1320 is used to receive a request message for requesting the establishment of a first area session, the request message including information of the first area, the first area session being used to send the first data of the first multicast broadcast MBS service;
  • the processing unit 1310 is used to send a response message through the transceiver unit 1320 when there is an overlap between the second area corresponding to the first area and the second area session, the response message indicating that the establishment of the first area session has failed; wherein, the second area session is used to send the second data of the first MBS service.
  • the transceiver unit 1320 is used to receive a request message for requesting the establishment of a first area session, the request message including information of the first area, the first area session being used to send first data of the first MBS service; the processing unit 1310 is used to determine, based on the cell identifier and corresponding relationship information contained in the information of the first area, that the first area includes an NTN cell, and/or, based on the tracking area identifier and corresponding relationship information contained in the information of the first area, determine that the first area includes an NTN tracking area, then in response to the first request message, a response message is sent through the transceiver unit 1320, the response message indicating that the establishment of the first area session has failed.
  • the corresponding relationship information includes one of first corresponding relationship information and second corresponding relationship information, wherein the corresponding relationship information includes either first or second corresponding relationship information, the first corresponding relationship information including cell identifier and cell type corresponding relationship information, and/or tracking area identifier and tracking area type corresponding relationship information, the second corresponding relationship information including mapping cell identifier and NTN cell identifier corresponding relationship information, and/or mapping tracking area identifier and NTN tracking area identifier corresponding relationship information.
  • the transceiver unit 1320 is used to receive a request message for requesting the establishment of a first area session, the request message including information of the first area, the first area session being used to send first data of the first MBS service; the processing unit 1310 is used to send a first message through the transceiver unit 1320, the first message being used to request feedback from the network element storing the corresponding relationship information whether the establishment of the first area session for the first area is permitted, the first message including information of the first area; the processing unit 1310 is used to receive a second message from the network element storing the corresponding relationship through the transceiver unit 1320, the second message indicating that the establishment of the first area session for the first area is not possible, the processing unit 1310 sends a response message through the transceiver unit 1320 according to the second message, the response message being used to indicate that the establishment of the first area session has failed.
  • the processing unit 1310 is used to send a request message for requesting the establishment of a first area session through the transceiver unit 1320, the request message including information of the first area; wherein, the first area overlaps with the second area corresponding to the established second area session, the second area session is used to send the second data of the first MBS service, and the first area session is used to send the first data of the first MBS service; the transceiver unit 1320 is used to receive a response message corresponding to the request message, the response message indicating that the establishment of the first area session has failed; the processing unit 1310 is used to send a request message for requesting the establishment of a new session through the transceiver unit 1320, the request message for requesting the establishment of a new session including information of the overlapping area, the new session being used to send the first data.
  • processing unit 1310 and the transceiver unit 1320 can be obtained directly from the relevant descriptions in the method embodiments shown in the above figures, and will not be repeated here.
  • the processing circuit 1410 may include one or more processors, or all or part of the circuitry in one or more processors for control or processing functions.
  • the communication device 1400 may also include a communication circuit 1420.
  • the communication circuit 1420 can be a transceiver, a transceiver circuit, or an interface circuit.
  • the communication circuit 1420 can be a transceiver circuit or an interface circuit.
  • the communication device is a server
  • the communication circuit can be a transceiver circuit or an interface circuit.
  • the communication device 1400 may also include a memory 1430.
  • the memory 1430 is used to store instructions executed by the processor, or to store input data required by the processor to run the instructions, or to store data generated after the processor runs the instructions.
  • the processor is used to implement the functions of the processing unit and the communication circuit is used to implement the functions of the transceiver unit.
  • the chip When the communication device 1400 is a chip applied to the aforementioned device, the chip implements the functions of the corresponding device in the above method embodiments.
  • the chip receives information from other modules (such as radio frequency modules or antennas) in the device, which is sent to the device by other devices; or, the chip sends information to other modules (such as radio frequency modules or antennas) in the device.
  • processors in the embodiments of this application may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.
  • CPU Central Processing Unit
  • DSP digital signal processors
  • ASIC application-specific integrated circuits
  • FPGA field-programmable gate arrays
  • a general-purpose processor may be a microprocessor or any conventional processor.
  • This application provides another example of a communication device, which includes at least one processor and at least one memory coupled together.
  • the at least one processor is used to store instructions, which, when executed by the at least one processor, cause the communication device to perform the methods described in the above embodiments.
  • communication device 1500 includes a processor 1510 and a memory 1530.
  • the processor 1510 and the memory 1530 are coupled together.
  • the memory 1530 stores instructions, and when the instructions stored in the memory 1530 are executed by the processor 1510, the communication device 1500 performs the methods performed by the related devices in the above embodiments.
  • processor 1510 and memory 1530 can also be integrated together, for example, into a single chip.
  • the method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor.
  • the software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium.
  • the storage medium can also be a component of the processor.
  • the processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a network-side device or a terminal-side device.
  • the processor and storage medium can also exist as discrete components in a network-side device or a terminal-side device.
  • implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof.
  • software When implemented using software, it can be implemented entirely or partially in the form of a computer program product.
  • the computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, a server, a network device, a user equipment, or other programmable device.
  • the computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another.
  • the computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media.
  • the available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive.
  • the computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.
  • This application provides a communication system that may include an access network device and an AF (Automatic Front-End).
  • the access network device can implement the methods and functions shown in Figure 7, and the AF can implement the methods and functions shown in Figure 7.
  • the communication system may also include other network elements, such as one or more of AMF, SMF, NEF, etc.
  • An example of this communication system can be illustrated by the system architecture used in the process shown in Figure 7.
  • This application also provides a communication system, which may include an access network device and an AF.
  • the access network device can implement the methods and functions shown in Figure 9, and the AF can implement the methods and functions shown in Figure 9.
  • the communication system may also include other network elements, such as one or more of AMF, SMF, NEF, etc.
  • An example of this communication system can be the system architecture applied in the process shown in Figure 9.
  • This application also provides a communication system that may include a NEF and an AF.
  • the NEF can implement the methods and functions shown in Figure 11 or Figure 12
  • the AF can implement the methods or functions shown in Figure 11 or Figure 12.
  • the communication system may also include other network elements, such as one or more of AMF, SMF, access network equipment, etc.
  • An example of this communication system can be the system architecture applied in the process shown in Figure 11 or Figure 12.
  • At least one means one or more, and “more than one” means two or more.
  • “And/or” describes the relationship between related objects, indicating that three relationships can exist.
  • a and/or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural.
  • the character “/” generally indicates an “or” relationship between the preceding and following related objects; in the formulas of this application, the character “/” indicates a “division” relationship between the preceding and following related objects.
  • “Including at least one of A, B, and C” can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种通信方法及装置，涉及无线通信技术领域。该方法包括：网络设备接收用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息，其中，所述第一区域与已建立的第二区域会话对应的第二区域存在交叠，所述第二区域会话用于发送第一MBS业务的第二数据；该网络设备响应于所述请求消息，建立第一区域会话，所述第一区域会话对应所述第一区域中除与所述第二区域存在交叠的区域以外的其他区域，所述第一区域会话用于发送所述第一MBS业务的第一数据。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2024年6月7日提交中华人民共和国国家知识产权局、申请号为202410742052.X、发明名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信技术领域，尤其涉及一种通信方法及装置。
背景技术
多播广播业务(multicast and broadcast service，MBS)是第三代合作伙伴计划(3rd generation partnership project，3GPP)为了有效地利用移动通信网络资源而引入，其在移动通信网络中提供一个数据源向多个用户发送数据的点到多点业务，实现网络资源共享，提高资源(尤其是空口资源)利用率。
位置相关MBS(location dependent MBS)属于一种MBS业务，可以实现在不同的区域发送相同MBS业务的不同数据。
对于位置相关MBS业务，针对在同一区域发送相同MBS业务的不同数据的业务需求，目前缺乏相应解决方案。
发明内容
本申请实施例提供了一种通信方法及装置，对于位置相关MBS业务，针对在同一区域发送相同MBS业务的不同数据的业务需求，提供解决方案。
第一方面，提供一种通信方法，该方法可以应用于网络侧，比如应用于网络侧的接入网设备，或者接入网设备中的模块(例如电路，芯片或芯片系统等)、或者能实现全部或部分接入网设备功能的逻辑节点、逻辑模块或软件。以接入网设备为例，在该方法中，接入网设备接收用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息，其中，所述第一区域与已建立的第二区域会话对应的第二区域存在交叠，所述第二区域会话用于发送第一MBS业务的第二数据；接入网设备响应于所述请求消息，建立第一区域会话，所述第一区域会话对应所述第一区域中除与所述第二区域存在交叠的区域以外的其他区域，所述第一区域会话用于发送所述第一MBS业务的第一数据。
可以理解，第一MBS会话用于传输第一MBS业务，所述第一区域会话和所述第二区域会话是所述第一MBS会话关联的不同的区域会话。换言之，在所述第一MBS会话内，所述第一区域会话的标识是用于标识和位置相关的内容的唯一标识。
采用上述实现方式，针对第一区域和第二区域存在交叠的情况，可以在建立第一区域会话时，将该交叠区域排除在第一区域会话对应的MBS服务区域之外，这样就可以避免新建立的第一区域会话对已建立的第二区域会话造成影响，以保证第二区域(包括交叠区域)内的终端设备依然可以接收第二数据。
可选的，所述用于请求建立第一区域会话的请求消息中还包括所述第一MBS会话的标识和所述第一区域会话的标识。
可选的，所述第一区域的信息包括以下一项或多项：小区标识和跟踪区标识。可选的，所述小区标识为NTN小区对应的映射小区的标识，和/或，所述跟踪区标识为NTN跟踪区对应的映射跟踪区的标识。
一种可能的实现方式中，该方法还包括：发送第一信息，所述第一信息指示未针对所述交叠的区域建立区域会话。
可选的，所述第一信息包括所述交叠区域的信息以及第一指示信息；其中，所述第一指示信息指示所述交叠的区域未被包括在所述第一区域会话对应的区域中，或者所述第一指示信息指示请求建立的第一区域会话所对应的区域与另一区域会话所对应的区域存在交叠。
可选的，所述第一信息可以包括在响应消息中，该响应消息中还包括所述第一MBS会话的标识和所述第一区域会话的标识。
采用上述实现方式，接入网设备可以向应用功能(application function，AF)或MBS服务器通知该交叠区域未包含在第一区域会话对应的区域中，并将该交叠区域通知给AF(或MBS服务器)，这样可以使得AF(或MBS服务器)获得第一区域会话对应的MBS服务区域，并可以针对该交叠区域发起新的会话建立流程。
一种可能的实现方式中，该方法还包括：接入网设备收用于请求建立新的会话的请求消息，所述请求消息中包括所述交叠的区域的信息，所述新的会话用于发送所述第一数据。
通过上述实现方式在降低或避免新的区域会话对原有区域会话造成影响的基础上，还可以针对上述交叠区域建立新的会话用来传输第一数据，用以保证该交叠区域内的终端设备既可以接收第二数据还可以接收第一数据，从而满足业务需求。
一种可能的实现方式中，所述新的会话为第二MBS会话，所述第一MBS会话与所述第二MBS会话不同。
可选的，所述第一MBS会话为位置相关MBS业务的会话；所述第二MBS会话为非位置相关的MBS业务的会话，或者所述第二MBS会话为位置相关的MBS业务的会话。
第二方面，提供一种通信方法，该方法可以应用于网络侧，比如应用于网络侧的AF或MBS服务器，或者AF或MBS服务器中的模块(例如电路，芯片或芯片系统等)、或者能实现全部或部分AF或MBS服务器功能的逻辑节点、逻辑模块或软件。以AF为例，在该方法中，AF发送用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息，其中，所述第一区域与已建立的第二区域会话对应的第二区域存在交叠，所述第二区域会话用于发送第一MBS业务的第二数据；AF接收第一信息，所述第一信息指示未针对所述交叠的区域建立区域会话；AF发送用于请求建立新的会话的请求消息，所述用于请求建立新的会话的请求消息中包括所述交叠的区域的信息，所述新的会话用于发送所述第一数据。
一种可能的实现方式中，所述第一信息包括所述交叠区域的信息以及第一指示信息；其中，所述第一指示信息指示所述交叠的区域未被包括在所述第一区域会话对应的区域中，或者所述第一指示信息指示请求建立的第一区域会话所对应的区域与另一区域会话所对应的区域存在交叠。
一种可能的实现方式中，所述新的会话为第二MBS会话，所述第一MBS会话与所述第二MBS会话不同。
可选的，所述第一MBS会话为位置相关MBS业务的会话；所述第二MBS会话为非位置相关的MBS业务的会话，或者所述第二MBS会话为位置相关的MBS业务的会话。
一种可能的实现方式中，上述方法还包括：AF向所述交叠区域内的终端设备发送宣告消息，所述宣告消息中包括所述第一MBS会话的标识和所述第二MBS会话的标识，所述宣告消息用于指示所述终端设备接收所述第一MBS会话的数据和所述第二MBS会话的数据，所述第一MBS会话的数据包括所述第二数据，所述第二MBS会话的数据包括所述第一数据。
第三方面，提供一种通信方法，该方法可以应用于网络侧，比如应用于网络侧的接入网设备或网络开放功能(network exposure function，NEF)，或者接入网设备或NEF中的模块(例如电路，芯片或芯片系统等)、或者能实现全部或部分接入网设备或NEF功能的逻辑节点、逻辑模块或软件。以接入网设备为例，在该方法中，接入网设备接收用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息，所述第一区域会话用于发送第一MBS业务的第一数据；若所述第一区域与第二区域会话对应的第二区域存在交叠，则发送响应消息，所述响应消息指示所述第一区域会话建立失败，其中，所述第二区域会话用于发送所述第一MBS业务的第二数据。
上述实现方式中，针对请求建立的第一区域会话对应的第一区域和已经建立的第二区域会话对应的第二区域存在交叠的情况，接入网设备可以拒绝建立第一区域会话，这样就可以避免对已建立的第二区域会话造成影响，以保证第二区域(包括交叠区域)内的终端设备依然可以接收第二数据。
一种可能的实现方式中，该方法还包括：获取所述第二区域会话的上下文信息，所述上下文信息包括所述第二区域的信息；根据所述第二区域的信息和所述第一区域的信息，确定所述第一区域与所述第二区域存在交叠。
一种可能的实现方式中，所述响应消息中包括以下一项或多项：所述第一区域会话建立失败的原因，或者处理建议。
上述实现方式中，接入网设备可以将第一区域会话建立失败的原因和/或处理建议反馈给AF或MBS服务器，从而可以使AF或MBS服务器进行相应处理。
一种可能的实现方式中，所述响应消息中包括用于指示所述第一区域会话建立失败的原因的失败原因指示信息，所述失败原因指示信息用于指示以下一项或多项：无法建立位置相关的MBS业务的会话；或者，请求建立的第一区域会话所对应的第一区域中包括非陆地网络NTN类型的区域；或者，针对所述第一MBS会话，请求建立的第一区域会话对应的所述第一区域，与另一区域会话所对应的区域存在交叠。
一种可能的实现方式中，所述响应消息中包括用于指示处理建议的处理建议指示信息，所述处理建议指示信息用于指示以下一项或多项：建立非位置相关的MBS业务的会话，所述非位置相关的MBS业务的会话的MBS服务区域为所述第一区域；或者，建立位置相关的MBS业务的会话，所述位置相关的MBS业务的会话的MBS服务区域为所述第一区域；或者，分别针对所述第一区域内的终端设备建立单播会话，所述单播会话用于传输所述第一数据。
一种可能的实现方式中，该方法还包括：接收用于请求建立新的会话的请求消息，所述用于请求建立新的会话的请求消息中包括所述交叠的区域的信息，所述新的会话用于发送所述第一数据；响应于所述用于请求建立新的会话的请求消息，建立所述新的会话，或者向会话管理功能网元发送用于请求建立所述新的会话的会话建立请求消息。
上述实现方式中，在避免对原有区域会话造成影响的基础上，还可以针对上述第一区域建立新的会话用来传输第一数据，用以保证该交叠区域内的终端设备既可以接收第二数据还可以接收第一数据，从而满足业务需求。
一种可能的实现方式中，所述新的会话为第二MBS会话，所述第一MBS会话与所述第二MBS会话不同。
一种可能的实现方式中，所述第一MBS会话为位置相关MBS业务的会话；所述第二MBS会话为非位置相关的MBS业务的会话，或者所述第二MBS会话为位置相关的MBS业务的会话。
第四方面，提供一种通信方法，该方法可以应用于网络侧，比如应用于网络侧的AF或MBS服务器，或者AF或MBS服务器中的模块(例如电路，芯片或芯片系统等)、或者能实现全部或部分AF或MBS服务器功能的逻辑节点、逻辑模块或软件。以AF为例，在该方法中，AF发送用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息；其中，所述第一区域与已建立的第二区域会话对应的第二区域存在交叠，所述第二区域会话用于发送第一MBS业务的第二数据，所述第一区域会话用于发送所述第一MBS业务的第一数据；AF接收所述请求消息对应的响应消息，所述响应消息指示所述第一区域会话建立失败；AF发送用于请求建立新的会话的请求消息，所述用于请求建立新的会话的请求消息中包括所述交叠的区域的信息，所述新的会话用于发送所述第一数据。
一种可能的实现方式中，所述响应消息中包括以下一项或多项：所述第一区域会话建立失败的原因，或者处理建议。
一种可能的实现方式中，所述响应消息中包括用于指示所述第一区域会话建立失败的原因的失败原因指示信息，所述失败原因指示信息用于指示以下一项或多项：无法建立位置相关的MBS业务的会话；或者，请求建立的第一区域会话所对应的第一区域中包括非陆地网络NTN类型的区域；或者，针对所述第一MBS会话，请求建立的第一区域会话对应的所述第一区域，与另一区域会话所对应的区域存在交叠。
一种可能的实现方式中，所述响应消息中包括用于指示处理建议的处理建议指示信息，所述处理建议指示信息用于指示以下一项或多项：建立非位置相关的MBS业务的会话，所述非位置相关的MBS业务的会话的MBS服务区域为所述第一区域；或者，建立位置相关的MBS业务的会话，所述位置相关的MBS业务的会话的MBS服务区域为所述第一区域；或者，分别针对所述第一区域内的终端设备建立单播会话，所述单播会话用于传输所述第一数据。
一种可能的实现方式中，所述新的会话为第二MBS会话，所述第一MBS会话与所述第二MBS会话不同。
一种可能的实现方式中，所述第一MBS会话为位置相关MBS业务的会话；所述第二MBS会话为非位置相关的MBS业务的会话，或者所述第二MBS会话为位置相关的MBS业务的会话。
第五方面，提供一种通信方法，该方法可以应用于网络侧，比如应用于网络侧的NEF，或者NEF中的模块(例如电路，芯片或芯片系统等)、或者能实现全部或部分NEF功能的逻辑节点、逻辑模块或软件。以NEF为例，在该方法中，NEF接收用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息，所述第一区域会话用于发送第一MBS业务的第一数据；NEF根据所述第一区域的信息中包含的小区标识以及对应关系信息，确定所述第一区域中包括NTN小区，和/或，根据所述第一区域的信息中包含的跟踪区的标识以及所述对应关系信息，确定所述第一区域中包括NTN跟踪区，则响应于所述第一请求消息发送响应消息，所述响应消息指示所述第一区域会话建立失败。其中，所述对应关系信息包括第一对应关系信息和第二对应关系信息中的一项，其中，所述对应关系信息包括第一对应关系信息或第二对应关系信息，所述第一对应关系信息包括小区标识和小区类型的对应关系信息，和/或跟踪区标识和跟踪区类型的对应关系信息，所述第二对应关系信息包括映射小区标识和NTN小区标识的对应关系信息，和/或，映射跟踪区标识和NTN跟踪区标识的对应关系信息。
第六方面，提供一种通信方法，该方法可以应用于网络侧，比如应用于网络侧的NEF，或者NEF中的模块(例如电路，芯片或芯片系统等)、或者能实现全部或部分NEF功能的逻辑节点、逻辑模块或软件。以NEF为例，在该方法中，NEF接收用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息，所述第一区域会话用于发送第一MBS业务的第一数据；NEF发送第一消息，所述第一消息用于请求存储有对应关系信息的网元反馈是否允许针对第一区域建立第一区域会话，所述第一消息中包括所述第一区域的信息；NEF从存储有所述对应关系的网元接收第二消息，所述第二消息指示无法针对第一区域建立第一区域会话，NEF根据所述第二消息发送响应消息，该响应消息用于指示所述第一区域会话建立失败。
可选的，存储有所述对应关系信息的网元用于根据所述第一区域的信息和所述对应关系信息确定所述第一区域中是否包括NTN小区和/或NTN跟踪区。
可选的，所述对应关系信息包括第一对应关系信息和第二对应关系信息中的一项，其中，所述第一对应关系信息包括小区标识和小区类型的对应关系信息，和/或跟踪区标识和跟踪区类型的对应关系信息，所述第二对应关系信息包括映射小区标识和NTN小区标识的对应关系信息，和/或，映射跟踪区标识和NTN跟踪区标识的对应关系信息。
基于上述第五方面或第六方面中任一项所述的方法，在一种可能的实现方式中，所述响应消息中包括以下一项或多项：所述第一区域会话建立失败的原因，或者处理建议。
基于上述第五方面或第六方面中任一项所述的方法，在一种可能的实现方式中，所述响应消息中包括用于指示所述第一区域会话建立失败的原因的失败原因指示信息，所述失败原因指示信息用于指示以下一项或多项：无法建立位置相关的MBS业务的会话；或者，请求建立的第一区域会话所对应的第一区域中包括非陆地网络NTN类型的区域；或者，针对所述第一MBS会话，请求建立的第一区域会话对应的所述第一区域，与另一区域会话所对应的区域存在交叠。
基于上述第五方面或第六方面中任一项所述的方法，在一种可能的实现方式中，所述响应消息中包括用于指示处理建议的处理建议指示信息，所述处理建议指示信息用于指示以下一项或多项：建立非位置相关的MBS业务的会话，所述非位置相关的MBS业务的会话的MBS服务区域为所述第一区域；或者，建立位置相关的MBS业务的会话，所述位置相关的MBS业务的会话的MBS服务区域为所述第一区域；或者，分别针对所述第一区域内的终端设备建立单播会话，所述单播会话用于传输所述第一数据。
基于上述第五方面或第六方面中任一项所述的方法，在一种可能的实现方式中，还包括：接收用于请求建立新的会话的请求消息，所述用于请求建立新的会话的请求消息中包括所述交叠的区域的信息，所述新的会话用于发送所述第一数据；响应于所述用于请求建立新的会话的请求消息，建立所述新的会话，或者向会话管理功能网元发送用于请求建立所述新的会话的会话建立请求消息。
基于上述第五方面或第六方面中任一项所述的方法，在一种可能的实现方式中，所述新的会话为第二MBS会话，所述第一MBS会话与所述第二MBS会话不同。
基于上述第五方面或第六方面中任一项所述的方法，在一种可能的实现方式中，所述第一MBS会话为位置相关MBS业务的会话；所述第二MBS会话为非位置相关的MBS业务的会话，或者所述第二MBS会话为位置相关的MBS业务的会话。
第七方面，提供一种通信装置，包括用于执行如上述第一方面中任一项所述方法的单元或者模块，或者包括用于执行如上述第二方面中任一项所述方法的单元或者模块，或者包括用于执行如上述第三方面中任一项所述方法的单元或者模块，或者包括用于执行如上述第四方面中任一项所述的方法的单元或者模块，或者包括用于执行如上述第五方面中任一项所述方法的单元或者模块，或者包括用于执行如上述第六方面中任一项所述方法的单元或者模块。
第八方面，提供一种通信装置，包括：一个或多个处理器配置用于执行如第一方面中任一项所述的方法，或者执行如第二方面中任一项所述的方法，或者执行如第三方面中任一项所述的方法，或者执行如第四方面中任一项所述的方法，或者执行如第五方面中任一项所述的方法，或者执行如第六方面中任一项所述的方法。
第九方面，提供一种通信系统，该通信系统中可以包括接入网设备和AF；其中，所述接入网设备可以实现如第一方面中任一项所述的方法，所述AF可以实现如第二方面中任一项所述的方法；或者，所述接入网设备可以实现如第三方面中任一项所述的方法，所述AF可以实现如第四方面中任一项所述的方法。
第十方面，提供一种通信系统，该通信系统中可以包括NEF和AF；其中，所述NEF可以实现如第五方面或第六方面中任一项所述的方法，所述AF可以实现如第四方面中任一项所述的方法。
第十一方面，提供一种可读存储介质，所述可读存储介质存储有程序或指令，当所述程序或指令在装置上运行时，使得所述装置执行如第一方面中任一项所述的方法，或者执行如第二方面中任一项所述的方法，或者执行第三方面中任一项所述的方法，或者执行如第四方面中任一项所述的方法，或者执行如第五方面中任一项所述的方法，或者执行如第六方面中任一项所述的方法。
第十二方面，提供一种芯片系统，用于支持计算机装置实现如第一方面中任一项所述的方法，或者实现如第二方面中任一项所述的方法，或者实现如第三方面中任一项所述的方法，或者实现如第四方面中任一项所述的方法，或者实现如第五方面中任一项所述的方法，或者实现如第六方面中任一项所述的方法。
第十三方面，提供一种程序产品，所述程序产品中包含程序；当所述程序在计算机上运行时，使得所述计算机执行如第一方面中任一项所述的方法，或者执行如第二方面中任一项所述的方法，或者执行如第三方面中任一项所述的方法，或者执行如第四方面中任一项所述的方法，或者执行如第五方面中任一项所述的方法，或者执行如第六方面中任一项所述的方法。
附图说明
图1为本申请实施例适用的基于服务化接口的5G网络架构的示意图；
图2为本申请实施例适用的基于点对点接口的5G网络架构的示意图；
图3为本申请实施例适用的NTN网络的示意图；
图4为本申请实施例适用的MBS传输方式的示意图；
图5为本申请实施例适用的一种广播业务的会话建立过程示意图；
图6为位置相关MBS业务的传输示意图；
图7为本申请实施例提供的一种通信方法的流程示意图；
图8为本申请实施例中针对位置相关MBS在同一区域发送不同的数据的示意图；
图9为本申请实施例提供的另一种通信方法的流程示意图；
图10为本申请实施例中针对位置相关MBS在同一区域发送不同的数据的示意图；
图11为本申请实施例提供的另一种通信方法的流程示意图；
图12为本申请实施例提供的另一种通信方法的流程示意图；
图13为本申请实施例提供的一种通信装置的结构示意图；
图14为本申请实施例提供的另一种通信装置的结构示意图；
图15为本申请实施例提供的另一种通信装置的结构示意图。
具体实施方式
以下，首先对本申请实施例涉及的部分术语和技术进行解释说明，以便于本领域技术人员理解。
(一)非陆地网络(non-terrestrial networks，NTN)和陆地网络(terrestrial networks，TN)
非陆地网络，简称NTN或NTN网络，是指至少部分网络设备在非陆地上部署的网络，例如将飞行器(例如包括飞机或无人机)或者卫星等引入通信系统作为中继节点或者作为基站使用的通信网络。相应的，陆地网络，可以被简称为TN或TN网络，是网络设备全部部署在陆地上的网络。
在NTN中，在上行方向上，终端设备通过卫星将数据发送到基站，在下行方向上，基站通过卫星将数据发送到终端设备。由于卫星到地面的距离很远，一个卫星的覆盖区域较大，也就是说空口小区的覆盖半径较大。
NTN和TN的网络架构可以遵循3GPP标准组制定的下一代移动通信网络系统(Next Generation System)架构，该架构也可以称为5G网络架构。该架构支持3GPP标准组定义的无线接入技术(如长期演进(long term evolution，LTE)接入技术，5G无线接入网(radio access network，RAN)接入技术等)接入到5G核心网(core network，CN)，还支持使用非3GPP(non-3GPP)接入技术通过非3GPP转换功能(non-3GPP interworking function，N3IWF)或下一代接入网关(next generation packet data gateway，ngPDG)接入到核心网。
图1为基于服务化架构的5G网络架构示意图。图1所示的5G网络架构中可包括接入网设备以及核心网设备。终端设备通过接入网设备和核心网设备接入数据网络(data network，DN)。其中，核心网设备包括但不限于以下网元中的部分或者全部：鉴权服务器功能(authentication server function，AUSF)网元、统一数据管理(unified data management，UDM)网元、统一数据库(unified data repository，UDR)网元(未在图中示出)、网络存储功能(network repository function，NRF)网元、网络开放功能(network exposure function，NEF)网元、网络切片选择功能(network slice selection function，NSSF)网元、网络切片选择的认证和授权功能(network slice-specific authentication and authorization function，NSSAAF)网元、网络切片准入控制功能(network slice admission control function，NSACF)网元、应用功能(application function，AF)网元、策略控制功能(policy control function，PCF)网元、接入和移动管理功能网元(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、用户面功能(user plane function，UPF)网元、绑定支持功能(binding support function，BSF)网元(图中未示出)。
终端设备可以是用户设备(user equipment，UE)、移动台、移动终端设备等。终端设备可以广泛应用于各种场景，例如，设备到设备(device-to-device，D2D)、车物(vehicle to everything，V2X)通信、机器类通信(machine-type communication，MTC)、物联网(internet of things，IOT)、虚拟现实、增强现实、工业控制、自动驾驶、远程医疗、智能电网、智能家具、智能办公、智能穿戴、智能交通、智慧城市等。终端设备可以是手机、平板电脑、带无线收发功能的电脑、可穿戴设备、车辆、城市空中交通工具(如无人驾驶机、直升机等)、轮船、机器人、机械臂、智能家居设备等。
接入网设备为具有无线收发功能的设备，用于与所述终端设备进行通信。所述接入网设备包括但不限于基站(基站收发站点(base transceiver station，BTS)，Node B,eNodeB/eNB，或gNodeB/gNB)、收发点(transmission reception point，TRP)，第三代合作伙伴计划(3rd generation partnership project，3GPP)后续演进的基站，Wi-Fi系统中的接入节点，无线中继节点，无线回传节点等。所述基站可以是：宏基站，微基站，微微基站，小站，中继站等。多个基站可以支持同一种接入技术的网络，也可以支持不同接入技术的网络。基站可以包含一个或多个共站或非共站的传输接收点。所述接入网设备还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器、集中单元(centralized unit，CU)，和/或分布单元(distributed unit，DU)。所述接入网设备还可以是服务器等。
接入网设备和终端设备可以是固定位置的，也可以是可移动的。接入网设备和终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和人造卫星上。本申请的实施例对接入网设备和终端设备的应用场景不做限定。
AMF网元，负责UE的移动性管理，包括移动状态管理，分配UE的临时身份标识，认证和授权UE。
SMF网元，负责UPF网元的选择，UPF网元的重选，IP地址分配，负责承载的建立、修改和释放，服务质量(quality of service，QoS)控制。
UPF网元，支持以下全部或者部分功能：将协议数据单元(protocol data unit，PDU)会话与数据网络互连；分组路由和转发(例如，支持对流量进行上行分类(uplink classifier)后转发到数据网络)；数据包检测。
UDM网元，负责管理签约数据，当签约数据修改的时候，负责通知相应的网元。
图1中Nnssf、Nnef、Nnrf、Npcf、Nudm、Naf、Nnssaaf、Nausf、Namf、Nsmf、Nnsacf分别为上述NSSF、NEF、NRF、PCF、UDM、AF、NSSAAF、AUSF、AMF、SMF和NSACF提供的服务化接口，用于调用相应的服务化操作。N1、N2、N3、N4、N6和N9为接口序列号，这些接口序列号的含义如下：
N1：AMF与终端设备之间的接口，可以用于向终端设备传递非接入层(non access stratum，NAS)信令(如包括来自AMF的QoS规则)等。
N2：AMF与接入网设备之间的接口，可以用于传递核心网侧至接入网设备的无线承载控制信息等。
N3：接入网设备与UPF之间的接口，主要用于传递接入网设备与UPF间的上下行用户面数据。
N4：SMF与UPF之间的接口，可以用于控制面与用户面之间传递信息，包括控制面向用户面的转发规则、QoS规则、流量统计规则等的下发以及用户面的信息上报。
N6：UPF与DN的接口，用于传递UPF与DN之间的上下行用户数据流。
N9：UPF网元和UPF网元之间的用户面接口，用于传递UPF网元间的上下行用户数据流。
图2为基于点对点接口的5G网络架构示意图，其中的网元的功能的介绍可以参考图1中对应的网元的功能的介绍，不再赘述。图2与图1的主要区别在于：图1中的各个控制面网元之间的接口是服务化的接口，图2中的各个控制面网元之间的接口是点对点的接口。
应理解，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。可选的，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
本申请中的移动性管理网元、会话管理网元、数据管理网元、网络存储功能网元分别可以是5G系统中的AMF网元、SMF网元、NEF网元，也可以是未来通信如6G网络中具有上述AMF网元、SMF网元、NEF网元的功能的网元，本申请对此不限定。在本申请的实施例中，以AMF网元、SMF网元、NEF网元分别为移动性管理网元、会话管理网元、数据管理网元、网络存储功能网元的一个示例进行描述。并且，将AMF网元、SMF网元、NEF网元分别简称为AMF、SMF、NEF。
为便于说明，本申请实施例以基站、UE分别作为接入网设备、终端设备的一个具体示例进行说明，后续任意位置出现的基站、UE均可以分别替换为接入网设备、终端设备。
基于上述图1和图2所示的网络系统架构，图3示出了一种NTN网络的示意图，其中，卫星可以作为终端设备和地面基站之间的中继节点，也可以作为基站。
(二)空口小区标识(Uu cell ID)、映射小区标识(mapped cell ID)
空口小区标识，即空口小区的标识。TN中，空口小区标识包括物理小区标识(physical cell identification，PCI)、载波频率(如绝对无线载频信道号(absolute radio frequency channel number，ARFCN))和全球小区识别码(cell global identification，GCI)等。对于核心网来说，通常使用CGI来标识小区。在一些场景下，一些核心网网元，例如NEF、AMF等，可以基于CGI映射出对应的地理位置区域。
但是NTN中，空口小区的覆盖半径较大，无法使用CGI来标识一个空口小区，核心网无法映射出对应的地理位置区域。因此，在NTN场景下，引入了映射小区标识(mapped cell ID)的概念，一个空口小区可以关联到多个mapped cell ID，每一个mapped cell ID都对应固定的地理位置区域(fixed geographical area)。在一些NTN场景下，卫星相对于地面静止，使得一个NTN小区对应的mapped cell ID不随时间变化而变化；在另一些NTN场景下，卫星相对于地面移动(earth-moving)，使得一个NTN小区对应的mapped cell ID随时间变化而变化。对于核心网和基站之间的NG接口来说，交互的消息中的NR CGI字段填充的是mapped cell ID，而使得基站和核心网能明确终端设备当前所处的地理位置。对于基站之间的Xn接口，交互映射空口小区标识、映射小区标识中的任何一个均可。
应理解，映射小区标识的作用是映射地理位置区域，并不代表该地理位置区域的空口小区覆盖情况，并不代表该地理位置区域一定有信号覆盖。
一个跟踪区(tracking area，TA)可以包括一个或多个小区，不同的跟踪区可以使用跟踪区标识(tracking area identity，TAI)进行区分。类似的，对于跟踪区，也存在NTN跟踪区。一个NTN跟踪区的TAI可以对应一个或多个映射跟踪区标识(mapped TAI)。一个mapped TAI可以对应一个或多个mapped cell ID。
(三)多播广播业务(multicast and broadcast service，MBS)
MBS是同时面向多个终端设备传输的业务，例如直播业务、公共安全业务、批量软件更新业务等。MBS的业务数据来自MBS服务器，该MBS服务器也称为数据服务器，可以提供MBS数据。例如，AF可以充当MBS服务器。
首先MBS服务器将MBS的数据发送给核心网设备，然后核心网设备将MBS数据发送给接入网设备，最后接入网设备将MBS数据发送给接收MBS的一个或多个终端设备。该过程中，核心网设备通过一个公共的传输通道即MBS会话将MBS数据发送给接入网设备，接入网设备可以通过以下两种方式将MBS数据发送给终端设备：方式1)采用点到多点(point to multi-point，PTM)传输方式；方式2)采用点到点(point to point，PTP)传输方式。如图4所示，为PTP传输和PTM传输的示意图。
应理解，MBS仅是一种示例性命名，不同通信制式下对多播广播业务的命名可以不同，例如，在长期演进(long term evolution，LTE)中多播广播业务可以称为多媒体广播多播业务(multimedia broadcast multicast service，MBMS)，在新空口(new radio，NR)中多播广播业务可以称为MBS，在未来通信发展中，多播广播业务也可以命名为其他，本申请不做具体限定。
本申请实施例中，MBS也可以称为“MBS服务”、“MBS业务”、“MBS广播服务”、“MBS会话”或“MBS广播业务”等。
提供MBS的区域，可以称为“MBS服务区域”、“MBS业务区域”、“MBS广播服务区域”、“MBS会话区域”、“MBS广播业务区域”、“MBS区域”、“多播服务区域(MBS service area)”、“MBS的服务区域”或“服务区域”等。
MBS的业务类型可以包括组播(multicast)业务(也可以称为多播业务)、广播(broadcast)业务。本申请中MBS可以替换为组播或者广播。
组播业务是针对高服务质量(quality of service，QoS)需求业务设计的，可以针对组播业务进行组管理，可以提供和单播业务相同的QoS等级。具体的，对于组播业务，核心网(core network，CN)可以管理终端设备的加入和退出。对于无线接入网(radio access network，RAN)，支持以PTP或PTM传输方式向终端设备发送数据，并且支持由RAN控制的PTP和PTM之间的动态切换。组播业务提供给无线资源控制(radio resource control，RRC)连接态终端设备，可以由RAN和CN维护MBS组对应的终端设备信息。组播业务还支持由核心网触发的MBS会话(session)去激活/激活，终端设备不感知业务状态。
广播业务是针对相对低QoS要求的服务设计的，是尽力而为地保证QoS要求(best effort QoS)。广播业务支持任何RRC状态的终端设备，RAN和CN不需要维护接收相关广播业务的终端设备组，当有业务正在提供时，终端设备组根据配置信息自主进行接收。广播业务的数据传输和组播业务一样是只针对下行传输设计的，与组播业务不同的是广播业务只支持PTM传输方式，对于终端设备来说，广播业务的配置和组播业务的配置是完全独立的。
广播业务限定在一定的范围内提供。可选的，对于一个广播业务，也可以在不同的区域范围内提供不同的数据内容(即本地广播业务)。
不同于传统的单播流程，广播业务是一种自上而下的会话建立过程。如图5所示，首先，内容提供方(例如应用功能(application function，AF)或MBS服务器等)将用于建立广播业务的会话所需的相关信息(例如广播的区域、发送数据所需的QoS信息等)提供给SMF(如图中的MB-SMF)，其中，MB-SMF为multicast/broadcast session management function的英文简称，即多播/广播会话管理功能；此后核心网设备根据QoS信息确定对应的策略、建立对应的QoS流，并在对应的基站(gNB)和UPF(如图中的MB-UPF)建立广播会话的上下文。
(四)位置相关MBS业务(location dependent MBS service)
位置相关MBS业务的一种类型为本地多播广播业务(local MBS service)。本地MBS服务特性，体现为业务内容和区域相关，只有服务区域内的终端设备可以接收内容数据，而不允许MBS服务区外的终端设备接收位置特定的内容。位置相关MBS业务对应的多播服务区域(MBS service area)(即MBS服务区域)可以由一组跟踪区和/或一组小区(cell)组成，用于指示特定的范围。
对于位置相关MBS业务，一个MBS会话使用唯一一个会话标识来进行标识，MBS会话的标识可以是MBS会话标识(MBS Session ID)或临时移动组标识(temporary mobile group identity，TMGI)等。一个MBS会话可以关联多个MBS服务区域，每个MBS服务区域由一个区域会话标识(area session ID)来进行标识，也就是说，一个MBS会话可以关联一个或多个MBS区域会话，或者说一个MBS会话标识可以关联一个或多个区域会话标识。同一个MBS会话的不同area session ID所对应的数据内容不同，数据来源也可能不同。换言之，区域会话标识(如area session ID)和MBS会话的标识(例如TMGI)一起可以标识某个MBS会话在某个特定MBS业务区域的数据流。终端设备不感知area session ID，只感知MBS会话标识。
位置相关MBS业务的示例如天气预报、地图更新等。如图6所示，TMGI#A对应的MBS会话关联小区cell#1中的区域1和小区cell#2中的区域2，针对区域1建立有区域会话1(即Area session#1)，针对区域2建立有区域会话2(即Area session#1)。基站通过区域会话1(Area session#1)广播区域1的天气数据，通过区域会话2(Area session#2)广播区域2的天气数据。
在NTN场景下，一个空口小区在核心网被映射到多个映射小区(mapped cell)。对于位置相关MBS业务，基站在一个空口小区范围内的一个区域上仅能发送相应区域会话对应的数据，例如图6中，基站仅能在小区cell#1中的区域1通过区域会话1(Area session#1)广播区域1的天气数据。如果一个空口小区范围内的一个区域已经存在区域会话，则当内容提供方(例如AF)请求针对该区域建立新的区域会话以便广播新的数据时，则可能发生以下情况中的一种：
情况1：网络侧(例如核心网设备或基站)判断针对本次请求建立区域会话的区域已经存在区域会话(称为旧的区域会话)，因此拒绝针对该区域建立新的区域会话，导致无法实现在该区域广播旧的区域会话对应的数据和新的数据的业务需求；
情况2：网络侧(例如核心网设备或基站)判断针对本次请求建立区域会话的区域已经存在区域会话(称为旧的区域会话)，因此在该区域不再广播旧的区域会话对应的数据，而是广播新的区域会话对应的数据。也就是说，新的区域会话将会覆盖旧的区域会话，导致无法实现在该区域同时广播旧的区域会话对应的数据和新的区域会话对应的数据的业务需求。
在TN场景下也存在上述类似问题。
为此，本申请实施例提供了一种通信方法以及可以实现该方法的相关装置，用以针对位置相关MBS业务，提供在同一区域发送不同的数据的解决方案，进而可以实现针对位置相关MBS业务，在同一区域发送不同的数据。
下面结合附图对本申请实施例进行详细说明。
本申请实施例提供的一种通信方法中，针对同一MBS会话，在当前请求建立第一区域会话的情况下，如果当前请求建立的第一区域会话所对应的第一区域与已建立的第二区域会话所对应的第二区域存在交叠区域，则接入网设备可以建立第一区域会话，但该第一区域会话对应区域中不包括上述交叠区域，从而可以降低或避免新建立的第一区域会话对原有的第二区域会话的影响。
可选的，接入网设备还可以将该交叠区域指示给内容提供方(即MBS服务器，例如AF等)，以使得内容提供方针对该交叠区域建立新的会话，从而可以在该交叠区域传输与第一区域会话对应的数据相同的数据，进而可以实现在该交叠区域能够传输同一MBS会话的不同数据。
其中，第一区域会话和第二区域会话是第一MBS会话关联的区域会话，或者说第一区域会话和第二区域会话属于第一MBS会话。
基于图1或图2所示的架构，参见图7，为本申请实施例提供的通信方法的流程示意图。
图7中，以AF作为内容提供方为例描述。应理解，本流程是以MBS业务的内容提供方是AF为例描述的，MBS业务的内容提供方也可以是其他设备，本申请不予限制。
如图7所示，该流程可以包括以下步骤：
步骤701：AF向NEF发送会话建立请求消息，该会话建立请求消息用于请求建立第一区域会话。
其中，第一区域会话为接入网设备与核心网中的用户面功能网元(如UPF)之间的用户面通道。第一区域会话用于传输第一MBS会话的第一数据，也就是说，用户面网元可以基于第一区域会话以组播或多播或广播方式发送第一数据。
会话建立请求消息中可以包括第一MBS会话的标识，用以表明请求建立的第一区域会话属于第一MBS会话，或者说第一区域会话是第一MBS关联的一个区域会话。另一种情况下，会话建立请求消息中未包含第一MBS会话的标识，此时，MBS会话的标识会在步骤703中由MB-SMF网元分配。
会话建立请求消息中还包括第一区域的信息，用以指示请求建立的区域会话所对应的MBS服务区域。
一种可能的实现方式中，第一区域的信息可以包括一个或多个小区的信息，例如包括一个或多个小区的标识。示例性的，第一区域的信息可以包括小区列表，该小区列表中包括一个或多个小区的标识。
可选的，在NTN场景下，上述小区的标识为映射小区标识(mapped cell ID)。
可选的，在TN场景下，上述小区的标识为空口小区标识(Uu cell ID)，例如可以是CGI或PCI等标识。
另一种可能的实现方式中，第一区域的信息可以包括一个或多个跟踪区的信息，例如包括一个或多个跟踪区的标识。示例性的，第一区域的信息可以包括跟踪区列表，该跟踪区列表中包括一个或多个跟踪区的标识。
可选的，在NTN场景下，上述跟踪区的标识为映射跟踪区标识(mapped TAI)。一个mapped TAI可以对应一个或多个mapped cell ID。
可选的，在TN此场景下，上述跟踪区的标识为TAI。一个TAI可以对应一个或多个空口小区标识。
另一种可能的实现方式中，第一区域的信息可以包括地理区域信息。示例性的，该地理区域信息可以是定位系统坐标信息，或者是地址信息(例如街道名称)，或者是邮政编码(zip code)，或者是其他可以用于描述地理区域的信息，本申请不予限制。
应理解，第一区域的信息可以包括小区的标识、跟踪区的标识以及地理区域信息中的一项或多项。
会话建立请求消息中还可以包括第一指示信息，第一指示信息指示请求建立的第一区域会话为位置相关MBS业务的会话，或者说第一指示信息指示第一区域会话的类型为位置相关MBS业务会话类型。
一种可能的实现方式中，AF可以调用NEF提供的Nnef_MBSSession_Create request服务来触发第一区域会话的建立过程。
步骤702：NEF从AF接收到会话建立请求消息后，向MB-SMF发送会话建立请求消息，该会话建立请求消息用于请求建立第一区域会话。
该步骤中，NEF从AF接收到会话建立请求消息后，可以根据接收到的会话建立请求消息中包含的第一区域的信息，选择与第一区域位置匹配的MB-SMF，并向该MB-SMF发送会话建立请求消息。另一种可能的实现方式是，NEF根据本地存储的第一MBS会话的标识与MB-SMF的关联关系，选择MB-SMF，并向该MB-SMF发送会话建立请求消息。
NEF发送的会话建立请求消息中可以包括第一MBS会话的标识，用以表明请求建立的第一区域会话属于第一MBS会话，或者说第一区域会话是第一MBS关联的一个区域会话。
NEF发送的会话建立请求消息中还可以包括第一区域的信息，该信息指示的第一区域可以与NEF从AF接收到的第一区域的信息所指示的区域相同。
一种可能的实现方式中，如果NEF从AF接收到的第一区域的信息中包括地理区域信息，则NEF可以根据该地理区域信息获得对应的小区标识和/或跟踪区标识，并使用获得到的小区标识和/或跟踪区标识替换第一区域的信息中的地理区域信息，从而将替换后的第一区域的信息携带在发送给MB-SMF的会话建立请求消息中。
一种可能的实现方式中，NEF可以调用MB-SMF提供的Nmbsmf_MBSSession_Create Request服务来实现向MB-SMF发送会话建立请求消息。
步骤703：MB-SMF从NEF接收到会话建立请求消息后，向AMF发送会话建立请求消息，该会话建立请求消息用于请求建立第一区域会话。
该步骤中，MB-SMF从NEF接收到会话建立请求消息后，可以根据接收到的会话建立请求消息中包含的第一区域的信息，选择与第一区域位置匹配的AMF，并向该AMF发送会话建立请求消息。
可选地，MB-SMF分配第一MBS会话标识，例如，当从NEF接收到的会话建立请求消息中，未包含第一MBS会话的标识时。
MB-SMF发送的会话建立请求消息中可以包括第一MBS会话的标识，用以表明请求建立的第一区域会话属于第一MBS会话，或者说第一区域会话是第一MBS关联的一个区域会话。
MB-SMF发送的会话建立请求消息中还可以包括第一区域的信息，该信息可以与MB-SMF从NEF接收到的第一区域的信息相同。
MB-SMF发送的会话建立请求消息中还可以包括第一区域会话的标识。由于第一区域会话用于在第一区域发送第一数据，且第一区域会话属于第一MBS会话，因此第一区域会话的标识可以被理解为用于标识第一MBS会话的第一数据。第一区域会话的标识可以由该MB-SMF分配。
一种可能的实现方式中，MB-SMF可以调用AMF提供的Namf_MBSBroadcast_ContextCreate服务来实现向AMF发送会话建立请求消息。
步骤704：AMF从MB-SMF接收到会话建立请求消息后，向接入网设备发送会话建立请求消息，该会话建立请求消息用于请求建立第一区域会话。
AMF发送的会话建立请求消息中可以包括第一MBS会话的标识，用以表明请求建立的第一区域会话属于第一MBS会话，或者说第一区域会话是第一MBS关联的一个区域会话。
AMF发送的会话建立请求消息中还可以包括第一区域的信息，该信息可以与AMF从MB-SMF接收到的第一区域的信息相同。另一种实现的方式中，AMF发送的会话建立请求消息中包括第三区域的信息，该信息指示的第三区域属于或者包含于AMF从MB-SMF接收到的第一区域的信息所指示的第一区域。例如，AMF可能基于接入网设备支持的区域，向多个接入网设备发送消息，每个消息中的区域被适当缩小以适配接入网设备支持的区域。
AMF发送的会话建立请求消息中还可以包括第一区域会话的标识。
一种可能的实现方式中，AMF发送的会话建立请求消息为广播会话建立请求(BROADCAST SESSION SETUP REQUEST)消息。
步骤705：接入网设备从AMF接收到会话建立请求消息后，根据该会话建立请求消息中包括的第一区域的信息，确定第一区域与第二区域存在交叠区域。
其中，第二区域为第一MBS会话关联的第二区域会话所对应的MBS服务区域，第二区域会话用于向第二区域内的终端设备发送第一MBS业务的第二数据，通过第一区域会话发送的第一数据与通过第二区域会话发送的第二数据不同。也就是说，针对同一MBS会话关联的第一区域会话和第二区域会话，当前请求建立的第一区域会话对应的第一区域，与关联于同一MBS会话的另一区域会话所对应的MBS服务区域存在交叠。
由于第二区域会话为已建立的区域会话，因此接入网设备保存有第二区域会话的上下文信息，该上下文信息中包括第二区域会话对应的第二区域的信息。接入网设备可以根据接收到的会话建立请求消息中包含的第一区域的信息以及该接入网设备所保存的第二区域会话的上下文信息中包含的第二区域的信息，确定第一区域和第二区域是否存在交叠。
本申请实施例中，第一区域与第二区域存在交叠的区域，可以理解为：第一区域中既包括与第二区域存在交叠的部分，又包括与第二区域不存在交叠的部分区域。
示例性的，“第一区域与第二区域存在交叠的区域”具体可以包括以下情况：
情况1：第一区域的部分和第二区域的部分存在重合。例如，第一区域包括小区A和小区B，第二区域包括小区A和小区C，则第一区域和第二区域的交叠区域为小区A。
情况2：第一区域大于第二区域，且第二区域完全落入第一区域内。例如，第一区域包括小区A和小区B，第二区域包括小区A，则第一区域和第二区域的交叠区域为小区A。
步骤706：接入网设备建立第一区域会话，第一区域会话对应的区域为第一区域中除与第二区域存在交叠的区域以外的区域。
由于第一区域中还存在与第二区域不交叠的区域，例如上述情况1或情况2，则接入网设备可以建立第一区域会话，保存第一区域会话的上下文信息。第一区域会话的上下文信息中可以包括第一区域会话对应的MBS服务区域的信息，该MBS服务区域为第一区域中除上述交叠区域以外的区域，也就是说，第一区域会话对应的区域为第一区域中除与第二区域存在交叠的区域以外的区域。接入网设备可以从核心网接收第一MBS业务的第一数据，并可以根据第一区域会话的上下文信息中包含的MBS服务区域的信息，将该第一数据发送给第一区域中除交叠区域以外的区域内的终端设备。
接入网设备仍可以通过第二区域会话从核心网接收第一MBS业务的第二数据，并将该第二数据发送给第二区域内(包括交叠区域)的终端设备。
上述流程中，针对第一区域和第二区域存在交叠的情况，可以在建立第一区域会话时，将该交叠区域排除在第一区域会话对应的MBS服务区域之外，这样就可以避免新建立的第一区域会话对已建立的第二区域会话造成影响，以保证第二区域(包括交叠区域)内的终端设备依然可以接收第二数据。
通过上述实现方式在降低或避免新的区域会话对原有区域会话造成影响的基础上，本申请的一些实施例中，还可以针对上述交叠区域建立新的会话用来传输第一数据，用以保证该交叠区域内的终端设备既可以接收第二数据还可以接收第一数据，从而满足业务需求。
仍以图7所示的流程为例，一种可能的实现方式中，上述图7所示的流程还可以包括以下步骤：
步骤707：接入网设备向AMF发送第一信息(例如会话建立响应消息)，第一信息指示未针对上述交叠的区域建立区域会话。
一种可能的实现方式中，第一信息可以包括交叠区域的信息和第一指示信息。第一指示信息可以用于指示上述交叠的区域未被包括在第一区域会话对应的区域中，或者说第一指示信息可以用于指示请求建立的第一区域会话所对应的区域与另一区域会话所对应的区域存在交叠。
一种可能的实现方式中，第一信息可以是包含在会话建立响应消息中，或者第一信息可以被理解为会话建立响应消息。本流程中，以发送会话建立响应消息为例描述。
一种可能的实现方式中，交叠区域的信息可以包括一个或多个小区的标识，第一区域和第二区域在该一个或多个小区存在交叠。例如上述情况1或情况2或情况3中，该信息包括小区A的标识。又例如，该信息可以包括一个或多个跟踪区的标识，第一区域和第二区域在该一个或多个跟踪区存在交叠。
应理解，用于指示第一区域和第二区域的交叠区域的信息，可以包括小区标识、跟踪区标识中的一项或多项。
由于第一区域会话和第二区域会话均属于第一MBS业务，已建立的第二区域会话覆盖了上述交叠区域，因此接入网设备无法在上述交叠区域发送第一MBS业务的另一数据(即这里的第一数据)，但可以在第一区域内除该交叠区域以外的区域发送第一MBS业务的第一数据，因此该交叠区域也可以称为不被请求建立的区域会话(即第一区域会话)接受的区域，或者简称为不被接受的区域。相应的，第一区域内除交叠区域以外的区域可以称为被请求建立的区域会话(即第一区域会话)接受的区域，或者简称为被接受的区域。换言之，第一指示信息可以指示第一区域中被第一区域会话接受和/或不被接受的区域。
可选的，在上述第一指示信息指示上述交叠的区域未被包括在第一区域会话对应的区域中的基础上，还可以指示该交叠的区域未被包括在第一区域会话对应的区域的原因是：请求建立的第一区域会话所对应的区域与另一区域会话所对应的区域存在交叠。
另一种可能的实现方式中，该交叠的区域未被包括在第一区域会话对应的区域的原因，也可以通过第二指示信息进行指示。也就是说，第一信息中除了包括第一指示信息以外还可以包括第二指示信息。例如，接入网设备发送的会话建立响应消息中还包括第二指示信息，第二指示信息用于指示上述交叠区域不被第一区域会话接受的原因，或者说第二指示信息用于指示上述交叠区域未被包括在第一区域会话对应的区域内的原因。该原因具体可以是：针对同一MBS会话(即上述第一MBS会话)，请求建立的第一区域会话所对应的区域与已经建立的区域会话所对应的区域存在交叠。或者，该原因具体为：请求建立的第一区域会话所对应的区域中存在与已经建立的区域会话所对应的MBS服务区域发生交叠的区域。应理解，第二指示信息也可以称为原因信息或原因值。
一种可能的实现方式中，接入网设备发送的会话建立响应消息中还包括第一区域会话的标识，用以表明该会话建立响应消息是针对第一区域会话的会话建立响应消息。
一种可能的实现方式中，接入网设备发送的会话建立响应消息中还包括第一MBS会话的标识，用以表明请求建立的第一区域会话属于第一MBS会话，或者说第一区域会话是第一MBS关联的一个区域会话。
一种可能的实现方式中，接入网设备发送的会话建立响应消息可以是Namf_MBSBroadcast_ContextCreate Response消息。
步骤708：AMF从接入网设备接收到会话建立响应消息后，向MB-SMF发送会话建立响应消息。
一种可能的实现方式中，AMF发送的会话建立响应消息中包括上述第一信息。
一种可能的实现方式中，AMF发送的会话建立响应消息中还包括第一区域会话的标识，用以表明该会话建立响应消息是针对第一区域会话的会话建立响应消息。
一种可能的实现方式中，AMF发送的会话建立响应消息中还包括第一MBS会话的标识，用以表明请求建立的第一区域会话属于第一MBS会话，或者说第一区域会话是第一MBS关联的一个区域会话。
一种可能的实现方式中，AMF发送的会话建立响应消息可以是Namf_MBSBroadcast_ContextCreate Response消息。
步骤709：MB-SMF从AMF接收到会话建立响应消息后，向NEF发送会话建立响应消息。
一种可能的实现方式中，MB-SMF发送的会话建立响应消息中包括上述第一信息。
一种可能的实现方式中，MB-SMF发送的会话建立响应消息中还包括第一区域会话的标识，用以表明该会话建立响应消息是针对第一区域会话的会话建立响应消息。
一种可能的实现方式中，MB-SMF发送的会话建立响应消息中还包括第一MBS会话的标识，用以表明请求建立的第一区域会话属于第一MBS会话，或者说第一区域会话是第一MBS关联的一个区域会话。
一种可能的实现方式中，MB-SMF发送的会话建立响应消息可以是Nmbsmf_MBSSession_StatusNotify消息。
步骤710：NEF从MB-SMF接收到会话建立响应消息后，向AF发送会话建立响应消息。
NEF发送的会话建立响应消息中包括上述交叠区域的信息和第一指示信息，可选的，还可以包括第二指示信息。
一种可能的实现方式中，NEF发送的会话建立响应消息中，交叠区域的信息与NEF接收到的会话建立响应消息中包含的交叠区域的信息相同。
另一种可能的实现方式中，如果在步骤701中，NEF从AF接收到的第一区域的信息中包括地理位置信息，则在步骤710中，NEF根据从MB-SMF接收到的交叠区域的小区标识和/或跟踪区标识获得对应的地理位置信息，并将该地理位置信息作为交叠区域的信息，携带在会话建立响应消息中发送给AF。
一种可能的实现方式中，NEF发送的会话建立响应消息中还包括第一区域会话的标识，用以表明该会话建立响应消息是针对第一区域会话的会话建立响应消息。
一种可能的实现方式中，NEF发送的会话建立响应消息中还包括第一MBS会话的标识，用以表明请求建立的第一区域会话属于第一MBS会话，或者说第一区域会话是第一MBS关联的一个区域会话。
一种可能的实现方式中，NEF发送的会话建立响应消息可以是Nnef_MBSSession_StatusNotify消息。
步骤711：AF从NEF接收到会话建立响应消息后，根据该会话建立响应消息中包括的交叠区域的信息，针对该交叠区域会话建立请求消息，用于请求建立新的会话。通过该会话建立请求消息可以发起新的会话的建立过程，通过新的会话可以传输第一数据。
一种可能的实现方式中，AF可以发起第二MBS会话的建立过程，第二MBS会话为普通MBS会话，或者说第二MBS会话为非位置相关MBS业务的会话。例如，AF发送会话建立请求消息，该会话建立请求消息中包括上述交叠区域的信息，该会话建立请求消息用于请求建立第二MBS会话，第二MBS会话用于向该交叠区域内的终端设备发送上述第一数据。第二MBS会话的标识与第一MBS会话的标识不同，第二MBS会话对应的MBS服务区域包括上述交叠区域。
另一种可能的实现方式中，AF可以发起关联于第二MBS会话的区域会话的建立过程，该第二MBS会话为位置相关的MBS业务的会话。可选的，第二MBS会话可以仅关联第一区域，或者说第二MBS会话可以仅关联一个区域会话，该区域会话对应的MBS服务区域为上述交叠区域。例如，AF发送会话建立请求消息，该会话建立请求消息中包括上述交叠区域的信息，该会话建立请求消息用于请求建立一个区域会话(为区别上述第一区域会话和第二区域会话，这里可以称为第三区域会话)，该第三区域会话是第二MBS会话关联的唯一一个区域会话，该区域会话对应的MBS服务区域为上述交叠区域，该区域会话用于向该交叠区域内的终端设备发送上述第一数据。第二MBS会话的标识与第一MBS会话的标识不同。
可选的，AF还可以向第二MBS会话的MBS服务区域内的终端设备发送服务通告消息(例如service announcement)，用以在应用层通知终端设备在第二MBS会话的MBS服务区域接收第二MBS会话的数据(即第一数据)。
服务通告消息中可以包括第二MBS会话的标识和MBS服务区域的信息(该MBS服务区域即上述交叠区域)，从而使得终端设备可以接收第二MBS会话的数据。
可选的，服务通告消息中还可以包括第一MBS会话的标识和MBS服务区域的信息(该MBS服务区域包括上述交叠区域)，从而使得终端设备可以接收第一MBS会话的数据。
可选的，服务通过消息中还可以包括业务标识信息，例如，业务所对应的IP地址信息，例如IP五元组，或者业务对应的应用标识(APP ID)等。
处于交叠区域的终端设备接收到上述服务通过消息后，可以根据该服务通过消息接收第一MBS会话的数据(即第二数据)和第二MBS会话的数据(即第一数据)。
另一种可能的实现方式中，AF可以分别针对上述第一区域内与第二区域交叠的区域内的每个终端设备，发起会话建立过程，从而分别与这些终端设备建立单播会话，通过单播方式将第一区域会话对应的数据发送给上述交叠区域内的终端设备。
应理解，上述图7所示流程中的消息名称仅为一种可能的示例，本申请对消息名称不做限制。例如，会话建立请求消息可以用“第一请求消息”代替，会话建立响应消息可以用“第一响应消息”代替。
还应理解，上述图7所示的流程中，第一信息的发送方式仅为一种可能的示例，本申请对此不作限制。比如第一信息可以包括在会话建立响应消息中，会话建立响应消息也可以被看做是第一信息。
在另外的情况下，如果第一区域和第二区域不存在交叠的区域，则接入网设备建立第一区域会话，第一区域会话对应的区域为第一区域。基于第一区域会话，接入网设备从核心网获得第一MBS业务的第一数据，并将该第一数据以广播或多播方式发送给第一区域内的终端设备；基于第二区域会话，接入网设备从核心网获得第一MBS业务的第二数据，并将该第二数据以广播或多播方式发送给第二区域内的终端设备。
基于上述图7所示的流程，针对位置相关MBS业务，在请求建立的区域会话所对应的MBS服务区域与已存在的区域会话所对应的MBS服务区域发生交叠的情况下，可以针对该交叠区域建立新的会话，以传输所请求传输的第一数据，从而可以在该交叠区域既传输原有区域会话对应的第二数据，还可以传输新的会话对应的第一数据，进而可以实现在同一区域发送不同的数据。
如图8所示，第一区域会话和第二区域会话是第一MBS会话关联的两个不同的区域会话。第二区域会话为已建立的区域会话，其对应的MBS服务区域如图中所示的第二区域802。在针对第二区域802已经建立有第二区域会话用来传输第一MBS会话的第二数据的情况下，若针对第一区域801请求建立第一区域会话以用来传输第一MBS会话的第一数据，则第一区域会话对应的区域中不包括第一区域801和第二区域802的交叠区域803。针对交叠区域803可以建立第二MBS会话以用来传输第一数据。这样，在上述交叠区域803内的终端设备，既可以接收第一数据也可以接收第二数据，从而满足业务需求。
本申请实施例提供的另一种通信方法中，针对同一MBS会话，在当前请求建立第一区域会话的情况下，如果当前请求建立的第一区域会话所对应的第一区域与已建立的第二区域会话所对应的第二区域存在交叠，则接入网设备可以反馈区域会话建立失败信息，并指示出失败原因，以便内容提供方(即MBS服务器，例如AF等)根据该失败原因进行相应处理，例如针对该交叠区域建立新的会话，从而可以在该交叠区域传输与第一区域会话对应的数据相同的数据，进而可以实现在该交叠区域能够传输同一MBS会话的不同数据。
其中，第一MBS会话可以关联多个区域会话，第一区域会话和第二区域会话是第一MBS关联的区域会话，或者说第一区域会话和第二区域会话属于第一MBS会话。第一区域会话对应的服务区域和第二区域会话对应的服务区域在第一MBS会话对应的服务区域内。
基于图1或图2所示的架构，参见图9，为本申请实施例提供的通信方法的流程示意图，如图9所示，该流程可以包括以下步骤：
步骤901：AF向NEF发送会话建立请求消息，该会话建立请求消息用于请求建立第一区域会话。
该步骤的具体实现方式可以参考图7中的步骤701。
步骤902：NEF从AF接收到会话建立请求消息后，向MB-SMF发送会话建立请求消息，该会话建立请求消息用于请求建立第一区域会话。
该步骤的具体实现方式可以参考图7中的步骤702。
步骤903：MB-SMF从NEF接收到会话建立请求消息后，向AMF发送会话建立请求消息，该会话建立请求消息用于请求建立第一区域会话。
该步骤的具体实现方式可以参考图7中的步骤703。
步骤904：AMF从MB-SMF接收到会话建立请求消息后，向接入网设备发送会话建立请求消息，该会话建立请求消息用于请求建立第一区域会话。
该步骤的具体实现方式可以参考图7中的步骤704。
步骤905：接入网设备从AMF接收到会话建立请求消息后，根据该会话建立请求消息中包括的第一区域的信息，确定第一区域与第二区域存在交叠。
其中，第二区域为第一MBS会话关联的第二区域会话对应的服务区域，第二区域会话用于向第二区域内的终端设备发送第一MBS业务的第二数据，通过第一区域会话发送的第一数据与通过第二区域会话发送的第二数据不同。也就是说，针对同一MBS会话关联的第一区域会话和第二区域会话，当前请求建立的第一区域会话对应的第一区域，与已建立的第二区域会话对应的第二区域存在交叠。
由于第二区域会话为已建立的区域会话，因此接入网设备保存有第二区域会话的上下文信息，该上下文信息中包括第二区域会话对应的第二区域的信息。接入网设备可以根据接收到的会话建立请求消息中包含的第一区域的信息以及该接入网设备所保存的第二区域会话的上下文信息中包含的第二区域的信息，确定第一区域和第二区域是否存在交叠。
本申请实施例中，第一区域和第二区域存在交叠，可以理解为：第一区域和第二区域存在部分交叠，或第一区域和第二区域重合。
示例性的，“第一区域和第二区域存在交叠”具体可以包括以下情况：
情况1：第一区域的部分和第二区域的部分存在重合。例如，第一区域包括小区A和小区B，第二区域包括小区A和小区C，则第一区域和第二区域的交叠区域为小区A。
情况2：第一区域大于第二区域，且第二区域完全落入第一区域内。例如，第一区域包括小区A和小区B，第二区域包括小区A，则第一区域和第二区域的交叠区域为小区A。
情况3：第一区域小于第二区域，且第一区域完全落入第二区域内。例如，第一区域包括小区A，第二区域包括小区A和小区B，则第一区域和第二区域的交叠区域为小区A。
情况4：第一区域和第二区域完全重合。例如，第一区域包括小区A和小区B，第二区域也包括小区A和小区B，则第一区域和第二区域的交叠区域为小区A和小区B。
步骤906：接入网设备向AMF发送会话建立响应消息，该会话建立响应消息指示第一区域会话建立失败。
一种可能的实现方式中，该会话建立响应消息中包括第一区域会话建立失败的原因和/或处理建议。
可选的，上述第一区域会话建立失败的原因可以通过指示信息(或称原因值)来指示。
可选的，上述处理建议可以通过相应的指示信息来指示。
可选的，可以将会话建立失败的原因的指示信息和处理建议的指示信息联合编码，也就是说，可以通过一个指示信息指示第一区域会话建立失败的原因和处理建议。
一种可能的实现方式中，失败原因的指示信息(原因值)所指示的失败原因为：无法建立位置相关的MBS业务的会话。由于第一区域和第二区域存在交叠，因此接入网设备拒绝针对第一区域建立第一区域会话。
一种可能的实现方式中，失败原因的指示信息(原因值)所指示的失败原因为：请求建立的第一区域会话所对应的第一区域中包括NTN类型的区域，例如NTN小区和/或NTN跟踪区。
可选的，一些实施例中，可以预先设置小区标识和小区类型的对应关系信息。换言之，该对应关系信息可以针对单个小区，指示出该小区是否是NTN类型的小区。这样接入网设备可以根据接收到的会话建立请求消息中的第一区域的信息中包含的小区标识查询该对应关系信息，从而确定第一区域会话所对应的第一区域中是否包括NTN小区。类似的，可以预先设置跟踪区标识和跟踪区类型的对应关系信息，这样接入网设备可以根据接收到的会话建立请求消息中的第一区域的信息中包含的跟踪区标识查询该对应关系信息，从而确定第一区域会话所对应的第一区域中是否包括NTN跟踪区。
可选的，另一些实施例中，可以预先设置映射小区的小区标识(mapped cell ID)和空口小区的小区标识(Uu cell ID)的对应关系信息，这样接入网设备可以根据接收到的会话建立请求消息中的第一区域的信息中包含的mapped cell ID查询该对应关系信息，从而确定第一区域会话所对应的第一区域中是否包括NTN小区。类似的，可以预先设置映射跟踪区标识(mapped TAI)和NTN跟踪区标识的对应关系信息，这样接入网设备可以根据接收到的会话建立请求消息中的第一区域的信息中包含的mapped TAI查询该对应关系信息，从而确定第一区域会话所对应的第一区域中是否包括NTN跟踪区。
可以将上述对应关系信息配置在接入网设备上；也可以将上述对应关系信息配置在接入网设备可以访问的其他设备上，接入网设备可以从该其他设备获得上述对应关系信息，或者接入网设备请求该其他设备基于该对应关系信息确定当前请求建立的第一区域会话所对应的第一区域中包括NTN小区。
另一种可能的实现方式中，失败原因的指示信息(原因值)所指示的失败原因为：针对第一MBS会话，请求建立的第一区域会话对应的第一区域，与另一区域会话所对应的区域存在交叠。
一种可能的实现方式中，处理建议的指示信息所指示的处理方式为：针对重叠区域，建议建立非位置相关的MBS业务的会话，该非位置相关的MBS业务的会话的MBS服务区域为第一区域。
另一种可能的实现方式中，处理建议的指示信息所指示的处理方式为：建立位置相关的MBS业务的会话，该位置相关的MBS业务的会话的MBS服务区域为第一区域。可选的，该位置相关的MBS业务的会话仅关联第一区域，或者说该位置相关的MBS会话仅关联一个区域会话，该区域会话对应的MBS服务区域为第一区域。
另一种可能的实现方式中，处理建议的指示信息所指示的处理建议为：分别针对第一区域内的终端设备建立单播会话，所述单播会话用于传输第一数据。也就是说，分别针对第一区域内的每个终端设备，发起会话建立过程，从而通过单播方式将第一数据发送给终端设备。
一种可能的实现方式中，在NTN场景中，接入网设备发送的会话建立响应消息中包括第一区域的信息。例如，第一区域的信息可以包括NTN小区的标识和/或NTN跟踪区的标识。接入网设备在接收到会话建立请求消息后，可以根据该会话建立请求消息中第一区域的信息中的映射小区的小区标识，获得对应的NTN小区的标识，并将该NTN小区的标识携带在会话建立响应消息中。类似的，接入网设备在接收到会话建立请求消息后，可以根据该会话建立请求消息中第一区域的信息中的映射跟踪区的标识，获得对应的NTN跟踪区的标识，并将该NTN跟踪区的标识携带在会话建立响应消息中。
可选的，在会话建立响应消息中包括上述第一区域的信息的基础上，该会话建立响应消息中还可以包括上述第一区域会话建立失败的原因和/或处理建议。
一种可能的实现方式中，接入网设备发送的会话建立响应消息中还包括第一区域会话的标识，用以表明该会话建立响应消息是针对第一区域会话的会话建立响应消息。
一种可能的实现方式中，接入网设备发送的会话建立响应消息中还包括第一MBS会话的标识，用以表明请求建立的第一区域会话属于第一MBS会话，或者说第一区域会话是第一MBS关联的一个区域会话。
一种可能的实现方式中，接入网设备发送的会话建立响应消息可以是Namf_MBSBroadcast_ContextCreate Response消息。
步骤907：AMF从接入网设备接收到会话建立响应消息后，向MB-SMF发送会话建立响应消息。
可选的，该会话建立响应消息中包括上述第一区域会话建立失败的原因和/或处理建议。
一种可能的实现方式中，AMF发送的会话建立响应消息中还包括上述第一区域的信息。例如，第一区域的信息可以包括NTN小区的标识和/或NTN跟踪区的标识。
一种可能的实现方式中，AMF发送的会话建立响应消息中还包括第一区域会话的标识，用以表明该会话建立响应消息是针对第一区域会话的会话建立响应消息。
一种可能的实现方式中，AMF发送的会话建立响应消息中还包括第一MBS会话的标识，用以表明请求建立的第一区域会话属于第一MBS会话，或者说第一区域会话是第一MBS关联的一个区域会话。
一种可能的实现方式中，AMF发送的会话建立响应消息可以是Namf_MBSBroadcast_ContextCreate Response消息。
步骤908：MB-SMF从AMF接收到会话建立响应消息后，向NEF发送会话建立响应消息。
可选的，该会话建立响应消息中包括上述第一区域会话建立失败的原因和/或处理建议。
一种可能的实现方式中，MB-SMF发送的会话建立响应消息中还包括上述第一区域的信息。例如，第一区域的信息可以包括NTN小区的标识和/或NTN跟踪区的标识。
一种可能的实现方式中，MB-SMF发送的会话建立响应消息中还包括第一区域会话的标识，用以表明该会话建立响应消息是针对第一区域会话的会话建立响应消息。
一种可能的实现方式中，MB-SMF发送的会话建立响应消息中还包括第一MBS会话的标识，用以表明请求建立的第一区域会话属于第一MBS会话，或者说第一区域会话是第一MBS关联的一个区域会话。
一种可能的实现方式中，MB-SMF发送的会话建立响应消息可以是Nmbsmf_MBSSession_StatusNotify消息。
步骤909：NEF从MB-SMF接收到会话建立响应消息后，向AF发送会话建立响应消息。
可选的，该会话建立响应消息中包括上述第一区域会话建立失败的原因和/或处理建议。
一种可能的实现方式中，NEF发送的会话建立响应消息中还包括上述第一区域的信息。例如，第一区域的信息可以包括NTN小区的标识和/或NTN跟踪区的标识。
可选的，如果在步骤701中，NEF从AF接收到的第一区域的信息为地理位置信息，则在步骤909中，NEF根据上述NTN小区的标识和/或NTN跟踪区的标识，获得对应的地理位置信息，并将该地理位置信息作为第一区域的信息携带在会话建立响应消息中发送给AF。
一种可能的实现方式中，NEF发送的会话建立响应消息中还包括第一区域会话的标识，用以表明该会话建立响应消息是针对第一区域会话的会话建立响应消息。
一种可能的实现方式中，NEF发送的会话建立响应消息中还包括第一MBS会话的标识，用以表明请求建立的第一区域会话属于第一MBS会话，或者说第一区域会话是第一MBS关联的一个区域会话。
一种可能的实现方式中，NEF发送的会话建立响应消息可以是Nnef_MBSSession_StatusNotify消息。
上述流程中，针对第一区域和第二区域存在交叠的情况，接入网设备可以拒绝建立第一区域会话，这样就可以避免对已建立的第二区域会话造成影响，以保证第二区域(包括交叠区域)内的终端设备依然可以接收第二数据。
在一些实施例中，接入网设备可以将第一区域会话建立失败的原因和/或处理建议反馈给AF或MBS服务器，从而可以使AF或MBS服务器进行相应处理。
通过上述实现方式在避免对原有区域会话造成影响的基础上，本申请的一些实施例中，还可以针对上述第一区域建立新的会话用来传输第一数据，用以保证该交叠区域内的终端设备既可以接收第二数据还可以接收第一数据，从而满足业务需求。
仍以图9所示的流程为例，一种可能的实现方式中，上述图9所示的流程还可以包括以下步骤：
步骤910：AF从NEF接收到会话建立响应消息后，根据该会话建立响应消息中包括的信息(例如第一区域会话建立失败的原因和/或处理建议，和/或上述第一区域的信息)，针对第一区域发起新的会话的建立过程，通过新的会话传输第一数据。
一种可能的实现方式中，AF可以发起第二MBS会话的建立过程，第二MBS会话为普通MBS会话，或者说第二MBS会话为非位置相关MBS业务的会话。例如，AF发送会话建立请求消息，该请求消息中包括上述第一区域的信息，该会话建立请求消息用于请求建立第二MBS会话，第二MBS会话用于向第一区域内的终端设备发送上述第一数据。第二MBS会话的标识与第一MBS会话的标识不同，第二MBS会话对应的MBS服务区域包括上述第一区域。这样，当接入网设备接收到用于请求建立第二MBS会话的会话建立请求消息后，可以建立第二MBS会话，并可以在第二MBS会话的MBS服务区域(即第一区域)内发送第一数据。
另一种可能的实现方式中，AF可以发起关联于第二MBS会话的区域会话的建立过程，该第二MBS会话为位置相关的MBS业务的会话，该区域会话对应的MBS服务区域为第一区域。可选的，第二MBS会话仅关联第一区域，或者说第二MBS会话仅关联一个区域会话。例如，AF发送会话建立请求消息，该请求消息中包括上述第一区域的信息，该会话建立请求消息用于请求建立一个区域会话(为区别上述第一区域会话和第二区域会话，这里可以称为第三区域会话)，该区域会话是第二MBS会话关联的唯一一个区域会话，该区域会话对应的MBS服务区域为上述第一区域，该区域会话用于向该第一区域内的终端设备发送上述第一数据。第二MBS会话的标识与第一MBS会话的标识不同。这样，当接入网设备接收到用于请求建立该第三区域会话的会话建立请求消息后，可以建立相应的区域会话，并可以在该区域会话的MBS服务区域(即第一区域)内发送第一数据。
可选的，AF还可以向第二MBS会话的MBS服务区域内的终端设备发送服务通告消息(例如service announcement)，用以在应用层通知终端设备在第二MBS会话的MBS服务区域接收第二MBS会话的数据(即第一数据)以及在第一MBS会话的MBS服务区域接收第一MBS会话的数据。服务通告消息中可以包括第二MBS会话的标识和MBS服务区域的信息，以及包括第一MBS会话的标识和MBS服务区域的信息，从而使得终端设备可以接收第二MBS会话的数据和第一MBS会话的数据。
本申请实施例中，根据会话建立响应消息中包括的信息，针对第一区域发起新的会话的建立过程的实现方式可以包括以下几种：
方式1：
会话建立响应消息中包括用于指示第一区域会话建立失败的原因的第一原因值，该第一原因值所指示的失败原因为：无法建立位置相关的MBS业务的会话。
根据该失败原因，AF可以尝试针对第一区域建立非位置相关的MBS业务的会话。具体实现方式可以参考前文描述。
可选的，在该实现方式中，AF在针对第一区域建立非位置相关的MBS业务的会话之前，可以分析失败原因，并根据失败原因确定对应的处理方式。例如，AF可以获取第一MBS会话关联的其他区域会话对应的MBS服务区域，并确定第一区域与该其他区域会话对应的MBS服务区域是否存在交叠，如果存在交叠，则可以确定针对第一区域建立非位置相关的MBS业务的会话。
方式2：
在NTN场景下，会话建立响应消息中包括用于指示第一区域会话建立失败的原因的第二原因值，该第二原因值所指示的失败原因为：请求建立的第一区域会话所对应的第一区域中包括NTN类型的区域。
根据该失败原因，AF可以尝试建立非位置相关的MBS业务的会话。或者，AF也可以建立位置相关的MBS业务的会话，可选的，该位置相关的MBS业务的会话仅关联第一区域，或者说该位置相关的MBS会话仅关联一个区域会话。该区域会话对应的MBS服务区域为第一区域。具体实现方式可以参考前文描述。
可选的，该实现方式中，由于第二原因值指示出当前请求建立的第一区域会话所对应的第一区域中包括NTN类型的区域，因此AF可以确定第一区域会话的失败原因可能是在NTN场景下，第一区域与同一MBS会话关联的其他区域会话所对应的MBS服务区域之间存在交叠所导致的，因此可以确定针对第一区域建立非位置相关的MBS业务的会话，或者建立位置相关的MBS业务的会话。
相比于上述方式1，由于方式2中的原因值所指示的失败原因其信息量较多，或者说给出的失败原因更具体，这样可以降低AF的处理逻辑，提供AF的处理灵活性，有助于AF采用适合的方式进行处理。
方式3：
在NTN场景下，会话建立响应消息中包括用于指示第一区域会话建立失败的原因的第二原因值以及第一区域的信息。
根据该失败原因，AF可以尝试建立非位置相关的MBS业务的会话。或者，AF也可以建立位置相关的MBS业务的会话，且该位置相关的MBS业务的会话仅关联第一区域，或者说该位置相关的MBS会话仅关联一个区域会话，该区域会话对应的MBS服务区域为第一区域。
与上述方式2类似，由于第二原因值指示出当前请求建立的第一区域会话所对应的第一区域中包括NTN类型的区域，因此AF可以确定第一区域会话的失败原因可能是在NTN场景下，第一区域与同一MBS会话关联的其他区域会话所对应的MBS服务区域之间存在交叠所导致的，因此可以确定针对第一区域建立非位置相关的MBS业务的会话，或者建立位置相关的MBS业务的会话。
方式4：会话建立响应消息中包括用于指示第一区域会话建立失败的原因的第三原因值，该第三原因值所指示的失败原因为：当前请求建立的第一区域会话对应的第一区域，与关联于同一MBS会话的另一区域会话所对应的MBS服务区域存在交叠。
根据该失败原因，AF可以尝试建立非位置相关的MBS业务的会话。或者，AF也可以建立位置相关的MBS业务的会话，且该位置相关的MBS业务的会话仅关联第一区域，或者说该位置相关的MBS会话仅关联一个区域会话，该区域会话对应的MBS服务区域为第一区域。
可选的，该实现方式中，由于第三原因值指示出当前请求建立的第一区域会话对应的第一区域，与关联于同一MBS会话的另一区域会话所对应的MBS服务区域存在交叠，因此AF可以无需进行失败原因分析，即可确定针对第一区域建立非位置相关的MBS业务的会话，或者建立位置相关的MBS业务的会话。
相比于上述方式1或上述方式2或上述方式3，由于方式4中的原因值所指示的失败原因其信息量更多，或者说给出的失败原因更具体，这样可以降低AF的处理逻辑，提供AF的处理灵活性，有助于AF采用适合的方式进行处理。
方式5：
会话建立响应消息中包括处理建议的指示信息，该处理建议为：建议建立普通MBS会话，也即建立非位置相关的MBS业务的会话。
根据该处理建议，AF可以建立非位置相关的MBS业务的会话。
相比于上述方式1，由于方式5中的会话建立响应消息中给出了处理建议，因此AF可以根据该处理建议执行相应的处理，从而可以降低AF的处理逻辑。
方式6：
在NTN场景下，会话建立响应消息中包括第一区域的信息。
根据该失败原因，AF可以尝试建立非位置相关的MBS业务的会话。或者，AF也可以建立位置相关的MBS业务的会话，且该位置相关的MBS业务的会话仅关联第一区域，或者说该位置相关的MBS会话仅关联一个区域会话，该区域会话对应的MBS服务区域为第一区域。
可选的，该实现方式中，由于会话建立响应消息中包括第一区域的信息，该第一区域为NTN类型的区域，例如NTN小区的标识和/或NTN跟踪区的标识，因此AF可以确定第一区域会话的失败原因可能是在NTN场景下，第一区域与同一MBS会话关联的其他区域会话所对应的MBS服务区域之间存在交叠所导致的，因此可以确定针对第一区域建立非位置相关的MBS业务的会话，或者建立位置相关的MBS业务的会话。
相比于上述方式1，由于方式6中会话建立响应消息中的信息量较多，这样可以降低AF的处理逻辑，提供AF的处理灵活性，有助于AF采用适合的方式进行处理。
应理解，以上仅示例性示出了可能的几种处理方式，本申请对此不作限制。
上述流程中，接入网设备仍可以通过第二区域会话从核心网接收第一MBS业务的第二数据，并将该第二数据发送给第二区域内(包括交叠区域)的终端设备。
在另外的情况下，如果第一区域和第二区域不存在交叠区域，则接入网设备建立第一区域会话，第一区域会话对应的区域为第一区域。基于第一区域会话，接入网设备从核心网获得第一MBS业务的第一数据，并将该第一数据以广播或多播方式发送给第一区域内的终端设备；基于第二区域会话，接入网设备从核心网获得第一MBS业务的第二数据，并将该第二数据以广播或多播方式发送给第二区域内的终端设备。
基于上述图9所示的流程，针对位置相关MBS业务，在因请求建立的区域会话所对应的MBS服务区域与已存在的区域会话所对应的MBS服务区域发生交叠而导致当前请求的区域会话建立失败的情况下，可以针对该区域建立新的会话，MB-SMF向AMF发送会话建立请求消息，AMF向接入网设备发送会话建立请求消息，以传输所请求传输的第一数据，从而可以在该交叠区域既传输原有区域会话对应的第二数据，还可以传输新的会话对应的第一数据，进而可以实现在同一区域发送不同的数据。
如图10所示，第一区域会话和第二区域会话是第一MBS会话关联的两个不同的区域会话。第二区域会话为已建立的区域会话，其对应的MBS服务区域如图中所示的第二区域1002。在针对第二区域1002已经建立有第二区域会话用来传输第一MBS会话的第二数据的情况下，若AF针对第一区域1001请求建立第一区域会话以用来传输第一MBS会话的第一数据，则由于第一区域1001和第二区域1002存在交叠，接入网设备拒绝建立第一区域会话。AF可以针对第一区域1001发起第二MBS会话的建立流程，从而建立第二MBS会话，第二MBS会话对应的区域为第一区域1001。这样，交叠区域1003内的终端设备，可以基于第二区域会话接收第二数据，并可以基于第二MBS会话接收第一数据，从而满足业务需求。
本申请实施例提供的另一种通信方法中，针对同一MBS会话，在当前请求建立第一区域会话的情况下，如果当前请求建立的第一区域会话所对应的第一区域与已建立的第二区域会话所对应的第二MBS服务区域存在交叠，则NEF可以反馈区域会话建立失败信息，并指示出失败原因，以便内容提供方(即MBS服务器，例如AF等)根据该失败原因进行相应处理，例如针对该交叠区域建立新的会话，从而可以在该交叠区域传输与第一区域会话对应的数据相同的数据，进而可以实现在该交叠区域能够传输同一MBS会话的不同数据。
其中，第一MBS会话可以关联多个区域会话，第一区域会话和第二区域会话是第一MBS关联的区域会话，或者说第一区域会话和第二区域会话属于第一MBS会话。第一区域会话对应的服务区域和第二区域会话对应的服务区域在第一MBS会话对应的服务区域内。
基于图1或图2所示的架构，参见图11，为本申请实施例提供的通信方法的流程示意图，如图11所示，该流程可以包括以下步骤：
步骤1101：AF向NEF发送会话建立请求消息，该会话建立请求消息用于请求建立第一区域会话。
该步骤的具体实现方式可以参考图7中的步骤701。
步骤1102：NEF从AF接收到会话建立请求消息后，确定第一区域中包括NTN类型的区域，例如，确定第一区域中包括NTN小区和/或NTN跟踪区。
一种可能的实现方式中，可以预先设置第一对应关系信息，第一对应关系信息包括小区标识和小区类型的对应关系信息。换言之，该对应关系信息可以针对单个小区，指示出该小区是否是NTN类型的小区。这样NEF可以根据接收到的会话建立请求消息中的第一区域的信息中包含的小区标识查询该对应关系信息，从而确定第一区域会话所对应的第一区域中是否包括NTN小区。
类似的，第一对应关系信息中还可以包括跟踪区标识和跟踪区类型的对应关系信息。也就是说，可以预先设置跟踪区标识和跟踪区类型的对应关系信息，这样NEF可以根据接收到的会话建立请求消息中的第一区域的信息中包含的跟踪区标识查询该对应关系信息，从而确定第一区域会话所对应的第一区域中是否包括NTN跟踪区。
另一种可能的实现方式中，可以预先设置第二对应关系信息，第二对应关系信息包括映射小区的小区标识(mapped cell ID)和空口小区的小区标识(Uu cell ID)的对应关系信息，这样NEF可以根据接收到的会话建立请求消息中的第一区域的信息中包含的mapped cell ID查询该对应关系信息，从而确定第一区域会话所对应的第一区域中是否包括NTN小区。
类似的，第二对应关系信息中还可包括映射跟踪区标识(mapped TAI)和NTN跟踪区标识的对应关系信息。也就是说，可以预先设置映射跟踪区标识(mapped TAI)和NTN跟踪区标识的对应关系信息，这样NEF可以根据接收到的会话建立请求消息中的第一区域的信息中包含的mapped TAI查询该对应关系信息，从而确定第一区域会话所对应的第一区域中是否包括NTN跟踪区。
在一种实现的方式中，可以将上述对应关系信息配置在NEF上。
在另一种实现的方式中，可以将上述对应关系信息配置在NRF或者UDM中，NEF可以向NRF查询从而获取对应关系，或者获取第一区域中是否包括NTN小区的信息。
步骤1103：NEF向AF发送会话建立响应消息，该会话建立响应消息用于指示第一区域会话建立失败。
一种可能的实现方式中，该会话建立响应消息中包括第一区域会话建立失败的原因和/或处理建议。失败原因和处理建议的相关描述可以参考图9中的步骤906中的相关内容。
一种可能的实现方式中，在NTN场景中，NEF发送的会话建立响应消息中包括第一区域的信息。例如，第一区域的信息可以包括NTN小区的标识和/或NTN跟踪区的标识。NEF在接收到会话建立请求消息后，可以根据该会话建立请求消息中第一区域的信息中的映射小区的小区标识，获得对应的NTN小区的标识，并将该NTN小区的标识携带在会话建立响应消息中。类似的，NEF在接收到会话建立请求消息后，可以根据该会话建立请求消息中第一区域的信息中的映射跟踪区的标识，获得对应的NTN跟踪区的标识，并将该NTN跟踪区的标识携带在会话建立响应消息中。
可选的，在会话建立响应消息中包括上述第一区域的信息的基础上，该会话建立响应消息中还可以包括上述第一区域会话建立失败的原因和/或处理建议。
一种可能的实现方式中，NEF发送的会话建立响应消息中还包括第一区域会话的标识，用以表明该会话建立响应消息是针对第一区域会话的会话建立响应消息。
一种可能的实现方式中，NEF发送的会话建立响应消息中还包括第一MBS会话的标识，用以表明请求建立的第一区域会话属于第一MBS会话，或者说第一区域会话是第一MBS关联的一个区域会话。
一种可能的实现方式中，NEF发送的会话建立响应消息可以是Nnef_MBSSession_Create response消息，或者是Nnef_MBSSession_StatusNotify消息。
步骤1104：AF从NEF接收到会话建立响应消息后，根据该会话建立响应消息中包括的信息(例如第一区域会话建立失败的原因和/或处理建议，和/或上述第一区域的信息)，针对第一区域发起新的会话的建立过程，通过新的会话传输第一数据。
该步骤的具体实现方式可以参考图9中的步骤910。
在另外的情况下，如果NEF确定第一区域中不包括NTN类型的区域，则可以继续执行后续的会话建立流程，例如向MB-SMF发送会话建立请求消息，以使得接入网设备建立第一区域会话，第一区域会话对应的区域为第一区域。基于第一区域会话，接入网设备从核心网获得第一MBS业务的第一数据，并将该第一数据以广播或多播方式发送给第一区域内的终端设备；基于第二区域会话，接入网设备从核心网获得第一MBS业务的第二数据，并将该第二数据以广播或多播方式发送给第二区域内的终端设备。
基于上述图11所示的流程，针对位置相关MBS业务，在当前请求建立的第一区域会话对应的第一区域中包括NTN类型的区域的情况下，可能存在请求建立的区域会话所对应的MBS服务区域与已存在的区域会话所对应的MBS服务区域发生交叠而导致当前请求的区域会话建立失败，为此AF可以针对该区域建立新的会话，以传输所请求传输的第一数据，从而可以在该交叠区域既传输原有区域会话对应的第二数据，还可以传输新的会话对应的第一数据，进而可以实现在同一区域发送不同的数据。
另一方面，相比于图9所示的流程，采用图11所示的方法可以减少信令交互，使得AF可以更快地响应会话建立失败信息进行相应处理，从而可以降低MBS业务的处理时延。
本申请实施例提供的另一种通信方法中，针对同一MBS会话，在当前请求建立第一区域会话的情况下，如果当前请求建立的第一区域会话所对应的第一区域与已建立的第二区域会话所对应的第二MBS服务区域存在交叠，则NEF可以反馈区域会话建立失败信息，并指示出失败原因，以便内容提供方(即MBS服务器，例如AF等)根据该失败原因进行相应处理，例如针对该交叠区域建立新的会话，从而可以在该交叠区域传输与第一区域会话对应的数据相同的数据，进而可以实现在该交叠区域能够传输同一MBS会话的不同数据。
其中，第一MBS会话可以关联多个区域会话，第一区域会话和第二区域会话是第一MBS关联的区域会话，或者说第一区域会话和第二区域会话属于第一MBS会话。第一区域会话对应的服务区域和第二区域会话对应的服务区域在第一MBS会话对应的服务区域内。
基于图1或图2所示的架构，参见图12，为本申请实施例提供的通信方法的流程示意图。与图11所示的方法不同的是，NEF通过与其他网元交互来获得区域会话建立失败信息，可选的，还可以获得失败原因和/或处理建议。
如图12所示，该流程可以包括以下步骤：
步骤1201：AF向NEF发送会话建立请求消息，该会话建立请求消息用于请求建立第一区域会话。
该步骤的具体实现方式可以参考图7中的步骤701。
步骤1202：NEF从AF接收到会话建立请求消息后，向NRF发送第一消息，该第一消息用于请求反馈是否允许针对第一区域建立第一区域会话。
可选的，第一消息中包括第一区域的信息。
一种可能的实现方式中，NEF可以通过调用NRF的Nnrf_NFDiscovery_Request Request服务，向NRF发送第一消息。
步骤1203：NRF向NEF发送第二消息，第二消息指示无法针对第一区域建立第一区域会话。
一种可能的实现方式中，如果NRF确定第一区域中包括NTN类型的区域(例如NTN小区和/或NTN跟踪区)，则确定无法针对第一区域建立第一区域会话。
另一种可能的实现方式中，如果NRF确定当前请求建立的第一区域会话对应的第一区域，与关联于同一MBS会话的另一区域会话所对应的MBS服务区域存在交叠，则确定无法针对第一区域建立第一区域会话。
本申请实施例中，NRF可以采用以下几种方式确定第一区域中是否包含NTN类型的区域：
第一方式：可以在NRF上设置小区标识和小区类型的对应关系信息。换言之，该对应关系信息可以针对单个小区，指示出该小区是否是NTN类型的小区。这样NRF可以根据接收到的第一区域的信息中包含的小区标识查询该对应关系信息，从而确定第一区域中是否包括NTN小区。
类似的，可以在NRF上设置跟踪区标识和跟踪区类型的对应关系信息，这样NRF可以根据接收到的第一区域的信息中包含的跟踪区标识查询该对应关系信息，从而确定第一区域中是否包括NTN跟踪区。
上述对应关系信息独立于MB-SMF的配置信息和AMF的配置信息。
第二方式：可以在NRF上设置映射小区的小区标识(mapped cell ID)和空口小区的小区标识(Uu cell ID)的对应关系信息，这样NRF可以根据接收到的第一区域的信息中包含的mapped cell ID查询该对应关系信息，从而确定第一区域中是否包括NTN小区。
类似的，可以在NRF上设置映射跟踪区标识(mapped TAI)和NTN跟踪区标识的对应关系信息，这样NRF可以根据接收到的第一区域的信息中包含的mapped TAI查询该对应关系信息，从而确定第一区域中是否包括NTN跟踪区。
上述对应关系信息独立于MB-SMF的配置信息和AMF的配置信息。
第三方式：可以在NRF上存储的MB-SMF的配置信息(或称为NF profile)中设置映射小区的标识和NTN小区的标识的对应关系信息。NRF可以根据接收到的第一区域的信息中包含的映射小区的标识查询该对应关系信息，从而确定第一区域中是否包括NTN小区。
类似的，可以在NRF上存储的MB-SMF的配置信息(或称为NF profile)中设置映射跟踪区的标识(mapped cell ID)和空口小区的小区标识(Uu cell ID)的对应关系信息，这样NRF可以根据接收到的第一区域的信息中包含的mapped cell ID查询该对应关系信息，从而确定第一区域中是否包括NTN小区。
第四方式：可以在NRF上存储的AMF的配置信息(或称为NF profile)中设置映射小区的标识和NTN小区的标识的对应关系信息。NRF可以根据接收到的第一区域的信息中包含的映射小区的标识查询该对应关系信息，从而确定第一区域中是否包括NTN小区。
类似的，可以在NRF上存储的AMF的配置信息(或称为NF profile)中设置映射跟踪区的标识(mapped cell ID)和空口小区的小区标识(Uu cell ID)的对应关系信息，这样NRF可以根据接收到的第一区域的信息中包含的mapped cell ID查询该对应关系信息，从而确定第一区域中是否包括NTN小区。
一种可能的实现方式中，第二消息中还可以包括无法针对第一区域建立第一区域会话的原因。NRF可以确定无法针对第一区域建立第一区域会话的原因，并将该原因的指示信息(或称原因值)携带在第二消息中。
示例性的，失败原因的指示信息(原因值)所指示的失败原因为：无法建立位置相关的MBS业务的会话。由于第一区域中包括NTN类型的区域，或者由于第一区域和同一MBS会话关联的其他区域会话所对应的MBS服务区域存在交叠，因此NRF确定无法针对第一区域建立第一区域会话。
又示例性的，失败原因的指示信息(原因值)所指示的失败原因为：当前请求建立的第一区域会话所对应的第一区域中包括NTN类型的区域，例如NTN小区和/或NTN跟踪区。
再示例性的，失败原因的指示信息(原因值)所指示的失败原因为：当前请求建立的第一区域会话对应的第一区域，与关联于同一MBS会话的另一区域会话所对应的MBS服务区域存在交叠。
一种可能的实现方式中，第二消息中还可以包括处理建议。NRF在确定无法针对第一区域建立第一区域会话的情况下，可以确定建议的处理方式(即处理建议)，并将用于指示处理建议的指示信息携带在第二消息中。
示例性的，处理建议的指示信息所指示的处理方式为：针对重叠区域，建议建立非位置相关的MBS业务的会话。
又示例性的，处理建议的指示信息所指示的处理方式为：建立位置相关的MBS业务的会话，该区域会话对应的MBS服务区域为第一区域。可选的，该位置相关的MBS业务的会话仅关联第一区域，或者说该位置相关的MBS会话仅关联一个区域会话。
再示例性的，处理建议的指示信息所指示的处理建议为：分别针对第一区域内的每个终端设备，发起会话建立过程，从而通过单播方式将第一数据发送给终端设备。
应理解，第二消息中可以包括失败原因，或者包括处理建议，或者包括既包括失败原因又包括处理建议。
一种可能的实现方式中，第二消息中包括用于指示无法针对第一区域建立第一区域会话的指示信息。
一种可能的实现方式中，在NTN场景中，第二消息中包括第一区域的信息。例如，第一区域的信息可以包括NTN小区的标识和/或NTN跟踪区的标识。NRF在确定无法针对第一区域建立第一区域会话的情况下，可以根据第一区域的信息中的映射小区的小区标识获得对应的NTN小区的标识，并将该NTN小区的标识携带在第二消息中。类似的，NEF在确定无法针对第一区域建立第一区域会话的情况下，可以根据第一区域的信息中的映射跟踪区的标识获得对应的NTN跟踪区的标识，并将该NTN跟踪区的标识携带在第二消息中。
一种可能的实现方式中，第二消息中还包括第一区域会话的标识。
一种可能的实现方式中，第二消息中还包括第一MBS会话的标识。
一种可能的实现方式中，第二消息为Nnrf_NFDiscovery_Request Response消息。
步骤1204：NEF根据接收到的第二消息，向AF发送会话建立响应消息，该会话建立响应消息用于指示第一区域会话建立失败。
该步骤的具体实现方式可以参考图11中的步骤1103。
步骤1205：AF从NEF接收到会话建立响应消息后，根据该会话建立响应消息中包括的信息(例如第一区域会话建立失败的原因和/或处理建议，和/或上述第一区域的信息)，针对第一区域发起新的会话的建立过程，通过新的会话传输第一数据。
该步骤的具体实现方式可以参考图11中的步骤1104。
上述图12所示的方法中，以NEF与NRF交互为例描述。应理解，NRF可以被替换为其他网元，NEF可以通过与该其他网元进行交互来获得区域会话建立失败信息，可选的，还可以获得失败原因和/或处理建议。
在另外的情况下，如果NRF确定允许针对第一区域建立第一区域会话，则可以继续执行后续的会话建立流程，例如向MB-SMF发送会话建立请求消息，MB-SMF向AMF发送会话建立请求消息，AMF向接入网设备发送会话建立请求消息，以使得接入网设备建立第一区域会话，第一区域会话对应的区域为第一区域。基于第一区域会话，接入网设备从核心网获得第一MBS业务的第一数据，并将该第一数据以广播或多播方式发送给第一区域内的终端设备；基于第二区域会话，接入网设备从核心网获得第一MBS业务的第二数据，并将该第二数据以广播或多播方式发送给第二区域内的终端设备。
基于上述图12所示的流程，针对位置相关MBS业务，在当前请求建立的第一区域会话对应的第一区域中包括NTN类型的区域的情况下，可能存在请求建立的区域会话所对应的MBS服务区域与已存在的区域会话所对应的MBS服务区域发生交叠而导致当前请求的区域会话建立失败，为此AF可以针对该区域建立新的会话，以传输所请求传输的第一数据，从而可以在该交叠区域既传输原有区域会话对应的第二数据，还可以传输新的会话对应的第一数据，进而可以实现在同一区域发送不同的数据。
另一方面，相比于图9所示的流程，采用图12所示的方法可以减少信令交互，使得AF可以更快地响应会话建立失败信息进行相应处理，从而可以降低MBS业务的处理时延。
可以理解的是，为了实现上述实施例中功能，网络设备和终端设备包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本申请中所公开的实施例描述的各示例的单元及方法步骤，本申请能够以硬件或硬件和计算机软件相结合的形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用场景和设计约束条件。
图13和图14为本申请的实施例提供的可能的通信装置的结构示意图。这些通信装置可以用于实现上述方法实施例中的相关设备(例如接入网设备，或NEF，或AF)的功能，因此也能实现上述方法实施例所具备的有益效果。在本申请的实施例中，该通信装置可以是上述设备或上述设备中的模块(如芯片)。
如图13所示，通信装置1300包括处理单元1310和收发单元1320。通信装置1300用于实现上述图7、图9、图11或图12中任一附图所示的方法实施例中的相关设备的功能。
当通信装置1300用于实现图7所示的方法实施例中接入网设备的功能时：收发单元1320用于接收用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息，其中，所述第一区域与已建立的第二区域会话对应的第二区域存在交叠，所述第二区域会话用于发送第一MBS业务的第二数据；处理单元1310用于响应于所述请求消息，建立第一区域会话，所述第一区域会话对应所述第一区域中除与所述第二区域存在交叠的区域以外的其他区域，所述第一区域会话用于发送所述第一MBS业务的第一数据。
当通信装置1300用于实现图7所示的方法实施例中AF的功能时：处理单元1310用于通过收发单元1320发送用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息，其中，所述第一区域与已建立的第二区域会话对应的第二区域存在交叠，所述第二区域会话用于发送第一MBS业务的第二数据；收发单元1320用于接收第一信息，所述第一信息指示未针对所述交叠的区域建立区域会话；处理单元1310用于通过收发单元1320发送用于请求建立新的会话的请求消息，所述用于请求建立新的会话的请求消息中包括所述交叠的区域的信息，所述新的会话用于发送所述第一数据。
当通信装置1300用于实现图9所示方法实施例中接入网设备的功能时：收发单元1320用于接收用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息，所述第一区域会话用于发送第一多播广播MBS业务的第一数据；处理单元1310用于在所述第一区域与第二区域会话对应的第二区域存在交叠的情况下，通过收发单元1320发送响应消息，所述响应消息指示所述第一区域会话建立失败；其中，所述第二区域会话用于发送所述第一MBS业务的第二数据。
当通信装置1300用于实现图10所示方法实施例中NEF的功能时：收发单元1320用于接收用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息，所述第一区域会话用于发送第一MBS业务的第一数据；处理单元1310用于根据所述第一区域的信息中包含的小区标识以及对应关系信息，确定所述第一区域中包括NTN小区，和/或，根据所述第一区域的信息中包含的跟踪区的标识以及所述对应关系信息，确定所述第一区域中包括NTN跟踪区，则响应于所述第一请求消息通过收发单元1320发送响应消息，所述响应消息指示所述第一区域会话建立失败。其中，所述对应关系信息包括第一对应关系信息和第二对应关系信息中的一项，其中，所述对应关系信息包括第一对应关系信息或第二对应关系信息，所述第一对应关系信息包括小区标识和小区类型的对应关系信息，和/或跟踪区标识和跟踪区类型的对应关系信息，所述第二对应关系信息包括映射小区标识和NTN小区标识的对应关系信息，和/或，映射跟踪区标识和NTN跟踪区标识的对应关系信息。
当通信装置1300用于实现图11所示方法实施例中NEF的功能时：收发单元1320用于接收用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息，所述第一区域会话用于发送第一MBS业务的第一数据；处理单元1310用于通过收发单元1320发送第一消息，所述第一消息用于请求存储有对应关系信息的网元反馈是否允许针对第一区域建立第一区域会话，所述第一消息中包括所述第一区域的信息；处理单元1310用于通过收发单元1320从存储有所述对应关系的网元接收第二消息，所述第二消息指示无法针对第一区域建立第一区域会话，处理单元1310根据所述第二消息通过收发单元1320发送响应消息，该响应消息用于指示所述第一区域会话建立失败。
当通信装置1300用于实现图9或图11或图12所示的方法实施例中AF的功能时：处理单元1310用于通过收发单元1320发送用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息；其中，所述第一区域与已建立的第二区域会话对应的第二区域存在交叠，所述第二区域会话用于发送第一MBS业务的第二数据，所述第一区域会话用于发送所述第一MBS业务的第一数据；收发单元1320用于接收所述请求消息对应的响应消息，所述响应消息指示所述第一区域会话建立失败；处理单元1310用于通过收发单元1320发送用于请求建立新的会话的请求消息，所述用于请求建立新的会话的请求消息中包括所述交叠的区域的信息，所述新的会话用于发送所述第一数据。
有关上述处理单元1310和收发单元1320更详细的描述可以直接参考上述附图所示的方法实施例中相关描述直接得到，这里不加赘述。
本申请的一些实施例提供一种通信装置1400，该通信装置包括处理电路1410。该处理电路1410中可以包括一个或多个处理器，或一个或多个处理器中用于控制或处理功能的全部或部分电路。
该通信装置1400还可以包括通信电路1420。
其中，通信装置1400为接入网设备的情况下，通信电路1420可以为收发器或收发电路或接口电路。通信装置1400为用于接入网设备的芯片时，通信电路1420可以为收发电路或接口电路。通信装置为服务器时，通信电路可以为收发电路或接口电路。
可选的，该通信装置1400中还可以包括存储器1430。该存储器1430用于存储处理器执行的指令或存储处理器运行指令所需要的输入数据或存储处理器运行指令后产生的数据。
当通信装置1400用于实现上述附图所示的方法时，处理器用于实现上述处理单元的功能，通信电路用于实现上述收发单元的功能。
当上述通信装置1400为应用于上述设备的芯片时，该芯片实现上述方法实施例中相应设备的功能。该芯片从设备中的其它模块(如射频模块或天线)接收信息，该信息是其他设备发送给该设备的；或者，该芯片向该设备中的其它模块(如射频模块或天线)发送信息。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其它通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请中，提供通信装置的另一种示例，该通信装置包括至少一个处理器和至少一个存储器，该至少一个处理器和该至少一个存储器耦合，该至少一个存储器用于存储指令，当该指令被该至少一个处理器执行时，使得通信装置执行上述实施例中的方法。以通信装置包括一个处理器和一个存储器为例，如图15所示，通信装置1500包括一个处理器1510和一个存储器1530。处理器1510和存储器1530耦合，存储器1530中存储有指令，当存储器1530中存储的指令被处理器1510执行时，通信装置1500执行上述实施例中相关设备执行的方法。
应理解，处理器1510和存储器1530也可以集成在一起，比如集成在一个芯片中。
本申请的实施例中的方法步骤可以在硬件中实现，也可以在可由处理器执行的软件指令中实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器、闪存、只读存储器、可编程只读存储器、可擦除可编程只读存储器、电可擦除可编程只读存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于网络侧设备或终端侧设备中。处理器和存储介质也可以作为分立组件存在于网络侧设备或终端侧设备中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、服务器、网络设备、用户设备或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序或指令可以从一个网站站点、计算机、服务器或数据中心通过有线或无线方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，数字视频光盘；还可以是半导体介质，例如，固态硬盘。该计算机可读存储介质可以是易失性或非易失性存储介质，或可包括易失性和非易失性两种类型的存储介质。
本申请实施例提供了一种通信系统，该通信系统中可以包括接入网设备和AF。其中，接入网设备可以实现如图7中的接入网设备实现的方法和功能，AF可以实现如图7中AF实现的方法和功能。可选的，该通信系统中还可以包括其他网元，比如包括AMF、SMF、NEF等网元中的一个或多个。该通信系统的一种示例可以如图7所示流程所应用的系统架构。
本申请实施例还提供了一种通信系统，该通信系统中可以包括接入网设备和AF。其中，接入网设备可以实现如图9中的接入网设备实现的方法和功能，AF可以实现如图9中AF实现的方法和功能。可选的，该通信系统中还可以包括其他网元，比如包括AMF、SMF、NEF等网元中的一个或多个。该通信系统的一种示例可以如图9所示流程所应用的系统架构。
本申请实施例还提供了一种通信系统，该通信系统中可以包括NEF和AF。其中，NEF可以实现如图11或图12中的NEF实现的方法和功能，AF可以实现如图11或图12中AF实现的方法或功能。可选的，该通信系统中还可以包括其他网元，比如包括AMF、SMF、接入网设备等网元中的一个或多个。该通信系统的一种示例可以如图11或图12所示流程所应用的系统架构。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A,B可以是单数或者复数。在本申请的文字描述中，字符“/”，一般表示前后关联对象是一种“或”的关系；在本申请的公式中，字符“/”，表示前后关联对象是一种“相除”的关系。“包括A，B和C中的至少一个”可以表示：包括A；包括B；包括C；包括A和B；包括A和C；包括B和C；包括A、B和C。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。

Claims (47)

  1. 一种通信方法，其特征在于，所述方法包括：
    接收用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息；其中，所述第一区域与已建立的第二区域会话对应的第二区域存在交叠，所述第二区域会话用于发送第一多播广播MBS业务的第二数据；
    响应于所述请求消息，建立第一区域会话，所述第一区域会话对应所述第一区域中除与所述第二区域存在交叠的区域以外的其他区域，所述第一区域会话用于发送所述第一MBS业务的第一数据。
  2. 如权利要求1所述的方法，其特征在于，还包括：
    发送第一信息，所述第一信息指示未针对所述交叠的区域建立区域会话。
  3. 如权利要求2所述的方法，其特征在于，所述第一信息包括所述交叠区域的信息以及第一指示信息；
    其中，所述第一指示信息指示所述交叠的区域未被包括在所述第一区域会话对应的区域中，或者所述第一指示信息指示请求建立的第一区域会话所对应的区域与另一区域会话所对应的区域存在交叠。
  4. 如权利要求1-3任一项所述的方法，其特征在于，还包括：
    接收用于请求建立新的会话的请求消息，所述用于请求建立新的会话的请求消息中包括所述交叠的区域的信息，所述新的会话用于发送所述第一数据。
  5. 如权利要求4所述的方法，其特征在于，所述新的会话为第二MBS会话，所述第一MBS会话与所述第二MBS会话不同。
  6. 如权利要求5所述的方法，其特征在于，所述第一MBS会话为位置相关MBS业务的会话；
    所述第二MBS会话为非位置相关的MBS业务的会话；或者，所述第二MBS会话为位置相关的MBS业务的会话。
  7. 一种通信方法，其特征在于，所述方法包括：
    发送用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息；其中，所述第一区域与已建立的第二区域会话对应的第二区域存在交叠，所述第二区域会话用于发送第一多播广播MBS业务的第二数据；
    接收第一信息，所述第一信息指示未针对所述交叠的区域建立区域会话；
    发送用于请求建立新的会话的请求消息，所述用于请求建立新的会话的请求消息中包括所述交叠的区域的信息，所述新的会话用于发送所述第一数据。
  8. 如权利要求7所述的方法，其特征在于，所述第一信息包括所述交叠区域的信息以及第一指示信息；
    其中，所述第一指示信息指示所述交叠的区域未被包括在所述第一区域会话对应的区域中，或者所述第一指示信息指示请求建立的第一区域会话所对应的区域与另一区域会话所对应的区域存在交叠。
  9. 如权利要求7-8任一项所述的方法，其特征在于，所述新的会话为第二MBS会话，所述第一MBS会话与所述第二MBS会话不同。
  10. 如权利要求9所述的方法，其特征在于，所述第一MBS会话为位置相关MBS业务的会话；
    所述第二MBS会话为非位置相关的MBS业务的会话；或者，所述第二MBS会话为位置相关的MBS业务的会话。
  11. 一种通信方法，其特征在于，所述方法包括：
    接收用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息，所述第一区域会话用于发送第一多播广播MBS业务的第一数据；
    若所述第一区域与第二区域会话对应的第二区域存在交叠，则发送响应消息，所述响应消息指示所述第一区域会话建立失败；其中，所述第二区域会话用于发送所述第一MBS业务的第二数据。
  12. 如权利要求11所述的方法，其特征在于，还包括：
    获取所述第二区域会话的上下文信息，所述上下文信息包括所述第二区域的信息；
    根据所述第二区域的信息和所述第一区域的信息，确定所述第一区域与所述第二区域存在交叠。
  13. 如权利要求11-12任一项所述的方法，其特征在于，所述响应消息中包括以下一项或多项：所述第一区域会话建立失败的原因，或者处理建议。
  14. 如权利要求13所述的方法，其特征在于，所述响应消息中包括用于指示所述第一区域会话建立失败的原因的失败原因指示信息，所述失败原因指示信息用于指示以下一项或多项：
    无法建立位置相关的MBS业务的会话；或者
    请求建立的第一区域会话所对应的第一区域中包括非陆地网络NTN类型的区域；或者
    针对所述第一MBS会话，请求建立的第一区域会话对应的所述第一区域，与另一区域会话所对应的区域存在交叠。
  15. 如权利要求13所述的方法，其特征在于，所述响应消息中包括用于指示处理建议的处理建议指示信息，所述处理建议指示信息用于指示以下一项或多项：
    建立非位置相关的MBS业务的会话，所述非位置相关的MBS业务的会话的MBS服务区域为所述第一区域；或者
    建立位置相关的MBS业务的会话，所述位置相关的MBS业务的会话的MBS服务区域为所述第一区域；或者
    分别针对所述第一区域内的终端设备建立单播会话，所述单播会话用于传输所述第一数据。
  16. 如权利要求11-15任一项所述的方法，其特征在于，还包括：
    接收用于请求建立新的会话的请求消息，所述用于请求建立新的会话的请求消息中包括所述交叠的区域的信息，所述新的会话用于发送所述第一数据；
    响应于所述用于请求建立新的会话的请求消息，建立所述新的会话，或者向会话管理功能网元发送用于请求建立所述新的会话的会话建立请求消息。
  17. 如权利要求16所述的方法，其特征在于，所述新的会话为第二MBS会话，所述第一MBS会话与所述第二MBS会话不同。
  18. 如权利要求17所述的方法，其特征在于，所述第一MBS会话为位置相关MBS业务的会话；
    所述第二MBS会话为非位置相关的MBS业务的会话；或者，所述第二MBS会话为位置相关的MBS业务的会话。
  19. 一种通信方法，其特征在于，所述方法包括：
    发送用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息；其中，所述第一区域与已建立的第二区域会话对应的第二区域存在交叠，所述第二区域会话用于发送第一多播广播MBS业务的第二数据，所述第一区域会话用于发送所述第一MBS业务的第一数据；
    接收所述请求消息对应的响应消息，所述响应消息指示所述第一区域会话建立失败；
    发送用于请求建立新的会话的请求消息，所述用于请求建立新的会话的请求消息中包括所述交叠的区域的信息，所述新的会话用于发送所述第一数据。
  20. 如权利要求19所述的方法，其特征在于，所述响应消息中包括以下一项或多项：所述第一区域会话建立失败的原因，或者处理建议。
  21. 如权利要求20所述的方法，其特征在于，所述响应消息中包括用于指示所述第一区域会话建立失败的原因的失败原因指示信息，所述失败原因指示信息用于指示以下一项或多项：
    无法建立位置相关的MBS业务的会话；或者
    请求建立的第一区域会话所对应的第一区域中包括非陆地网络NTN类型的区域；或者
    针对所述第一MBS会话，请求建立的第一区域会话对应的所述第一区域，与另一区域会话所对应的区域存在交叠。
  22. 如权利要求20所述的方法，其特征在于，所述响应消息中包括用于指示处理建议的处理建议指示信息，所述处理建议指示信息用于指示以下一项或多项：
    建立非位置相关的MBS业务的会话，所述非位置相关的MBS业务的会话的MBS服务区域为所述第一区域；或者
    建立位置相关的MBS业务的会话，所述位置相关的MBS业务的会话的MBS服务区域为所述第一区域；或者
    分别针对所述第一区域内的终端设备建立单播会话，所述单播会话用于传输所述第一数据。
  23. 如权利要求19-22任一项所述的方法，其特征在于，所述新的会话为第二MBS会话，所述第一MBS会话与所述第二MBS会话不同。
  24. 如权利要求23所述的方法，其特征在于，所述第一MBS会话为位置相关MBS业务的会话；
    所述第二MBS会话为非位置相关的MBS业务的会话；或者，所述第二MBS会话为位置相关的MBS业务的会话。
  25. 一种通信方法，其特征在于，包括：
    接收用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息，所述第一区域会话用于发送第一多播广播MBS业务的第一数据；
    若根据所述第一区域的信息以及对应关系信息，确定所述第一区域中包括非陆地网络NTN小区和/或NTN跟踪区，则响应于所述第一请求消息发送响应消息，所述响应消息指示所述第一区域会话建立失败；
    其中，所述第一区域的信息中包括小区标识和/或跟踪区的标识，所述对应关系信息包括第一对应关系信息和第二对应关系信息中的一项，所述第一对应关系信息包括小区标识和小区类型的对应关系信息，和/或跟踪区标识和跟踪区类型的对应关系信息，所述第二对应关系信息包括映射小区标识和NTN小区标识的对应关系信息，和/或，映射跟踪区标识和NTN跟踪区标识的对应关系信息。
  26. 如权利要求25所述的方法，其特征在于，所述响应消息中包括以下一项或多项：所述第一区域会话建立失败的原因，或者处理建议。
  27. 如权利要求26所述的方法，其特征在于，所述响应消息中包括用于指示所述第一区域会话建立失败的原因的失败原因指示信息，所述失败原因指示信息用于指示以下一项或多项：
    无法建立位置相关的MBS业务的会话；或者，
    请求建立的第一区域会话所对应的第一区域中包括非陆地网络NTN类型的区域；或者，
    针对所述第一MBS会话，请求建立的第一区域会话对应的所述第一区域，与另一区域会话所对应的区域存在交叠。
  28. 如权利要求26所述的方法，其特征在于，所述响应消息中包括用于指示处理建议的处理建议指示信息，所述处理建议指示信息用于指示以下一项或多项：
    建立非位置相关的MBS业务的会话，所述非位置相关的MBS业务的会话的MBS服务区域为所述第一区域；或者，
    建立位置相关的MBS业务的会话，所述位置相关的MBS业务的会话的MBS服务区域为所述第一区域；或者，
    分别针对所述第一区域内的终端设备建立单播会话，所述单播会话用于传输所述第一数据。
  29. 如权利要求25-28任一项所述的方法，其特征在于，还包括：
    接收用于请求建立新的会话的请求消息，所述用于请求建立新的会话的请求消息中包括所述交叠的区域的信息，所述新的会话用于发送所述第一数据；
    响应于所述用于请求建立新的会话的请求消息，建立所述新的会话，或者向会话管理功能网元发送用于请求建立所述新的会话的会话建立请求消息。
  30. 如权利要求29所述的方法，其特征在于，所述新的会话为第二MBS会话，所述第一MBS会话与所述第二MBS会话不同。
  31. 如权利要求30所述的方法，其特征在于，所述第一MBS会话为位置相关MBS业务的会话；所述第二MBS会话为非位置相关的MBS业务的会话，或者所述第二MBS会话为位置相关的MBS业务的会话。
  32. 一种通信方法，其特征在于，包括：
    接收用于请求建立第一区域会话的请求消息，所述请求消息中包括第一区域的信息，所述第一区域会话用于发送第一多播广播MBS业务的第一数据；
    发送第一消息，所述第一消息用于请求存储有对应关系信息的网元反馈是否允许针对第一区域建立第一区域会话，所述第一消息中包括所述第一区域的信息；
    从存储有所述对应关系的网元接收第二消息，所述第二消息指示无法针对第一区域建立第一区域会话；
    根据所述第二消息发送响应消息，该响应消息用于指示所述第一区域会话建立失败。
  33. 如权利要求32所述的方法，其特征在于，存储有所述对应关系信息的网元用于根据所述第一区域的信息和所述对应关系信息确定所述第一区域中是否包括非陆地网络NTN小区和/或NTN跟踪区。
  34. 如权利要求32-33任一项所述的方法，其特征在于，所述对应关系信息包括第一对应关系信息和第二对应关系信息中的一项，其中，所述第一对应关系信息包括小区标识和小区类型的对应关系信息，和/或跟踪区标识和跟踪区类型的对应关系信息，所述第二对应关系信息包括映射小区标识和NTN小区标识的对应关系信息，和/或，映射跟踪区标识和NTN跟踪区标识的对应关系信息。
  35. 如权利要求32-34任一项所述的方法，其特征在于，所述响应消息中包括以下一项或多项：所述第一区域会话建立失败的原因，或者处理建议。
  36. 如权利要求35所述的方法，其特征在于，所述响应消息中包括用于指示所述第一区域会话建立失败的原因的失败原因指示信息，所述失败原因指示信息用于指示以下一项或多项：
    无法建立位置相关的MBS业务的会话；或者，
    请求建立的第一区域会话所对应的第一区域中包括非陆地网络NTN类型的区域；或者，
    针对所述第一MBS会话，请求建立的第一区域会话对应的所述第一区域，与另一区域会话所对应的区域存在交叠。
  37. 如权利要求35所述的方法，其特征在于，所述响应消息中包括用于指示处理建议的处理建议指示信息，所述处理建议指示信息用于指示以下一项或多项：
    建立非位置相关的MBS业务的会话，所述非位置相关的MBS业务的会话的MBS服务区域为所述第一区域；或者，
    建立位置相关的MBS业务的会话，所述位置相关的MBS业务的会话的MBS服务区域为所述第一区域；或者，
    分别针对所述第一区域内的终端设备建立单播会话，所述单播会话用于传输所述第一数据。
  38. 如权利要求32-37任一项所述的方法，其特征在于，还包括：
    接收用于请求建立新的会话的请求消息，所述用于请求建立新的会话的请求消息中包括所述交叠的区域的信息，所述新的会话用于发送所述第一数据；
    响应于所述用于请求建立新的会话的请求消息，建立所述新的会话，或者向会话管理功能网元发送用于请求建立所述新的会话的会话建立请求消息。
  39. 如权利要求38所述的方法，其特征在于，所述新的会话为第二MBS会话，所述第一MBS会话与所述第二MBS会话不同。
  40. 如权利要求39所述的方法，其特征在于，所述第一MBS会话为位置相关MBS业务的会话；所述第二MBS会话为非位置相关的MBS业务的会话，或者所述第二MBS会话为位置相关的MBS业务的会话。
  41. 一种通信装置，其特征在于，包括用于执行如权利要求1-6任一项所述方法的单元或者模块，或者包括用于执行如权利要求7-10任一项所述方法的单元或者模块，或者包括用于执行如权利要求11-18任一项所述方法的单元或者模块，或者包括用于执行如权利要求19-24任一项所述方法的单元或者模块，或者包括用于执行如权利要求25-31任一项所述方法的单元或者模块，或者包括用于执行如权利要求32-40任一项所述方法的单元或者模块。
  42. 一种通信装置，其特征在于，包括：一个或多个处理器配置用于执行如权利要求1-6中任一项所述的方法，或者执行如权利要求7-10任一项所述的方法，或者执行如权利要求11-18任一项所述的方法，或者执行如权利要求19-24任一项所述的方法，或者执行如权利要求25-31任一项所述的方法，或者执行如权利要求32-40任一项所述的方法。
  43. 一种通信系统，其特征在于，包括接入网设备和应用功能网元；
    所述接入网设备用于实现如权利要求1-6任一项所述的方法，所述应用功能网元用于实现如权利要求7-10任一项所述的方法；或者，所述接入网设备用于实现如权利要求11-18任一项所述的方法，所述应用功能网元用于实现如权利要求19-24任一项所述的方法。
  44. 一种通信系统，其特征在于，包括网络开放功能网元和应用功能网元；
    所述网络开放功能网元用于实现权利要求25-31中任一项所述的方法，或者用于实现权利要求32-40中任一项所述的方法，所述应用功能网元用于实现如权利要求19-24中任一项所述的方法。
  45. 一种可读存储介质，其特征在于，所述可读存储介质存储有程序或指令，当所述程序或指令在装置上运行时，使得所述装置执行如权利要求1-6任一项所述的方法，或者执行如权利要求7-10任一项所述的方法，或者执行如权利要求11-18任一项所述的方法，或者执行如权利要求19-24任一项所述的方法，或者执行如权利要求25-31任一项所述的方法，或者执行如权利要求32-40任一项所述的方法。
  46. 一种芯片系统，其特征在于，包括处理器，用于支持计算机装置实现如权利要求1-6任一项所述的方法，或者实现如权利要求7-10任一项所述的方法，或者实现如权利要求11-18任一项所述的方法，或者实现如权利要求19-24任一项所述的方法，或者实现如权利要求25-31任一项所述的方法，或者实现如权利要求32-40任一项所述的方法。
  47. 一种程序产品，其特征在于，所述程序产品中包含程序；当所述程序在计算机上运行时，使得所述计算机执行如权利要求1-6任一项所述的方法，或者执行如权利要求7-10任一项所述的方法，或者执行如权利要求11-18任一项所述的方法，或者执行如权利要求19-24任一项所述的方法，或者执行如权利要求25-31任一项所述的方法，或者执行如权利要求32-40任一项所述的方法。
PCT/CN2025/098036 2024-06-07 2025-05-29 一种通信方法及装置 Pending WO2025251997A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202410742052.X 2024-06-07
CN202410742052.XA CN121099276A (zh) 2024-06-07 2024-06-07 一种通信方法及装置

Publications (1)

Publication Number Publication Date
WO2025251997A1 true WO2025251997A1 (zh) 2025-12-11

Family

ID=97888706

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/098036 Pending WO2025251997A1 (zh) 2024-06-07 2025-05-29 一种通信方法及装置

Country Status (2)

Country Link
CN (1) CN121099276A (zh)
WO (1) WO2025251997A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100322128A1 (en) * 2006-10-17 2010-12-23 Panasonic Corporation Multicast service provision in a mobile communication system having overlapping pool areas
CN105340322A (zh) * 2013-04-16 2016-02-17 爱立信(中国)通信有限公司 用于处理通信网络中失效的方法和节点
CN108347699A (zh) * 2017-01-22 2018-07-31 中兴通讯股份有限公司 会话处理方法及装置
WO2022241691A1 (zh) * 2021-05-19 2022-11-24 华为技术有限公司 一种组播/广播通信方法和装置
WO2023134437A1 (zh) * 2022-01-17 2023-07-20 华为技术有限公司 通信方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100322128A1 (en) * 2006-10-17 2010-12-23 Panasonic Corporation Multicast service provision in a mobile communication system having overlapping pool areas
CN105340322A (zh) * 2013-04-16 2016-02-17 爱立信(中国)通信有限公司 用于处理通信网络中失效的方法和节点
CN108347699A (zh) * 2017-01-22 2018-07-31 中兴通讯股份有限公司 会话处理方法及装置
WO2022241691A1 (zh) * 2021-05-19 2022-11-24 华为技术有限公司 一种组播/广播通信方法和装置
WO2023134437A1 (zh) * 2022-01-17 2023-07-20 华为技术有限公司 通信方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling (Release 16)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 25.413, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. V16.0.0, 31 March 2020 (2020-03-31), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 455, XP051861351 *

Also Published As

Publication number Publication date
CN121099276A (zh) 2025-12-09

Similar Documents

Publication Publication Date Title
US12538185B2 (en) Methods of delivery mode switch for multicast and broadcast service in a 5G network
US20220174119A1 (en) Session establishment method and device
US20230017217A1 (en) Multicast or broadcast session establishment and management
CN114270885A (zh) 移动通信网络中支持多播和广播服务的网络结构及服务提供方法
JP7318118B2 (ja) データ伝送方法並びにその装置、コンピュータプログラム、制御装置及びアプリケーションサーバ
JP2021504982A (ja) メッセージマルチキャスト方法、メッセージブロードキャスト方法およびデバイス
US12563631B2 (en) Multicast broadcast service control
US20240422861A1 (en) Communication method and apparatus
WO2025201142A1 (zh) 一种通信方法和装置
WO2025251997A1 (zh) 一种通信方法及装置
CN115706932B (zh) 一种配置mbs会话的方法和装置
WO2023231032A1 (zh) 非激活态组播业务区域的确定方法、配置方法、及装置
CN117858183A (zh) 通信方法、装置及系统
US20260040402A1 (en) Communication method and apparatus
US20240179801A1 (en) Communication method and apparatus
CN118338408B (zh) 通信方法、通信装置及通信系统
WO2024094128A1 (zh) 一种通信方法及装置
WO2025087070A1 (zh) 一种通信方法及装置
WO2023179331A1 (zh) 一种发送数据包的方法、通信装置及通信系统
WO2023197737A1 (zh) 报文发送方法、pin管理方法、通信装置及通信系统
WO2025044957A1 (zh) 通信方法及相关装置
WO2025086786A1 (zh) 一种通信方法、通信装置及通信系统
CN120692542A (zh) 一种通信方法及其装置
WO2022229883A1 (en) 5mbs amf involvement on signaling efficiency
CN119906972A (zh) 一种通信方法、通信装置及通信系统

Legal Events

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

Ref document number: 25819050

Country of ref document: EP

Kind code of ref document: A1