A data communication method and apparatus

Abstract

This application relates to a data communication method and apparatus. In this method, a session management function sends a first message to an access management function based on the context information of the multicast session corresponding to the Multicast / Broadcast Service (MBS). The first message triggers the reporting of the location information of a first terminal device. When the location information indicates the location of the first terminal device, and the session management function determines that the first terminal device is outside the service area of ​​the MBS based on its location, or when the location information indicates that the first terminal device is outside the service area of ​​the MBS, the session management function stops sending data to the first terminal device. Through this solution, the session management function can determine whether the terminal device can receive or should continue receiving data at its current location, and stop sending data to the terminal device when it cannot receive or should not continue receiving data, thereby reducing the waste of transmission resources and improving the data transmission success rate.

Description

[0001] This application is a divisional application. The original application has the application number 202110915505.0 and the original application date is August 10, 2021. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication technology, and in particular to a data communication method and apparatus. Background Technology

[0003] Related technologies have proposed a unicast-based multicast transmission method, in which the user plane function establishes a unicast user plane connection for the terminal device, and the access network device and the terminal device communicate using a unicast channel or a multicast channel.

[0004] In some communication scenarios, terminal devices can receive data from local multicast and broadcast services (MBS). Local MBS allows data receivers to receive different data for the same service when they move to different areas. For example, local MBS can be used to propagate map data, and application functions (AFs) can broadcast different local map data in different areas. If the AF triggers an update to the local MBS area, or if the terminal device moves, the terminal device may stop receiving local MBS data, and the core network equipment may stop sending local MBS data to the terminal device.

[0005] However, in this communication scenario, the core network equipment only focuses on the authorization and management control of the terminal equipment. It cannot know whether the terminal equipment can correctly receive the local MBS data, and therefore cannot determine whether to provide the local MBS data to the terminal equipment. This may lead to a waste of transmission resources and failure to send MBS data. Summary of the Invention

[0006] This application provides a data communication method and apparatus to reduce the waste of transmission resources and improve the data transmission success rate of MBS.

[0007] Firstly, a data communication method is provided, comprising the following steps: A session management function sends a first message to an access management function based on the context information of a multicast session corresponding to an MBS. The first message triggers the reporting of the location information of a first terminal device, wherein the first terminal device belongs to the multicast group corresponding to the MBS. The session management function receives the location information of the first terminal device from the access management function. When the location information indicates the location of the first terminal device, and the session management function determines that the first terminal device is located outside the service area of ​​the MBS based on the location of the first terminal device, or when the location information indicates that the first terminal device is located outside the service area of ​​the MBS, the session management function stops sending MBS data to the first terminal device.

[0008] The session management function can be a session management function (SMF) entity, such as a unicast SMF. The access management function can be an access and mobility management function (AMF) entity.

[0009] The location information of the first terminal device can be the identifier of the cell where the first terminal device is currently camped or accessed, or it can be used to indicate whether the first terminal device is outside the service area of ​​MBS. In this way, the session management function can determine whether the terminal device can receive MBS data at its current location, and stop sending MBS data to the terminal device when the terminal device cannot receive or should no longer receive MBS data, thus reducing the waste of transmission resources and improving the success rate of MBS data transmission. In this application, the session management function can also proactively trigger the acquisition of the location information of the first terminal device based on the context information of the multicast session.

[0010] The session management function stops sending MBS data to the first terminal device, which can also be understood as the session management function removing (or determining to remove) the first terminal device from the multicast session, or removing (or determining to remove) the first terminal device from the multicast group corresponding to the multicast session.

[0011] In this application, MBS includes local MBS. Local MBS can specifically refer to local MBS service scenarios, or it can refer to other MBS service scenarios that are limited by regional transmission.

[0012] Optionally, the first message carries the identification information of the first terminal device. There can be one or more first terminal devices. Based on the identification information of one or more first terminal devices, the access management function can determine which terminal device(s) location information to report.

[0013] In one possible implementation, the first message can be a subscription message, which is used to subscribe to the location information of the first terminal device.

[0014] Optionally, the subscription message may also carry information about MBS's business area.

[0015] In one possible implementation, before the session management function receives the location information from the first terminal device of the access management function, the session management function may also receive a second message from the first terminal device, the second message being used to request to join a multicast session or multicast group.

[0016] In one possible implementation, before receiving location information from the first terminal device of the access management function, the session management function can also receive a third message from the multicast / broadcast session management function. This third message is used to update the service area of ​​the MBS. After each update of the MBS's service area, the session management function can determine whether the UE's location has moved out of the MBS's service area, thereby further reducing the waste of transmission resources. Optionally, the third message can also carry information about the new MBS's service area.

[0017] In one possible implementation, when the session management function sends a first message to the access management function based on the context information of the multicast group corresponding to the MBS, it can adopt one or more of the following methods: If the context information includes the type of multicast session of the multicast group, and the type is local MBS, then the session management function sends a first message to the access management function; or if the context information includes first indication information, and the first indication information is used to indicate obtaining the location information of the terminal device, then the session management function sends a first message to the access management function; or if the context information includes information about the service area of ​​the MBS, then the session management function sends a first message to the access management function; or if the service type (servicetype) in the context information is multicast service, and the context information includes information about the service area of ​​the MBS, then the session management function sends a first message to the access management function. The session management function can determine whether it needs to obtain the location information of the first terminal device based on the context information of the multicast group, thereby determining whether to actively obtain the location information of the first terminal device.

[0018] In one possible implementation, when the session management function stops sending MBS data to the first terminal device, it can do so in the following ways: the session management function notifies the user plane function to stop sending MBS data to the first terminal device; or the session management function sends a fourth message to the access network device, which triggers the access network device to delete the information of the first terminal device from the context information corresponding to the multicast group; or the session management function sends a fifth message to the access network device, which triggers the access network device to delete the information of the multicast group from the context information of the first terminal device; or the session management function sends a sixth message to the access network device, which instructs the access network device to stop sending MBS data to the first terminal device.

[0019] The information of the multicast group may include the identification information of the multicast group; and / or the QoS (Quality of Service) flow information of the unicast service corresponding to the multicast group.

[0020] In one possible implementation, if the first terminal device receives MBS data via a separate transmission method, the session management function can also send a first message to the access management function. Here, "the first terminal device receives MBS data via a separate transmission method" can be understood as the first terminal device receiving MBS data via unicast, or the first terminal device not supporting receiving MBS data via multicast, or the access network device currently hosted by the first terminal device not supporting sending and receiving MBS data via multicast, or the MBS data being sent to the first terminal via a unicast session of the first terminal.

[0021] Secondly, a data communication method is provided, comprising the following processes: an access network device obtains information about the service area of ​​an MBS; if a first terminal device is located outside the service area of ​​the MBS, the access network device stops sending MBS data to the first terminal device, or notifies the first terminal device to stop receiving MBS data.

[0022] In this method, the access network device can determine whether the terminal device can receive MBS data at its current location, and when the terminal device cannot receive or should not continue to receive local MBS data, it can stop sending MBS data to the terminal device or notify the terminal device to stop receiving MBS data. This can reduce the waste of transmission resources and improve the success rate of MBS data transmission.

[0023] In one possible implementation, when the access network device stops sending MBS data to the first terminal device, one or more of the following methods can be used: the access network device sends a seventh message to the session management function, which triggers the session management function to configure the first terminal device to stop receiving MBS data; or the access network device sends the location information of the first terminal device to the session management function and receives an eighth message from the session management function, which triggers the access network device to delete the information of the first terminal device from the context information corresponding to the multicast group, and the access network device deletes the information of the first terminal device from the context information corresponding to the multicast group according to the eighth message; or the access network device sends the location information of the first terminal device to the session management function and receives a ninth message from the session management function, which triggers the access network device to delete the information of the multicast group from the context information of the first terminal device, and the access network device deletes the information of the multicast group from the context information of the first terminal device according to the eighth message; or the access network device releases or deletes the context information of the first terminal device.

[0024] In one possible implementation, when the access network device notifies the first terminal device to stop receiving MBS data, the following method can be used: the access network device sends a tenth message to the first terminal device, which is used to configure the first terminal device to stop receiving MBS data.

[0025] Thirdly, a data communication method is provided, including the following process: the access network device obtains information about the service area of ​​the MBS; if the coverage area of ​​the access network device does not overlap with the service area of ​​the MBS, the access network device triggers the release of the shared tunnel corresponding to the MBS.

[0026] In one possible implementation, the fact that the coverage area of ​​the access network device does not overlap with the service area of ​​the MBS includes one or more of the following: all cells or tracking areas of the access network device are not located in the service area of ​​the MBS, or the cells or tracking areas for which the access network device provides coverage services are not located in the service area of ​​the MBS, or the cells or tracking areas available to the access network device are not located in the service area of ​​the MBS, or the cells or tracking areas included in the access network device are not located in the service area of ​​the MBS.

[0027] In one possible implementation, when an access network device obtains information about the service area of ​​an MBS, it can receive information about the service area from the MBS's multicast / broadcast session management function, network storage function, unified data management function, unified data storage function, policy control function, or network open function.

[0028] The network storage function can be a network repository function (NRF), the unified data management function can be a unified data management (UDM), the unified data storage function can be a unified data repository (UDR), the policy control function can be a policy control function (PCF), and the network exposure function can be a network exposure function (NEF).

[0029] In this method, when the coverage area of ​​the access network device does not overlap with the service area of ​​MBS, the terminal device residing in the access network device cannot or should not continue to receive MBS data. Therefore, the access network device can trigger the process of releasing the shared tunnel so that the terminal devices in the coverage area of ​​the access network device do not receive MBS data, which can reduce the waste of transmission resources and improve the data transmission success rate of MBS.

[0030] Fourthly, a data communication method is provided, comprising the following process: an access network device obtains information about the service area of ​​an MBS; if the first cell or first tracking area of ​​the access network device is located outside the service area of ​​the MBS, the access network device stops transmitting MBS data in the first cell or first tracking area.

[0031] In this method, when the first cell or the first tracking area is outside the service area of ​​MBS, the terminal devices residing in the first cell or the first tracking area cannot receive or should not continue to receive MBS data. Therefore, the access network device can stop sending MBS data to the first cell or the first tracking area, thereby reducing the waste of transmission resources and improving the data transmission success rate of MBS.

[0032] In one possible implementation, when the access network device stops transmitting MBS data in the first cell or the first tracking area, it may employ one or more of the following methods: the access network device sends an eleventh message to the session management function, the eleventh message being used to trigger the session management function to configure the terminal devices in the first cell or the first tracking area to stop receiving MBS data; or the access network device deletes the information of the terminal devices in the first cell or the first tracking area from the context information corresponding to the multicast group; or the access network device deletes the information of the multicast group from the context information of the terminal devices in the first cell or the first tracking area; or the access network device releases or deletes the context information of the terminal devices in the first cell or the first tracking area.

[0033] Fifthly, a communication device is provided, which can be the aforementioned session management function or access network device, or a chip disposed in the session management function or access network device. This communication device can implement the method provided by any of the designs in the first, second, third, or fourth aspects described above.

[0034] The communication device includes modules, units, or means that implement the methods described above. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0035] A sixth aspect provides a communication device including a transceiver unit. Optionally, the communication device further includes a processing unit. The communication device can implement the methods provided in any of the designs in the first, second, third, or fourth aspects.

[0036] A seventh aspect provides a communication device including a processor. The processor can be used to perform the methods provided by any of the designs in the first, second, third, or fourth aspects described above. Optionally, the device further includes a memory, the processor being coupled to the memory, the memory storing computer programs or instructions, and the processor can execute the programs or instructions in the memory to enable the device to perform the methods provided by any of the designs in the first, second, third, or fourth aspects described above.

[0037] Eighthly, a communication device is provided, comprising an interface circuit and a logic circuit coupled to the interface circuit. The interface circuit may be a code / data read / write interface circuit, used to receive computer-executed instructions (stored in memory, possibly read directly from memory, or possibly via other devices) and transmit them to the logic circuit, so that the logic circuit executes the computer-executed instructions to perform the method provided by any of the designs in the first, second, third, or fourth aspects described above.

[0038] In some possible designs, the communication device can be a chip or a chip system.

[0039] A ninth aspect provides a communication device including a processor and a memory. The processor is configured to read instructions stored in the memory, receive signals via a receiver, and transmit signals via a transmitter to execute the method provided in any of the designs described in the first, second, third, or fourth aspects.

[0040] Optionally, there can be one or more processors, and there can also be one or more memories. Optionally, the memory can be integrated with the processor, or the memory can be set separately from the processor.

[0041] In the specific implementation process, the memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or set on different chips. This application does not limit the type of memory or the way the memory and processor are set.

[0042] The communication device can be a chip. The processor can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. The memory can be integrated into the processor or located outside the processor and exist independently.

[0043] A tenth aspect provides a processor, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the method provided in any one of the designs described in the first, second, third, or fourth aspects.

[0044] In specific implementation, the processor can be a chip, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0045] Eleventhly, a communication device is provided, comprising: logic circuitry and an input / output interface for communicating with a module outside the communication device; the logic circuitry for executing computer programs or instructions to perform the methods provided by any of the designs in any of the preceding aspects. The communication device may be a session management function or access network device as described in the first, second, third, or fourth aspects, or a device including the aforementioned session management function or access network device, or a device included in the aforementioned session management function or access network device, such as a chip.

[0046] Alternatively, the input / output interface can be a code / data read / write interface circuit or a communication interface, which is used to receive computer programs or instructions (which are stored in memory, may be read directly from memory, or may be transmitted through other devices) and transmit them to the input / output interface so that the input / output interface can run the computer programs or instructions to perform any of the methods described above.

[0047] Optionally, the communication device can be a chip.

[0048] In a twelfth aspect, a computer program product is provided, comprising: a computer program (also referred to as code or instructions) that, when run, causes a computer to perform the method provided by any one of the designs in the first, second, third, or fourth aspects described above.

[0049] In a thirteenth aspect, a computer-readable medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the methods provided by any one of the designs in the first, second, third, or fourth aspects described above.

[0050] In a fourteenth aspect, a chip system is provided, comprising a processor and an interface for supporting a communication device in implementing the functions provided by any one of the designs in the first, second, third, or fourth aspects described above. In one possible design, the chip system further includes a memory for storing necessary information and data of the aforementioned communication device. The chip system may be composed of chips or may include chips and other discrete devices.

[0051] In a fifteenth aspect, a chip device is provided, the chip device including an input interface and / or an output interface. The input interface can implement the receiving function provided by any one of the designs in the first, second, third, or fourth aspects described above, and the output interface can implement the transmitting function provided by any one of the designs in the first, second, third, or fourth aspects described above.

[0052] In a sixteenth aspect, a functional entity is provided for implementing the method provided by any one of the designs in the first to third or fourth aspects described above.

[0053] In a seventeenth aspect, a communication system is provided, including the session management function and access management function of the first aspect described above.

[0054] Optionally, the communication system may also include access network equipment and / or terminal equipment.

[0055] Eighteenth aspect: A communication system is provided, including the access network equipment and terminal equipment described in the second, third, or fourth aspects above.

[0056] Optionally, the communication system may also include session management functions and / or access network equipment.

[0057] The technical effects of any of the design methods in aspects five through eighteen can be found in the technical effects of aspects one through four mentioned above, and will not be repeated here. Attached Figure Description

[0058] Figure 1 This is a schematic diagram of the architecture of a communication system; Figure 2 A schematic diagram of a communication process provided in an embodiment of this application; Figure 3 A schematic diagram of a communication process provided in an embodiment of this application; Figure 4 A schematic diagram of a communication process provided in an embodiment of this application; Figure 5 A schematic diagram of a communication process provided in an embodiment of this application; Figure 6 A schematic diagram of a communication process provided in an embodiment of this application; Figure 7 A schematic diagram of a communication process provided in an embodiment of this application; Figure 8 A schematic diagram of a communication process provided in an embodiment of this application; Figure 9 A schematic diagram of a communication process provided in an embodiment of this application; Figure 10 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application; Figure 11 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application; Figure 12 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0059] The present application will now be described in further detail with reference to the accompanying drawings.

[0060] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0061] Additionally, in the embodiments of this application, the term "exemplary" is used to indicate that it is an example, illustration, or illustration. Any embodiment or design that is described as "exemplary" in this application should not be construed as being more preferred or advantageous than other embodiments or design options. Rather, the use of the term "exemplary" is intended to present the concept in a specific manner.

[0062] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0063] The following explanations of some terms used in the embodiments of this application are provided to facilitate understanding by those skilled in the art.

[0064] 1) User equipment (UE), also known as terminal equipment, is a device with wireless transceiver capabilities that can communicate with one or more core network (CN) devices through access network devices in the radio access network (RAN).

[0065] User equipment can also be referred to as an access terminal, terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, user agent, or user device, etc. User equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as on ships); and it can be deployed in the air (such as on airplanes, balloons, and satellites). User equipment can be a cellular phone, cordless phone, session initiation protocol (SIP) phone, smartphone, mobile phone, wireless local loop (WLL) station, personal digital assistant (PDA), etc. Alternatively, user equipment can also be a handheld device with wireless communication capabilities, a computing device or other device connected to a wireless modem, vehicle-mounted equipment, wearable device, drone equipment, or a terminal in the Internet of Things (IoT), vehicle-to-everything (V2X) network, any form of terminal in 5G networks and future networks, relay user equipment, or a terminal in a future evolved public land mobile network (PLMN), etc. The relay user equipment can be, for example, a 5G residential gateway (RG). User equipment can also be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. This application does not limit the type or category of terminal equipment.

[0066] 2) Network equipment refers to devices that can provide wireless access functionality to terminals. Network equipment can support at least one wireless communication technology, such as Long Term Evolution (LTE) or New Radio (NR).

[0067] Network equipment may include access network equipment. Examples of network equipment include, but are not limited to: next-generation base stations or next-generation node Bs (gNBs) in 5G networks, evolved node Bs (eNBs), radio network controllers (RNCs), node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved node Bs or home node Bs (HNBs)), baseband units (BBUs), transmitting and receiving points (TRPs), transmitting points (TPs), mobile switching centers, small cells, and micro cells. Network equipment may also be radio controllers, centralized units (CUs), and / or distributed units (DUs) in cloud radio access networks (CRAN) scenarios, or network equipment may be relay stations, access points, vehicle-mounted equipment, terminals, wearable devices, and network equipment in future mobile communications or future evolved PLMNs.

[0068] Obviously, network devices can also include core network devices. For example, core network devices may include SMFs, etc. Optionally, core network devices may include application functions (AFs). It should be noted that core network devices may also not include AFs.

[0069] Optionally, the access network equipment includes unicast access network equipment and / or multicast (MB) access network equipment. The unicast access network equipment can be either an access network equipment supporting unicast sessions or an access network equipment used to manage unicast sessions; the multicast access network equipment can be either an access network equipment supporting multicast sessions or an access network equipment used to manage multicast sessions, without limitation. Managing multicast sessions may refer to storing the context information of the multicast sessions.

[0070] Optionally, the session management functions include unicast session management functions and / or multicast session management functions. The unicast session management functions can be either session management functions that support unicast sessions or session management functions used to manage unicast sessions; the multicast session management functions can be either session management functions that support multicast sessions or session management functions used to manage multicast sessions.

[0071] 3) Multicast session, used to transmit data for multicast or multicast broadcast services. For example, it can be a Protocol Data Unit (PDU) session used to transmit multicast data. Multicast sessions are also called multicast sessions, broadcast sessions, or multicast and broadcast service (MBS) sessions.

[0072] For example, a multicast session supports broadcast and / or multicast services, enabling the simultaneous transmission of broadcast or multicast data to multiple users within a specific range. In other words, a multicast session can achieve point-to-multipoint data transmission.

[0073] For the same MBS service area, there may be one or more corresponding multicast groups. And / or for the same multicast group, there may be one or more MBS service areas. The service area of ​​an MBS can include one or more service areas. The service area of ​​an MBS refers to the service area capable of transmitting MBS data, meaning that terminal devices within the MBS service area can receive MBS data. For example, the service area of ​​an MBS can be represented by elements such as a multicast session cell ID list and / or a tracking area identity list (TAI list).

[0074] Multiple terminal devices receiving the same multicast data can belong to a multicast group. That is, one piece of multicast data can correspond to one multicast group or one multicast session. Optionally, there is a one-to-one correspondence between multicast sessions and multicast groups. The session identifier of a multicast session and the group identifier of a multicast group can also correspond one-to-one. Alternatively, a multicast session and a multicast group can share a single identifier, meaning one identifier can uniquely identify both a multicast session and a multicast group; in other words, the session identifier of a multicast session and the group identifier of a multicast group are the same.

[0075] It is understood that, unless otherwise specified, the concepts of "multicast", "broadcast", and "groupcast" can be used interchangeably in the embodiments of this application.

[0076] In this application, "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0077] In this application, "at least one" means one or more, and "multiple" means two or more.

[0078] In addition, it should be understood that in the description of this application, the words "first" and "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance or order.

[0079] The technical solutions of this application can be applied to various communication systems. For example, LTE systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, 5G communication systems or NR, and other future communication systems such as 6G.

[0080] To facilitate understanding of the embodiments of this application, Figure 1 The application scenario used in this application is illustrated using the 5G network architecture shown as an example. Figure 1 This is a 5G network architecture, which may include: a user equipment (UE) 101 part, a network equipment part, and a data network (DN) 104 part.

[0081] The network equipment includes the access network (AN) 102, user plane function (UPF) 103, AMF 105, SMF 106, PCF 107, UDM 108, etc. The portion of the network equipment excluding the access network 102 can be referred to as the core network.

[0082] Data network DN 104 is used to provide data transmission services to users, such as Internet Protocol Multimedia Subsystem (IMS) and the Internet.

[0083] Application function AF109 is responsible for providing services to the 3rd generation partnership project (3GPP) network, such as influencing service routing and interacting with the PCF for policy control.

[0084] For example, the network functions in a carrier network are briefly described below.

[0085] AN 102 is used for UE101 to access the operator's network. AN can include 3GPP NG-RAN and / or non-3GPP ANs, etc., without limitation here. For example, UE101 connects to a service node in the operator's network via AN 102. In the embodiments of this application, AN 102 can refer to the access network itself or to access network equipment; no distinction is made here. It is understood that this application does not limit the specific type of access network equipment. In systems employing different radio access technologies, the names of devices with access network equipment functions may differ. Optionally, in some deployments of access network equipment, the access equipment may include CU and DU, etc.

[0086] The policy control function PCF 107 is responsible for providing policy rules, such as quality of service (QoS) policies and slice selection policies, to the access and mobility management function AMF105 and the session management function SMF106.

[0087] Unified Data Management (UDM) 108 is responsible for storing user data, such as contract data, authentication / authorization information, etc.

[0088] The Access and Mobility Management Function (AMF 105) is responsible for mobility management in mobile network devices, such as user location updates, user network registration, and user handover.

[0089] The Session Management Function (SMF) 106 is responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting User Plane Functions (UPFs) to provide packet forwarding capabilities.

[0090] User plane function UPF 103 is responsible for processing user messages, such as forwarding and billing.

[0091] Figure 1 N1, N2, N3, N4, N5, N6, N7, N8, N10, N11, and N25 are interface sequence numbers. For example, the meaning of the above interface sequence numbers can be found in the definitions in the 3GPP standard protocols; this application does not limit the meaning of the above interface sequence numbers. It should be noted that... Figure 1 The example provided only uses terminal device 110 as the UE. Figure 1 The interface names between the various network functions in this application are merely examples. In actual implementations, the interface names of this system architecture may be other names, and this application does not limit them.

[0092] This application provides a data communication method and apparatus, which can be applied to... Figure 1 In the communication system shown, the method allows the session management function to trigger the reporting of the location information of the first terminal device based on the context information of the multicast session corresponding to the MBS. Upon receiving the location information of the first terminal device, the session management function stops sending MBS data to the first terminal device when the first terminal device is outside the service area of ​​the MBS. This proactive approach of obtaining the terminal device's location information to determine whether the terminal device can or should receive MBS data at its current location, and stopping the transmission of MBS data when the terminal device cannot or should not receive it, reduces waste of transmission resources and improves the success rate of MBS data transmission. Unless otherwise specified, the MBS involved in the embodiments of this application may include a local MBS. A local MBS may specifically refer to a local MBS service scenario, or it may refer to other MBS service scenarios that are limited by regional transmission.

[0093] Figure 2 A possible data communication method provided in this application embodiment includes the following steps: S201: The session management function sends the first message based on the context information of the multicast session corresponding to the MBS.

[0094] Correspondingly, the access management function receives the first message.

[0095] The first message can be used to trigger the reporting of the location information of the first terminal device.

[0096] The first terminal device belongs to the multicast group corresponding to the MBS. The first terminal device can be one or more group members, without restriction. For example, the first terminal device can be all or some members of the multicast group.

[0097] Specifically, the first terminal device belonging to the multicast group corresponding to MBS may include one or more of the following situations: the first terminal device may be a member of the multicast group that has already joined the multicast session, the first terminal device may be a member that has requested to join the multicast group, or the first terminal device is a member in the multicast group.

[0098] The session management function can be an SMF entity, such as a unicast SMF or an MB-SMF. In this embodiment, the session management function is described using a unicast SMF as an example. The access management function can be an AMF entity.

[0099] The session management function can obtain the context information of the multicast session corresponding to the MBS from the multicast / broadcast session management function (such as MB-SMF), or from the AF, or from the network storage function (such as NRF), or from the unified data management function (such as UDM), or from the unified data storage function (such as URM), or from the policy control function (such as PCF), or from the network open function (such as NEF), etc. There are no restrictions on the method by which the session management function obtains the context information of the multicast session corresponding to the MBS.

[0100] The multicast session corresponding to the MBS is used to transmit MBS data. Generally, one multicast session corresponds to one multicast group. Terminal devices can join the multicast session or multicast group corresponding to the MBS to receive MBS data.

[0101] The context information of a multicast session corresponding to an MBS may include, but is not limited to, one or more of the following: the session identifier of the multicast session, the group identifier of the multicast group, the multicast session type of the multicast group, the first indication information used to indicate the acquisition of the location information of the terminal device, the service area information of the MBS, the service type, and the QoS flow information of the multicast session (such as QoS flow information or guaranteed flow bit information). The multicast session type of a multicast group includes local MBS, etc. The service type is used to indicate unicast or multicast services. The context of a multicast session can also be referred to as the context information corresponding to a multicast group. The service area information of the MBS can be represented by elements such as the Cell ID list and / or TAI list of the multicast session.

[0102] In one example, the session management function in S201 can determine whether it is necessary to obtain the location information of the terminal device based on the context information of the multicast session corresponding to the MBS. When it is determined that the location information of the terminal device needs to be obtained, the session management function sends a first message to trigger the acquisition of the location information of the terminal device.

[0103] In one implementation, if the context information of the multicast session includes the type of the multicast session in the multicast group, and the type is a local MBS, the session management function can send a first message to the access management function. That is, when the type is a local MBS, the session management function can determine that the location of the first terminal device needs to be obtained, thereby triggering the acquisition of the location of the first terminal device.

[0104] In another implementation, if the context information of the multicast session includes first indication information, and this first indication information is used to indicate obtaining the location information of the first terminal device, the session management function can send a first message to the access management function. That is, when the first indication information indicates obtaining the location information of the first terminal device, the session management function can determine that it needs to obtain the location of the first terminal device, thereby triggering the acquisition of the location of the first terminal device.

[0105] In another implementation, if the context information of the multicast session includes information about the MBS's service area, the session management function can send a first message to the access management function. That is, if the context information includes information about the MBS's service area, the session management function can determine that it needs to obtain the location information of the first terminal device, thereby triggering the acquisition of the first terminal device's location. Optionally, the session management function can also determine the local MBS corresponding to the multicast session based on the MBS's service area information (such as a Cell ID list and / or TAI list).

[0106] In another implementation, if the multicast session context information includes a service type of multicast service and information about the MBS's service area, the session management function can send a first message to the access management function. In other words, in this case, the session management function can determine that it needs to obtain the location information of the first terminal device, thereby triggering the acquisition of the first terminal device's location.

[0107] Optionally, before sending the first message, the session management function may also send a first message to the access management function based on the MBS capabilities of the access network device. The access network device here can correspond to the access network device currently hosted by the terminal device. For example, when the access network device currently hosted by the terminal device does not support MBS (or when the access network device currently hosted by the terminal device does not support sending and receiving MBS data via multicast), the session management function sends the first message to the access management function. Similarly, when the terminal device receives MBS data via individual delivery, the session management function sends the first message to the access management function. The unicast delivery method can be unicast or 5GC individual MBS traffic delivery, etc.

[0108] The first message is used to trigger the reporting of the location information of the first terminal device. Then, the session management function can determine whether the first terminal device needs to receive or should continue to receive MBS data, and whether the first terminal device can receive MBS data, based on the location information of the first terminal device.

[0109] Optionally, the first message carries the identification information of the first terminal device, or the identification information of the multicast group corresponding to the MBS. For example, when the first terminal device is a member of all members in the multicast group corresponding to the MBS, the first message may carry the identification information of the multicast group. The identification information of the first terminal device may be one or more of the following: the IP address of the first terminal device, a globally unique temporary UE identity (GUTI), an international mobile subscriber identification number (IMSI), a temporary mobile subscriber identity (TMSI), a subscription permanent identifier (SUPI), or a subscription concealed identifier (SUCI), etc. The identification information of the multicast group may be one or more of the following: the session identifier of the multicast session, the IP address of the multicast group, a temporary mobile group identifier (TMGI), etc.

[0110] For example, the first message can be a subscription message used to subscribe to the location information of the first terminal device. Optionally, the subscription message can carry information about the MBS's service area. This allows the session management function to determine whether the MBS's service area has been updated based on the MBS's service area information, and also to determine whether the first terminal device is within or outside the MBS's service area based on the first terminal device's location and the MBS's service area.

[0111] Optionally, prior to S201, the session management function could also receive information from the first terminal device requesting to join a multicast session or multicast group, update the instruction information for the service area of ​​the MBS, and information about the service area of ​​the MBS.

[0112] For example, the session management function can receive a second message from the first terminal device, which is used to request joining a multicast session or multicast group. Optionally, the second message may carry the identification information of the multicast group or the session identifier of the multicast session, and may also carry the location information of the first terminal device.

[0113] For example, the session management function can receive a third message from the multicast / broadcast session management function, which is used to update the service area of ​​the MBS. Optionally, the third message may carry the identification information of the multicast group or the session identifier of the multicast session, and may also carry the updated service area information of the MBS (described below as the information of the new MBS service area).

[0114] For example, the session management function can receive service area information of the MBS sent by the multicast / broadcast session management function, or the session management function can receive service area information of the MBS sent by the UDR, or the session management function can receive service area information of the MBS sent by the UDM, or the session management function can receive service area information of the MBS sent by the PCF. Unless otherwise specified, the service area information of the MBS involved in the embodiments of this application can be information of the initially provided service area, or it can be information of a new service area.

[0115] In one possible implementation, the first message could be an N11 message, such as the service (Namf_Communication_N1N2MessageTransfer) used by the session management function to call the AMF interface for communication services to transmit N1N2 messages.

[0116] S202: The access management function sends the location information of the first terminal device.

[0117] Correspondingly, the session management function receives the location information of the first terminal device.

[0118] The location information of the first terminal device can be information indicating the location of the first terminal device, or it can be information indicating that the first terminal device is located outside or within the service area of ​​the MBS. The location of the first terminal device can be its latest location. The location of the first terminal device can be represented by one or more of the following information: the current geographical location of the first terminal device (e.g., latitude and longitude coordinates), the IP address of the terminal device, the cell the terminal device is currently residing in, the base station the terminal device is currently residing in, etc.

[0119] The location information of the first terminal device can be information indicating the location of the first terminal device, or it can be information indicating that the first terminal device is located outside or within the service area of ​​the MBS. The location of the first terminal device can be its latest location. The location of the first terminal device can be represented by one or more of the following information: the current geographical location of the first terminal device, the IP address of the terminal device, the cell the terminal device is currently residing in, the base station the terminal device is currently residing in, etc.

[0120] Optionally, the session management function can also receive information about the MBS's service area sent by the multicast / broadcast session management function. The multicast / broadcast session management function can obtain information about the MBS's service area from the NRF, NEF, PCF, AF, or locally.

[0121] The timing of when the multicast / broadcast session management function sends MBS service area information to the session management function is not restricted. For example, the multicast / broadcast session management function can save the session state of the multicast session. When the session state is active, the multicast / broadcast session management function sends MBS service area information to the session management function. When the session state is deactivated, the multicast / broadcast session management function may not send MBS service area information to the session management function, or the multicast / broadcast session management function may wait until the multicast session is about to be activated (such as when an activation request or activation notification is received) or is in an active state before sending MBS service area information to the session management function. For example, the multicast / broadcast session management function can send an information notification message (Nmbsmf_Information_Notify) to the session management function, which carries MBS service area information.

[0122] The access management function can obtain the location information of the first terminal device. One possible way is that after receiving the first message, the access management function sends a location reporting control message to the access network device. Subsequently, the access management function receives location report messages sent from the access network device and obtains the latest location information of the first terminal device.

[0123] S203: When the location information of the first terminal device meets the first condition, the session management function stops sending MBS data to the first terminal device.

[0124] The first condition can be location information used to indicate the location of the first terminal device, and the session management function can determine that the first terminal device is located outside the service area of ​​the MBS based on the location of the first terminal device. Alternatively, the first condition can be location information used to indicate that the first terminal device is located outside the service area of ​​the MBS.

[0125] When the location of the first terminal device meets the first condition, the session management function can stop sending MBS data to the first terminal device in one or more of the following ways. Optionally, in the following ways, the session management function can also send information about the service area of ​​MBS to the first terminal device.

[0126] Method 1: The session management function notifies the user plane function (such as UPF) to stop sending MBS data to the first terminal device. In this method, the user plane function may not send MBS data.

[0127] Method 2: The session management function sends a fourth message to the access network device. This fourth message triggers the access network device to delete the information of the first terminal device from the context information corresponding to the multicast group. The information of the first terminal device may include, but is not limited to, one or more of the following: the device identifier of the first terminal device, the location of the first terminal device, and the context information of the first terminal device. The context information of the first terminal device may include, but is not limited to, one or more of the following: the device identifier of the first terminal device, the cell the first terminal device is currently camped on, the base station the first terminal device is currently camped on, the IP address of the first terminal device, the location information of the first terminal device, and information about the multicast groups the first terminal device has joined.

[0128] Method 3: The session management function sends a fifth message to the access network device. This fifth message triggers the access network device to delete the multicast group information from the context information of the first terminal device. The multicast group information includes, but is not limited to, one or more of the following: multicast group identification information, unicast QoS stream information corresponding to the multicast group, etc. The unicast QoS stream corresponding to the multicast group refers to the unicast QoS stream used to transmit MBS data. The QoS stream can be uniquely identified by its QoS Flow ID (QFI).

[0129] Method 4: The session management function sends a sixth message to the access network device, which instructs the access network device to stop sending MBS data to the first terminal device. In this method, the user plane function can send MBS data to the access network device, but the access network device does not send MBS data.

[0130] It is worth noting that the session management function sending the fourth / fifth / sixth message to the access network device can refer to the session management function sending the fourth / fifth / sixth message directly to the access network device, or it can refer to the session management function sending the information in the fourth / fifth / sixth message to the access network device through the access management function (that is, the access management function re-determines and sends the message based on the information in the fourth / fifth / sixth message sent by the session management function).

[0131] In this embodiment, the session management function can proactively trigger the acquisition of the terminal device's location information based on the terminal device's context information, thereby determining whether the terminal device can receive or should continue to receive MBS data at its current location, and stopping the transmission of MBS data to the terminal device when the terminal device cannot receive or should not continue to receive MBS data. This can reduce the waste of transmission resources and improve the success rate of MBS data transmission.

[0132] Figure 3 A possible data communication method provided in this application embodiment includes the following steps: S301: Access network equipment obtains information about the service area of ​​MBS.

[0133] In S301, one possible implementation is that the access network device obtains information about the service area of ​​the MBS from the multicast / broadcast NRF, NEF, UDM, UDR, or AF. Optionally, the multicast / broadcast session management function can proactively send the service area information of the MBS to the access network device, or the multicast / broadcast session management function can send the service area information of the MBS to the access network device after receiving an information acquisition request from the access network device. In this embodiment, the timing of the multicast / broadcast session management function sending the service area information of the MBS is not limited.

[0134] For example, the multicast / broadcast session management function can send information about the service area of ​​the MBS to the access management function, and the access management function can then send this information about the service area of ​​the MBS to the access network devices. For instance, the multicast / broadcast session management function can send an accept request response message (Nmbsmf_Reception_Request Response) or an accept start response message (Nmbsmf_Reception_Start Response) to the access management function, and this Nmbsmf_Reception_Request Response or Nmbsmf_Reception_Start Response carries the information about the service area of ​​the MBS.

[0135] S302: If the first terminal device is located outside the service area of ​​MBS, the access network device stops sending MBS data to the first terminal device, or notifies the first terminal device to stop receiving MBS data.

[0136] The access network device can obtain the location of the first terminal device and the information of the service area of ​​MBS in S301. Therefore, the access network device can determine that the first terminal device is located outside or inside the service area of ​​MBS.

[0137] When the first terminal device is located outside the MBS service area, the access network device may stop sending MBS data to the first terminal device in one or more of the following ways. Optionally, in the following ways, the access network device may also send information about the MBS service area to the first terminal device.

[0138] Method 1: The access network device sends a seventh message to the session management function. This seventh message triggers the session management function to configure the first terminal device to stop receiving MBS data. This seventh message may also include the session identifier of the multicast session, such as TMGI. After receiving this seventh message, the session management function can stop sending MBS data to the first terminal device. See S203 above for details, which will not be elaborated here.

[0139] Method 2: The access network device sends the location information of the first terminal device to the session management function and receives an eighth message from the session management function. The eighth message triggers the access network device to delete the information of the first terminal device from the context information corresponding to the multicast group. Based on the eighth message, the access network device deletes the information of the first terminal device from the context information corresponding to the multicast group.

[0140] Method 3: The access network device sends the location information of the first terminal device to the session management function and receives the ninth message from the session management function. The ninth message triggers the access network device to delete the multicast group information from the context information of the first terminal device. Based on the eighth message, the access network device deletes the multicast group information from the context information of the first terminal device.

[0141] Method 4: The access network device releases or deletes the context information of the first terminal device.

[0142] When the first terminal device is located within the MBS service area, the access network device can notify the first terminal device to stop receiving MBS data in the following way: the access network device sends a tenth message to the first terminal device, which configures the first terminal device to stop receiving MBS data. If the user plane function subsequently sends MBS data to the first terminal device, the first terminal device can refuse to receive the MBS data, or the first terminal device can choose not to process the received MBS data.

[0143] It is worth noting that the session management function sending the eighth / ninth / tenth message to the access network device can refer to the session management function sending the eighth / ninth / tenth message directly to the access network device, or it can refer to the session management function sending the information in the eighth / ninth / tenth message to the access network device through the access management function (i.e., the access management function re-determines and sends the message based on the information in the eighth / ninth / tenth message sent by the session management function).

[0144] In this embodiment, the access network device can determine whether the terminal device can receive or should continue receiving MBS data at its current location, and when the terminal device cannot receive or should not continue receiving MBS data, it can stop sending MBS data to the terminal device or notify the terminal device to stop receiving MBS data. This can reduce the waste of transmission resources and improve the success rate of MBS data transmission.

[0145] Figure 4 A possible data communication method provided in this application embodiment includes the following steps: The process of S401 can be found in S301, and the similarities will not be repeated here.

[0146] S402: If the coverage area of ​​the access network device does not overlap with the service area of ​​the MBS, the access network device triggers the release of the shared tunnel corresponding to the MBS.

[0147] It should be noted that a shared tunnel is established between a multicast / broadcast user plane function (such as an MB-UPF entity) and an access network device (such as a RAN) for transmitting MBS data. The access network device here can be any access network device with MBS capability (i.e., supporting multicast). The shared tunnel can correspond to the N3mb reference point described in the standard. The shared tunnel can be used solely for transmitting downlink data.

[0148] The multicast / broadcast user plane function sends MBS data to the access network device through a shared tunnel. The access network device can then send the MBS data to the terminal device residing in this access network device via point-to-point and / or point-to-multipoint transmission methods, so as to the terminal device that has joined the multicast session.

[0149] Shared tunnels can be based on the General Packet Radio Service (GPRS) Tunnel Protocol-User Plane (GTP-U) protocol. One implementation of a shared tunnel involves the MB-UPF establishing a separate shared tunnel for each access network device. In other words, the MB-UPF sends MBS data to each RAN separately, for example, when the access network device does not support multicast (also known as IP multicast data reception) or the transport network (i.e., the network from the MB-UPF to the RAN) does not support multicast (also known as IP multicast data transmission). Another implementation involves the MB-UPF sending one copy of the MBS data, which is then copied at a router in the transport network. The final copy of the data reaches different access network devices. For example, in this implementation, the access network devices support IP multicast data reception, and the transport network supports IP multicast data transmission.

[0150] The coverage area of ​​the access network equipment includes the access equipment's cell or tracking area (TA). The access network equipment can provide services to terminal devices within its coverage area or tracking area. Areas where the coverage area of ​​the access network equipment does not overlap with the service area of ​​the MBS include: All cells or tracking areas of the access network equipment are not located within the MBS's service area, or The cells or tracking areas provided by the access network equipment are not located within the MBS's service area, or The cells or tracking areas available to the access network equipment are not located within the MBS's service area, or The cells or tracking areas included in the access network equipment are not located within the MBS's service area.

[0151] The description of how access network equipment triggers the release of the shared tunnel corresponding to MBS can be found in the 3GPP standard, and will not be elaborated here.

[0152] In this embodiment, when the coverage area of ​​the access network does not overlap with the service area of ​​the MBS, the access network device can trigger the process of releasing the shared tunnel, so that the terminal devices within the coverage area of ​​the access network device do not receive MBS data, which can reduce the waste of transmission resources and improve the data transmission success rate of MBS.

[0153] Figure 5 A data communication method provided in this application includes the following steps: The process of S501 can be found in S301, and the similarities will not be repeated here.

[0154] S502: If the first cell or first tracking area of ​​the access network device is outside the service area of ​​MBS, the access network device shall stop sending MBS data in the first cell or first tracking area.

[0155] When the first cell or first tracking area of ​​the access network equipment is outside the service area of ​​MBS, the terminal equipment in the first cell or first tracking area cannot receive MBS data.

[0156] When the first cell or first tracking area of ​​the access network device is outside the service area of ​​MBS, the access network device may stop transmitting MBS data in the first cell or first tracking area in one or more of the following ways. Optionally, in the following ways, the access network device may also transmit the service area of ​​MBS to terminal devices within the first cell or first tracking area.

[0157] Method 1: The access network device sends an eleventh message to the session management function. The eleventh message triggers the session management function to configure terminal devices in the first cell or the first tracking area to stop receiving MBS data. This eleventh message may also include a session identifier for the multicast session. After receiving this eleventh message, the session management function can stop sending MBS data to terminal devices in the first cell or the first tracking area. See S203 above for details, which will not be elaborated here.

[0158] Method 2: The access network device deletes the terminal device information in the first cell or first tracking area from the context information corresponding to the multicast group. Optionally, the access network device may send the location information of the terminal device in the first cell or first tracking area, or an indication that the first cell or first tracking area is located outside the service area of ​​the MBS, to the session management function. The access network device receives a twelfth message from the session management function, which triggers the access network device to delete the terminal device information in the first cell or first tracking area from the context information corresponding to the multicast group.

[0159] Method 3: The access network device deletes multicast group information from the context information of terminal devices in the first cell or first tracking area. Optionally, the access network device may send the location information of terminal devices in the first cell or first tracking area, or an indication that the first cell or first tracking area is located outside the service area of ​​the MBS, to the session management function. The access network device receives a thirteenth message from the session management function, which triggers the access network device to delete the multicast group information from the context information of terminal devices in the first cell or first tracking area.

[0160] Method 4: The access network device releases or deletes the context information of the terminal device in the first cell or the first tracking area.

[0161] It is worth noting that the session management function sending the eleventh / twelfth / thirteenth message to the access network device can refer to the session management function sending the eleventh / twelfth / thirteenth message directly to the access network device, or it can refer to the session management function sending the information in the eleventh / twelfth / thirteenth message to the access network device through the access management function (i.e., the access management function re-determines and sends the message based on the information in the eleventh / twelfth / thirteenth message sent by the session management function).

[0162] In this embodiment, when the first cell or the first tracking area is outside the service area of ​​MBS, the terminal devices residing in the first cell or the first tracking area cannot receive or should not continue to receive MBS data. Therefore, the access network device can stop sending MBS data to the first cell or the first tracking area, which can reduce the waste of transmission resources and improve the success rate of MBS data transmission.

[0163] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0164] The above communication method is explained below with several specific communication processes.

[0165] Figure 6 One possible communication process provided for an embodiment of this application includes the following steps: S601: MB-SMF obtains information about the MBS service area.

[0166] S601 is an optional step. For example, when the multicast session of the local MBS is active, the MB-SMF executes S601; when the multicast session of the local MBS is inactive, the MB-SMF does not execute S601.

[0167] The optional MBS service area information can be the initial MBS service area information or the updated MBS service area information.

[0168] S602: In the MB-SMF sending the MBS update notification message to the SMF, the MBS update notification message includes information about the service area of ​​the MBS.

[0169] Alternatively, information about the MBS's business area can also be carried in the information notification message (Nmbsmf_Information_Notify).

[0170] S603: The SMF updates the saved service area information of the MBS based on the received service area information of the MBS.

[0171] S604: In the MB-SMF sending the MBS update notification message to the RAN, the MBS update notification message includes information about the service area of ​​the MBS.

[0172] Generally, when the service area of ​​an MBS is updated, the MB-SMF sends the service area information of the MBS to the RAN. This service area information is the updated (new / updated) service area information of the MBS.

[0173] For example, the MB-SMF can send a receive request response message (Nmbsmf_Reception_RequestResponse) to the AMF, which includes information about the MBS's service area. The AMF then sends this information to the RAN.

[0174] S605: RAN determines whether its coverage area is outside the service area of ​​MBS.

[0175] The process of S605 can be found in S402 above, and will not be repeated here.

[0176] S606: If the RAN's coverage area is outside the MBS's service area, the RAN triggers the release process of the MBS's corresponding sharedtunnel.

[0177] Optionally, after receiving the service area information of MBS, RAN can send an MBS update notification response message to MB-SMF.

[0178] When the RAN's coverage area is outside the MBS's service area, or when the UE is outside the MBS's service area, the RAN can trigger one or more UEs to stop receiving MBS data. For specific implementation methods of the RAN triggering the UE to stop receiving MBS data, please refer to Implementation Method 1 (S607-S609), Implementation Method 2 (S610-S611), or Implementation Method 3 (S612).

[0179] S607: The RAN sends an N2 message to the SMF to trigger the SMF to configure the UE to stop receiving data from the MBS.

[0180] The N2 message includes the PDU session ID and N2 information. Optionally, the N2 information may include the MBS session ID, such as TMGI, and may also include indications that the UE is located outside the MBS service area, and / or the UE's location information (such as the cell ID or tracking area ID of the UE's current camp).

[0181] The RAN can determine whether to stop sending MBS data to the UE and send the N2 message. For example, the RAN can determine whether to stop sending MBS data to the UE based on the UE's location information and the MBS service area information, or based on indication information that the UE is located outside the MBS service area.

[0182] S608: SMF determines whether to stop sending MBS data to UE.

[0183] In this S608, the SMF determines whether to stop sending MBS data to the UE based on the UE's location information and the MBS's service area information, or determines whether to stop sending MBS data to the UE based on the indication information that the UE is located outside the MBS's service area.

[0184] Alternatively, in S608, the SMF can determine whether to stop sending MBS data to the UE based on the N2 message.

[0185] S609: The SMF sends an N2 message to the RAN to notify it to stop sending MBS data to the UE.

[0186] The N2 message may include N2 information, which includes context information of the multicast group. This context information does not include information about the multicast group (such as information about the unicast QoS flow corresponding to the multicast group), or the N2 information is used to trigger the RAN to delete the unicast QoS flow information corresponding to the multicast group in the context information of the UE.

[0187] The N2 message may optionally include N1 information, which includes information about MBS business data.

[0188] S610: RAN releases or deletes UE information from the context information corresponding to the multicast group.

[0189] Alternatively, the RAN can release or delete multicast group information from the UE's context information.

[0190] S611: The RAN sends an N2 message to the SMF, and the N2 message triggers the SMF to configure itself to stop sending MBS data to the UE.

[0191] The N2 message carries N2 information and a session identifier for the PDU session. Optionally, the N2 information may include a session identifier for the multicast session and / or an indication to trigger SMF configuration to stop sending MBS data to the UE.

[0192] S612: The RAN does not delete (or retains) the UE's context information, but sends a configuration message to the UE. This configuration message is used to configure the UE to stop receiving data from the UE's MBS.

[0193] Alternatively, the RAN may not send MBS data to the UE.

[0194] It is worth noting that in some implementations of this embodiment, steps S607-S611 are optional steps; in other implementations, steps S607-S609 and S612 are optional steps; and in yet another implementation, steps S610-S612 are optional steps.

[0195] In this embodiment, the RAN obtains the latest location information of the UE. When the UE is outside the service area of ​​the MBS, the UE no longer receives data from the MBS, eliminating the need for additional signaling. Furthermore, in S612, if the RAN does not delete the UE's context information, the ping-pong effect caused by the UE moving back and forth within the MBS service area can be resolved, thereby improving the stability of the communication system.

[0196] Figure 7 One possible communication process provided for an embodiment of this application includes the following steps: S701: UE requests to join multicast group.

[0197] For example, the UE sends a PDU session modification request message to the SMF, which contains the session identifier of the multicast session (such as TMGI or IP multicast address).

[0198] S702: The SMF determines the location information of the UE that needs to be obtained based on the context information corresponding to the multicast group.

[0199] SMF can obtain the context information of a multicast session, i.e., the context information corresponding to the multicast group, based on the session identifier of the multicast session.

[0200] For example, the context information corresponding to a multicast group may include indication information for obtaining the UE's location information, or the context information corresponding to a multicast group may include information that the multicast session type is local MBS, or the context information corresponding to a multicast group may include information about the service area of ​​the MBS. The SMF can then determine that the UE's location information needs to be obtained.

[0201] S703: SMF sends an N11 message to AMF. The N11 message includes the session identifier of the multicast session and optionally includes information about the service area of ​​MBS.

[0202] If the N11 message does not include information about the MBS's service area, the AMF can obtain this information based on the session identifier of the multicast session. For example, the AMF can send a query request message to the Network Storage Function (NRF), UDM, or PCF, which includes the session identifier of the multicast session. The NRF, UDM, or PCF can then send a query response message to the AMF, which includes information about the MBS's service area.

[0203] Optionally, the N11 message may also include N2 information, which is forwarded by the AMF to the RAN. The N2 information includes the session identifier of the multicast session and optionally includes information about the MBS's service area. In this case, the AMF may not need to obtain the MBS's service area information.

[0204] S704: The AMF sends an N2 message to the RAN, which includes the session identifier of the multicast session and optionally includes information about the service area of ​​the MBS.

[0205] If the N2 message includes a session identifier for a multicast session, the RAN can determine whether the context information of the multicast group corresponding to the session identifier for the multicast session is stored.

[0206] If the RAN stores the context information of the multicast group corresponding to the session identifier, the RAN can detect whether one or more UEs that are located within the RAN's coverage area and are receiving data from the MBS are located within the MBS's service area. If the UE is located outside the MBS's service area, the UE is triggered to stop receiving MBS data.

[0207] If the RAN does not save the context information of the multicast group corresponding to the session identifier, the RAN can execute S705.

[0208] S705: RAN obtains information about the service area of ​​MBS.

[0209] S705 is an optional step.

[0210] The RAN can obtain information about the service area of ​​the MBS from the MB-SMF. For example, the RAN sends a request message to the AMF, which includes the session identifier of the multicast session. Then the AMF sends a request message to the MB-SMF, which also includes the session identifier of the multicast session. The MB-SMF sends the service area information of the MBS to the AMF, and the AMF then sends the service area information of the MBS back to the RAN.

[0211] When the RAN determines that the UE is outside the service area of ​​the MBS, it executes S706.

[0212] S706: RAN sends N2 message to AMF.

[0213] The N2 message includes one or more of the following information: UE location information (such as the cell identifier where the UE is located), indication information that the UE is located outside the service area of ​​the MBS, UE identification information, and the UE list corresponding to the UE (the UE list includes multiple UEs).

[0214] S707: AMF sends N11 message to SMF.

[0215] N11 messages can be subscription messages (Namf_EventExposure_Subscribe Notify) or update context messages (Nsmf_PDUSession_UpdateSMContext request).

[0216] The N11 message includes one or more of the following information: UE location information, indication that the UE is located outside the MBS service area, UE identification information, UE list corresponding to the UE, and session identifier of the multicast session.

[0217] S708: SMF determines whether to stop sending MBS data to UE.

[0218] For the procedures in S709-S714, please refer to S607-S612.

[0219] S715: When the service area of ​​MBS is updated, MB-SMF can send an MBS update notification message to SMF, which includes information about the new service area of ​​MBS.

[0220] SMF can update the information of the MBS's business area stored locally based on the information of the new MBS's business area.

[0221] S716: The SMF sends an MBS update notification message to the RAN, which includes information about the new MBS service area.

[0222] After receiving information about the service area of ​​a new MBS, the RAN can continue to detect whether one or more UEs located within the RAN's coverage area and receiving data from the MBS are located within the MBS's service area.

[0223] In this embodiment, when the UE joins a multicast group and the RAN establishes context information for a multicast session, the RAN can detect whether the UE in the multicast group is outside the service area of ​​the MBS. When the UE moves out of the service area of ​​the MBS, the RAN can report the information of the UE that has moved out of the service area of ​​the MBS without introducing additional signaling.

[0224] Figure 7 In the illustrated embodiment, the RAN and / or SMF can determine whether the UE has moved out of the MBS's service area. Figure 6 In the illustrated embodiment, the RAN primarily determines whether the UE has moved out of the MBS's service area. Figure 7 China does not restrict whether the RAN supports multicast.

[0225] Figure 8 One possible communication process provided for an embodiment of this application includes the following steps: The procedures for S801-S802 can be found in S701-S702.

[0226] S803: SMF sends an event exposure subscription message (Namf_EventExposure_Subscribe) to AMF, which includes the session identifier of the multicast session.

[0227] The event disclosure subscription message may also include one or more of the following information: UE identification information, MBS service area information.

[0228] Alternatively, the event exposure subscription message can replace the PDU session update context response message (Nsmf_PDUSession_UpdateSMContext response).

[0229] S804: The AMF obtains information about the MBS's service area from the UDM (or NRF or PCF).

[0230] S805: The AMF sends a location report control message to the RAN.

[0231] Optionally, location reporting controls include information about the MBS's business area.

[0232] S806: The RAN sends a location report message to the AMF.

[0233] The location report message includes the UE's location information.

[0234] S807: The AMF sends a subscription notification message (Namf_EventExposure_Subscribe Notify) to the SMF, which includes the UE's location information.

[0235] S808: MB-SMF sends an MBS update notification message to SMF, which includes information about the new MBS service area.

[0236] S809: SMF stops sending MBS data to the UE when the UE is outside the MBS service area.

[0237] For the procedures in S810-S815, please refer to S607-S612.

[0238] Figure 8 The communication process shown is Figure 7 They are similar, but the difference lies in the messages exchanged between SMF and AMF. Figure 8 China does not restrict whether the RAN supports multicast.

[0239] Figure 9 One possible communication process provided for an embodiment of this application includes the following steps: The procedures in S901-S902 can be found in S701-S702.

[0240] S903: The SMF sends an N2 SM message to the RAN, which includes the session identifier of the multicast session.

[0241] S904: RAN sends a response message to SMF for sending an N2 SM message.

[0242] The response message to the N2 SM message is used to indicate whether the RAN supports multicast.

[0243] S905: If the delivery mode is "individual MBS delivery", SMF determines to trigger the subscription event.

[0244] If the delivery mode is not "individual MBS delivery", such as "shared delivery", SMF can determine that the subscription event will not be triggered.

[0245] S906: SMF sends an event exposure subscription message (Namf_EventExposure_Subscribe) to AMF.

[0246] The event disclosure subscription message may include one or more of the following information: session identifier of the multicast session, UE identification information, and MBS service area information.

[0247] For the procedures in S907-S909, please refer to S805-S807.

[0248] The procedures in S910-S916 can be found in S809-S815.

[0249] The process in S917 can be found in S715.

[0250] Based on the same technical concept as the above-described data communication method, embodiments of this application also provide a communication device, such as... Figure 10 As shown, the communication device 1000 includes a processing unit 1001 and a transceiver unit 1002. The communication device 1000 can be used to implement the methods described in the above method embodiments. The device 1000 can be applied to a session management function or an access network device, or located in a session management function or an access network device. The functions implemented by the optional transceiver unit 1002 can be accomplished by a communication interface.

[0251] In one possible embodiment, when the device 1000 performs session management, the transceiver unit 1002 is used to send a first message to the access management function according to the context information of the multicast session corresponding to the MBS. The first message is used to trigger the reporting of the location information of the first terminal device, and the first terminal device belongs to the multicast group corresponding to the MBS. The device also receives the location information of the first terminal device from the access management function. The processing unit 1001 is used to stop sending MBS data to the first terminal device when the location information is used to indicate the location of the first terminal device and the location of the first terminal device determines that the first terminal device is located outside the service area of ​​the MBS, or when the location information indicates that the first terminal device is located outside the service area of ​​the MBS.

[0252] In one implementation, the first message carries the identification information of the first terminal device.

[0253] In one implementation, the first message is a subscription message, which is used to subscribe to the location information of the first terminal device.

[0254] In one implementation, the subscription message carries information about the MBS's business area.

[0255] In one implementation, the transceiver unit 1002 is further configured to receive a second message from the first terminal device, the second message being used to request joining a multicast session; or to receive a third message from the multicast / broadcast session management function, the third message being used to update the service area of ​​the MBS.

[0256] In one implementation, the transceiver unit 1002 is specifically configured to send a first message to the access management function if the context information includes the type of multicast session of the multicast group, and the type is local MBS; or if the context information includes first indication information, and the first indication information is used to indicate the acquisition of the location information of the terminal device, send a first message to the access management function; or if the context information includes information about the service area of ​​the MBS, send a first message to the access management function; or if the service type in the context information is multicast service, and the context information includes information about the service area of ​​the MBS, send a first message to the access management function.

[0257] In one implementation, the processing unit 1001 is specifically used to notify the user plane function to stop sending MBS data to the first terminal device through the transceiver unit 1002; or to send a fourth message to the access network device through the transceiver unit 1002, the fourth message being used to trigger the access network device to delete the information of the first terminal device in the context information corresponding to the multicast group; or to send a fifth message to the access network device through the transceiver unit 1002, the fifth message being used to trigger the access network device to delete the information of the multicast group in the context information of the first terminal device; or to send a sixth message to the access network device through the transceiver unit 1002, the sixth message being used to instruct the access network device to stop sending MBS data to the first terminal device.

[0258] In one implementation, the information of the multicast group includes: the identification information of the multicast group; or the information of the unicast QoS stream corresponding to the multicast group.

[0259] In another possible embodiment, when the device 1000 is an access network device, the processing unit 1001 is used to obtain information about the service area of ​​MBS; the transceiver unit 1002 is used to stop sending MBS data to the first terminal device if the first terminal device is located outside the service area of ​​MBS, or to notify the first terminal device to stop receiving MBS data through the transceiver unit 1001; and / or to trigger the release of the shared tunnel corresponding to MBS if the coverage area of ​​the access network device does not intersect with the service area of ​​MBS; and / or to stop sending MBS data in the first cell or the first tracking area if the first cell or the first tracking area of ​​the access network device is located outside the service area of ​​MBS.

[0260] In one implementation, the transceiver unit 1002 is specifically used to receive information from the service area of ​​the MBS of the multicast / broadcast session management function.

[0261] In one implementation, the processing unit 1001 is specifically configured to send a seventh message to the session management function via the transceiver unit 1001, the seventh message being used to trigger the session management function to configure the first terminal device to stop receiving MBS data; or send the location information of the first terminal device to the session management function via the transceiver unit 1001 and receive an eighth message from the session management function, the eighth message being used to trigger the access network device to delete the information of the first terminal device in the context information corresponding to the multicast group, and delete the information of the first terminal device in the context information corresponding to the multicast group according to the eighth message; or send the location information of the first terminal device to the session management function via the transceiver unit 1001 and receive a ninth message from the session management function, the ninth message being used to trigger the access network device to delete the information of the multicast group in the context information of the first terminal device, and delete the information of the multicast group in the context information of the first terminal device according to the eighth message; or release or delete the context information of the first terminal device.

[0262] In one implementation, the transceiver unit 1001 is specifically used to send a tenth message to the first terminal device, the tenth message being used to configure the first terminal device to stop receiving MBS data.

[0263] In one implementation, the processing unit 1001 is specifically used to send an eleventh message to the session management function through the transceiver processing 1002. The eleventh message is used to trigger the session management function to configure the terminal devices in the first cell or the first tracking area to stop receiving MBS data; or to delete the information of the terminal devices in the first cell or the first tracking area from the context information corresponding to the multicast group; or to delete the information of the multicast group from the context information of the terminal devices in the first cell or the first tracking area; or to release or delete the context information of the terminal devices in the first cell or the first tracking area.

[0264] It should be noted that the module division in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, exist as separate physical units, or have two or more units integrated into one unit. The integrated units can be implemented in hardware or as software functional units. For example, a transceiver unit may include a receiving unit and / or a transmitting unit.

[0265] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the integrated unit can be stored in a storage medium as a computer software product, including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application.

[0266] like Figure 11 As shown in the diagram, this application also provides a schematic diagram of the structure of a communication device 1100. The device 1100 can be used to implement the methods described in the above method embodiments, as can be seen in the descriptions in the above method embodiments.

[0267] Device 1100 includes one or more processors 1101. Processor 1101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., a base station, terminal, or chip), execute software programs, and process data from the software programs. The communication device may include a transceiver unit for inputting (receiving) and outputting (transmitting) signals. For example, the transceiver unit can be a transceiver, an RF chip, etc.

[0268] The apparatus 1100 includes one or more processors 1101, which can implement the methods in the embodiments shown above. Optionally, in addition to implementing the methods in the embodiments shown above, the processors 1101 can also implement other functions.

[0269] In one design, processor 1101 can execute instructions that cause device 1100 to perform the methods described in the above method embodiments. The instructions may be stored wholly or partially within processor 1101, such as instruction 1103 being wholly or partially stored in processor 1101, or instruction 1103 being stored in processor 1101 and instruction 1104 being stored in memory 1102 coupled to the processor. Processor 1101 can simultaneously execute instructions 1103 and 1104 to cause device 1100 to perform the methods described in the above method embodiments. Instructions 1103 and 1104 are also referred to as computer programs.

[0270] In another possible design, the communication device 1100 may also include circuitry that can perform the functions described in the foregoing method embodiments.

[0271] In another possible design, device 1100 may include one or more memories 1102 storing instructions 1104, which can be executed on processor 1101 to cause device 1100 to perform the methods described in the above method embodiments. Optionally, memory 1102 may also store data. Processor 1101 may also optionally store instructions and / or data. For example, one or more memories 1102 may store the correspondences described in the above embodiments, or related parameters or tables involved in the above embodiments. The processor and memory may be configured separately or integrated together.

[0272] In another possible design, device 1100 may also include transceiver 1105 and antenna 1106. Processor 1101, which may be called a processing unit, controls the device (terminal or base station). Transceiver 1105, which may be called a transceiver, transceiver circuit, or transceiver unit, is used to realize the device's transmission and reception functions through antenna 1106.

[0273] The processor can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), one or more integrated circuits for controlling the execution of the program in this application, a general-purpose processor, a digital signal processor (DSP), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software modules can be stored in a storage medium located in memory.

[0274] The memory can be volatile or non-volatile, or a combination of both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory. The memory may be standalone and connected to the processor via communication lines. The memory may also be integrated with the processor.

[0275] This application also provides a computer-readable medium having a computer program stored thereon, which, when executed by a computer, implements the data communication method of any of the above method embodiments.

[0276] This application also provides a computer program product, including a computer program that, when executed by a computer, implements the data communication method of any of the above method embodiments.

[0277] This application also provides a communication system, including a terminal device and a network device. The network device may include one or more of session management functions, access network devices, and access management functions. The terminal device and the network device can implement any of the above-described method embodiments.

[0278] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be the communication device described above. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. The computer-readable storage medium can be the storage medium or the memory described above.

[0279] In one possible design, when the aforementioned communication device is a chip, such as a chip in a network device, or a chip in a terminal device, the determining unit or processor 1101 can be one or more logic circuits, and the transmitting unit or receiving unit or transceiver 1105 can be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver 1105 can also be a transmitting unit and a receiving unit, where the transmitting unit can be an output interface and the receiving unit can be an input interface, integrated into one unit, such as an input / output interface. Figure 12 As shown, Figure 12 The communication device shown includes a logic circuit 1201 and an interface circuit 1202. That is, the aforementioned determining unit or processor 1101 can be implemented using the logic circuit 1201, and the transmitting unit, receiving unit, or transceiver 1105 can be implemented using the interface circuit 1202. The logic circuit 1201 can be a chip, processing circuit, integrated circuit, or system-on-chip (SoC) chip, etc., and the interface circuit 1202 can be a communication interface, input / output interface, etc. In this embodiment, the logic circuit and the interface circuit can also be coupled to each other. The specific connection method of the logic circuit and the interface circuit is not limited in this embodiment.

[0280] In some embodiments of this application, the logic circuit 1201 and interface circuit 1202 can be used to perform the aforementioned session management functions or functions or operations performed by the access network device. The interface circuit 1202 can be used to receive signals from other communication devices besides the communication device 1200 and transmit them to the logic circuit 1201, or to send signals from the logic circuit 1201 to other communication devices besides the communication device 1200. The logic circuit 1201 can be used to implement any of the above method embodiments by executing code instructions.

[0281] For example, interface circuit 1202 is used to send a first message to the access management function based on the context information of the multicast session corresponding to MBS. The first message is used to trigger the reporting of the location information of the first terminal device, where the first terminal device belongs to the multicast group corresponding to MBS; and to receive the location information of the first terminal device from the access management function. Logic circuit 1201 is used to stop sending MBS data to the first terminal device when the location information indicates the location of the first terminal device, and the session management function determines that the first terminal device is located outside the service area of ​​MBS based on the location of the first terminal device, or when the location information indicates that the first terminal device is located outside the service area of ​​MBS. The functions or operations performed by the network device or terminal device can refer to the foregoing method embodiments, and will not be repeated here.

[0282] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0283] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0284] In the embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be indirect couplings or communication connections through some interfaces, apparatuses, or units, or they may be electrical, mechanical, or other forms of connection.

[0285] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments of this application, depending on actual needs.

[0286] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0287] From the above description of the embodiments, those skilled in the art will clearly understand that this application can be implemented in hardware, firmware, or a combination thereof. When implemented in software, the above functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transmission of a computer program from one place to another. Storage media can be any available medium that a computer can access.

[0288] In summary, the above are merely embodiments of the technical solutions of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the scope of protection of this application.

Claims

1. A data communication method, applied to an access network device or a chip in an access network device, characterized in that, include: Obtain information about the service area of ​​the multicast / broadcast service MBS; If the first terminal device is located outside the service area of ​​the MBS, notify the first terminal device to stop receiving data from the MBS; and / or If the coverage area of ​​the access network device does not overlap with the service area of ​​the MBS, then the shared tunnel corresponding to the MBS is released; and / or If the first cell or first tracking area of ​​the access network device is outside the service area of ​​the MBS, the transmission of MBS data in the first cell or first tracking area shall be stopped.

2. The method as described in claim 1, characterized in that, The fact that the coverage area of ​​the access network device does not overlap with the service area of ​​the MBS means that none of the cells or tracking areas of the access network device are located within the service area of ​​the MBS.

3. The method as described in claim 1 or 2, characterized in that, The acquisition of MBS service area information includes: Receive information from the service area of ​​the MBS from the multicast / broadcast session management function.

4. The method according to any one of claims 1-3, characterized in that, The notification to the first terminal device to stop receiving data from the MBS includes: A tenth message is sent to the first terminal device, the tenth message being used to configure the first terminal device to stop receiving data from the MBS.

5. The method according to any one of claims 1-3, characterized in that, The step of stopping the transmission of MBS data in the first cell or the first tracking area includes: Send an eleventh message to the session management function, the eleventh message being used to trigger the session management function to configure the terminal devices in the first cell or the first tracking area to stop receiving data from the MBS; or Delete the information of the terminal device in the first cell or the first tracking area from the context information corresponding to the multicast group; or Delete the multicast group information from the context information of the terminal device in the first cell or the first tracking area; or Release or delete the context information of the terminal device in the first cell or the first tracking area.

6. A communication device, characterized in that, include: The transceiver unit is used to acquire information about the service area of ​​the multicast / broadcast service (MBS). The processing unit is configured to, if the first terminal device is located outside the service area of ​​the MBS, notify the first terminal device to stop receiving data from the MBS through the transceiver unit; And / or if the coverage area of ​​the access network device does not overlap with the service area of ​​the MBS, then release the shared tunnel corresponding to the MBS; and / or if the first cell or the first tracking area of ​​the access network device is located outside the service area of ​​the MBS, stop sending the data of the MBS in the first cell or the first tracking area.

7. A communication device, characterized in that, Includes functions and / or units for performing the method as described in any one of claims 1-5.

8. A communication device, characterized in that, It includes a processor and a memory, wherein the processor is coupled to the memory; The memory stores computer programs or instructions; The processor is configured to execute a computer program or instructions in the memory to cause the apparatus to perform the method as described in any one of claims 1-5.

9. A communication device, characterized in that, It includes a logic circuit and an interface circuit. The interface circuit is used to receive signals from other communication devices besides the communication device and transmit them to the logic circuit, or to send signals from the logic circuit to other communication devices besides the communication device. The logic circuit executes code instructions to implement the method as described in any one of claims 1-5.

10. A computer-readable storage medium, characterized in that, It includes a computer program or instructions that, when run on a computer, cause the method as described in any one of claims 1-5 to be performed.

11. A computer program product, characterized in that, It includes a computer program or instructions that, when run on a computer, cause the method as described in any one of claims 1-5 to be performed.

Images