WO2024032555A1 - 一种通信方法和通信装置 - Google Patents

一种通信方法和通信装置 Download PDF

Info

Publication number
WO2024032555A1
WO2024032555A1 PCT/CN2023/111503 CN2023111503W WO2024032555A1 WO 2024032555 A1 WO2024032555 A1 WO 2024032555A1 CN 2023111503 W CN2023111503 W CN 2023111503W WO 2024032555 A1 WO2024032555 A1 WO 2024032555A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
information
edrx
multicast
network device
Prior art date
Application number
PCT/CN2023/111503
Other languages
English (en)
French (fr)
Inventor
李濛
潘奇
张海森
杨艳梅
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024032555A1 publication Critical patent/WO2024032555A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast

Definitions

  • the embodiments of the present application relate to the field of communication, and more specifically, to a communication method and a communication device.
  • Access network equipment can save terminal energy consumption by configuring extended discontinuous reception (eDRX) for the terminal.
  • eDRX extended discontinuous reception
  • the terminal in the sleep state of eDRX is unreachable, that is, the terminal cannot receive downlink data.
  • a terminal can receive multicast service data (which may be referred to as multicast data) by joining a multicast session, and during the transmission process of multicast data, the terminal remains in a connected state. Due to the limited capacity of the access network equipment, the access network equipment only supports a limited number of terminals to remain connected.
  • the terminal receives multicast data in an inactive state. Specifically, when the access network equipment resources are insufficient, the access network equipment can convert the terminal that has joined the multicast session into an inactive state, and notify the terminal to receive multicast data through broadcast or other methods, thereby realizing the terminal Receive multicast data in inactive state.
  • how to manage eDRX of terminals in an inactive state has become an urgent problem to be solved.
  • This application provides a communication method and communication device, which can realize eDRX management of terminals in an inactive state.
  • a communication method is provided.
  • the method can be executed by a core network device or by a module or unit in the core network device.
  • a core network device For convenience of description, it will be collectively referred to as the core network device below.
  • the method includes: the core network device learns that the terminal has joined the multicast session; the core network device sends first information, the first information is used to notify the refusal to configure eDRX in an inactive state for the terminal, or the The first information is used to indicate that the terminal is not suitable for eDRX in the inactive state.
  • the core network device when the first information is used to notify the refusal to configure eDRX in the inactive state for the terminal, the core network device sends the first information to the access network device.
  • the core network device when the first information is used to indicate that the terminal is not suitable for eDRX in the inactive state, the core network device sends the first information to the access network device or the terminal.
  • the core network device can notify the access network device to refuse to configure eDRX in the inactive state for the terminal, or instruct the terminal not to use eDRX in the inactive state in order to facilitate access.
  • the network access device does not configure eDRX in the inactive state for the terminal according to the notification or instruction of the core network device; or the core network device indicates to the terminal that the terminal does not apply eDRX in the inactive state so that the terminal can request to update the terminal in the access network device.
  • the eDRX capability (updated to not support eDRX) enables the access network equipment to not configure eDRX in the inactive state for the terminal based on the updated eDRX capability of the terminal, thereby realizing eDRX management of the terminal.
  • not configuring eDRX in the inactive state for the terminal helps to ensure the transmission of multicast data corresponding to the multicast session.
  • the core network device sends the first information, including: when at least one of the following conditions is met, the core network device sends the first information: The access network equipment provided by the terminal does not support eDRX, the terminal does not support eDRX, or the multicast session meets preset conditions; wherein the preset conditions are: the multicast session is in an active state, The multicast service corresponding to the multicast session does not support eDRX, or the multicast session is in an active state and the multicast service corresponding to the multicast session does not support eDRX.
  • the “following conditions” here refer to: the access network equipment that provides services for the terminal does not support eDRX, the terminal does not support eDRX, or the multicast session meets preset conditions.
  • the core network device can further determine whether the above conditions are met. When the above conditions are met, the core network device sends the first message to notify the refusal to configure the terminal. eDRX in the inactive state or indicating that the terminal is not applicable to eDRX in the inactive state. In this way, the judgment results of the core network equipment can be made more accurate.
  • the first information when the first information is used to notify a refusal to configure eDRX in an inactive state for the terminal, the first information includes a refusal Information, the rejection information is used to indicate refusal to configure eDRX in an inactive state for the terminal.
  • the method further includes: the core network device receiving second information, the second information being used to request that the terminal be configured with a non-standard eDRX in active state.
  • the access network device when the access network device determines to convert the terminal to the inactive state, it can request the core network device to configure eDRX in the inactive state for the terminal.
  • the core network device receives the request from the access network device.
  • it can be combined with the fact that the terminal has joined the multicast session to determine that eDRX in the inactive state is not allowed to be configured for the terminal, thereby rejecting the request of the access network device, so that the access network device does not configure the inactive state for the terminal after the request is rejected.
  • eDRX so that eDRX in the inactive state is not configured for the terminal when the terminal has joined the multicast session, which helps to ensure the transmission of multicast data corresponding to the multicast session.
  • the rejection information includes a reason for refusing to configure eDRX in an inactive state for the terminal; wherein the reason includes at least one of the following: The terminal has joined a multicast session, the access network equipment that provides services to the terminal does not support eDRX, the terminal does not support eDRX, or the multicast session meets preset conditions; wherein the preset condition is : The multicast session is in an active state, and the multicast service corresponding to the multicast session does not support eDRX, or the multicast session is in an active state, and the multicast service corresponding to the multicast session does not support eDRX.
  • the method further includes: the core network device receiving third information from the access network device, and the third information is To indicate that the access network equipment does not support eDRX.
  • the access network device can report to the core network device whether it supports eDRX, so that the core network device can determine whether to allow inactive eDRX to be configured for the terminal based on the eDRX capability of the access network device.
  • the core network device is an access and mobility management function network element or a session management function network element.
  • the core network device is an access and mobility management functional network element
  • the method further includes: the access and mobility management The functional network element receives service information from the session management function, where the service information is used to indicate that the multicast service corresponding to the multicast session does not support eDRX.
  • the core network device can determine whether to allow eDRX in the inactive state to be configured for the terminal based on whether the multicast service corresponding to the multicast session that the terminal has joined supports eDRX.
  • the service information includes the type of the multicast service, and the type is a delay-sensitive type.
  • the core network device is an access and mobility management functional network element
  • the method further includes: the access and mobility management The functional network element receives fourth information from the session management functional network element, where the fourth information is used to indicate that the terminal has joined the multicast session.
  • the session management function network element provides the access and mobility management function network element with information that the terminal has joined the multicast session, so that the access and mobility management function network element can send the third message based on the terminal having joined the multicast session. a message.
  • a communication method is provided.
  • the method can be executed by the access network device or by a module or unit in the access network device.
  • the access network device For convenience of description, it will be collectively referred to as the access network device below.
  • the method includes: when the access network device determines to convert the terminal to the inactive state, the access network device sends second information to the core network device, the second information is used to request to configure the inactive state for the terminal. eDRX in the inactive state; the access network device receives the first information from the core network device, the first information is used to notify the refusal to configure eDRX in the inactive state for the terminal; the access network device According to the first information, eDRX in an inactive state is not configured for the terminal.
  • the access network device when it determines to convert the terminal to the inactive state, it can request the core network device to configure eDRX in the inactive state for the terminal, and do not configure the eDRX for the terminal after the request is rejected by the core network device.
  • the terminal configures eDRX in the inactive state, so that eDRX in the inactive state is not configured for the terminal when the terminal has joined the multicast session, thereby realizing eDRX management of the terminal.
  • the first information includes rejection information
  • the rejection information is used to indicate a refusal to configure eDRX in an inactive state for the terminal.
  • the rejection information includes a reason for refusing to configure eDRX in an inactive state for the terminal; wherein the reason includes at least one of the following: The terminal has joined a multicast session, the access network device does not support eDRX, the terminal does not support eDRX, or the multicast session meets a preset condition; wherein the preset condition is: the multicast The session is in an active state and the multicast service corresponding to the multicast session does not support eDRX, or the multicast session is in an active state and the multicast service corresponding to the multicast session does not support eDRX.
  • the core network device is an access and mobility management function network element or a session management function network element.
  • a communication method is provided.
  • the method can be executed by the access network device or by a module or unit in the access network device.
  • the access network device For convenience of description, it will be collectively referred to as the access network device below.
  • the method includes: the access network device receives first information from the core network device, the first information is used to indicate that the terminal is not suitable for eDRX in the inactive state; when the access network device determines to convert the terminal When in the inactive state, the access network device does not configure eDRX in the inactive state for the terminal according to the first information.
  • the core network device when the terminal has joined the multicast session, can indicate to the access network device that the terminal is not suitable for eDRX in the inactive state, and the access network device can not configure it for the terminal according to the instruction of the core network device.
  • eDRX in the inactive state to achieve eDRX management of the terminal.
  • not configuring eDRX in the inactive state for the terminal helps to ensure the transmission of multicast data corresponding to the multicast session.
  • the core network device is an access and mobility management function network element or a session management function network element.
  • a communication method is provided.
  • the method can be executed by the access and mobility management function network element, or can be executed by a module or unit in the access and mobility management function network element.
  • access and mobility management functional network elements For the convenience of description, hereinafter, they are collectively referred to as access and mobility management functional network elements.
  • the method includes: the access and mobility management function network element receives second information from the access network device, the second information is used to request to configure eDRX in an inactive state for the terminal; the access and mobility The management function network element sends the second information to a first session management function network element and a second session management function network element.
  • the first session management function network element is used to manage the multicast session associated with the terminal.
  • the second session management function network element is used to manage a unicast session that is not associated with the multicast session of the terminal; the access and mobility management function network element receives information from the first session management function The first information of the functional network element, the first information is used to notify the refusal to configure eDRX in the inactive state for the terminal; the access and mobility management functional network element sends the said first information, and/or, sending fifth information to the second session management function network element, where the fifth information is used to trigger the second session management function network element to stop configuring the inactive state for the terminal. eDRX.
  • the access network device interacts with the first session management function network element through the access and mobility management function network element.
  • the access and mobility management function network element may request the first session management function network element and the second session management function network element to configure eDRX in the inactive state for the terminal, and when the access and mobility management function network element receives After receiving the first information from the first session management function network element, the access and mobility management function network element sends the fifth information to the second session management function network element, so as to trigger the second session management function network element to stop configuring non-standard terminal configurations for the terminal. eDRX in the activated state, thereby realizing eDRX management of the terminal.
  • not configuring eDRX in the inactive state for the terminal helps to ensure the transmission of multicast data corresponding to the multicast session.
  • the information received by the access and mobility management function network element and the information sent by the access and mobility management function network element are both called first information or second information, the access and mobility management function network element
  • the information received by the management function network element and the information sent by the access and mobility management function network element can be implemented in the same way or in different ways (for example, through different messages and/or information elements), without limitation.
  • the first information includes rejection information
  • the rejection information is used to indicate a refusal to configure eDRX in an inactive state for the terminal.
  • the rejection information includes rejecting the request for the terminal.
  • the reason why the terminal configures eDRX in the inactive state includes at least one of the following: the terminal has joined a multicast session, the access network device does not support eDRX, the terminal does not support eDRX, or the The multicast session satisfies preset conditions; wherein the preset conditions are: the multicast session is in an active state, the multicast service corresponding to the multicast session does not support eDRX, or the multicast session is in an active state and The multicast service corresponding to the multicast session does not support eDRX.
  • a communication method is provided.
  • the method can be executed by the access network device or by a module or unit in the access network device.
  • the access network device For convenience of description, it will be collectively referred to as the access network device below.
  • the method includes: the access network device learns that the terminal has joined the multicast session; and when the access network device determines to convert the terminal to an inactive state, the access network device does not configure inactivation for the terminal. eDRX in state.
  • the access network device when the terminal has joined the multicast session, the access network device does not configure eDRX in the inactive state for the terminal, thereby realizing eDRX management of the terminal.
  • not configuring eDRX in the inactive state for the terminal helps to ensure the transmission of multicast data corresponding to the multicast session.
  • the access network device does not configure eDRX for the terminal, including: when at least one of the following conditions is met, the access network device does not configure eDRX for the terminal.
  • the terminal configures eDRX in an inactive state: the access network device does not support eDRX, the terminal does not support eDRX, or the multicast session meets a preset condition; wherein the preset condition is: the multicast session The multicast session is in an active state and the multicast service corresponding to the multicast session does not support eDRX, or the multicast session is in an active state and the multicast service corresponding to the multicast session does not support eDRX.
  • the “following conditions” here refer to: the access network device does not support eDRX, the terminal does not support eDRX, or the multicast session meets preset conditions.
  • the access network device can further determine whether the above conditions are met. When the above conditions are met, the access network device does not configure the inactive state for the terminal. eDRX. In this way, the judgment result of the access network device can be made more accurate.
  • the method further includes: the access network device receiving service information from the session management function, the service information being used to indicate the The multicast service corresponding to the multicast session does not support eDRX.
  • the access network device can determine whether to allow eDRX in the inactive state to be configured for the terminal based on whether the multicast service corresponding to the multicast session that the terminal has joined supports eDRX.
  • the service information includes the type of the multicast service, and the type is a delay-sensitive type.
  • a communication method is provided.
  • the method can be executed by a terminal or by a module or unit in the terminal.
  • a terminal For convenience of description, it will be collectively referred to as the terminal below.
  • the method includes: the terminal learns that the terminal has joined the multicast session and the terminal supports eDRX; and the terminal sends sixth information to the access network device, where the sixth information is used to indicate that the terminal does not support eDRX.
  • the terminal that supports eDRX can provide the access network device with information that it does not support eDRX, so that the access network device can determine whether to convert the terminal into an inactive state.
  • eDRX in the inactive state can not be configured for the terminal according to the fact that the terminal does not support eDRX, thereby realizing eDRX management of the terminal.
  • not configuring eDRX in the inactive state for the terminal helps to ensure the transmission of multicast data corresponding to the multicast session.
  • the terminal sends sixth information to the access network device, including: when at least one of the following conditions is met, the terminal sends the sixth information to the access network device Sending the sixth information: receiving the first information from the core network device, the access network device does not support eDRX, the terminal does not support eDRX, or the multicast session meets preset conditions; wherein, the The first information is used to indicate that the terminal is not suitable for eDRX in the inactive state.
  • the preset conditions are: the multicast session is in the active state, the multicast service corresponding to the multicast session does not support eDRX, or all The multicast session is in an active state and the multicast service corresponding to the multicast session does not support eDRX.
  • the “following conditions” here refer to: receiving the first information from the core network device, the access network device does not support eDRX, the terminal does not support eDRX, or the multicast session meets preset conditions.
  • the terminal can further determine whether the above condition is satisfied.
  • the terminal provides sixth information to the terminal. In this way, the judgment result of the terminal can be made more accurate.
  • the core network device is an access and mobility management function network element or a session management function network element.
  • the method further includes: the terminal receiving service information from the session management function, the service information being used to indicate the multicast session The corresponding multicast service does not support eDRX.
  • the terminal can determine whether to provide the sixth information to the access network device according to whether the multicast service corresponding to the multicast session to which the terminal has joined supports eDRX.
  • the service information includes the type of the multicast service, and the type is a delay-sensitive type.
  • the method before the terminal sends the sixth information to the access network device, the method further includes: the terminal sends the sixth information to the access network device.
  • the device sends seventh information, where the seventh information is used to indicate that the terminal supports eDRX.
  • the terminal can update its eDRX capability on the access network device.
  • the method further includes: after the terminal leaves all multicast sessions to which the terminal has joined, the terminal The network access device sends eighth information, where the eighth information is used to indicate that the terminal supports eDRX.
  • the terminal can request to update its eDRX capabilities on the access network equipment.
  • a communication method is provided.
  • the method can be executed by the session management function network element, or can be executed by a module or unit in the session management function network element.
  • the session management function network For the convenience of description, it will be collectively referred to as the session management function network below. Yuan.
  • the method includes: the session management function network element receives second information from the access network device, the second information is used to request to configure eDRX in an inactive state for the terminal; the session management function network element performs the following steps according to the first
  • the second information is to establish a transmission channel between the unicast user plane functional network element and the multicast user plane functional network element.
  • the transmission channel is used to transmit the multicast data of the terminal; the session management functional network element provides access to
  • the network device sends ninth information, where the ninth information is used to indicate that eDRX in an inactive state is successfully configured for the terminal.
  • the access network device can convert the terminal into an inactive state and configure eDRX for the terminal, thereby realizing eDRX management of the terminal.
  • the method further includes: the session management function network element sending an eDRX buffer to the unicast user plane function network element or the multicast user plane function network element.
  • Information, the eDRX cache information is used to cache the multicast data.
  • the access network device when a terminal joins a multicast session, can convert the terminal into an inactive state and configure eDRX for the terminal, and the unicast user plane functional network element or the multicast user plane functional network element can The terminal's multicast data is cached to prevent the terminal from missing multicast data and help ensure the transmission of multicast services.
  • multicast data is cached by the multicast user plane functional network element, and the cache point is relatively high, which helps to reduce the amount of data cached by the network.
  • a communication method is provided.
  • the method can be executed by a multicast user plane functional network element, or can be executed by a module or unit in the multicast user plane functional network element.
  • Multicast user plane functional network element For convenience of description, it will be collectively referred to as Multicast user plane functional network element.
  • the method includes: the multicast user plane functional network element receives eDRX cache information from the session management function network element, and the eDRX cache information is used to cache the multicast data of the terminal; the multicast user plane functional network element is configured according to the eDRX caches information and caches multicast data of the terminal.
  • the access network device can convert the terminal into an inactive state and configure eDRX for the terminal, and the multicast user plane functional network element caches the multicast data of the terminal. This prevents the terminal from missing multicast data and helps ensure the transmission of multicast services.
  • multicast data is cached by the multicast user plane functional network element, and the cache point is relatively high, which helps to reduce the amount of data cached by the network.
  • a ninth aspect provides a communication device, which is used to perform the method provided by any of the above aspects or its implementation.
  • the device may include units and/or modules, such as a processing unit and/or a communication unit, for executing the method provided by any of the above aspects or implementations thereof.
  • the device is a core network device, an access network device, an access and mobility management function network element, a terminal, a session management function or a multicast user plane function network element.
  • the communication unit may be a transceiver, or input/output interface, or or communication interface; the processing unit may be at least one processor.
  • the transceiver is a transceiver circuit.
  • the input/output interface is an input/output circuit.
  • the device is a chip or chip used in core network equipment, access network equipment, access and mobility management function network elements, terminals, session management functions or multicast user plane function network elements. system or circuit.
  • the communication unit It can be the input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip, chip system or circuit, etc.; the processing unit can be at least one processor, processing circuit or logic circuit, etc.
  • a communication device which device includes: a memory for storing a program; at least one processor for executing the computer program or instructions stored in the memory to execute any of the above aspects or the implementation provided by it. method.
  • the device is a core network device, an access network device, an access and mobility management function network element, a terminal, a session management function or a multicast user plane function network element.
  • the device is a chip or chip used in core network equipment, access network equipment, access and mobility management function network elements, terminals, session management functions or multicast user plane function network elements. system or circuit.
  • a communication device in an eleventh aspect, includes: at least one processor and a communication interface.
  • the at least one processor is used to obtain computer programs or instructions stored in a memory through the communication interface to execute any of the above aspects. or methods provided by its implementation.
  • the communication interface can be implemented by hardware or software.
  • the device further includes the memory.
  • a twelfth aspect provides a processor for executing the methods provided in the above aspects.
  • processor output, reception, input and other operations can be understood as processor output, reception, input and other operations.
  • transmitting and receiving operations performed by the radio frequency circuit and the antenna, which is not limited in this application.
  • a computer-readable storage medium stores program code for device execution.
  • the program code includes a method for executing any of the above aspects or its implementation.
  • a fourteenth aspect provides a computer program product containing instructions.
  • the computer program product When the computer program product is run on a computer, it causes the computer to execute the method provided by any of the above aspects or its implementation.
  • a fifteenth aspect provides a chip.
  • the chip includes a processor and a communication interface.
  • the processor reads instructions stored in the memory through the communication interface and executes the method provided by any of the above aspects or its implementation.
  • the communication interface can be implemented by hardware or software.
  • the chip also includes a memory, in which computer programs or instructions are stored.
  • the processor is used to execute the computer programs or instructions stored in the memory.
  • the processor is used to execute Methods provided by any of the above aspects or their implementations.
  • a sixteenth aspect provides a communication system, including the above core network equipment, access network equipment, access and mobility management function network elements, terminals, session management functions or multicast user plane function network elements. at least one.
  • Figure 1 is a schematic diagram of a network architecture suitable for embodiments of the present application.
  • Figure 2 is a schematic diagram of the network architecture of a multicast/broadcast service.
  • Figure 3 is a schematic flow chart of the communication method 300 provided by this application.
  • Figure 4 is a schematic flow chart of the communication method 400 provided by this application.
  • Figure 5 is a schematic flow chart of the communication method 500 provided by this application.
  • Figure 6 is a schematic flow chart of the communication method 600 provided by this application.
  • Figure 7 is an example of the communication method of the present application.
  • Figure 8 is another example of the communication method of the present application.
  • Figure 9 is another example of the communication method of the present application.
  • Figure 10 is another example of the communication method of the present application.
  • Figure 11 is another example of the communication method of the present application.
  • Figure 12 is another example of the communication method of the present application.
  • Figure 13 is a schematic diagram of transmitting multicast data.
  • Figure 14 is another example of the communication method of the present application.
  • Figure 15 is another schematic diagram of transmitting multicast data.
  • Figure 16 is a schematic structural diagram of a device provided by an embodiment of the present application.
  • Figure 17 is a schematic structural diagram of another device provided by an embodiment of the present application.
  • Form indicating” or “instructing” may include direct indication and indirect indication, or “for indicating” or “instructing” may indicate explicitly and/or implicitly.
  • indicating information I when describing certain information as indicating information I, it may include that the information directly indicates I or indirectly indicates I, but it does not mean that the information must contain I.
  • an implicit indication may be based on the location and/or resources used for transmission; an explicit indication may be based on one or more parameters, and/or one or more indexes, and/or one or more bits it represents. model.
  • the first, second, third, fourth and various numerical numbers are only for convenience of description and are not used to limit the scope of the embodiments of the present application. For example, distinguish different fields, different information, etc.
  • Words such as “exemplary”, “for example”, “exemplarily”, “as (another) example” and the like are used to mean examples, illustrations or illustrations. Any embodiment or design described herein as “example” is not intended to be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the word example is intended to present a concept in a concrete way.
  • At least one means one or more, and “plurality” means two or more.
  • “And/or” describes the association of associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the related objects are in an “or” relationship.
  • “At least one of the following” or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items).
  • At least one of a, b and c can mean: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a , b and c.
  • a, b and c can be single or multiple respectively.
  • network element A sending messages, information or data to network element B, and network element B receiving messages, information or data from network element A are intended to illustrate the messages, information or data. It is to be sent to which network element, and it does not limit whether they are sent directly or indirectly through other network elements.
  • the embodiments provided in this application can be applied to various communication systems.
  • the fifth generation ( 5th generation, 5G) or new radio (NR) system long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division Duplex (time division duplex, TDD) system, etc.
  • the embodiments provided in this application can also be applied to non-terrestrial network (NTN) communication systems such as satellite communication systems.
  • NTN non-terrestrial network
  • D2D device-to-device
  • V2X vehicle-to-everything
  • M2M machine-to-machine
  • MTC machine type Communication
  • Internet of things Internet of things, IoT
  • the embodiments provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system.
  • Figure 1 shows a schematic diagram of a network architecture.
  • the network architecture takes the 5th generation system (5GS) as an example.
  • the network architecture may include three parts, namely user equipment (user equipment, UE), data network (data network, DN), and operator network.
  • the operator network may include one or more of the following network elements: (radio) access network (R)AN) equipment, user plane function (UPF) network element, Access and mobility management function (AMF) network element, session management function (SMF) network element, policy control function (PCF) network element, unified data management (unified data management, UDM) network elements and Application function (AF) network element.
  • R radio access network
  • UPF user plane function
  • AMF Access and mobility management function
  • SMF session management function
  • PCF policy control function
  • UDM unified data management
  • AF Application function
  • the part other than (R)AN can be called the core network.
  • the (wireless) access network equipment UPF network element, AMF network element, SMF network element, PCF network element, UDM network element, and AF network element are referred to as (R)AN, UPF, AMF, and SMF respectively.
  • R the (wireless) access network equipment
  • UPF network element UPF network element
  • AMF network element AMF network element
  • SMF network element PCF network element
  • UDM network element AF network element
  • AF network element referred to as (R)AN, UPF, AMF, and SMF respectively.
  • PCF PCF
  • UDM UDM
  • AF AF network element
  • UE may also be called terminal, user, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal equipment, wireless communication equipment, user agent or user device, etc. , for the convenience of description, they are collectively referred to as terminals below.
  • a terminal is a device that can access a wireless communication network.
  • Air interface technology such as NR or LTE
  • Air interface technology can be used to communicate between the terminal and the (R)AN.
  • Air interface technology (such as NR or LTE) can also be used to communicate between terminals.
  • the terminal can be a mobile phone, a tablet, a computer with wireless transceiver functions, a virtual reality (VR) terminal, an augmented reality (AR) terminal, or a terminal in satellite communications.
  • VR virtual reality
  • AR augmented reality
  • terminals in integrated access and backhaul (IAB) systems terminals in WiFi communication systems, terminals in industrial control, terminals in self-driving (self-driving), Terminals in remote medical, terminals in smart grid, terminals in transportation safety, terminals in smart city, terminals in smart home, etc. .
  • (R)AN can be a device used to communicate with a terminal, or it can be a device that connects the terminal to a wireless communication network.
  • RAN may be a node in a wireless access network.
  • base station evolved base station (evolved NodeB, eNodeB), transmission reception point (TRP), home base station (e.g., home evolved NodeB, or home Node B, HNB), Wi-Fi access point Access point (AP), mobile switching center, next generation base station (next generation NodeB, gNB) in 5G mobile communication system, open radio access network (open radio access network, O-RAN or open RAN) Access network equipment, next-generation base stations in the sixth generation (6G) mobile communication system, or base stations in future mobile communication systems, etc.
  • R)AN can also be a module or unit that completes some functions of the base station. For example, it can be a centralized unit (CU), a distributed unit (DU), or a remote radio unit (RRU). ) or baseband unit (BBU), etc.
  • CU centralized unit
  • DU distributed unit
  • RRU remote radio unit
  • BBU baseband unit
  • (R)AN can also be equipment that assumes base station functions in D2D communication systems, V2X communication systems, M2M communication systems, and IoT communication systems.
  • (R)AN can also be a network device in NTN, that is, (R)AN can be deployed on high-altitude platforms or satellites.
  • (R)AN can be a macro base station, a micro base station or an indoor station, or a relay node or a donor node.
  • (R)AN does not limit the specific technology, equipment form, and name used by (R)AN.
  • (R)AN will be collectively referred to as access network equipment below.
  • UPF is mainly responsible for the forwarding and routing of user data in the terminal.
  • UPF can receive user plane data from the DN and send the user plane data to the terminal through the access network equipment.
  • UPF can also receive user plane data from the terminal through the access network equipment and forward it to the DN.
  • the transmission resources and scheduling functions in UPF network elements that provide services for terminals are managed and controlled by SMF.
  • DN is mainly used in operator networks that provide data services to terminals.
  • the Internet a third-party business network, or an IP multi-media service (IMS) network, etc.
  • IMS IP multi-media service
  • AS application servers
  • AMF is mainly responsible for terminal access control and mobility management, such as user location update, user registration network, or user switching.
  • SMF is mainly responsible for user plane network element selection, user plane network element redirection, Internet protocol (internet protocol, IP) address allocation, session establishment, modification and release, and QoS control.
  • Internet protocol Internet protocol, IP
  • PCF Policy and Charging Function
  • UDM is mainly responsible for terminal contract data management, including the storage and management of terminal identification, terminal access authorization, etc.
  • the AF mainly supports interaction with the 3GPP core network to provide services, such as affecting data routing decisions, policy control functions or providing third-party services to the network.
  • the AF can be the AF deployed by the operator's network itself, or it can be a third-party AF.
  • Figure 2 is a schematic diagram of the network architecture of a multicast/broadcast service.
  • the network architecture and the functions of the network elements shown in Figure 2 are enhanced and defined based on the network architecture and the functions of the network elements shown in Figure 1. For the sake of simplicity, only the multicast/broadcast service-specific functions of each network element in Figure 2 are described below.
  • PCF is mainly responsible for: QoS processing of multicast/broadcast service (MBS) sessions, providing policy information to multicast/broadcast SMF (MB-SMF), and communicating with user data repository (user data repository, UDR) to interactively obtain QoS information, etc.
  • MMS multicast/broadcast service
  • MB-SMF multicast/broadcast SMF
  • UDR user data repository
  • PCF is an optional network element. For example, this functional entity can be provided only when dynamic policy charging control (PCC) is used.
  • PCC dynamic policy charging control
  • MB-SMF is an entity that supports multicast/broadcast features.
  • MB-SMF is responsible for: management of MBS sessions, such as QoS control, etc.; configuring multicast/broadcast (multicast-broadcast UPF, MB-UPF); interacting with access network equipment to control broadcast flow (flow) transmission; and unicast SMF Interact to associate protocol data unit (PDU) sessions; interact with access network equipment to control the transmission of multicast streams, etc.
  • MB-SMF can also have the function of unicast SMF at the same time.
  • SMF is mainly responsible for: discovering MB-SMF, authenticating terminals to join MBS, interacting with MB-SMF to manage multicast session context, interacting with access network equipment to establish multicast transmission resources, etc.
  • MB-UPF is the gateway of the data plane of MBS. It is mainly responsible for: interacting with MB-SMF to obtain data forwarding rules, transmitting multicast data to the access network device through the shared delivery method (shared delivery method); and using the separate delivery method to UPF (individual delivery method) transmits multicast data, etc.
  • UPF is mainly responsible for: transmitting multicast data through individual delivery method (individual delivery method), for example, receiving multicast data from MB-UPF and transmitting multicast data to the terminal through PDU session, etc.
  • AMF is mainly responsible for: signaling routing (for example, signaling routing between (R)AN and MB-SMF), and selecting (R)AN for MBS, etc.
  • RAN is mainly responsible for: processing MBS QoS flows, sending data to terminals through point to multipoint (PTM) and point to point (PTP), and configuring the access stratum (AS) Receive broadcast streams, switch between PTM and PTP, support Xn and N2 switching of multicast sessions, process session signaling, and establish air interface broadcast and multicast resources, etc.
  • PTM point to multipoint
  • PTP point to point
  • AS access stratum
  • the main functions of the UE are: receiving multicast data through PTM/PTP, receiving multicast data/broadcast data through PTM, processing QoS, initiating session join (session join) and session leave (session leave), and resource management on the terminal side of MBS wait.
  • Multicast/broadcast service function (MBSF) network element 8. Multicast/broadcast service function (MBSF) network element
  • the MBSF network element hereinafter referred to as MBSF, mainly supports the following functions: business layer functions, interworking with LTE MBS, interacting with AF and MB-SMF to support MBS session operations, determining transmission parameters and MBS session types, selecting MB- SMF controls MBSTF, determines the sender's IP multicast address, etc.
  • MBSF is an optional network element.
  • Multicast/broadcast service transmission function (MBSTF) network element 10. Multicast/broadcast service transmission function (MBSTF) network element
  • the MBSTF network element hereinafter referred to as MBSTF, mainly supports the following functions: an anchor point for MBS data; serving as a source of IP multicast; supporting general transmission functions such as frames, multi-streams, and forward error correction (FEC); Send the input file as an object or object flow in a multicast or broadcast manner, etc.
  • MBSTF is an optional network element.
  • AF mainly supports the following functions: providing business information to the core network (core network) and requesting multicast or broadcast services, as well as instructing session operations with MBS, etc.
  • UDM mainly supports subscription/subscription management of multicast sessions, etc.
  • NRF mainly includes the following functions: supporting the management of MB-SMF serving MBS sessions, including saving the MBS session ID of MB-SMF services, etc.
  • NEF mainly includes the following functions: select MB-SMF; interact with AF and MB-SMF to implement MBS session operations, determine transmission parameters, etc.; provide AF with MBS process interfaces such as service configuration, MBS session configuration, QoS management interfaces, etc.
  • each network element can communicate with each other through interfaces.
  • the interface between each network element can be a point-to-point interface or a service-based interface, which is not limited by this application.
  • network architecture shown above is only an illustrative description, and the network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture that can realize the functions of each of the above network elements is applicable to the embodiments of the present application.
  • each function or network element shown in Figures 1 and 2 can be understood as network elements used to implement different functions, and for example, can be combined into a network slice as needed.
  • These network elements can be independent devices, or they can be integrated into the same device to implement different functions, or they can be network elements in hardware devices, software functions running on dedicated hardware, or platforms (for example, cloud The virtualization function instantiated on the platform), this application does not limit the specific form of the above network elements.
  • a session used to transmit multicast services can be called a multicast session.
  • the characteristic of a multicast session is that a group of terminals receive the same data.
  • a multicast session may also be called a multicast MBS session or a multicast session, and is collectively referred to as a multicast session in this application.
  • a terminal can receive multicast service data by joining a multicast session.
  • the data of the multicast service can be referred to as multicast data.
  • join multicast session can also be replaced by "join multicast group” without restriction.
  • DRX technology In order to reduce terminal power consumption, DRX technology is introduced into the communication system. DRX technology can make the terminal enter sleep state periodically to achieve the purpose of reducing terminal power consumption.
  • a DRX cycle includes a sleep period and an activation period. During the activation period, the terminal monitors and receives the downlink channel; during the sleep period, the terminal does not need to turn on the receiver to receive data on the downlink channel, thereby reducing terminal power consumption.
  • the DRX cycle can be divided into short DRX cycle and long DRX cycle.
  • DRX can be extended to eDRX.
  • eDRX can change the terminal's DRX cycle from a maximum of 10.24 seconds (s) to more than 10,000 seconds, allowing the terminal to spend less time turning on the receiver, thereby further reducing terminal power consumption.
  • eDRX can include long eDRX (long eDRX), and the cycle length of long eDRX can be greater than 10.24 seconds.
  • eDRX in this application can also be replaced by eDRX cycle, long eDRX, long eDRX cycle, or eDRX with a cycle length greater than 10.24 seconds.
  • Figure 3 is a schematic flow chart of the communication method 300 provided by this application.
  • Method 300 may be executed by access network equipment and core network equipment, or may be executed by modules or units in access network equipment and core network equipment. This application will not limit the method. For convenience of description, it will be collectively referred to as access network equipment below. and core network equipment. Method 300 includes at least part of the following.
  • Step 301 The core network device learns that the terminal has joined the multicast session.
  • the core network device is SMF or AMF.
  • SMF can learn that the terminal has joined the multicast session during the process of the terminal joining the multicast session.
  • the SMF can receive multicast information based on the non-access stratum (Non-Access Stratum, NAS) message sent by the terminal. Session identification and/or join request (join request) information judgment.
  • NAS non-access stratum
  • the SMF further obtains the terminal's subscription information (for example, whether the terminal is authorized to join certain multicast sessions) from the local or UDM, and/or obtains the terminal's subscription information from the local or MB-SMF.
  • the context information includes whether the multicast session is open to all terminals. For example, if the subscription information of the terminal includes information that the terminal is authorized to join a multicast session (for example, the subscription information includes identification information of the multicast session, where the identification of the multicast session may be, for example, a temporary multicast group identification) group identifier, TMGI)), then SMF learns that the terminal has joined the multicast session. If the terminal's subscription information does not include information that the terminal is authorized to join the multicast session, but the context information of the multicast session always includes that the multicast session is open to all terminals, then SMF learns that the terminal has joined the multicast session.
  • step 301 includes: the AMF receives the fourth information from the SMF, and accordingly, the SMF sends the fourth information to the AMF, where the fourth information is used to indicate that the terminal has joined the multicast session; Four messages learn that the terminal has joined the multicast session. Among them, for SMF, SMF can learn that the terminal has joined the multicast session during the process of the terminal joining the multicast session.
  • the fourth information includes an identification of the multicast session to which the terminal has joined.
  • the identifier of the multicast session may be, for example, a temporary multicast group identifier (TMGI). It can be understood that the fourth information indicates in an implicit manner that the terminal has joined the multicast session corresponding to the identifier of the multicast session.
  • the fourth information includes the identification of the multicast session that the terminal has joined and the first indication information.
  • the identifier of the multicast session may be, for example, TMGI, and the first indication information is used to indicate that the terminal has joined the multicast session. It can be understood that the fourth information indicates through display that the terminal has joined the multicast session and the identifier of the multicast session.
  • step 301 specifically includes: SMF sending fourth information to AMF when the multicast session is active, and accordingly, AMF receives the fourth information from SMF.
  • Step 302 The core network device sends the first information.
  • the first information is used to notify the refusal to configure eDRX in the inactive state for the terminal, or the first information is used to indicate that the terminal is not suitable for eDRX in the inactive state.
  • the terminal is not suitable for eDRX in the inactive state
  • the terminal is not allowed to be configured with eDRX in the inactive state
  • the terminal is not configured with eDRX in the inactive state
  • the terminal is not allowed to be configured with eDRX in the inactive state
  • the terminal is converted to the inactive state of eDRX
  • the terminal is not applicable to eDRX
  • the terminal is not converted to the eDRX in the inactive state
  • the terminal does not enter the eDRX in the inactive state” or "The terminal is not sent to the inactive state”.
  • eDRX in active state etc.
  • “refuse to configure eDRX in the inactive state for the terminal” can also use the following description: “refuse to convert the terminal into the inactive state of eDRX”, “refuse to convert the terminal into eDRX in the inactive state”, “reject the terminal Enter eDRX in the inactive state” or “Refuse to send the terminal to eDRX in the inactive state”, etc.
  • the first information when the first information is used to notify a refusal to configure eDRX in an inactive state for the terminal, the first information includes rejection information, and the refusal information is used to indicate a refusal to configure eDRX in an inactive state for the terminal.
  • the rejection information may include a reason for refusing to configure eDRX in an inactive state for the terminal. The reason varies with the information considered by the core network device when sending the first information, and will be described below.
  • the first information may be RRC inactive assistance information (RIAI), and the first information does not include the UE specific extended idle DRX value. idle mode DRX values).
  • RIAI RRC inactive assistance information
  • the first information may be included in the PDU Session Resource Setup Request Transfer (PDU Session Resource Setup Request Transfer) message, or included in the PDU Session Resource Modify Request Transfer (PDU Session Resource Modify Request Transfer) message. )information.
  • step 302 when the first information is used to notify the refusal to configure eDRX in the inactive state for the terminal, step 302 includes: the core network device sends the first information to the access network device. And before step 302, the method 300 also includes step 303, and step 303 is as follows.
  • Step 303 When the access network device determines to convert the terminal to the inactive state, the access network device sends the second information to the core network device.
  • the core network device receives the second information from the access network device.
  • the second information is used to request to configure eDRX in an inactive state for the terminal.
  • the second information is used to request to convert the terminal to an inactive state and the second information carries eDRX information, where the eDRX information includes a period for the terminal to enter eDRX, and so on.
  • "Request” can also be replaced by "instruction” or "configuration”, etc.
  • Step 303 can also be described as: the access network device determines to convert the terminal to an inactive state, and the access network device sends a Second information.
  • the access network device determines to convert the terminal to the inactive state before the access network device sends the second information, or after the access network device sends the second information, without limitation.
  • the access network device may use RRC inactive assistance information (RIAI) and other possible information (such as the implementation of the access network device, or the current status of the access network device). load, etc.), decide to convert the terminal to an inactive state.
  • RRC inactive assistance information RIAI
  • other possible information such as the implementation of the access network device, or the current status of the access network device. load, etc.
  • the interaction between the access network device and the SMF passes through the AMF.
  • the SMF sends the first information to the access network device through the AMF.
  • the access network device may send the second information to the SMF through the AMF.
  • the information received by the AMF and the information sent by the AMF are both called first information or second information
  • the information received by the AMF and the information sent by the AMF may be implemented in the same way or in different ways (for example, via different messages and/or cells), without limitation.
  • the SMF can send the first information to the AMF through the N11 message; after receiving the N11 message from the SMF, the AMF sends the N2 message to the access network device according to the first information, that is, through the N2 message or the cells in the N2 message.
  • the access network equipment transmits the first information.
  • the access network device may send the second information to the AMF through the N2 message; after receiving the N2 message from the access network device, the AMF sends a PDU session update session management context request message to the SMF based on the second information (such as Nsmf_PDUsession_UpdateSMContext request), that is, the second information is transmitted to SMF through the PDU session update session management context request message or the information element therein.
  • the AMF may send the second information to one or more SMFs.
  • the AMF may send the second information to the first SMF for managing the unicast session associated with the multicast session of the terminal and the first SMF for managing the multicast session that is not associated with the terminal.
  • the second SMF of the unicast session sends the second information.
  • the core network device may be the first SMF, and after the AMF receives the first information from the first SMF, the AMF sends the fifth information to the second SMF.
  • the second SMF receives the fifth information from the AMF, where the fifth information is used to trigger the second SMF to stop configuring eDRX in the inactive state for the terminal; the second SMF stops configuring eDRX in the inactive state for the terminal.
  • the second SMF stopping to configure eDRX in the inactive state for the terminal may include: the second SMF disables cached data.
  • the second SMF sends a multicast-specific configuration message to the UPF, and the multicast-specific configuration message does not contain an eDRX cache indication, or contains instruction information to clear the eDRX cache.
  • the UPF here can be the UPF managed by the second SMF.
  • the second SMF sends a configuration message for multicast to the UPF, and the configuration message for multicast sets the Buffer Action Rule (BAR) to 0, or contains an instruction to clear the BAR. information.
  • BAR Buffer Action Rule
  • the second SMF sends a configuration message for multicast to the UPF.
  • the multicast creation (or update) forwarding action rule (Create/Update Forwarding Action Rule,
  • the BAR identifier corresponding to Create/Update FAR) is set to a special value (such as 0) to indicate that caching is not required, or the Create/Update FAR for multicast does not include the corresponding BAR identifier.
  • the second SMF sends a configuration message for multicast to the UPF.
  • the configuration message for multicast includes a delete (or release) forwarding action rule (Delete/Release Forwarding Action Rule) for multicast. ,Delete/Release FAR), and the BAR identifier contained in Delete/Release FAR is set to a special value to indicate that caching is not required, or the configuration message for multicast contains deletion (or release) forwarding for multicast Action rules (Delete/Release Forwarding Action Rule, Delete/Release FAR), and Delete/Release FAR includes the corresponding BAR identifier.
  • stop configuring eDRX in the inactive state for the terminal can also use the following description: “restore the original state of the terminal”, “cancel the configuration of eDRX in the inactive state for the terminal” or “withdraw the configuration of the inactive state for the terminal” eDRX under "etc.
  • step 302 includes: the core network device sends the first information to the access network device or the terminal.
  • the first information can be carried in the RIAI.
  • the SMF sends the first information to the access network device through the AMF.
  • the information received by the AMF and the information sent by the AMF are both called first information
  • the information received by the AMF and the information sent by the AMF may be implemented in the same way or in different ways (for example, through different messages). and/or cells), without limitation.
  • step 302 includes: if the terminal has joined the multicast session, the core network device sends the first information. It can be understood that after the core network device learns that the terminal has joined the multicast session, the core network device can send the first message to notify the refusal to configure eDRX in the inactive state for the terminal or to instruct the terminal not to use eDRX in the inactive state. . In this implementation, if the first information includes a rejection reason, the reason is that the terminal has joined the multicast session.
  • step 302 includes: when at least one of the following conditions is met, the core network device sends the first information: the access network device that provides services for the terminal does not support eDRX, the terminal does not support eDRX, or The multicast session meets the preset conditions, where the preset conditions are: the multicast session is active, the multicast service corresponding to the multicast session does not support eDRX, or the multicast session is active and the multicast service corresponding to the multicast session eDRX is not supported. It can be understood that after the core network device learns that the terminal has joined the multicast session, the core network device further determines whether the above conditions are met.
  • the core network device sends the first message to notify that the terminal is refused to be configured with non-configuration information.
  • eDRX in the active state or indicating that the terminal is not applicable to eDRX in the inactive state.
  • the reason includes at least one of the following reasons: the terminal has joined the multicast session, the access network equipment that provides services to the terminal does not support eDRX, the terminal does not support eDRX, or Multicast sessions meet preset conditions.
  • the core network device sends the first information; if the terminal has joined the multicast session and the multicast session is in the deactivated state, the access network device supports eDRX, and the terminal supports eDRX, the core network device does not send the first information .
  • the preset condition is that the multicast service corresponding to the multicast session does not support eDRX. If the terminal has joined the multicast session and the multicast service corresponding to the multicast session does not support eDRX, and/or the access network equipment eDRX is not supported, and/or the terminal does not support eDRX, the core network device sends the first information; if the terminal has joined the multicast session and the multicast service corresponding to the multicast session supports eDRX, and the access network equipment supports eDRX, If the terminal supports eDRX, the core network device does not send the first information.
  • the preset condition is that the multicast session is active and the multicast service corresponding to the multicast session does not support eDRX. If the terminal has joined the multicast session and the multicast session meets the preset conditions, and/or access If the network equipment does not support eDRX, and/or the terminal does not support eDRX, the core network equipment sends the first information; if the terminal has joined the multicast session and the multicast session does not meet the preset conditions, the access network equipment supports eDRX , and when the terminal supports eDRX, the core network device does not send the first information.
  • the method 300 also includes step 304: the core network device receives third information from the access network device, and accordingly, the access network device sends the third information to the core network device, where the third information is used to indicate the access network device. Whether the network access device supports eDRX. For example, when the access network device is powered on, the third information may be reported to the core network device.
  • the third information may be carried in a next generation (interface) configuration request (NG set request) message.
  • NG set request next generation configuration request
  • the access network device can send the third information to the SMF through the AMF.
  • the third information received by the AMF and the third information sent by the AMF to the SMF may be implemented in the same way or in different ways (for example, through different messages and/or information elements), without limitation.
  • method 300 also includes: the AMF receives service information from the SMF, and accordingly, the SMF sends the service information to the AMF, where the service information is used to indicate the multicast service corresponding to the multicast session. Whether to support eDRX.
  • the service information may include the type of multicast service.
  • the multicast service type is a delay-sensitive type, it can be considered that the multicast service supports eDRX.
  • the multicast service type is a non-delay-sensitive type, it can be considered that the multicast service does not support eDRX.
  • the service information may include second indication information, and the second indication information is used to indicate whether the multicast service supports eDRX.
  • the second indication information may be one or several bits, that is, the service information may indicate whether the multicast service supports eDRX in a display manner.
  • Step 305 The access network device does not configure eDRX in the inactive state for the terminal according to the first information.
  • not configuring eDRX in the inactive state for the terminal can also be understood as not performing the operation of configuring eDRX for the terminal, which can also be described as follows: “not converting the terminal to the inactive state using eDRX” or “not Transition terminal to eDRX state”.
  • method 300 also includes: the access network device converts the terminal to an inactive state, keeps the terminal in a connected state, converts the terminal to an idle state, converts the terminal to an inactive state and configures DRX for the terminal, and configures the terminal with DRX. Convert to the inactive state and configure only DRX for the terminal without eDRX information, convert the terminal to the inactive state and only include RAN-Paging Cycle (ran-PagingCycle) information in the terminal configuration information, or convert the terminal to In the inactive state, the configuration information of the terminal only contains RAN-Paging Cycle (ran-PagingCycle) information and does not contain RAN-Extended Paging Cycle (ran-ExtendedPagingCycle). Further optionally, the DRX period is no longer than 2.56s.
  • the access network device converts the terminal to an inactive state, keeps the terminal in a connected state, converts the terminal to an idle state, converts the terminal to an inactive state and configures DRX for the terminal, and configures the
  • conversion can also be described as “release”, “switching”, “configuration”, or “setting”, etc.
  • step 305 includes: when the access network device determines to convert the terminal to the inactive state, the access network device does not Configure eDRX in the inactive state for the terminal.
  • the core network device can notify the access network device of the rejection Configure eDRX in the inactive state for the terminal or indicate to the access network device that the terminal is not suitable for eDRX in the inactive state, so that when the access network device converts the terminal to the inactive state, it can do so according to the notification or instruction of the core network device.
  • Configure eDRX in the inactive state for the terminal to ensure the transmission of multicast data corresponding to the multicast session.
  • Figure 4 is a schematic flow chart of the communication method 400 provided by this application.
  • Method 400 may be executed by access network equipment and core network equipment, or may be executed by modules or units in access network equipment and core network equipment. This application will not limit the method. For convenience of description, it will be collectively referred to as access network equipment below. and core network equipment. Method 400 includes at least some of the following.
  • Step 401 The access network device learns that the terminal has joined the multicast session.
  • the access network device can learn that the terminal has joined the multicast session during the process of the terminal joining the multicast session.
  • the access network device can learn that the terminal has joined the multicast session based on receiving the N2 information sent by the SMF from the address allocated to the terminal, and the information contains the identifier of the multicast session.
  • the access network device receives a PDU session resource establishment request (PDU SESSION RESOURCE SETUP REQUEST) sent from the AMF.
  • the request message contains a PDU session resource modification establishment request transfer (PDU Session Resource SetupRequest Transfer).
  • PDU Session Resource SetupRequest Transfer contains MBS session establishment request list (MBS Session Setup Request List), and the list contains multicast session ID information (such as MBS Session ID, which can be TMGI).
  • the access network device receives a PDU Session Resource Modify Request (PDU SESSION RESOURCE MODIFY REQUEST) sent from the AMF, and the request message contains a PDU Session Resource Modify Request Transfer (PDU Session Resource Modify Request Transfer).
  • the request transfer message contains MBS. Session establishment request or modification list (MBS Session Setup or Modify Request List), and the list contains multicast session ID information (such as MBS Session ID, which can be TMGI).
  • Step 402 When the access network device determines to convert the terminal to the inactive state, the access network device does not configure eDRX in the inactive state for the terminal.
  • not configuring eDRX in the inactive state for the terminal can also be understood as not performing the operation of configuring eDRX for the terminal, which can also be described as follows: “not converting the terminal to the inactive state using eDRX” or “not Transition terminal to eDRX state”.
  • method 400 also includes: the access network device converts the terminal to an inactive state, keeps the terminal in a connected state, converts the terminal to an idle state, converts the terminal to an inactive state and configures DRX for the terminal, and configures the terminal with DRX. Convert to the inactive state and configure only DRX for the terminal without eDRX information, convert the terminal to the inactive state and only include RAN-Paging Cycle (ran-PagingCycle) information in the terminal configuration information, or convert the terminal to In the inactive state, the configuration information of the terminal only contains RAN-Paging Cycle (ran-PagingCycle) information and does not contain RAN-Extended Paging Cycle (ran-ExtendedPagingCycle). Further optionally, the DRX period is no longer than 2.56s.
  • the access network device converts the terminal to an inactive state, keeps the terminal in a connected state, converts the terminal to an idle state, converts the terminal to an inactive state and configures DRX for the terminal, and configures the
  • conversion can also be described as “release”, “switching”, “configuration”, or “setting”, etc.
  • step 402 includes: if the terminal has joined the multicast session, the access network device does not configure eDRX in the inactive state for the terminal. It can be understood that when the conditions for converting the terminal to the inactive state are met, the access network device further considers whether the terminal has joined the multicast session, and does not configure eDRX for the terminal if the terminal has joined the multicast session. Or it can also be understood that the access network device determines that the conditions for converting the terminal to an inactive state and configuring eDRX for the terminal are not met based on the fact that the terminal has joined the multicast session.
  • step 402 includes: when at least one of the following conditions is met, the access network device does not configure eDRX in the inactive state for the terminal: the access network device does not support eDRX, and the terminal does not support eDRX. , or the multicast session meets the preset conditions, where the preset conditions are: the multicast session is active, the multicast service corresponding to the multicast session does not support eDRX, or the multicast session is active and the multicast service corresponding to the multicast session is active.
  • the broadcast service does not support eDRX.
  • the access network device learns that the terminal has joined the multicast session, when it decides that the access network will convert the terminal to an inactive state, it determines whether the above conditions are met. When the above conditions are met, the access network device Network access equipment does not configure eDRX in the inactive state for terminals.
  • the preset condition is that the multicast session is active
  • the access network equipment does not support eDRX
  • the terminal does not support eDRX
  • the access network equipment does not configure eDRX in the inactive state for the terminal
  • the terminal has joined the multicast session and the multicast session is in the deactivated state
  • the access network equipment supports eDRX
  • the terminal supports eDRX
  • the The network access device can configure eDRX in the inactive state for the terminal.
  • the preset condition is that the multicast service corresponding to the multicast session does not support eDRX. If the terminal has joined the multicast session and the multicast service corresponding to the multicast session does not support eDRX, and/or the access network equipment eDRX is not supported, and/or, the terminal does not support eDRX, Then the access network equipment does not configure eDRX in the inactive state for the terminal; if the terminal has joined a multicast session and the multicast service corresponding to the multicast session supports eDRX, the access network equipment supports eDRX, and the terminal supports eDRX, then The access network equipment can configure eDRX in the inactive state for the terminal.
  • the preset condition is that the multicast session is active and the multicast service corresponding to the multicast session does not support eDRX. If the terminal has joined the multicast session and the multicast session meets the preset conditions, and/or access If the network equipment does not support eDRX, and/or the terminal does not support eDRX, the access network equipment does not configure eDRX in the inactive state for the terminal; if the terminal has joined the multicast session and the multicast session does not meet the preset conditions, When the access network equipment supports eDRX and the terminal supports eDRX, the access network equipment can configure eDRX in the inactive state for the terminal.
  • method 400 also includes step 403: the access network device receives service information from the SMF, and accordingly, the SMF sends the service information to the access network device, where the service information is used to indicate the multicast service corresponding to the multicast session. Whether to support eDRX.
  • the service information may include the type of multicast service.
  • the multicast service type is a delay-sensitive type, it can be considered that the multicast service supports eDRX.
  • the multicast service type is a non-delay-sensitive type, it can be considered that the multicast service does not support eDRX.
  • the service information may include second indication information, and the second indication information is used to indicate whether the multicast service supports eDRX.
  • the second indication information may be one or several bits, that is, the service information may indicate whether the multicast service supports eDRX in a display manner.
  • the access network device can determine not to configure eDRX in the inactive state for the terminal, thereby ensuring the transmission of multicast data corresponding to the multicast session.
  • Figure 5 is a schematic flow chart of the communication method 500 provided by this application.
  • Method 500 may be executed by the terminal and the access network equipment, or may be executed by modules or units in the terminal and the access network equipment, which is not limited in this application. For the convenience of description, they are collectively referred to as the terminal and the access network equipment below. Method 500 includes at least some of the following.
  • Step 501 The terminal learns that the terminal has joined the multicast session.
  • the terminal supports eDRX.
  • One possible implementation method is that the terminal can learn that the terminal has joined the multicast session during the process of the terminal joining the multicast session.
  • the terminal can learn that the terminal has joined the multicast session according to the NAS message sent from the AMF, and the NAS message contains the identifier of the multicast session.
  • the terminal receives the PDU session establishment acceptance (PDU SESSION ESTABLISHMENT ACCEPT) message sent from the AMF, and the message contains the MBS Session ID (such as TMGI).
  • the MBS Session ID is included in the received MBS information (Received MBS information)
  • the received MBS information is included in the received MBS container (Received MBS container)
  • the received MBS container is included in the PDU session establishment Receiving message.
  • the terminal can learn that the terminal has joined the multicast session.
  • the access network device receives the PDU SESSION MODIFICATION COMMAND message sent from the AMF, and the message contains the MBS Session ID (such as TMGI).
  • the MBS Session ID is included in the received MBS information (Received MBS information)
  • the received MBS information is included in the received MBS container (Received MBS container)
  • the received MBS container is included in the PDU session modification in the command message.
  • the terminal can learn that the terminal has joined the multicast session.
  • Step 502 The terminal sends sixth information to the access network device.
  • the access network device receives the sixth information from the terminal.
  • the sixth information is used to indicate that the terminal does not support eDRX.
  • the access network device can not configure eDRX in the inactive state for the terminal according to the sixth information when making a judgment to convert the terminal to the inactive state, thereby ensuring that the multicast Transmission of multicast data corresponding to the session.
  • step 502 includes: the terminal sends sixth information to the access network device through the AMF.
  • the terminal sends a registration request message carrying sixth information to the AMF, and the sixth information may be the eDRX capability information of the terminal; after receiving the registration request message of the terminal, the AMF sends the sixth information to the access network device through the terminal context update message. information.
  • the sixth information may be carried in the RIAI.
  • the terminal sends the sixth information to the access network device through the AMF
  • the implementation of the sixth information received by the AMF and the sixth information sent by the AMF may be the same or different (for example, through different messages and /or cells), are not restricted.
  • step 502 includes: if the terminal has joined the multicast session, the terminal sends sixth information. It can be understood that after the terminal learns that the terminal has joined the multicast session, the terminal can send the sixth information to the access network device to indicate to the access network device that the terminal does not support eDRX.
  • step 502 includes: the terminal sends the sixth information to the access network device when at least one of the following conditions is met: the terminal receives the first information from the core network device, the access network device does not eDRX is supported, the terminal does not support eDRX, or the multicast session meets preset conditions.
  • the first information is used to indicate that the terminal is not applicable to eDRX.
  • the preset conditions are: the multicast session is active and the multicast service corresponding to the multicast session is eDRX is not supported, or the multicast session is active and the multicast service corresponding to the multicast session does not support eDRX. It can be understood that after the terminal learns that the terminal has joined the multicast session, the terminal further determines whether the above conditions are met. When the above conditions are met, the terminal sends sixth information to the access network device to indicate to the access network device that the terminal does not Support eDRX.
  • the terminal may not send the sixth information to the access network equipment.
  • the preset condition is that the multicast service corresponding to the multicast session does not support eDRX. If the terminal has joined the multicast session and the multicast service corresponding to the multicast session does not support eDRX, and/or, a message from the core network is received.
  • the preset condition is that the multicast session is active and the multicast service corresponding to the multicast session does not support eDRX. If the terminal has joined the multicast session and the multicast session meets the preset conditions, and/or receives The first information comes from the core network equipment, and/or the access network equipment does not support eDRX, and/or the terminal does not support eDRX, then the terminal sends the sixth information to the access network equipment; if the terminal has joined the multicast session If the multicast session does not meet the preset conditions, the first information from the core network device is not received, the access network device supports eDRX, and the terminal supports eDRX, the terminal may not send the sixth information to the access network device. .
  • method 500 also includes step 503: the terminal receives service information from the SMF, and accordingly, the SMF sends the service information to the terminal, where the service information is used to indicate whether the multicast service corresponding to the multicast session supports eDRX.
  • Service information can be included in messages such as PDU session modification command, PDU session modification acceptance, and PDU session establishment response.
  • the service information may include the type of multicast service.
  • the multicast service type is a delay-sensitive type, it can be considered that the multicast service supports eDRX.
  • the multicast service type is a non-delay-sensitive type, it can be considered that the multicast service does not support eDRX.
  • the service information may include second indication information, and the second indication information is used to indicate whether the multicast service supports eDRX.
  • the second indication information may be one or several bits, that is, the service information may indicate whether the multicast service supports eDRX in a display manner.
  • method 500 further includes: the terminal sends seventh information to the access network device, and accordingly, the base station receives the seventh information from the terminal, wherein the Seven information is used to indicate that the terminal supports eDRX.
  • the method for the terminal to send the seventh information to the access network device may refer to the method for the terminal to send the sixth information to the access network device, which will not be described again here.
  • method 500 also includes: after the terminal leaves all multicast sessions that the terminal has joined, the terminal sends eighth information to the access network device, correspondingly , the base station receives eighth information from the terminal, where the eighth information is used to indicate that the terminal supports eDRX.
  • the method for the terminal to send the eighth information to the access network device may refer to the method for the terminal to send the sixth information to the access network device, which will not be described again here.
  • step 502 can also be replaced with: the terminal sends a registration request message to the AMF, and the registration request message does not contain the requested extended DRX parameters (Requested extended DRX parameters); after receiving the registration request message from the terminal Finally, the AMF updates the terminal context of the access network device according to the registration request message that does not contain the requested extended DRX parameters. Specifically, the AMF sends RIAI information to the access network device through the terminal context update message, and the RIAI does not contain the UE specific extended idle mode DRX value (UE specific extended idle mode DRX).
  • Figure 6 is a schematic flow chart of the communication method 600 provided by this application.
  • Method 600 may be performed by the access network device, SMF, UPF, and MB-UPF, or may be performed by the access network device, SMF, UPF, and This application will not limit the execution of modules or units in MB-UPF. For convenience of description, they will be collectively referred to as access network equipment, SMF, UPF and MB-UPF below. Method 600 includes at least some of the following.
  • Step 601 The access network device sends second information to the SMF.
  • the SMF receives the second information from the access network device.
  • the second information is used to request to configure eDRX in an inactive state for the terminal.
  • the second information is used to request to convert the terminal to an inactive state and the second information carries eDRX information, where the eDRX information includes a period for the terminal to enter eDRX, and so on.
  • the interaction between the access network device and the SMF can be through the AMF.
  • the information received by the AMF and the information sent by the AMF are both called second information
  • the information received by the AMF and The information sent by the AMF can be implemented in the same way or in different ways (for example, through different messages and/or information elements) without limitation.
  • the access network device can send the second information to the AMF through the N2 message; after receiving the N2 message from the access network device, the AMF sends a PDU session update session management context request message (such as Nsmf_PDUsession_UpdateSMContext request), that is, the second information is transmitted to SMF through the PDU session update session management context request message or the information element therein.
  • a PDU session update session management context request message such as Nsmf_PDUsession_UpdateSMContext request
  • Step 602 After receiving the second information, the SMF establishes a transmission channel between UPF and MB-UPF based on the second information.
  • the transmission channel between UPF and MB-UPF is used to transmit multicast data of the terminal.
  • the multicast data here can be multicast data when the terminal is in the eDRX sleep state.
  • Step 602 can be understood as triggering SMF to establish a transmission channel between UPF and MB-UPF when configuring inactive eDRX for the terminal.
  • the SMF may previously learn that the access network device providing services for the terminal supports multicast. That is, when the access network device supports multicast, the SMF can establish a transmission channel between the UPF and MB-UPF after receiving the second information.
  • SMF establishes a transmission channel between UPF and MB-UPF based on the second information. It may be that SMF creates a new transmission channel between UPF and MB-UPF based on the second information, or it may be that SMF modifies it based on the second information.
  • the existing transmission channel between UPF and MB-UPF enables the channel to transmit multicast data of terminals.
  • SMF sends an N4 message to UPF.
  • UPF receives an N4 message from SMF.
  • the N4 message is used to inquire whether a transmission channel from UPF to MB-UPF has been established; UPF sends an N4 message to SMF.
  • SMF receives the response message from UPF, where the response message includes the first downlink tunnel identifier; SMF sends a request message to MB-SMF, correspondingly, MB-SMF receives the request message from SMF, where The request message includes the first downlink tunnel identifier; MB-SMF and MB-UPF interact to establish a transmission channel between UPF and MB-UPF; MB-SMF sends a response message to the request message to SMF.
  • SMF receives the response message from MB- SMF response message.
  • the first downlink tunnel identifier is the tunnel identifier of the transmission channel; if a transmission channel has not yet been established between UPF and MB-UPF, the first downlink tunnel identifier Tunnel ID assigned to UPF.
  • SMF sends an N4 message to UPF.
  • UPF receives an N4 message from SMF.
  • the N4 message is used to inquire whether a transmission channel from UPF to MB-UPF has been established; UPF sends N4 to SMF.
  • the response message of the message corresponds to SMF, where the response message includes SSM information; SMF sends a request message to MB-SMF.
  • MB-SMF receives the request message from SMF, where the request message includes SSM information; MB-SMF and MB-UPF interact to establish a transmission channel between UPF and MB-UPF.
  • MB-UPF provides the second downlink tunnel identifier for multicast to MB-SMF; MB-SMF
  • the SMF sends a response message to the request message.
  • the SMF receives a response message from the MB-SMF, where the response message includes the second downlink tunnel identifier; the SMF provides the second downlink tunnel identifier to the UPF.
  • Step 603 SMF sends eDRX cache information to UPF or MB-UPF.
  • UPF or MB-SMF receives the eDRX cache information from SMF.
  • the eDRX cache information is used to cache multicast data of the terminal.
  • the eDRX cache information includes third indication information and a period for the terminal to enter eDRX, where the third indication information is used to instruct to stop the transmission of the terminal's multicast data and cache the terminal's multicast data.
  • the eDRX cache information includes configuration information and a period for the terminal to enter eDRX, where the configuration information is used to configure UPF or MB-UPF so that UPF or MB-UPF caches the multicast data of the terminal.
  • UPF caches the multicast data of the terminal. That is, MB-UPF can transmit the multicast data of the terminal to UPF through the transmission channel between UPF and MB-UPF, and the UPF can cache it. Later, when the terminal becomes reachable again, UPF can send the cached data to the terminal.
  • MB-UPF caches the multicast data of the terminal. That is, MB-UPF can cache the multicast data of the terminal.
  • MB-UPF can transmit the cached multicast data to UPF through the transmission channel between UPF and MB-UPF. After being transmitted from UPF to the terminal.
  • step 603 can be implemented through step 602.
  • the SMF sends the eDRX cache information to the UPF through the N4 message sent to the UPF.
  • the SMF sends the eDRX cache information to the MB-SMF through the request message sent to the MB-SMF. information, and then MB-SMF can send eDRX cache information to MB-UPF during the interaction with MB-UPF.
  • Step 603 can also be implemented through other signaling independent of step 602.
  • Step 604 The SMF sends ninth information to the access network device.
  • the access network device receives the ninth information from the SMF.
  • the ninth information is used to indicate that eDRX in the inactive state is successfully configured for the terminal.
  • the access network device can initiate the RRC connection release process and configure eDRX for the terminal.
  • the interaction between the access network device and the SMF can be through the AMF.
  • the information received by the AMF and the information sent by the AMF are both called ninth information, the information received by the AMF and The information sent by the AMF can be implemented in the same way or in different ways (for example, through different messages and/or information elements) without limitation.
  • the access network device can convert the terminal into an inactive state and configure eDRX for the terminal, and UPF or MB-UPF caches the terminal's multicast data to ensure multicast Transmission of data.
  • the SMF after receiving the second information, the SMF caches the terminal's multicast data or the SMF notifies the MB-SMF to cache the terminal's multicast data.
  • the eDRX information may correspond to the eDRX cache information above.
  • Figure 7 is an example of the communication method of the present application.
  • the access network device may or may not support multicast.
  • Step 701 The terminal registers with the network and negotiates eDRX parameters for connection management (CM)-idle state (IDLE) with the network.
  • CM connection management
  • IDLE connection management
  • the terminal when the terminal supports eDRX, the terminal carries information indicating that the terminal supports eDRX in the registration request message sent to the AMF; if the terminal is allowed to enter the eDRX state, then the AMF carries in the registration acceptance message sent to the terminal. Information indicating that the terminal is allowed to enter eDRX, and information about the paging time window (PTW).
  • the terminal When the terminal does not support eDRX, the terminal carries information indicating that the terminal does not support eDRX in the registration request message sent to the AMF.
  • step 701 For a more detailed description of step 701, reference may be made to the existing technology and will not be described again here.
  • Step 702 The terminal requests to join the multicast session, and accordingly, the core network device establishes related resources for the multicast session.
  • the terminal sends a PDU session modification request message or a PDU session establishment request message to the core network device, and the message carries the identifier of the multicast session that the terminal requests to join; the core network device generates the multicast session based on the identifier of the multicast session that the terminal requests to join.
  • the context corresponding to the multicast session and the optional unicast QoS flow information corresponding to the multicast session are sent to the access network device; the access network device establishes or modifies the multicast based on the received information.
  • the context corresponding to the session, and optionally establishes a unicast context are sent to the access network device.
  • step 702 For a more detailed description of step 702, reference may be made to the existing technology and will not be described again here.
  • step 702 the SMF can learn that the terminal has joined the multicast session.
  • Step 703 After the terminal joins the multicast session, the SMF sends the N11 message to the AMF.
  • the AMF receives the N11 message from the SMF.
  • the N11 message is used to notify the AMF that the terminal has joined the multicast session.
  • the N11 message includes the identification of the multicast session to which the terminal joins (for example, a temporary multicast group identifier (TMGI)).
  • the N11 message also includes indication information #1, which is used to indicate that the terminal has joined the multicast session.
  • the N11 message does not include indication information #1, it can be considered that the multicast session identifier included in the N11 message implicitly indicates that the terminal has joined the multicast session corresponding to the identifier.
  • the SMF can only send the N11 message to the AMF when the multicast session joined by the terminal is active.
  • the N11 message can implicitly indicate that the multicast session is active.
  • Step 704 The access network device reports to the AMF whether the access network device supports eDRX.
  • One possible implementation method is that when the access network device is powered on, the access network device reports to the AMF whether it supports eDRX. For example, the access network device carries the eDRX capability information of the access network device in the next generation application protocol (NGAP) setup request message (NGAP setup request). The eDRX capability information is used to indicate whether the access network device Support eDRX.
  • NGAP next generation application protocol
  • Step 704 is an optional step.
  • Step 705 AMF determines whether the terminal can be converted to the inactive state of eDRX (ie, RRC inactive with eDRX) based on whether the access network equipment supports eDRX, whether the terminal supports eDRX, and whether the terminal has joined the multicast session.
  • eDRX ie, RRC inactive with eDRX
  • the AMF determines that the terminal is not suitable for eDRX in the inactive state.
  • the access network equipment supports eDRX
  • the terminal supports eDRX
  • the terminal does not join the multicast session
  • AMF determines that the terminal is suitable for eDRX in the inactive state.
  • step 704 the AMF may not consider whether the access network device supports eDRX when determining whether the terminal can be converted to the inactive state of eDRX.
  • Step 706 The AMF sends instruction information #2 to the access network device.
  • the access network device receives indication information #2 from the AMF.
  • the indication information #2 is used to indicate whether the terminal is suitable for eDRX in the inactive state.
  • Instruction information #2 may correspond to the first information above.
  • indication information #2 can be carried in RRC inactive assistance information (RRAI).
  • RRAI RRC inactive assistance information
  • Step 707 The access network device converts or not converts the terminal to the inactive state of eDRX according to the instruction information #2.
  • the access network device when the indication information #2 is used to indicate that the terminal is not applicable to eDRX in the inactive state, the access network device does not convert the terminal to the inactive state of eDRX.
  • the instruction information #2 is used to instruct the terminal to apply eDRX in the inactive state, the access network device further combines other information (such as whether the access network device supports eDRX (if step 704 is not performed), the implementation of the access network device, and the current load of the access network equipment, etc.), determine whether to convert the terminal to the inactive state of eDRX or not to convert the terminal to the inactive state of eDRX.
  • the access network device when the terminal has joined the multicast session, the access network device does not convert the terminal to the inactive state of eDRX, which helps ensure the transmission of multicast services.
  • Figure 8 is another example of the communication method of the present application.
  • the access network device supports multicast. Since the access network device supports multicast, the access network device knows whether the terminal has joined the multicast session and the status of the multicast session.
  • Step 801 The terminal registers with the network and negotiates eDRX parameters for CM-IDLE with the network.
  • Step 802 The terminal requests to join the multicast session, and accordingly, the core network device establishes related resources for the multicast session.
  • Steps 801 to 802 may refer to steps 701 to 702, which will not be described in detail here.
  • Step 803 The access network device converts or does not convert the terminal to the inactive state of eDRX based on whether the access network device supports eDRX, whether the terminal supports eDRX, and whether the terminal has joined the multicast session.
  • One possible implementation method is that when the access network device does not support eDRX, and/or the terminal does not support eDRX, and/or the terminal has joined a multicast session, the access network device does not convert the terminal to eDRX deactivation. state.
  • the access network device can convert the terminal to the inactive state of eDRX, but whether the access network device converts the terminal to the inactive state of eDRX state, it also depends on whether other conditions that need to be met to convert the terminal to the inactive state of eDRX are met (for example, the implementation of the access network equipment or the current load of the access network equipment, etc.).
  • the access network device can further consider the status of the multicast session joined by the terminal. For example, when the access network device does not support eDRX, and/or the terminal does not support eDRX, and/or the terminal has joined a multicast session and the multicast session is active, the access network device does not convert the terminal to eDRX The inactive state of eDRX; otherwise, the access network equipment can convert the terminal to the inactive state of eDRX, but whether the access network equipment converts the terminal to the inactive state of eDRX depends on whether the inactive state of converting the terminal to eDRX is met. When there are other conditions that need to be met in the activation state (for example, the implementation of the access network device or the current load of the access network device, etc.).
  • the access network device Preparing to convert the terminal to the inactive state of eDRX helps ensure the transmission of multicast services.
  • Figure 9 is another example of the communication method of the present application.
  • Step 901 The terminal registers with the network and negotiates eDRX parameters for CM-IDLE with the network.
  • Step 902 The terminal requests to join the multicast session, and accordingly, the core network device establishes related resources for the multicast session.
  • steps 901 to 902 reference may be made to steps 701 to 702, which will not be described in detail here.
  • Step 903 After the terminal joins the multicast session, the SMF sends the N11 message to the AMF.
  • the AMF receives the N11 message from the SMF.
  • the N11 message is used to notify the AMF that the terminal has joined the multicast session.
  • the N11 message includes the identification of the multicast session to which the terminal joins (for example, TMGI).
  • the N11 message also includes indication information #1, which is used to indicate that the terminal has joined the multicast session.
  • the N11 message does not include indication information #1, it can be considered that the multicast session identifier included in the N11 message implicitly indicates that the terminal has joined the multicast session corresponding to the identifier.
  • the SMF can only send the N11 message to the AMF when the multicast session joined by the terminal is active.
  • the N11 message can implicitly indicate that the multicast session is active.
  • Step 904 The access network device decides to convert the terminal to the inactive state of eDRX based on the RIAI and other possible information (such as the implementation of the access network device or the current load of the access network device, etc.).
  • Step 905 Before converting the terminal to the inactive state of eDRX, the access network device sends the N2 message to the AMF.
  • the AMF receives the N2 message from the access network device.
  • the N2 message is used to request to convert the terminal to an inactive state of eDRX, and the message carries eDRX information (for example, the period for the terminal to enter eDRX, etc.).
  • the AMF can learn based on the N2 message that the access network equipment plans to convert the terminal to the inactive state of eDRX.
  • steps 904 to 905 For a more detailed description of steps 904 to 905, reference may be made to the existing technology and will not be described in detail here.
  • Step 906 The AMF determines that the terminal is not suitable for eDRX in the inactive state based on the information obtained in step 903 (such as TMGI and/or indication information #1).
  • Step 907 The AMF sends the N2 message to the access network device.
  • the access network device receives the N2 message from the AMF.
  • the N2 message is used to reject the request to convert the terminal to the inactive state of eDRX.
  • the N2 message includes rejection information and rejection reason, where the rejection information is used to indicate rejection of converting the terminal to the inactive state of eDRX, and the rejection reason includes that the terminal has joined the multicast session.
  • Step 908 The access network device does not convert the terminal to the inactive state of eDRX according to the N2 message in step 907.
  • the access network device when the terminal has joined the multicast session, the access network device does not convert the terminal to the inactive state of eDRX, which helps ensure the transmission of multicast services.
  • Figure 10 is another example of the communication method of the present application.
  • Step 1001 The terminal registers with the network and negotiates eDRX parameters for CM-IDLE with the network.
  • Step 1002 The terminal requests to join the multicast session, and accordingly, the core network device establishes related resources for the multicast session.
  • Steps 1001 to 1002 may refer to steps 701 to 702, which will not be described in detail here.
  • Step 1003 The access network device decides to convert the terminal to an inactive state based on the RIAI and other possible information (such as the implementation of the access network device or the current load of the access network device, etc.).
  • Step 1004 The access network device sends the N2 message to the AMF.
  • the AMF receives the N2 message from the access network device.
  • the N2 message is used to request to convert the terminal to an inactive state of eDRX, and the message carries eDRX information (for example, the period for the terminal to enter eDRX, etc.).
  • the AMF can learn based on the N2 message that the access network equipment plans to convert the terminal to the inactive state of eDRX, so as to subsequently notify the SMF corresponding to the PDU session in the active state of the user plane to convert the terminal to the inactive state of eDRX.
  • the inactive state of eDRX is the state of eDRX.
  • steps 1003 to 1004 For a more detailed description of steps 1003 to 1004, reference may be made to the existing technology and will not be described in detail here.
  • Step 1005 AMF sends the N11 message to SMF.
  • SMF receives the N11 message from AMF.
  • the N11 message is used to request to convert the terminal to the inactive state of eDRX, and the message carries eDRX information (for example, the period for the terminal to enter eDRX, etc.).
  • N11 message is Nsmf_PDUSessionUpdateSMContext request.
  • Step 1006 Based on the fact that the terminal has joined the multicast session, the SMF determines that the terminal is not suitable for eDRX in the inactive state.
  • the SMF can learn that the terminal has joined the multicast session through step 1002.
  • Step 1007 SMF sends the N11 message to AMF.
  • the AMF receives the N11 message from the SMF.
  • the N11 message is used to reject the request to convert the terminal to the inactive state of eDRX.
  • the N11 message includes rejection information and rejection reason, where the rejection information is used to refuse to convert the terminal to the inactive state of eDRX, and the rejection reason includes that the terminal has joined the multicast session.
  • N11 message is Nsmf_PDUSessionUpdateSMContext response.
  • Step 1008 If the AMF also sends an N11 message to other SMFs in step 1004, then after receiving the N11 message in step 1007, the AMF sends an N11 message to other SMFs.
  • the N11 message is used to withdraw the request to convert the terminal to the inactive state of eDRX.
  • the N11 message may carry instruction information #3, and the instruction information #3 is used to instruct to stop converting the terminal to the inactive state of eDRX.
  • Step 1009 The AMF sends the N2 message to the access network device.
  • the access network device receives the N2 message from the AMF.
  • the N2 message is used to reject the request of the access network device to convert the terminal to the inactive state of eDRX.
  • the N2 message includes rejection information and rejection reason, where the rejection information is used to refuse to convert the terminal to the inactive state of eDRX, and the rejection reason includes that the terminal has joined the multicast session.
  • Step 1010 The access network device does not convert the terminal to the inactive state of eDRX according to the N2 message in step 1009.
  • the access network device when the terminal has joined the multicast session, the access network device does not convert the terminal to the inactive state of eDRX, which helps ensure the transmission of multicast services.
  • Figure 11 is another example of the communication method of the present application.
  • Step 1101 The terminal registers with the network and negotiates eDRX parameters for CM-IDLE with the network.
  • Step 1102 The terminal requests to join the multicast session, and accordingly, the core network device establishes related resources for the multicast session.
  • Steps 1101 to 1102 may refer to steps 701 to 702, which will not be described in detail here.
  • Step 1103 SMF sends the N1 message to the terminal.
  • the terminal receives the N1 message from the SMF.
  • the N1 message includes service characteristics of the multicast service corresponding to the multicast session.
  • the multicast session here can be a multicast session joined by the terminal.
  • the service characteristics of the multicast service may be used to determine or indicate whether the multicast service supports eDRX.
  • the service characteristics of the multicast service may include whether the multicast service supports eDRX, whether the multicast service is a delay-sensitive type, etc.
  • the N11 message may be the message in step 1102, that is, step 1103 may be implemented through step 1102, or in other words, step 1103 is a part of step 1102.
  • the N11 message may be a response message to the multicast session join request message, such as a PDU session modification command, etc.
  • the service characteristic of the multicast service may be an information element in the message.
  • the N11 message may be a newly added message used to transmit the service characteristics of the multicast service.
  • Step 1104 When the following conditions are met, the terminal sends a registration request message to the AMF in order to re-negotiate the terminal's eDRX capabilities with the network:
  • Condition 1 The terminal has joined the multicast session
  • Condition 2 The service characteristics of the multicast service carried in the N1 message received in step 1403 indicate that the multicast service does not support eDRX;
  • Condition 3 eDRX parameters for CM-IDLE have been negotiated with the network before, and information indicating that the terminal is allowed to enter eDRX and PTW information are received.
  • the registration request message does not carry information indicating that the terminal supports eDRX or carries information indicating that the terminal does not support eDRX.
  • the terminal since the terminal has joined the multicast session, information indicating that the terminal supports eDRX will not be carried when the terminal initiates the registration process again.
  • the terminal can carry information indicating that the terminal supports eDRX when initiating the registration process again.
  • Step 1105 After receiving the registration request message from the terminal, the AMF sends a terminal context update message to the access network device.
  • the access network device receives the terminal context update message from the AMF.
  • the terminal context update message does not include information indicating that the terminal supports eDRX, or the terminal context update message includes information indicating that the terminal does not support eDRX.
  • the UE specific extended idle mode DRX is not carried in the RIAI information, or the UE specific extended idle mode DRX is carried in the RIAI information, but the UE specific extended idle mode DRX is a special value.
  • a possible implementation manner is that before the AMF sends the terminal context update message to the access network device, the AMF determines that the RIAI information has been provided to the access network device before.
  • the AMF determines that RIAI information has been provided to the access network device before, and the RIAI information includes information indicating that the terminal is allowed to enter eDRX.
  • Step 1106 The access network device does not convert the terminal to the inactive state of eDRX according to the updated terminal context.
  • the access network device when the terminal has joined the multicast session, the access network device will not convert the terminal to the inactive state of eDRX.
  • the access network device when the terminal has joined the multicast session, can convert the terminal to the inactive state of eDRX, and the multicast data is cached in the core network device and changes to the eDRX state again at the terminal. It is sent to the terminal only when it is reachable.
  • the access network device can convert the terminal to the inactive state of eDRX, and the multicast data can be cached in the UPF.
  • Figure 12 is another example of the communication method of the present application.
  • Step 1201 The terminal registers with the network and negotiates eDRX parameters for CM-IDLE with the network.
  • Step 1202 The terminal requests to join the multicast session, and accordingly, the core network device establishes related resources for the multicast session.
  • Steps 1201 to 1202 may refer to steps 701 to 702, which will not be described in detail here.
  • Step 1203 The AMF sends the N2 message to the access network device.
  • the access network device receives the N2 message from the AMF.
  • the N2 message includes RIAI.
  • the RIAI carries the information required to convert the terminal to the inactive state, such as registration area, periodic registration time, UE specific extended idle mode DRX values (UE specific extended idle mode DRX values), etc.
  • Step 1204 The access network device decides to use the terminal based on the RIAI and other possible information (such as the implementation of the access network device, the UE's radio capability (UE Radio Capability) to support eDRX, or the current load of the access network device, etc.) Convert to RRC inactive state.
  • UE Radio Capability UE Radio Capability
  • Step 1205 The access network device sends the N2 message to the AMF.
  • the AMF receives the N2 message from the access network device.
  • the N2 message includes eDRX information (for example, the period for the terminal to enter eDRX, eDRX indication, buffering time, etc.).
  • eDRX information for example, the period for the terminal to enter eDRX, eDRX indication, buffering time, etc.
  • the AMF can learn based on the N2 message that the access network equipment plans (or prepares) to convert the terminal to the inactive state of eDRX, and then for the PDU session in the active state of the user plane, the AMF can notify The corresponding SMF.
  • the N2 message may be a UE Notification message, an RRC INACTIVE TRANSITION REPORT message, or other messages, which are not limited in this application.
  • Step 1206 AMF sends an update session management context request message (such as Nsmf_PDUSessionUpdateSMContext request) to the corresponding SMF.
  • an update session management context request message such as Nsmf_PDUSessionUpdateSMContext request
  • the SMF receives the update session management context request message from the AMF.
  • the update session management context request message carries instruction information #4 and eDRX information.
  • Instruction information #4 is used to instruct to stop user plane transmission and cache user plane multicast data.
  • the SMF starts to cache the downlink multicast data. If handled by MB-SMF Downstream multicast data, then SMF notifies MB-SMF to cache the downstream multicast data. If the downlink multicast data is processed by UPF or MB-UPF, the SMF may continue to perform step 1207.
  • indication information #4 may be a user plane suspend (UP Suspend) indication.
  • An example may be that the N2 message contains a list of PDU sessions that are active on the user plane, and the AMF notifies the corresponding SMF according to the list.
  • Step 1207 After receiving the update session management context request message in step 1206, SMF triggers the establishment of a transmission channel (or forwarding channel, channel, forwarding tunnel) from MB-UPF to UPF.
  • a transmission channel or forwarding channel, channel, forwarding tunnel
  • the SMF determines: a) For the terminal, there is currently no MB-UPF to UPF transmission channel; and/ Or, b) SMF has established a transmission channel from MB-UPF to UPF, but MB-UPF does not send data to UPF at this time (for example, MB-UPF is configured not to send data to UPF); and/or, c) The terminal is currently The resident access network equipment supports multicast (for example, the SMF receives the indication information "NG-RAN supports MBS" from the N2 message received by the access network equipment); the SMF triggers the establishment of MB- UPF to UPF transmission channel. "Create" here can refer to new creation or modification.
  • Step 1208 SMF sends an N4 message (such as an N4 session modification request message) to UPF.
  • N4 message such as an N4 session modification request message
  • UPF receives the N4 message from SMF.
  • the N4 message is used to request the establishment of a transmission channel from UPF to MB-UPF, or to ask UPF whether a transmission channel from UPF to MB-UPF has been established.
  • the N4 message includes eDRX information (buffer info for eDRX), multicast session identifier (such as TMGI), optional SSM and other information.
  • the eDRX information is used to cache the multicast data of the terminal.
  • the N4 message also includes configuration information.
  • the configuration information is used to configure: a) multicast data identification rules; b) multicast data forwarding rules, etc.
  • Step 1209 The UPF sends the response message or data packet of the N4 message in step 1208 to the SMF.
  • SMF receives the response message or data packet from UPF.
  • the response message includes downlink tunnel identification #1 (such as DL tunnel ID #1).
  • UPF determines whether a transmission channel from UPF to MB-UPF has been established. If the transmission channel from UPF to MB-UPF has not been established, UPF can return the downstream tunnel identification #1, or send the data packet according to the SSM information.
  • the UPF may also include whether the downlink tunnel identifier #1 is newly allocated in the N4 response message.
  • Step 1210 SMF sends the N16mb message to MB-SMF.
  • MB-SMF receives the N16mb message from SMF.
  • the N16mb message is used to request the establishment of a transmission channel from UPF to MB-UPF.
  • the N16mb message includes downlink tunnel identification #1.
  • the SMF may send the N16mb message to the MB-SMF.
  • Step 1211 MB-SMF and MB-UPF perform the N4mb session modification process.
  • MB-SMF may provide downlink tunnel identity #1 to MB-UPF or receive downlink tunnel identity #2 provided by MB-UPF for multicast.
  • Step 1212 MB-SMF sends the response message of the N16mb message in step 1210 to SMF.
  • the SMF receives the response message from the MB-SMF.
  • the response message carries downlink tunnel identification #2.
  • the SMF can configure the following content for the UPF after receiving the response message: a) multicast data identification rules; b) multicast data forwarding rules, etc.
  • the SMF may provide the downlink tunnel identification #2 to the UPF.
  • Step 1213 The SMF sends the response message to the N11 message in step 1206 to the AMF.
  • AMF receives the response message from SMF.
  • Step 1214 The AMF sends the response message of the N2 message in step 1205 to the access network device.
  • the access network device receives the response message from the AMF.
  • Step 1215 The access network device converts the terminal to the RRC inactive state of eDRX.
  • Figure 13 is a schematic diagram of transmitting multicast data.
  • the schematic diagram of transmitting multicast data shown in Figure 13 is based on the transmission method shown in Figure 12.
  • the access network device can convert the terminal to the inactive state of eDRX.
  • MB-UPF multicasts the multicast of terminal 1 in the eDRX state through the transmission channel between UPF and MB-UPF.
  • the data is transmitted to UPF, which caches the multicast data for terminal 1.
  • the access network equipment can convert the terminal to the inactive state of eDRX, and the multicast data can be cached in the UPF, thereby preventing the terminal from missing multicast data and helping to ensure multicast services. transmission.
  • the access network device when the terminal joins the multicast session, can convert the terminal to the inactive state of eDRX, and the multicast data can be cached in the MB-UPF.
  • Figure 14 is another example of the communication method of the present application.
  • Step 1401 The terminal registers with the network and negotiates eDRX parameters for CM-IDLE with the network.
  • Step 1402 The terminal requests to join the multicast session, and accordingly, the core network device establishes related resources for the multicast session.
  • Steps 1401 to 1402 may refer to steps 701 to 702, which will not be described in detail here.
  • Step 1403 The AMF sends the N2 message to the access network device.
  • the access network device receives the N2 message from the AMF.
  • the N2 message includes RIAI.
  • the RIAI carries the information required to convert the terminal to the inactive state, such as registration area, periodic registration time, UE specific extended idle mode DRX values (UE specific extended idle mode DRX values), etc.
  • Step 1404 The access network device decides to use the terminal based on the RIAI and other possible information (such as the implementation of the access network device, the UE's radio capability (UE Radio Capability) to support eDRX, or the current load of the access network device, etc.) Convert to RRC inactive state.
  • UE Radio Capability UE Radio Capability
  • Step 1405 The access network device sends the N2 message to the AMF.
  • the AMF receives the N2 message from the access network device.
  • the N2 message includes eDRX information (for example, the period for the terminal to enter eDRX, eDRX indication, buffering time, etc.).
  • eDRX information for example, the period for the terminal to enter eDRX, eDRX indication, buffering time, etc.
  • the AMF can learn based on the N2 message that the access network equipment plans (or prepares) to convert the terminal to the inactive state of eDRX, and then for the PDU session in the active state of the user plane, the AMF can notify The corresponding SMF.
  • the N2 message may be a UE Notification message, an RRC INACTIVE TRANSITION REPORT message, or other messages, which are not limited in this application.
  • Step 1406 AMF sends an update session management context request message (such as Nsmf_PDUSessionUpdateSMContext request) to the corresponding SMF.
  • an update session management context request message such as Nsmf_PDUSessionUpdateSMContext request
  • the SMF receives the update session management context request message from the AMF.
  • An example may be that the N2 message contains a list of PDU sessions that are active on the user plane, and the AMF notifies the corresponding SMF according to the list.
  • the update session management context request message carries instruction information #4 and eDRX information.
  • Instruction information #4 is used to instruct to stop user plane transmission and cache user plane multicast data.
  • the SMF starts to cache the downlink multicast data. If the downlink multicast data is processed by MB-SMF, the SMF notifies MB-SMF to cache the downlink multicast data. If the downlink multicast data is processed by UPF or MB-UPF, the SMF may continue to step 1407.
  • Step 1407 After receiving the update session management context request message in step 1406, SMF triggers the establishment of a transmission channel (or forwarding channel, channel, forwarding tunnel) from MB-UPF to UPF.
  • a transmission channel or forwarding channel, channel, forwarding tunnel
  • the SMF determines: a) for the terminal, there is currently no MB-UPF to UPF transmission channel; and /or, b) SMF establishes a transmission channel from MB-UPF to UPF, but MB-UPF does not send data to UPF at this time (for example, MB-UPF is configured not to send data to UPF); and/or, c) terminal
  • the currently resident access network device supports multicast (for example, in the N2 message received by the SMF from the access network device, the "Basic Station supports multicast (NG-RAN supports MBS)" indication information); SMF triggers the establishment of a transmission channel from MB-UPF to UPF.
  • the "establishment" here can refer to new creation or modification.
  • the judgment logic in step 1407 may or may not be executed without limitation.
  • Step 1408 SMF sends an N4 message (such as an N4 session modification request message) to UPF.
  • N4 message such as an N4 session modification request message
  • UPF receives the N4 message from SMF.
  • the N4 message is used to request the establishment of a transmission channel from UPF to MB-UPF, or to ask UPF whether a transmission channel from UPF to MB-UPF has been established.
  • the N4 message includes eDRX information, multicast session identifier (such as TMGI), optional SSM and other information, where the eDRX information is used to cache multicast data of the terminal.
  • the N4 message also includes configuration information.
  • the configuration information is used to configure: a) multicast data identification rules; b) multicast data forwarding rules, etc.
  • Step 1409 The UPF sends the response message or data packet of the N4 message in step 1408 to the SMF.
  • SMF receives the response message or data packet from UPF.
  • the response message includes downlink tunnel identification #1 (such as DL tunnel ID #1).
  • UPF determines whether a transmission channel from UPF to MB-UPF has been established. If the transmission channel from UPF to MB-UPF has not been established, UPF can return the downlink tunnel identification #1, or send the data packet according to the SSM information.
  • the UPF may also include whether the downlink tunnel identifier #1 is newly allocated in the N4 response message.
  • Step 1410 SMF sends the N16mb message to MB-SMF.
  • MB-SMF receives the N16mb message from SMF.
  • the N16mb message is used to request the establishment of a transmission channel from UPF to MB-UPF, and the N16mb message includes eDRX information.
  • the N16mb message includes downlink tunnel identification #1.
  • the SMF may send the N16mb message to the MB-SMF.
  • Step 1411 MB-SMF and MB-UPF perform the N4mb session modification process.
  • the MB-SMF may provide the eDRX information to the MB-UPF, and provide the downlink tunnel identification #1 to the MB-UPF or receive the downlink tunnel identification #2 provided by the MB-UPF for multicast.
  • Step 1412 MB-SMF sends the response message of the N16mb message in step 1410 to SMF.
  • the SMF receives the response message from the MB-SMF.
  • the response message carries downlink tunnel identification #2.
  • the SMF can configure the following content for the UPF after receiving the response message: a) multicast data identification rules; b) multicast data forwarding rules, etc.
  • the SMF may provide the downlink tunnel identification #2 to the UPF.
  • Step 1413 The SMF sends the response message to the N11 message in step 1406 to the AMF.
  • AMF receives the response message from SMF.
  • Step 1414 The AMF sends the response message of the N2 message in step 1405 to the access network device.
  • the access network device receives the response message from the AMF.
  • Step 1415 The access network device converts the terminal to the RRC inactive state of eDRX.
  • Figure 15 is another schematic diagram of transmitting multicast data.
  • the schematic diagram of transmitting multicast data shown in Figure 15 is based on the transmission method shown in Figure 14.
  • the access network device can convert the terminal to the inactive state of eDRX.
  • MB-UPF caches multicast data for the terminal in the eDRX state (such as terminal 1).
  • MB-UPF transmits the cached multicast data to UPF through the transmission channel between UPF and MB-UPF, and then UPF sends it to the terminal. .
  • the access network equipment can convert the terminal to the inactive state of eDRX, and the multicast data can be cached in MB-UPF, thereby preventing the terminal from missing multicast data and helping to ensure multicast data transmission. transmission of broadcast services.
  • MB-UPF Caching multicast data with a relatively high cache point helps reduce the amount of data cached by the network.
  • the device in Figure 16 or Figure 17 includes corresponding hardware structures and/or software modules to perform each function.
  • the units and method steps of each example described in conjunction with the embodiments disclosed in this application can be implemented in the form of hardware or a combination of hardware and computer software.
  • FIGS 16 and 17 are schematic structural diagrams of possible devices provided by embodiments of the present application. These devices can be used to implement the functions of core network equipment, access network equipment, access and mobility management functional network elements, terminals, session management functions or multicast user plane functional network elements in the above method embodiments, and therefore can also be implemented The above method embodiments have beneficial effects.
  • the device 1600 includes a transceiver unit 1610 and a processing unit 1620.
  • the transceiver unit 1610 when the device 1600 is used to implement the functions of the core network device in the above method embodiment, the transceiver unit 1610 is used to: learn that the terminal has joined the multicast session; send first information, the first information is used to: The notification refuses to configure eDRX in the inactive state for the terminal, or the first information is used to indicate that the terminal is not suitable for eDRX in the inactive state.
  • the transceiver unit 1610 is specifically configured to: send the first information when at least one of the following conditions is met: the access network equipment that provides services for the terminal does not support eDRX, and the terminal does not support eDRX. , or the multicast session meets a preset condition; wherein the preset condition is: the multicast session is in an active state, the multicast service corresponding to the multicast session does not support eDRX, or the multicast session The multicast service corresponding to the active state and the multicast session does not support eDRX.
  • the first information when the first information is used to notify a refusal to configure eDRX in an inactive state for the terminal, the first information includes refusal information, and the refusal information is used to indicate a refusal to configure eDRX for the terminal in an inactive state. eDRX in active state.
  • the transceiver unit 1610 is further configured to receive second information, where the second information is used to request to configure eDRX in an inactive state for the terminal.
  • the rejection information includes a reason for refusing to configure eDRX in an inactive state for the terminal; wherein the reason includes at least one of the following: the terminal has joined a multicast session, The access network equipment does not support eDRX, the terminal does not support eDRX, or the multicast session meets preset conditions; wherein the preset conditions are: the multicast session is active, the multicast session corresponds to The multicast service does not support eDRX, or the multicast session is in an active state and the multicast service corresponding to the multicast session does not support eDRX.
  • the transceiver unit 1610 is further configured to receive third information from the access network device, where the third information is used to indicate that the access network device does not support eDRX.
  • the core network device is an access and mobility management function network element or a session management function network element.
  • the core network device is an access and mobility management function network element
  • the transceiver unit 1610 is further configured to: receive service information from the session management function, where the service information is used to indicate the multicast session corresponding to Multicast services do not support eDRX.
  • the service information includes a type of the multicast service, and the type is a delay-sensitive type.
  • the core network device is an access and mobility management function network element
  • the transceiver unit 1610 is further configured to: receive fourth information from the session management function network element, where the fourth information is used to indicate to the terminal Joined multicast session.
  • the transceiver unit 1610 is configured to: when it is determined to convert the terminal to the inactive state, send the second information to the core network device , the second information is used to request to configure eDRX in the inactive state for the terminal; receive the first information from the core network device, the first information is used to notify the refusal to configure the inactive state for the terminal eDRX under.
  • the processing unit 1620 is configured to not configure eDRX in an inactive state for the terminal according to the first information.
  • the first information includes rejection information, and the rejection information is used to indicate a refusal to configure eDRX in an inactive state for the terminal.
  • the rejection information includes a reason for refusing to configure eDRX in an inactive state for the terminal; wherein the reason includes at least one of the following: the terminal has joined a multicast session, the access network device is not eDRX is supported, the terminal does not support eDRX, or the multicast session meets preset conditions; wherein the preset conditions are: the multicast session is in an active state, and the multicast service corresponding to the multicast session does not eDRX is supported, or the multicast session is in an active state and the multicast service corresponding to the multicast session does not support eDRX.
  • the core network device is an access and mobility management function network element or a session management function network element.
  • the transceiver unit 1610 is used to: receive first information from the core network device, where the first information is used to indicate that the terminal is not applicable to eDRX in the inactive state.
  • the processing unit 1620 is configured to: when it is determined to convert the terminal to the inactive state, not configure eDRX in the inactive state for the terminal according to the first information.
  • the core network device is an access and mobility management function network element or a session management function network element.
  • the transceiver unit 1610 when the device 1600 is used to implement the functions of the access network device in the above method embodiment, the transceiver unit 1610 is used to: learn that the terminal has joined the multicast session.
  • the processing unit 1620 is configured to: when determining to convert the terminal to the inactive state, not configure eDRX in the inactive state for the terminal.
  • the processing unit 1620 is specifically configured to: not configure eDRX in the inactive state for the terminal when at least one of the following conditions is met: the access network device does not support eDRX, the terminal does not support eDRX, or the multicast session satisfies preset conditions; wherein the preset conditions are: the multicast session is active, the multicast service corresponding to the multicast session does not support eDRX, or the multicast The session is active and the multicast service corresponding to the multicast session does not support eDRX.
  • the transceiver unit 1610 is also configured to receive service information from the session management function, where the service information is used to indicate that the multicast service corresponding to the multicast session does not support eDRX.
  • the service information includes a type of the multicast service, and the type is a delay-sensitive type.
  • the transceiver unit 1610 is used to: receive the second information from the access network device, the first The second information is used to request to configure eDRX in the inactive state for the terminal; the second information is sent to the first session management function network element and the second session management function network element, and the first session management function network element is used for management The unicast session associated with the multicast session of the terminal, the second session management function network element is used to manage the unicast session not associated with the multicast session of the terminal; receiving from the first session management The first information of the functional network element, the first information is used to notify the refusal to configure eDRX in the inactive state for the terminal; send the first information to the access network device, and/or, The second session management function network element sends fifth information, and the fifth information is used to trigger the second session management function network element to stop configuring eDRX in an inactive state for the terminal.
  • the first information includes rejection information, and the rejection information is used to indicate a refusal to configure eDRX in an inactive state for the terminal.
  • the rejection information includes a reason for refusing to configure eDRX in an inactive state for the terminal; wherein the reason includes at least one of the following: the terminal has joined a multicast session, the access network device is not eDRX is supported, the terminal does not support eDRX, or the multicast session meets preset conditions; wherein the preset conditions are: the multicast session is in an active state, and the multicast service corresponding to the multicast session does not eDRX is supported, or the multicast session is in an active state and the multicast service corresponding to the multicast session does not support eDRX.
  • the transceiver unit 1610 when the device 1600 is used to implement the functions of the terminal in the above method embodiment, the transceiver unit 1610 is used to: learn that the terminal has joined the multicast session and the terminal supports eDRX; and sends a message to the access network device. Sixth information, the sixth information is used to indicate that the terminal does not support eDRX.
  • the transceiver unit 1610 is specifically configured to: send the sixth information to the access network device when at least one of the following conditions is met: receiving the first information from the core network device, the access network device The network access device does not support eDRX, the terminal does not support eDRX, or the multicast session meets preset conditions; wherein the first information is used to indicate that the terminal is not suitable for eDRX in an inactive state, and the preset Assume that the condition is: the multicast session is in an active state, the multicast service corresponding to the multicast session does not support eDRX, or the multicast session is in an active state and the multicast service corresponding to the multicast session does not support eDRX. .
  • the core network device is an access and mobility management function network element or a session management function network element.
  • the transceiver unit 1610 is also configured to receive service information from the session management function, where the service information is used to indicate that the multicast service corresponding to the multicast session does not support eDRX.
  • the service information includes a type of the multicast service, and the type is a delay-sensitive type.
  • the transceiver unit 1610 is further configured to: send seventh information to the access network device, where the seventh information is used to indicate that the terminal supports eDRX.
  • the transceiver unit 1610 is further configured to: after the terminal leaves all multicast sessions that the terminal has joined, send eighth information to the access network device, where the eighth information is used to indicate that the The terminal supports eDRX.
  • the transceiver unit 1610 when the device 1600 is used to implement the function of the session management function network element in the above method embodiment, the transceiver unit 1610 is used to: receive second information from the access network device, the second information is used to Request to configure eDRX in inactive state for the terminal.
  • the processing unit 1620 is configured to: establish transmission between the unicast user plane functional network element and the multicast user plane functional network element according to the second information. Channel, the transmission channel is used to transmit multicast data of the terminal.
  • the transceiver unit 1610 is further configured to send ninth information to the access network device, where the ninth information is used to indicate that eDRX in the inactive state is successfully configured for the terminal.
  • the transceiver unit 1610 is further configured to send eDRX cache information to the unicast user plane functional network element or the multicast user plane functional network element, where the eDRX cache information is used to cache the multicast data.
  • the transceiver unit 1610 is used to: receive eDRX cache information from the session management function network element, the eDRX cache Information used to cache multicast data for endpoints.
  • the processing unit 1620 is configured to cache the multicast data of the terminal according to the eDRX cache information.
  • transceiver unit 1610 and processing unit 1620 For a more detailed description of the above-mentioned transceiver unit 1610 and processing unit 1620, reference may be made to the relevant descriptions in the above-mentioned method embodiments, which will not be described again here.
  • device 1700 includes processor 1710.
  • Processor 1710 is coupled to memory 1730 for storing instructions.
  • the processor 1710 is used to execute instructions in the memory 1730 to implement the functions of the above-mentioned processing unit 1620.
  • device 1700 also includes memory 1730.
  • the apparatus 1700 also includes an interface circuit 1720.
  • the processor 1710 and the interface circuit 1720 are coupled to each other.
  • the interface circuit 1720 may be a transceiver or an input-output interface.
  • the processor 1710 is used to execute instructions to realize the functions of the above-mentioned processing unit 1620, and the interface circuit 1720 is used to realize the functions of the above-mentioned transceiver unit 1610.
  • the chip when the device 1700 is a chip applied to core network equipment, access network equipment, access and mobility management function network elements, terminals, session management functions or multicast user plane function network elements, the chip implements the above In the method embodiment, the functions of core network equipment, access network equipment, access and mobility management function network elements, terminals, session management function or multicast user plane function network elements are included.
  • the chip receives information from other modules (such as radio frequency modules or antennas) in core network equipment, access network equipment, access and mobility management function network elements, terminals, session management functions or multicast user plane function network elements.
  • the information is sent by other devices to core network equipment, access network equipment, access and mobility management function network elements, terminals, session management function or multicast user plane function network elements; or, the chip Network access equipment, access and mobility management function network elements, terminals, session management functions or other modules (such as radio frequency modules or antennas) in the multicast user plane function network element send information.
  • the information is core network equipment, access Network equipment, access and mobility management function network elements, terminals, session management function or multicast user plane function network elements are sent to other devices.
  • the application also provides a communication device, including a processor, the processor is coupled to a memory, the memory is used to store computer programs or instructions and/or data, the processor is used to execute the computer programs or instructions stored in the memory, or read the memory storage data to perform the methods in each of the above method embodiments.
  • a communication device including a processor, the processor is coupled to a memory, the memory is used to store computer programs or instructions and/or data, the processor is used to execute the computer programs or instructions stored in the memory, or read the memory storage data to perform the methods in each of the above method embodiments.
  • the communication device includes memory.
  • the memory is integrated with the processor, or is provided separately.
  • the present application also provides a computer-readable storage medium, which stores the core network equipment, access network equipment, access and mobility management function network elements, terminals, session management functions or Computer instructions for a method performed by a multicast user plane functional network element.
  • the present application also provides a computer program product, which includes instructions. When executed by a computer, the instructions are used to implement core network equipment, access network equipment, access and mobility management function network elements, terminals, and sessions in each of the above method embodiments. Method for network elements to perform management functions or multicast user plane functions.
  • This application also provides a communication system, which includes the core network equipment, access network equipment, access and mobility management functional network elements, terminals, session management functions or multicast user plane functions in the above embodiments. At least one of the network elements.
  • processor in the embodiment of the present application can be a central processing unit (CPU), or other general-purpose processor, digital signal processor (DSP), or application-specific integrated circuit (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • CPU central processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor can be a microprocessor or any conventional processor.
  • the method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions.
  • Software instructions can be composed of corresponding software modules.
  • Software modules can be stored in random access memory, flash memory, read-only memory, etc.
  • An exemplary storage medium is coupled to the processor such that the processor can read information from the storage medium and write information to the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and storage media may be located in an ASIC.
  • the ASIC can be located in core network equipment, access network equipment, access and mobility management function network elements, terminals, session management functions or multicast user plane function network elements.
  • the processor and storage medium can also exist as discrete components in core network equipment, access network equipment, access and mobility management function network elements, terminals, session management functions or multicast user plane function network elements.
  • the computer program product includes one or more computer programs or instructions.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, a network device, a user equipment, or other programmable device.
  • the computer program or instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another.
  • the computer program or instructions may be transmitted from a website, computer, A server or data center transmits via wired or wireless means to another website site, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media.
  • the available media may be magnetic media, such as floppy disks, hard disks, and tapes; optical media, such as digital video optical disks; or semiconductor media, such as solid-state hard drives.

Landscapes

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

Abstract

本申请提供了一种通信方法和通信装置，在该方法中，在终端已经加入多播会话的情况下，核心网设备可以向接入网设备通知拒绝为终端配置非激活态下的eDRX或者向接入网设备指示终端不适用非激活态下的eDRX，使得接入网设备在将终端转换为非激活态时可以根据核心网设备的通知或指示不为终端配置非激活态下的eDRX，从而实现终端的eDRX管理以及保障多播业务的传输。

Description

一种通信方法和通信装置
本申请要求于2022年08月09日提交中国国家知识产权局、申请号为202210952997.5、申请名称为“一种通信方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，并且更具体地，涉及一种通信方法和通信装置。
背景技术
接入网设备可以通过为终端配置延长非连续接收(extended discontinuous reception，eDRX)来节省终端的能耗。处于eDRX的睡眠状态的终端不可达，即终端不能接收下行数据。
目前，终端可以通过加入多播会话来接收多播业务的数据(可以简称多播数据)，并且在多播数据的传输过程中，终端保持在连接态。由于接入网设备的容量有限，接入网设备仅支持有限数量的终端保持在连接态。为了在接入网设备资源不足的情况下仍能够保证多播数据的传输，提出了一种解决方案：终端在非激活态接收多播数据。具体地，在接入网设备资源不足的情况下，接入网设备可以将加入了多播会话的终端转换为非激活态，并通过广播方式或其他方式通知终端接收多播数据，从而实现终端在非激活态接收多播数据。在上述场景下，如何管理非激活态下的终端的eDRX成为急需解决的问题。
发明内容
本申请提供一种通信方法和通信装置，可以实现非激活态下的终端的eDRX的管理。
第一方面，提供了一种通信方法，所述方法可以由核心网设备执行，也可以由核心网设备中的模块或单元执行，为了描述方便，下文统一称为核心网设备。
所述方法包括：核心网设备获知终端已加入多播会话；所述核心网设备发送第一信息，所述第一信息用于通知拒绝为所述终端配置非激活态下的eDRX，或者所述第一信息用于指示所述终端不适用非激活态下的eDRX。
可选地，当第一信息用于通知拒绝为终端配置非激活态下的eDRX时，核心网设备向接入网设备发送第一信息。
可选地，当第一信息用于指示终端不适用非激活态下的eDRX时，核心网设备向接入网设备或终端发送第一信息。
基于上述方法，在终端已加入多播会话的情况下，核心网设备可以向接入网设备通知拒绝为终端配置非激活态下的eDRX，或者指示终端不适用非激活态下的eDRX，以便接入网设备根据核心网设备的通知或指示不为终端配置非激活态下的eDRX；或者核心网设备向终端指示终端不适用非激活态下的eDRX，以便终端请求更新在终端在接入网设备的eDRX能力(更新为不支持eDRX)，使得接入网设备根据更新后的终端的eDRX能力不为终端配置非激活态下的eDRX，从而实现终端的eDRX管理。
此外，在终端已加入多播会话的情况下，不为终端配置非激活态下的eDRX，有助于保障多播会话对应的多播数据的传输。
结合第一方面，在一种可能的实现方式中，所述核心网设备发送第一信息，包括：当以下条件中的至少一个被满足时，所述核心网设备发送所述第一信息：为所述终端提供服务的接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件；其中，所述预设条件为：所述多播会话处于激活态、所述多播会话对应的多播业务不支持eDRX、或所述多播会话处于激活态且所述多播会话对应的多播业务不支持eDRX。
这里的“以下条件”指的是：为所述终端提供服务的接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件。
基于上述方法，在核心网设备获知终端已加入多播会话后，核心网设备可以进一步判断上述条件是否被满足，当上述条件被满足时，核心网设备发送第一信息，以通知拒绝为终端配置非激活态下的eDRX或者指示终端不适用非激活态下的eDRX。这样，可以使得核心网设备的判断结果更准确。
结合第一方面或其任意实现方式，在另一种可能的实现方式中，当所述第一信息用于通知拒绝为所述终端配置非激活态下的eDRX时，所述第一信息包括拒绝信息，所述拒绝信息用于指示拒绝为所述终端配置非激活态下的eDRX。结合第一方面或其任意实现方式，在另一种可能的实现方式中，所述方法还包括：所述核心网设备接收第二信息，所述第二信息用于请求为所述终端配置非激活态下的eDRX。
基于上述方法，当接入网设备确定将终端转换为非激活态时，可以向核心网设备向核心网设备请求为终端配置非激活态下的eDRX，核心网设备接收到接入网设备的请求后，可以结合终端已加入多播会话判断不允许为终端配置非激活态下的eDRX，从而拒绝接入网设备的请求，使得接入网设备在请求被拒绝后不为终端配置非激活态下的eDRX，从而实现在终端已加入多播会话的情况下不为终端配置非激活态下的eDRX，有助于保障多播会话对应的多播数据的传输。
结合第一方面或其任意实现方式，在另一种可能的实现方式中，所述拒绝信息包括拒绝为所述终端配置非激活态下的eDRX的原因；其中，所述原因包括以下至少一个：所述终端已加入多播会话、为所述终端提供服务的接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件；其中，所述预设条件为：所述多播会话处于激活态、所述多播会话对应的多播业务不支持eDRX、或所述多播会话处于激活态且所述多播会话对应的多播业务不支持eDRX。
结合第一方面或其任意实现方式，在另一种可能的实现方式中，所述方法还包括：所述核心网设备接收来自所述接入网设备的第三信息，所述第三信息用于指示所述接入网设备不支持eDRX。
基于上述方法，接入网设备可以向核心网设备上报自己是否支持eDRX，使得核心网设备可以根据接入网设备的eDRX能力判断是否允许为终端配置非激活态下的eDRX。
结合第一方面或其任意实现方式，在另一种可能的实现方式中，所述核心网设备为接入和移动性管理功能网元或会话管理功能网元。
结合第一方面或其任意实现方式，在另一种可能的实现方式中，所述核心网设备为接入和移动性管理功能网元，所述方法还包括：所述接入和移动性管理功能网元接收来自会话管理功能的业务信息，所述业务信息用于指示所述多播会话对应的多播业务不支持eDRX。
基于上述方法，核心网设备可以根据终端已加入的多播会话对应的多播业务是否支持eDRX判断是否允许为终端配置非激活态下的eDRX。
结合第一方面或其任意实现方式，在另一种可能的实现方式中，所述业务信息包括所述多播业务的类型，所述类型为时延敏感类型。
结合第一方面或其任意实现方式，在另一种可能的实现方式中，所述核心网设备为接入和移动性管理功能网元，所述方法还包括：所述接入和移动性管理功能网元接收来自会话管理功能网元的第四信息，所述第四信息用于指示所述终端已加入多播会话。
基于上述方法，由会话管理功能网元向接入和移动性管理功能网元提供终端已加入多播会话的信息，使得接入和移动性管理功能网元可以基于终端已加入多播会话发送第一信息。
第二方面，提供了一种通信方法，所述方法可以由接入网设备执行，也可以由接入网设备中的模块或单元执行，为了描述方便，下文统一称为接入网设备。
所述方法包括：当接入网设备确定将终端转换为非激活态时，所述接入网设备向核心网设备发送第二信息，所述第二信息用于请求为所述终端配置非激活态下的eDRX；所述接入网设备接收来自所述核心网设备的第一信息，所述第一信息用于通知拒绝为所述终端配置非激活态下的eDRX；所述接入网设备根据所述第一信息，不为所述终端配置非激活态下的eDRX。
基于上述方法，当接入网设备确定将终端转换为非激活态时，可以向核心网设备向核心网设备请求为终端配置非激活态下的eDRX，并在请求被核心网设备拒绝后不为终端配置非激活态下的eDRX，从而实现在终端已加入多播会话的情况下不为终端配置非激活态下的eDRX，从而实现终端的eDRX管理。
此外，在终端已加入多播会话的情况下，不为终端配置非激活态下的eDRX，有助于保障多播会 话对应的多播数据的传输。
结合第二方面，在一种可能的实现方式中，所述第一信息包括拒绝信息，所述拒绝信息用于指示拒绝为所述终端配置非激活态下的eDRX。
结合第二方面或其任意实现方式，在另一种可能的实现方式中，所述拒绝信息包括拒绝为所述终端配置非激活态下的eDRX的原因；其中，所述原因包括以下至少一个：所述终端已加入多播会话、所述接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件；其中，所述预设条件为：所述多播会话处于激活态、所述多播会话对应的多播业务不支持eDRX、或所述多播会话处于激活态且所述多播会话对应的多播业务不支持eDRX。
结合第二方面或其任意实现方式，在另一种可能的实现方式中，所述核心网设备为接入和移动性管理功能网元或会话管理功能网元。
第三方面，提供了一种通信方法，所述方法可以由接入网设备执行，也可以由接入网设备中的模块或单元执行，为了描述方便，下文统一称为接入网设备。
所述方法包括：接入网设备接收来自核心网设备的第一信息，所述第一信息用于指示终端不适用非激活态下的eDRX；当所述接入网设备确定将所述终端转换为非激活态时，所述接入网设备根据所述第一信息，不为所述终端配置非激活态下的eDRX。
基于上述方法，在终端已加入多播会话的情况下，核心网设备可以向接入网设备指示终端不适用非激活态下的eDRX，接入网设备可以根据核心网设备的指示不为终端配置非激活态下的eDRX，从而实现终端的eDRX管理。
此外，在终端已加入多播会话的情况下，不为终端配置非激活态下的eDRX，有助于保障多播会话对应的多播数据的传输。
结合第三方面，在一种可能的实现方式中，所述核心网设备为接入和移动性管理功能网元或会话管理功能网元。
第四方面，提供了一种通信方法，所述方法可以由接入和移动性管理功能网元执行，也可以由接入和移动性管理功能网元中的模块或单元执行，为了描述方便，下文统一称为接入和移动性管理功能网元。
所述方法包括：接入和移动性管理功能网元接收来自接入网设备的第二信息，所述第二信息用于请求为终端配置非激活态下的eDRX；所述接入和移动性管理功能网元向第一会话管理功能网元和第二会话管理功能网元发送所述第二信息，所述第一会话管理功能网元用于管理与所述终端的多播会话相关联的单播会话，所述第二会话管理功能网元用于管理与所述终端的多播会话不关联的单播会话；所述接入和移动性管理功能网元接收来自所述第一会话管理功能网元的第一信息，所述第一信息用于通知拒绝为所述终端配置非激活态下的eDRX；所述接入和移动性管理功能网元向所述接入网设备发送所述第一信息，和/或，向所述第二会话管理功能网元发送第五信息，所述第五信息用于触发所述第二会话管理功能网元停止为所述终端配置非激活态下的eDRX。
基于上述方法，接入网设备通过接入和移动性管理功能网元与第一会话管理功能网元交互。接入和移动性管理功能网元可以向第一会话管理功能网元和第二会话管理功能网元请求为终端配置非激活态下的eDRX，并且在接入和移动性管理功能网元接收到来自第一会话管理功能网元的第一信息后，接入和移动性管理功能网元向第二会话管理功能网元发送第五信息，以便触发第二会话管理功能网元停止为终端配置非激活态下的eDRX，从而实现终端的eDRX管理。
此外，在终端已加入多播会话的情况下，不为终端配置非激活态下的eDRX，有助于保障多播会话对应的多播数据的传输。
需要说明的是，接入和移动性管理功能网元接收到的信息和接入和移动性管理功能网元发送的信息虽然都被称为第一信息或第二信息，但接入和移动性管理功能网元接收到的信息和接入和移动性管理功能网元发送的信息的实现方式可以相同，也可以不同(例如通过不同的消息和/或信元)，不予限制。
结合第四方面，在一种可能的实现方式中，所述第一信息包括拒绝信息，所述拒绝信息用于指示拒绝为所述终端配置非激活态下的eDRX。
结合第四方面或其任意实现方式，在另一种可能的实现方式中，所述拒绝信息包括拒绝为所述终 端配置非激活态下的eDRX的原因；其中，所述原因包括以下至少一个：所述终端已加入多播会话、所述接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件；其中，所述预设条件为：所述多播会话处于激活态、所述多播会话对应的多播业务不支持eDRX、或所述多播会话处于激活态且所述多播会话对应的多播业务不支持eDRX。
第五方面，提供了一种通信方法，所述方法可以由接入网设备执行，也可以由接入网设备中的模块或单元执行，为了描述方便，下文统一称为接入网设备。
所述方法包括：接入网设备获知终端已加入多播会话；在所述接入网设备确定将所述终端转换为非激活态时，所述接入网设备不为所述终端配置非激活态下的eDRX。
基于上述方法，在终端已加入多播会话的情况下，接入网设备不为终端配置非激活态下的eDRX，从而实现终端的eDRX管理。此外，在终端已加入多播会话的情况下，不为终端配置非激活态下的eDRX，有助于保障多播会话对应的多播数据的传输。
结合第五方面，在一种可能的实现方式中，所述接入网设备不为所述终端配置eDRX，包括：当以下条件中的至少一个被满足时，所述接入网设备不为所述终端配置非激活态下的eDRX：所述接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件；其中，所述预设条件为：所述多播会话处于激活态、所述多播会话对应的多播业务不支持eDRX、或所述多播会话处于激活态且所述多播会话对应的多播业务不支持eDRX。
这里的“以下条件”指的是：所述接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件。
基于上述方法，在接入网设备获知终端已加入多播会话后，接入网设备可以进一步判断上述条件是否被满足，当上述条件被满足时，接入网设备不为终端配置非激活态下的eDRX。这样，可以使得接入网设备的判断结果更准确。
结合第五方面或其任意实现方式，在另一种可能的实现方式中，所述方法还包括：所述接入网设备接收来自会话管理功能的业务信息，所述业务信息用于指示所述多播会话对应的多播业务不支持eDRX。
基于上述方法，接入网设备可以根据终端已加入的多播会话对应的多播业务是否支持eDRX判断是否允许为终端配置非激活态下的eDRX。
结合第五方面或其任意实现方式，在另一种可能的实现方式中，所述业务信息包括所述多播业务的类型，所述类型为时延敏感类型。
第六方面，提供了一种通信方法，所述方法可以由终端执行，也可以由终端中的模块或单元执行，为了描述方便，下文统一称为终端。
所述方法包括：终端获知所述终端已加入多播会话，所述终端支持eDRX；所述终端向接入网设备发送第六信息，所述第六信息用于指示所述终端不支持eDRX。
基于上述方法，在终端已加入多播会话的情况下，支持eDRX的终端可以向接入网设备提供自己不支持eDRX的信息，使得接入网设备在进行将终端转化为非激活态的判断时，可以根据终端不支持eDRX不为终端配置非激活态下的eDRX，从而实现终端的eDRX管理。
此外，在终端已加入多播会话的情况下，不为终端配置非激活态下的eDRX，有助于保障多播会话对应的多播数据的传输。
结合第六方面，在一种可能的实现方式中，所述终端向接入网设备发送第六信息，包括：当以下条件中的至少一个被满足时，所述终端向所述接入网设备发送所述第六信息：接收到来自核心网设备的第一信息、所述接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件；其中，所述第一信息用于指示所述终端不适用非激活态下的eDRX，所述预设条件为：所述多播会话处于激活态、所述多播会话对应的多播业务不支持eDRX、或所述多播会话处于激活态且所述多播会话对应的多播业务不支持eDRX。
这里的“以下条件”指的是：接收到来自核心网设备的第一信息、所述接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件。
基于上述方法，在获知终端已加入多播会话后，终端可以进一步判断上述条件是否被满足，当上述条件被满足时，终端向终端提供第六信息。这样，可以使得终端的判断结果更准确。
结合第六方面或其任意实现方式，在另一种可能的实现方式中，所述核心网设备为接入和移动性管理功能网元或会话管理功能网元。
结合第六方面或其任意实现方式，在另一种可能的实现方式中，所述方法还包括：所述终端接收来自会话管理功能的业务信息，所述业务信息用于指示所述多播会话对应的多播业务不支持eDRX。
基于上述方法，终端可以根据终端已加入的多播会话对应的多播业务是否支持eDRX判断是否向接入网设备提供第六信息。
结合第六方面或其任意实现方式，在另一种可能的实现方式中，所述业务信息包括所述多播业务的类型，所述类型为时延敏感类型。
结合第六方面或其任意实现方式，在另一种可能的实现方式中，在所述终端向接入网设备发送第六信息之前，所述方法还包括：所述终端向所述接入网设备发送第七信息，所述第七信息用于指示所述终端支持eDRX。
即当终端当前判断的结果与已经上报给接入网设备的eDRX能力不一致时，终端可以更新自己在接入网设备的eDRX能力。
结合第六方面或其任意实现方式，在另一种可能的实现方式中，所述方法还包括：在所述终端离开所述终端已加入的全部多播会话后，所述终端向所述接入网设备发送第八信息，所述第八信息用于指示所述终端支持eDRX。
即当终端离开终端已加入的全部多播会话后，终端可以请求更新自己在接入网设备的eDRX能力。
第七方面，提供了一种通信方法，所述方法可以由会话管理功能网元执行，也可以由会话管理功能网元中的模块或单元执行，为了描述方便，下文统一称为会话管理功能网元。
所述方法包括：会话管理功能网元接收来自接入网设备的第二信息，所述第二信息用于请求为终端配置非激活态下的eDRX；所述会话管理功能网元根据所述第二信息，建立单播用户面功能网元和多播用户面功能网元之间的传输通道，所述传输通道用于传输所述终端的多播数据；所述会话管理功能网元向接入网设备发送第九信息，所述第九信息用于指示成功为所述终端配置非激活态下的eDRX。
这样，在终端加入多播会话的情况下，接入网设备可以将终端转化为非激活态以及为终端配置eDRX，从而实现终端的eDRX管理。
结合第七方面，在一种可能的实现方式中，所述方法还包括：所述会话管理功能网元向所述单播用户面功能网元或所述多播用户面功能网元发送eDRX缓存信息，所述eDRX缓存信息用于缓存所述多播数据。
基于上述方法，在终端加入多播会话的情况下，接入网设备可以将终端转化为非激活态以及为终端配置eDRX，并且由单播用户面功能网元或多播用户面功能网元对终端的多播数据进行缓存，从而避免终端错过多播数据，有助于保障多播业务的传输。
此外，由多播用户面功能网元缓存多播数据，缓存点比较高，有助于降低网络缓存的数据量。
第八方面，提供了一种通信方法，所述方法可以由多播用户面功能网元执行，也可以由多播用户面功能网元中的模块或单元执行，为了描述方便，下文统一称为多播用户面功能网元。
所述方法包括：多播用户面功能网元接收来自会话管理功能网元的eDRX缓存信息，所述eDRX缓存信息用于缓存终端的多播数据；所述多播用户面功能网元根据所述eDRX缓存信息，缓存所述终端的多播数据。
基于上述方法，在终端加入多播会话的情况下，接入网设备可以将终端转化为非激活态以及为终端配置eDRX，并且由多播用户面功能网元对终端的多播数据进行缓存，从而避免终端错过多播数据，有助于保障多播业务的传输。
此外，由多播用户面功能网元缓存多播数据，缓存点比较高，有助于降低网络缓存的数据量。
第九方面，提供了一种通信装置，该装置用于执行上述任意一方面或其实现方式提供的方法。具体地，该装置可以包括用于执行上述任意一方面或其实现方式提供的方法的单元和/或模块，如处理单元和/或通信单元。
在一种实现方式中，该装置为核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元。当该装置为核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元时，通信单元可以是收发器，或，输入/输出接口，或 者通信接口；处理单元可以是至少一个处理器。可选地，收发器为收发电路。可选地，输入/输出接口为输入/输出电路。
在另一种实现方式中，该装置为用于核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元中的芯片、芯片系统或电路。当该装置为用于核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元中的芯片、芯片系统或电路时，通信单元可以是该芯片、芯片系统或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；处理单元可以是至少一个处理器、处理电路或逻辑电路等。
第十方面，提供了一种通信装置，该装置包括：存储器，用于存储程序；至少一个处理器，用于执行存储器存储的计算机程序或指令，以执行上述任意一方面或其实现方式提供的方法。
在一种实现方式中，该装置为核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元。
在另一种实现方式中，该装置为用于核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元中的芯片、芯片系统或电路。
第十一方面，提供了一种通信装置，该装置包括：至少一个处理器和通信接口，该至少一个处理器用于通过该通信接口获取存储在存储器的计算机程序或指令，以执行上述任意一方面或其实现方式提供的方法。该通信接口可以由硬件或软件实现。
在一种实现方式中，该装置还包括该存储器。
第十二方面，提供了一种处理器，用于执行上述各方面提供的方法。
对于处理器所涉及的发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，那么可以理解为处理器输出和接收、输入等操作，也可以理解为由射频电路和天线所进行的发送和接收操作，本申请对此不做限定。
第十三方面，提供了一种计算机可读存储介质，该计算机可读介质存储用于设备执行的程序代码，该程序代码包括用于执行上述任意一方面或其实现方式提供的方法。
第十四方面，提供了一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述任意一方面或其实现方式提供的方法。
第十五方面，提供了一种芯片，芯片包括处理器与通信接口，处理器通过通信接口读取存储器上存储的指令，执行上述任意一方面或其实现方式提供的方法。该通信接口可以由硬件或软件实现。
可选地，作为一种实现方式，芯片还包括存储器，存储器中存储有计算机程序或指令，处理器用于执行存储器上存储的计算机程序或指令，当计算机程序或指令被执行时，处理器用于执行上述任意一方面或其实现方式提供的方法。
第十六方面，提供了一种通信系统，包括上文的核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元中的至少一个。
附图说明
图1是适用于本申请的实施例的一种网络架构的示意图。
图2是一种多播/广播业务的网络架构示意图。
图3是本申请提供的通信方法300的示意性流程图。
图4是本申请提供的通信方法400的示意性流程图。
图5是本申请提供的通信方法500的示意性流程图。
图6是本申请提供的通信方法600的示意性流程图。
图7是本申请的通信方法的一个示例。
图8是本申请的通信方法的另一个示例。
图9是本申请的通信方法的另一个示例。
图10是本申请的通信方法的另一个示例。
图11是本申请的通信方法的另一个示例。
图12是本申请的通信方法的另一个示例。
图13是传输多播数据的一个示意图。
图14是本申请的通信方法的另一个示例。
图15是传输多播数据的另一个示意图。
图16是本申请的实施例提供的一种装置的结构示意图。
图17是本申请的实施例提供的另一装置的结构示意图。
具体实施方式
为便于理解本申请实施例，在介绍本申请的实施例之前，先做出以下几点说明。
“用于指示”或“指示”可以包括直接指示和间接指示，或者说“用于指示”或“指示”可以显式地和/或隐式地指示。例如，当描述某一信息用于指示信息I时，可以包括该信息直接指示I或间接指示I，而并不代表该信息中一定携带有I。又例如，隐式指示可以基于用于传输的位置和/或资源；显式指示可以基于一个或多个参数，和/或一个或多个索引，和/或一个或多个它所表示的位模式。
第一、第二、第三、第四以及各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围。例如，区分不同的字段、不同的信息等。
“示例的”、“例如”、“示例性地”、“作为(另)一个示例”等词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
“包括”、“包含”、“具有”及它们的变形都意味着“包括但不限于”，除非是以其他方式另外特别强调。
“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a、b和c中的至少一项(个)，可以表示：a，或，b，或，c，或，a和b，或，a和c，或，b和c，或，a、b和c。其中a、b和c分别可以是单个，也可以是多个。
“当……时”、“在……的情况下”、“若”以及“如果”等描述均指在某种客观情况下设备会做出相应的处理，并非是限定时间，且也不要求设备在实现时一定要有判断的动作，也不意味着存在其它限定。
在本申请实施例中，涉及网元A向网元B发送消息、信息或数据，以及网元B接收来自网元A的消息、信息或数据的相关描述，旨在说明该消息、信息或数据是要发给哪个网元，而并不限定它们之间是直接发送还是经由其他网元间接发送。
在本申请实施例中，将围绕包括多个设备、组件、模块等的系统来呈现各个方面、实施例或特征。应当理解的是，各个系统可以包括网络架构的示意图中涉及的所有设备、组件、模块，也可以仅包括其中的部分，不予限制。
本申请提供的实施例可以应用于各种通信系统。例如，第五代(5th generation，5G)或新无线(new radio，NR)系统、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)系统等。本申请提供的实施例还还可以应用于卫星通信系统等非陆地通信网络(non-terrestrial network，NTN)通信系统。本申请提供的实施例还可以应用于设备到设备(device to device，D2D)通信、车到万物(vehicle-to-everything，V2X)通信、机器到机器(machine to machine，M2M)通信、机器类型通信(machine type communication，MTC)、以及物联网(internet of things，IoT)通信系统或者其他通信系统。本申请提供的实施例还可以应用于未来的通信系统，如第六代移动通信系统。
示例性地，图1示出了一种网络架构的示意图。
如图1所示，该网络架构以5G系统(the 5th generation system，5GS)为例。该网络架构中可包括三部分，分别是用户设备(user equipment，UE)、数据网络(data network，DN)和运营商网络。其中，运营商网络可包括以下网元中的一个或多个：(无线)接入网((radio)access network，(R)AN)设备、用户面功能(user plane function，UPF)网元、接入和移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、策略控制功能(policy control function，PCF)网元、统一数据管理(unified data management，UDM)网元和 应用功能(application function，AF)网元。上述运营商网络中，除(R)AN之外的部分可以称为核心网。
在本申请中，将(无线)接入网设备、UPF网元、AMF网元、SMF网元、PCF网元、UDM网元、AF网元分别简称为(R)AN、UPF、AMF、SMF、PCF、UDM、AF。
下面对图1中涉及的各设备进行简单描述。
1、UE
UE也可以称为终端、用户、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端设备、无线通信设备、用户代理或用户装置等，为了描述方便，下文统一称为终端。
终端是一种可以接入无线通信网络的设备。终端与(R)AN之间可以采用空口技术(如NR或LTE)进行通信。终端与终端之间也可以采用空口技术(如NR或LTE)进行通信。具体地，终端可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、卫星通信中的终端、接入回传一化链路(integrated access and backhaul，IAB)系统中的终端、WiFi通信系统中的终端、工业控制(industrial control)中的终端、无人驾驶(self driving)中的终端、远程医疗(remote medical)中的终端、智能电网(smart grid)中的终端、运输安全(transportation safety)中的终端、智慧城市(smart city)中的终端、智慧家庭(smart home)中的终端等。
本申请的实施例对终端所采用的具体技术和具体设备形态不做限定。
2、(R)AN
(R)AN可以是用于与终端进行通信的设备，也可以是一种将终端接入无线通信网络的设备。
(R)AN可以为无线接入网中的节点。例如，基站(base station)、演进型基站(evolved NodeB，eNodeB)、发送接收点(transmission reception point，TRP)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、Wi-Fi接入点(access point，AP)、移动交换中心、5G移动通信系统中的下一代基站(next generation NodeB，gNB)、开放无线接入网(open radio access network，O-RAN或open RAN)中的接入网设备、第六代(6th generation，6G)移动通信系统中的下一代基站、或未来移动通信系统中的基站等。(R)AN还可以是完成基站部分功能的模块或单元，例如，可以是集中式单元(central unit，CU)、分布式单元(distributed unit，DU)、射频拉远单元(remote radio unit，RRU)或基带单元(baseband unit，BBU)等。
(R)AN还可以是D2D通信系统、V2X通信系统、M2M通信系统以及IoT通信系统中承担基站功能的设备等。(R)AN还可以是NTN中的网络设备，即(R)AN可以部署于高空平台或者卫星。(R)AN可以是宏基站，也可以是微基站或室内站，还可以是中继节点或施主节点等。
本申请的实施例对(R)AN所采用的具体技术、设备形态以及名称不做限定。为了描述方便，下文将(R)AN统一称为接入网设备。
3、UPF
UPF主要负责终端中的用户数据的转发和路由。例如，UPF可以从DN接收用户面数据，并通过接入网设备将用户面数据发送给终端。UPF还可以通过接入网设备从终端接收用户面数据，并转发到DN。UPF网元中为终端提供服务的传输资源和调度功能由SMF管理控制。
4、DN
DN主要用于为终端提供数据服务的运营商网络。例如，因特网(Internet)、第三方的业务网络、或IP多媒体服务业务(IP multi-media service，IMS)网络等。DN中可以由多个应用服务器(application server，AS)。
5、AMF
AMF主要负责终端的接入控制和移动性管理，如用户位置更新、用户注册网络、或用户切换等。
6、SMF
SMF主要负责用户面网元选择、用户面网元重定向、因特网协议(internet protocol，IP)地址分配、会话的建立、修改和释放以及QoS控制等。
7、PCF
PCF主要负责策略控制的决策、提供控制平面功能的策略规则、以及基于流量的计费控制功能等。
8、UDM
UDM主要负责终端的签约数据管理，包括终端标识的存储和管理、终端的接入授权等。
9、AF
AF主要支持与3GPP核心网交互来提供服务，例如影响数据路由决策、策略控制功能或者向网络提供第三方的服务。AF可以是运营商网络自身部署的AF，也可以是第三方AF。
图2是一种多播/广播业务的网络架构示意图。
其中，图2所示的网络架构和网元的功能是在图1所示的网络架构和网元的功能的基础上增强而定义的。为了简洁，下文仅对图2中各个网元特定于多播/广播业务的功能进行描述。
1、PCF
PCF主要负责：多播/广播业务(multicast-broadcast service，MBS)会话的QoS处理、向多播/广播SMF(multicast-broadcast SMF，MB-SMF)提供策略信息、以及与用户数据存储库(user data repository，UDR)交互获取QoS信息等。PCF是可选网元，例如，可以在使用动态策略计费控制(policy charging control，PCC)时才具备该功能实体。
2、MB-SMF
MB-SMF是一个具备支持多播/广播特性的实体。MB-SMF负责：MBS会话的管理，例如QoS控制等；配置多播/广播(multicast-broadcast UPF，MB-UPF)；与接入网设备交互以控制广播流(flow)传输；与单播SMF交互以关联协议数据单元(protocol data unit，PDU)会话；与接入网设备交互以控制多播流的传输等。MB-SMF还可以同时具备单播SMF的功能。
3、SMF
SMF主要负责：发现MB-SMF、终端加入MBS的认证、与MB-SMF交互以管理多播会话上下文、与接入网设备交互以建立多播传输资源等。
4、MB-UPF
MB-UPF是MBS的数据面的网关，主要负责：与MB-SMF交互以获取数据转发规则、向接入网设备通过共享传递方法(shared delivery method)传输多播数据；向UPF通过单独传递方法(individual delivery method)传输多播数据等。
5、UPF
UPF主要负责：通过单独传递方法(individual delivery method)传输多播数据，例如，从MB-UPF接收多播数据、并通过PDU会话向终端传输多播数据等。
6、AMF
AMF主要负责：信令路由(例如，(R)AN与MB-SMF之间信令路由)、以及为MBS选择(R)AN等。
7、(R)AN
(R)AN主要负责：处理MBS QoS流、通过点到多点(point to multipoint，PTM)、点到点(point to point，PTP)向终端发送数据、配置接入层(access stratum，AS)接收广播流、在PTM和PTP之间切换、支持多播会话的Xn和N2切换、处理会话信令、以及建立空口广播和多播资源等。
8、UE
UE主要功能为：通过PTM/PTP接收多播数据、通过PTM接收多播数据/广播数据、处理QoS、发起会话加入(session join)和会话离开(session leave)、以及MBS的终端侧的资源管理等。
9、多播/广播服务功能(multicast-broadcast service function，MBSF)网元
MBSF网元，下文简称为MBSF，主要支持以下功能：业务层功能、与LTE MBS的互通、与AF和MB-SMF交互以支持MBS会话的操作、确定传输参数和MBS会话的类型、选择MB-SMF控制MBSTF、以及确定发送者的IP多播地址等。MBSF为可选网元。
10、多播/广播服务传输功能(multicast-broadcast service transmission function，MBSTF)网元
MBSTF网元，下文简称为MBSTF，主要支持以下功能：MBS数据的锚点；作为IP多播的源；支持例如帧、多流、前向纠错(forward error correction，FEC)等通用传输功能；将输入的文件作为目标(object)或目标流(object flow)以多播或广播的方式发送等。MBSTF为可选网元。
11、AF
AF主要支持以下功能：向核心网(core network)提供业务信息并请求多播或广播服务、以及指示(instruct)与MBS会话操作等。
12、UDM
UDM主要支持多播会话的订阅/签约管理等。
13、网络功能库功能(network repository function，NRF)
NRF主要包括以下功能：支持对服务MBS会话的MB-SMF的管理，具体包括保存MB-SMF服务的MBS会话ID等。
14、网络开放功能(network exposure function，NEF)
NEF主要包括以下功能：选择MB-SMF；与AF以及MB-SMF交互以实现MBS会话操作、确定传输参数等；向AF提供MBS流程的接口如服务配置、MBS会话配置和QoS管理等接口等。
在图1和图2所示的网络架构中，各网元之间可以接口通信。各网元之间的接口可以是点对点接口，也可以是服务化接口，本申请不予限制。
应理解，上述所示的网络架构仅是示例性说明，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
还应理解，图1和图2中所示的各个功能或者网元，可以理解为用于实现不同功能的网元，例如可以按需组合成网络切片。这些网元可以各自独立的设备，也可以集成于同一设备中实现不同的功能，或者可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能，本申请对于上述网元的具体形态不作限定。
还应理解，上述命名仅为便于区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除在6G网络以及未来其它的网络中采用其他命名的可能。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称等。
为便于理解本申请实施例，首先对本申请中涉及到的术语做简单说明。
1、多播会话
用于传输多播业务的会话可以称为多播会话，多播会话的特点在于一组终端接收同一数据。多播会话也可以称为多播MBS会话或组播会话，在本申请中统一称为多播会话。
终端可以通过加入多播会话来接收多播业务的数据。多播业务的数据可以简称多播数据。
在本申请中，“加入多播会话”也可以替换为“加入多播群组”，不予限制。
2、DRX和eDRX
为了降低终端功耗，通信系统引入了DRX技术。DRX技术可以使终端周期性进入睡眠状态来达到降低终端功耗的目的。一个DRX周期包括睡眠期和激活期。在激活期内，终端监听并接收下行信道；在睡眠期内，终端可以不打开接收机接收下行信道的数据，从而降低终端功耗。DRX周期可以分为短DRX周期和长DRX周期。
进一步地，针对能力受限的终端，可以将DRX延长为eDRX。eDRX可以将终端的DRX周期从最大10.24秒(s)变为1万多秒，使得终端打开接收机的时间更少，进而进一步降低终端功耗。eDRX可以包括长eDRX(long eDRX)，长eDRX的周期长度可以大于10.24秒。本申请中的eDRX也可以替换为eDRX周期(cycle)、长eDRX、长eDRX周期、或周期长度大于10.24秒的eDRX。
上面对本申请中涉及到的术语做了简单说明，下文实施例中不再赘述。
下面对本申请实施例提供的通信方法进行详细描述。
图3是本申请提供的通信方法300的示意性流程图。
方法300可以由接入网设备和核心网设备执行，也可以由接入网设备和核心网设备中的模块或单元执行，本申请不予限制，为了描述方便，下文统一称为接入网设备和核心网设备。方法300包括以下内容的至少部分内容。
步骤301，核心网设备获知终端已加入多播会话。
可选地，核心网设备为SMF或AMF。
当核心网设备为SMF时，SMF可以在终端加入多播会话的过程中获知终端已加入多播会话。
具体地，SMF可以根据接收到终端发送的非接入层(Non-Access Stratum，NAS)消息中携带多播 会话的标识，和/或，加入请求(join request)信息判断。
又或者，SMF在接收到上述非接入层消息后，进一步从本地或UDM处获取终端的签约信息(例如终端是否被授权加入某些多播会话)，和/或从本地或MB-SMF处获取多播会话的上下文信息，上下文信息中包含多播会话是否对于所有终端均开放。例如，如果终端的签约信息中，包括终端被授权加入多播会话的信息(例如，签约信息包含多播会话的标识信息，其中，多播会话的标识例如可以为临时多播组标识(temporary multicast group identifier，TMGI))，那么SMF获知终端已加入多播会话。如果终端的签约信息中，不包括终端被授权加入多播会话的信息，但是多播会话的上下文信息总包含多播会话对于所有终端均开放，那么SMF获知终端已加入多播会话。
当核心网设备为AMF时，步骤301包括：AMF接收来自SMF的第四信息，相应地，SMF向AMF发送第四信息，其中，第四信息用于指示终端已加入多播会话；AMF根据第四信息获知终端已加入多播会话。其中，对于SMF，SMF可以在终端加入多播会话的过程中获知终端已加入多播会话。
可选地，第四信息包括终端已加入的多播会话的标识。其中，多播会话的标识例如可以为临时多播组标识(temporary multicast group identifier，TMGI)。可以理解为，第四信息通过隐示的方式指示终端已加入该多播会话的标识对应的多播会话。
可选地，第四信息包括终端已加入的多播会话的标识、以及第一指示信息。其中，多播会话的标识例如可以为TMGI，第一指示信息用于指示终端已加入多播会话。可以理解为，第四信息通过显示的方式指示终端已加入多播会话、以及该多播会话的标识。
可选地，步骤301具体包括：SMF在多播会话为激活态时向AMF发送第四信息，相应地，AMF接收来自SMF的第四信息。
步骤302，核心网设备发送第一信息。
其中，第一信息用于通知拒绝为终端配置非激活态下的eDRX，或者，第一信息用于指示终端不适用非激活态下的eDRX。
其中，“终端不适用于非激活态下的eDRX”也可以采用以下描述：“不允许为终端配置非激活态下的eDRX”、“不为终端配置非激活态下的eDRX”、“不将终端转换为eDRX的非激活态”、“终端不适用eDRX”、“不将终端转化为非激活态下的eDRX”、“终端不进入非激活态下的eDRX”或“不将终端发送至非激活态下的eDRX”等。
其中，“拒绝为终端配置非激活态下的eDRX”也可以采用以下描述：“拒绝将终端转换为eDRX的非激活态”、“拒绝将终端转化为非激活态下的eDRX”、“拒绝终端进入非激活态下的eDRX”或“拒绝将终端发送至非激活态下的eDRX”等。
可选地，当第一信息用于通知拒绝为终端配置非激活态下的eDRX时，第一信息包括拒绝信息，拒绝信息用于指示拒绝为终端配置非激活态下的eDRX。其中，拒绝信息可以包括拒绝为终端配置非激活态下的eDRX的原因，该原因随核心网设备在发送第一信息时考虑的信息不同而不同，将在下文进行描述。
可选地，当核心网设备为AMF时，第一信息可以是RRC非激活态辅助信息(RRC inactive assistance information，RIAI)，第一信息不包括UE特定的扩展的空闲态DRX值(UE specific extended idle mode DRX values)。
可选地，当核心网设备为SMF时，第一信息可以包含在PDU会话资源建立请求传输(PDU Session Resource Setup Request Transfer)消息，或者包含在PDU会话资源修改请求传输(PDU Session Resource Modify Request Transfer)消息。
可选地，当第一信息用于通知拒绝为终端配置非激活态下的eDRX时，步骤302包括：核心网设备向接入网设备发送第一信息。并且在步骤302之前，方法300还包括步骤303，步骤303如下。
步骤303，当接入网设备确定将终端转换为非激活态时，接入网设备向核心网设备发送第二信息。
相应地，核心网设备接收来自接入网设备的第二信息。
其中，第二信息用于请求为终端配置非激活态下的eDRX。例如，第二信息用于请求将终端转换为非激活态且第二信息携带eDRX的信息，其中，eDRX的信息包括终端进入eDRX的周期等。“请求”也可以替换为“指示”或“配置”等。
步骤303也可以描述为：接入网设备确定将终端转换为非激活态，接入网设备向核心网设备发送 第二信息。接入网设备确定将终端转换为非激活态可以在接入网设备发送第二信息之前执行，也可以在接入网设备发送第二信息之后执行，不予限制。
可选地，在步骤303中，接入网设备可以根据RRC非激活态辅助信息(RRC inactive assistance information，RIAI)、以及其他可能的信息(例如接入网设备的实现、或接入网设备当前的负载等)，决定将终端转换为非激活态。更详细的描述可以参考现有技术，在此不再赘述。
需要说明的是，若核心网设备为SMF，接入网设备与SMF之间的交互通过AMF。例如，SMF通过AMF向接入网设备发送第一信息。又例如，接入网设备可以通过AMF向SMF发送第二信息。在此情况下，AMF接收到的信息和AMF发送的信息虽然都被称为第一信息或第二信息，但AMF接收到的信息和AMF发送的信息的实现方式可以相同，也可以不同(例如通过不同的消息和/或信元)，不予限制。例如，SMF可以通过N11消息向AMF发送第一信息；AMF接收到来自SMF的N11消息后，根据其中的第一信息，向接入网设备发送N2消息，即通过N2消息或其中的信元向接入网设备传递第一信息。又例如，接入网设备可以通过N2消息向AMF发送第二信息；AMF接收到来自接入网设备的N2消息后，根据其中的第二信息，向SMF发送PDU会话更新会话管理上下文请求消息(如Nsmf_PDUsession_UpdateSMContext request)，即通过PDU会话更新会话管理上下文请求消息或其中的信元向SMF传递第二信息。
还需要说明的是，当核心网设备为SMF时，在接收到来自接入网设备的第二信息后，AMF可能会向一个或多个SMF发送第二信息。对于AMF向多个SMF发送第二信息的情况，例如，AMF可以向用于管理与终端的多播会话相关联的单播会话的第一SMF以及用于管理与终端的多播会话不关联的单播会话的第二SMF发送第二信息，在此情况下，核心网设备可以为第一SMF，并且在AMF接收到来自第一SMF的第一信息后，AMF向第二SMF发送第五信息，相应地，第二SMF接收来自AMF的第五信息，其中第五信息用于触发第二SMF停止为终端配置非激活态下的eDRX；第二SMF停止为终端配置非激活态下的eDRX。
其中，第二SMF停止为终端配置非激活态下的eDRX可以包括：第二SMF去使能缓存数据。
一种可能的实现方式，第二SMF向UPF发送针对多播的配置消息，针对多播的配置消息中不包含eDRX的缓存指示，或者包含清除eDRX缓存的指示信息。这里的UPF可以是第二SMF管理的UPF。
另一种可能的实现方式中，第二SMF向UPF发送针对多播的配置消息，针对多播的配置消息中将缓存动作规则(Buffer Action Rule,BAR)置为0，或者包含清除BAR的指示信息。
再一种可能的实现方式中，第二SMF向UPF发送针对多播的配置消息，针对多播的配置消息中，针对多播的创建(或者更新)转发动作规则(Create/Update Forwarding Action Rule,Create/Update FAR)对应的BAR标识置为特殊值(例如0)，用于指示不需要进行缓存，或者，针对多播的Create/Update FAR不包括对应的BAR标识。
又一种可能的实现方式中，第二SMF向UPF发送针对多播的配置消息，针对多播的配置消息中，包含针对多播的删除(或者释放)转发动作规则(Delete/Release Forwarding Action Rule,Delete/Release FAR)，且Delete/Release FAR包含的BAR标识置为特殊值，用于指示不需要进行缓存，或者，针对多播的配置消息中，包含针对多播的删除(或者释放)转发动作规则(Delete/Release Forwarding Action Rule,Delete/Release FAR)，且Delete/Release FAR包括对应的BAR标识。
其中，“停止为终端配置非激活态下的eDRX”也可以采用以下描述：“恢复终端的原有状态”、“取消为终端配置非激活态下的eDRX”或“撤回为终端配置非激活态下的eDRX”等。
可选地，当第一信息用于指示终端不适用非激活态下的eDRX时，步骤302包括：核心网设备向接入网设备或终端发送第一信息。可选地，第一信息可以携带在RIAI中。
需要说明的是，当核心网设备为SMF时，SMF通过AMF向接入网设备发送第一信息。在此情况下，AMF接收到的信息和AMF发送的信息虽然都被称为第一信息，但AMF接收到的信息和AMF发送的信息的实现方式可以相同，也可以不同(例如通过不同的消息和/或信元)，不予限制。
一种可能的实现方式，步骤302包括：若终端已加入多播会话，则核心网设备发送第一信息。可以理解为，在核心网设备获知终端已加入多播会话后，核心网设备便可发送第一信息，以通知拒绝为终端配置非激活态下的eDRX或者指示终端不适用非激活态下的eDRX。在该实现方式中，若第一信息包括拒绝原因，该原因为终端已加入多播会话。
另一种可能的实现方式，步骤302包括：当以下条件中的至少一个被满足时，核心网设备发送第一信息：为终端提供服务的接入网设备不支持eDRX、终端不支持eDRX、或多播会话满足预设条件，其中，预设条件为：多播会话处于激活态、多播会话对应的多播业务不支持eDRX、或多播会话处于激活态且多播会话对应的多播业务不支持eDRX。可以理解为，在核心网设备获知终端已加入多播会话后，核心网设备进一步判断上述条件是否被满足，当上述条件被满足时，核心网设备发送第一信息，以通知拒绝为终端配置非激活态下的eDRX或者指示终端不适用非激活态下的eDRX。在该实现方式中，若第一信息包括拒绝原因，该原因包括以下原因中的至少一个：终端已加入多播会话、为终端提供服务的接入网设备不支持eDRX、终端不支持eDRX、或多播会话满足预设条件。
例如，假设预设条件为多播会话处于激活态，若终端已加入多播会话且该多播会话处于激活态，和/或，接入网设设备不支持eDRX，和/或，终端不支持eDRX，则核心网设备发送第一信息；若终端已加入多播会话且该多播会话处于去激活态、接入网设设备支持eDRX、且终端支持eDRX，则核心网设备不发送第一信息。
又例如，假设预设条件为多播会话对应的多播业务不支持eDRX，若终端已加入多播会话且该多播会话对应的多播业务不支持eDRX，和/或，接入网设设备不支持eDRX，和/或，终端不支持eDRX，则核心网设备发送第一信息；若终端已加入多播会话且该多播会话对应的多播业务支持eDRX、接入网设设备支持eDRX、且终端支持eDRX，则核心网设备不发送第一信息。
又例如，假设预设条件为多播会话处于激活态且多播会话对应的多播业务不支持eDRX，若终端已加入多播会话且该多播会话满足预设条件，和/或，接入网设设备不支持eDRX，和/或，终端不支持eDRX，则核心网设备发送第一信息；若终端已加入多播会话且该多播会话不满足预设条件、接入网设设备支持eDRX、且终端支持eDRX时，则核心网设备不发送第一信息。
可选地，方法300还包括步骤304：核心网设备接收来自接入网设备的第三信息，相应地，接入网设备向核心网设备发送第三信息，其中，第三信息用于指示接入网设备是否支持eDRX。例如，当接入网设备在上电时，可以向核心网设备上报第三信息。
可选地，第三信息可以承载于下一代(接口)配置请求(NG set request)消息。
需要指出的是，当核心网设备为SMF时，接入网设备可以通过AMF向SMF发送第三信息。在此情况下，AMF接收到的第三信息和AMF向SMF发送的第三信息的实现方式可以相同，也可以不同(例如通过不同的消息和/或信元)，不予限制。
可选地，当核心网设备为AMF时，方法300还包括：AMF接收来自SMF的业务信息，相应地，SMF向AMF发送业务信息，其中，业务信息用于指示多播会话对应的多播业务是否支持eDRX。
作为一个示例，业务信息可以包括多播业务的类型。当多播业务类型为时延敏感类型时，可以认为该多播业务支持eDRX。当多播业务类型为非时延敏感类型时，可以认为该多播业务不支持eDRX。
作为另一个示例，业务信息可以包括第二指示信息，第二指示信息用于指示多播业务是否支持eDRX。第二指示信息可以为一个或若干个比特，即业务信息可以通过显示的方式指示多播业务是否支持eDRX。
步骤305，接入网设备根据第一信息，不为终端配置非激活态下的eDRX。
其中，“不为终端配置非激活态下的eDRX”也可以理解为不执行为终端配置eDRX的操作，其也可以采用以下描述：“不将终端转换为采用eDRX的非激活态”或“不将终端转换为eDRX状态”。
可选地，方法300还包括：接入网设备将终端转换为非激活态、将终端保持在连接态、将终端转换为空闲态、将终端转换为非激活态并为终端配置DRX、将终端转换为非激活态并仅为终端配置DRX且不包含eDRX信息、将终端转换为非激活态并在终端的配置信息中仅包含RAN-寻呼周期(ran-PagingCycle)信息、或将终端转换为非激活态并在终端的配置信息中仅包含RAN-寻呼周期(ran-PagingCycle)信息且不包含RAN-扩展的寻呼周期(ran-ExtendedPagingCycle)。进一步可选地，DRX周期不长于2.56s。
其中，“转换”也可以描述为“释放”、“切换”、“配置”、或“设置”等。
可选地，当第一信息用于指示终端不适用非激活态的eDRX时，步骤305包括：当接入网设备确定将终端转换为非激活态时，接入网设备根据第一信息，不为终端配置非激活态下的eDRX。
这样，通过方法300，在终端已经加入多播会话的情况下，核心网设备可以向接入网设备通知拒绝 为终端配置非激活态下的eDRX或者向接入网设备指示终端不适用非激活态下的eDRX，使得接入网设备在将终端转换为非激活态时可以根据核心网设备的通知或指示不为终端配置非激活态下的eDRX，从而保障该多播会话对应的多播数据的传输。
图4是本申请提供的通信方法400的示意性流程图。
方法400可以由接入网设备和核心网设备执行，也可以由接入网设备和核心网设备中的模块或单元执行，本申请不予限制，为了描述方便，下文统一称为接入网设备和核心网设备。方法400包括以下内容的至少部分内容。
步骤401，接入网设备获知终端已加入多播会话。
一种可能的实现方式，接入网设备可以在终端加入多播会话的过程中获知终端已加入多播会话。
具体地，接入网设备可以根据从为终端分配的地址处，接收到SMF发送的N2信息，并且信息中包含多播会话的标识来获知终端已加入多播会话。
又或者，接入网设备接收到来自AMF发送的PDU会话资源建立请求(PDU SESSION RESOURCE SETUP REQUEST)，请求消息中包含PDU会话资源修改建立请求传输(PDU Session Resource SetupRequest Transfer)，请求传输消息中包含MBS会话建立请求列表(MBS Session Setup Request List)，并且列表中包含多播会话ID的信息(例如MBS Session ID，其可以为TMGI)。
再或者，接入网设备接收到来自AMF发送的PDU会话资源修改请求(PDU SESSION RESOURCE MODIFY REQUEST)，请求消息中包含PDU会话资源修改请求传输(PDU Session Resource Modify Request Transfer)请求传输消息中包含MBS会话建立请求或修改列表(MBS Session Setup or Modify Request List)，并且列表中包含多播会话ID的信息(例如MBS Session ID，其可以为TMGI)。
步骤402，当接入网设备确定将终端转换为非激活态时，接入网设备不为终端配置非激活态下的eDRX。
其中，“不为终端配置非激活态下的eDRX”也可以理解为不执行为终端配置eDRX的操作，其也可以采用以下描述：“不将终端转换为采用eDRX的非激活态”或“不将终端转换为eDRX状态”。
可选地，方法400还包括：接入网设备将终端转换为非激活态、将终端保持在连接态、将终端转换为空闲态、将终端转换为非激活态并为终端配置DRX、将终端转换为非激活态并仅为终端配置DRX且不包含eDRX信息、将终端转换为非激活态并在终端的配置信息中仅包含RAN-寻呼周期(ran-PagingCycle)信息、或将终端转换为非激活态并在终端的配置信息中仅包含RAN-寻呼周期(ran-PagingCycle)信息且不包含RAN-扩展的寻呼周期(ran-ExtendedPagingCycle)。进一步可选地，DRX周期不长于2.56s。
其中，“转换”也可以描述为“释放”、“切换”、“配置”、或“设置”等。
一种可能的实现方式，步骤402包括：若终端已加入多播会话，则接入网设备不为终端配置非激活态下的eDRX。可以理解为，在满足将终端转换为非激活态的条件时，接入网设备进一步考虑终端是否已加入多播会话，并在终端已加入多播会话的情况下，不为终端配置eDRX。或者也可以理解为，接入网设备根据终端已加入多播会话，判断不满足将终端转换为非激活态同时为终端配置eDRX的条件。
另一种可能的实现方式，步骤402包括：当以下条件中的至少一个被满足时，接入网设备不为终端配置非激活态下的eDRX：接入网设备不支持eDRX、终端不支持eDRX、或多播会话满足预设条件，其中，预设条件为：多播会话处于激活态、多播会话对应的多播业务不支持eDRX、或多播会话处于激活态且多播会话对应的多播业务不支持eDRX。可以理解为，在接入网设备在获知终端已加入多播会话的情况下，当决定接入网将终端转换为非激活态时，判断上述条件是否被满足，当上述条件被满足时，接入网设备不为终端配置非激活态下的eDRX。
例如，假设预设条件为多播会话处于激活态，若终端已加入多播会话且该多播会话处于激活态，和/或，接入网设设备不支持eDRX，和/或，终端不支持eDRX，则接入网设备不为终端配置非激活态下的eDRX；若终端已加入多播会话且该多播会话处于去激活态、接入网设设备支持eDRX、且终端支持eDRX，则接入网设备可以为终端配置非激活态下的eDRX。
又例如，假设预设条件为多播会话对应的多播业务不支持eDRX，若终端已加入多播会话且该多播会话对应的多播业务不支持eDRX，和/或，接入网设设备不支持eDRX，和/或，终端不支持eDRX， 则接入网设备不为终端配置非激活态下的eDRX；若终端已加入多播会话且该多播会话对应的多播业务支持eDRX、接入网设设备支持eDRX、且终端支持eDRX，则接入网设备可以为终端配置非激活态下的eDRX。
又例如，假设预设条件为多播会话处于激活态且多播会话对应的多播业务不支持eDRX，若终端已加入多播会话且该多播会话满足预设条件，和/或，接入网设设备不支持eDRX，和/或，终端不支持eDRX，则接入网设备不为终端配置非激活态下的eDRX；若终端已加入多播会话且该多播会话不满足预设条件、接入网设设备支持eDRX、且终端支持eDRX时，则接入网设备可以为终端配置非激活态下的eDRX。
可选地，方法400还包括步骤403：接入网设备接收来自SMF的业务信息，相应地，SMF向接入网设备发送业务信息，其中，业务信息用于指示多播会话对应的多播业务是否支持eDRX。
作为一个示例，业务信息可以包括多播业务的类型。当多播业务类型为时延敏感类型时，可以认为该多播业务支持eDRX。当多播业务类型为非时延敏感类型时，可以认为该多播业务不支持eDRX。
作为另一个示例，业务信息可以包括第二指示信息，第二指示信息用于指示多播业务是否支持eDRX。第二指示信息可以为一个或若干个比特，即业务信息可以通过显示的方式指示多播业务是否支持eDRX。
这样，通过方法400，在终端已经加入多播会话的情况下，接入网设备可以确定不为终端配置非激活态下的eDRX，从而保障该多播会话对应的多播数据的传输。
图5是本申请提供的通信方法500的示意性流程图。
方法500可以由终端和接入网设备执行，也可以由终端和接入网设备中的模块或单元执行，本申请不予限制，为了描述方便，下文统一称为终端和接入网设备。方法500包括以下内容的至少部分内容。
步骤501，终端获知终端已加入多播会话。
其中，终端支持eDRX。
一种可能的实现方式，终端可以在终端加入多播会话的过程中获知终端已加入多播会话。
具体地，终端可以根据从AMF发送的NAS消息，并且NAS消息中包含多播会话的标识来获知终端已加入多播会话。
又或者，终端接收到来自AMF发送的PDU会话建立接受(PDU SESSION ESTABLISHMENT ACCEPT)消息，消息中包含MBS Session ID(例如TMGI)。一种可能的实现方式中，MBS Session ID包含在接收的MBS信息(Received MBS information)中，接收的MBS信息包含在接收的MBS容器(Received MBS container)中，接收的MBS容器包含在PDU会话建立接受消息中。此时，终端可以获知终端已加入多播会话。
再或者，接入网设备接收到来自AMF发送的PDU会话修改命令(PDU SESSION MODIFICATION COMMAND)消息，消息中包含MBS Session ID(例如TMGI)。一种可能的实现方式中，MBS Session ID包含在接收的MBS信息(Received MBS information)中，接收的MBS信息包含在接收的MBS容器(Received MBS container)中，接收的MBS容器包含在PDU会话修改命令消息中。此时，终端可以获知终端已加入多播会话。
步骤502，终端向接入网设备发送第六信息。
相应地，接入网设备接收来自终端的第六信息。
其中，第六信息用于指示终端不支持eDRX。
这样，在终端加入多播会话的情况下，接入网设备在进行将终端转化为非激活态的判断时，可以根据第六信息不为终端配置非激活态下的eDRX，从而保障该多播会话对应的多播数据的传输。
一种可能的实现方式，步骤502包括：终端通过AMF向接入网设备发送第六信息。例如，终端向AMF发送携带第六信息的注册请求消息，第六信息可以为终端的eDRX能力信息；在接收到终端的注册请求消息后，AMF通过终端上下文更新消息向接入网设备发送第六信息。可选地，第六信息可以被携带在RIAI中。
需要指出的是，当终端通过AMF向接入网设备发送第六信息时，AMF接收到的第六信息和AMF发送的第六信息的实现方式可以相同，也可以不同(例如通过不同的消息和/或信元)，不予限制。
一种可能的实现方式，步骤502包括：若终端已加入多播会话，则终端发送第六信息。可以理解为，在终端获知终端已加入多播会话后，终端便可向接入网设备发送第六信息，以向接入网设备指示终端不支持eDRX。
另一种可能的实现方式，步骤502包括：当以下条件中的至少一个被满足时，终端向接入网设备发送第六信息：接收到来自核心网设备的第一信息、接入网设备不支持eDRX、终端不支持eDRX、或多播会话满足预设条件，其中，第一信息用于指示终端不适用eDRX，预设条件为：多播会话处于激活态、多播会话对应的多播业务不支持eDRX、或多播会话处于激活态且多播会话对应的多播业务不支持eDRX。可以理解为，在终端获知终端已加入多播会话后，终端进一步判断上述条件是否被满足，当上述条件被满足时，向接入网设备发送第六信息，以向接入网设备指示终端不支持eDRX。
例如，假设预设条件为多播会话处于激活态，若终端已加入多播会话且该多播会话处于激活态，和/或，接收到来自核心网设备的第一信息，和/或，接入网设设备不支持eDRX，和/或，终端不支持eDRX，则终端向接入网设备发送第六信息；若终端已加入多播会话且该多播会话处于去激活态、未接收到来自核心网设备的第一信息、接入网设设备支持eDRX、且终端支持eDRX，则终端可以不向接入网设备发送第六信息。
又例如，假设预设条件为多播会话对应的多播业务不支持eDRX，若终端已加入多播会话且该多播会话对应的多播业务不支持eDRX，和/或，接收到来自核心网设备的第一信息，和/或，接入网设设备不支持eDRX，和/或，终端不支持eDRX，则终端向接入网设备发送第六信息；若终端已加入多播会话且该多播会话对应的多播业务支持eDRX、未接收到来自核心网设备的第一信息、接入网设设备支持eDRX、且终端支持eDRX，则终端可以不向接入网设备发送第六信息。
又例如，假设预设条件为多播会话处于激活态且多播会话对应的多播业务不支持eDRX，若终端已加入多播会话且该多播会话满足预设条件，和/或，接收到来自核心网设备的第一信息，和/或，接入网设设备不支持eDRX，和/或，终端不支持eDRX，则终端向接入网设备发送第六信息；若终端已加入多播会话且该多播会话不满足预设条件、未接收到来自核心网设备的第一信息、接入网设设备支持eDRX、且终端支持eDRX时，则终端可以不向接入网设备发送第六信息。
需要说明的还是，第一信息的相关描述可以参考方法300，在此不再赘述。
可选地，方法500还包括步骤503：终端接收来自SMF的业务信息，相应地，SMF向终端发送业务信息，其中，业务信息用于指示多播会话对应的多播业务是否支持eDRX。业务信息可以包含在PDU会话修改命令、PDU会话修改接受、PDU会话建立响应等消息中。
作为一个示例，业务信息可以包括多播业务的类型。当多播业务类型为时延敏感类型时，可以认为该多播业务支持eDRX。当多播业务类型为非时延敏感类型时，可以认为该多播业务不支持eDRX。
作为另一个示例，业务信息可以包括第二指示信息，第二指示信息用于指示多播业务是否支持eDRX。第二指示信息可以为一个或若干个比特，即业务信息可以通过显示的方式指示多播业务是否支持eDRX。
可选地，在上述实施例的另一种场景下，在步骤501之前，方法500还包括：终端向接入网设备发送第七信息，相应地，基站接收来自终端的第七信息，其中第七信息用于指示终端支持eDRX。终端向接入网设备发送第七信息的方式可以参考终端向接入网设备发送第六信息的方式，在此不再赘述。
可选地，在上述实施例的另一种场景下，在步骤502之后，方法500还包括：在终端离开终端已加入的全部多播会话后，终端向接入网设备发送第八信息，相应地，基站接收来自终端的第八信息，其中第八信息用于指示终端支持eDRX。终端向接入网设备发送第八信息的方式可以参考终端向接入网设备发送第六信息的方式，在此不再赘述。
在本申请的另一些场景中，步骤502也可以替换为：终端向AMF发送注册请求消息，注册请求消息中不包含请求的扩展DRX参数(Requested extended DRX parameters)；在接收到终端的注册请求消息后，AMF根据注册请求消息中不包含请求的扩展DRX参数，更新接入网设备的终端上下文。具体地，AMF通过终端上下文更新消息向接入网设备发送RIAI信息，在RIAI中不包含UE特定的扩展的空闲态DRX值(UE specific extended idle mode DRX)。
图6是本申请提供的通信方法600的示意性流程图。
方法600可以由接入网设备、SMF、UPF和MB-UPF执行，也可以由接入网设备、SMF、UPF和 MB-UPF中的模块或单元执行，本申请不予限制，为了描述方便，下文统一称为接入网设备、SMF、UPF和MB-UPF。方法600包括以下内容的至少部分内容。
步骤601，接入网设备向SMF发送第二信息。
相应地，SMF接收来自接入网设备的第二信息。
其中，第二信息用于请求为终端配置非激活态下的eDRX。例如，第二信息用于请求将终端转换为非激活态且第二信息携带eDRX的信息，其中，eDRX的信息包括终端进入eDRX的周期等。
“请求”也可以替换为“指示”或“配置”等。
需要说明的是，接入网设备与SMF之间的交互可以通过AMF，在此情况下，AMF接收到的信息和AMF发送的信息虽然都被称为第二信息，但AMF接收到的信息和AMF发送的信息的实现方式可以相同，也可以不同(例如通过不同的消息和/或信元)，不予限制。例如，接入网设备可以通过N2消息向AMF发送第二信息；AMF接收到来自接入网设备的N2消息后，根据其中的第二信息，向SMF发送PDU会话更新会话管理上下文请求消息(如Nsmf_PDUsession_UpdateSMContext request)，即通过PDU会话更新会话管理上下文请求消息或其中的信元向SMF传递第二信息。
步骤602，在接收到第二信息后，SMF根据第二信息，建立UPF和MB-UPF之间的传输通道。
其中，UPF和MB-UPF之间的传输通道用于传输终端的多播数据。这里的多播数据可以为终端处于eDRX睡眠状态时的多播数据。
步骤602可以理解为在为终端配置非激活态的eDRX时可以触发SMF建立UPF和MB-UPF之间的传输通道。
可选地，SMF此前可以获知为终端提供服务的接入网设备支持多播。即在接入网设备支持多播的情况下，SMF接收到第二信息后可以建立UPF和MB-UPF之间的传输通道。
需要指出的是，SMF根据第二信息建立UPF和MB-UPF之间的传输通道，可以是SMF根据第二信息新建UPF和MB-UPF之间的传输通道，也可以是SMF根据第二信息修改已有的UPF和MB-UPF之间的传输通道使得该通道可以传输终端的多播数据。
可选地，SMF建立UPF和MB-UPF之间的传输通道的方式有很多，不予限制。
一种可能的实现方式，SMF向UPF发送N4消息，相应地，UPF接收来自SMF的N4消息，其中，N4消息用于询问是否建立过UPF至MB-UPF的传输通道；UPF向SMF发送N4消息的响应消息，相应地，SMF接收来自UPF的响应消息，其中响应消息中包括第一下行隧道标识；SMF向MB-SMF发送请求消息，相应地，MB-SMF接收来自SMF的请求消息，其中请求消息包括第一下行隧道标识；MB-SMF与MB-UPF交互建立UPF与MB-UPF之间的传输通道；MB-SMF向SMF发送请求消息的响应消息，相应地，SMF接收来自MB-SMF的响应消息。其中，若UPF与MB-UPF之间已经存在传输通道，则第一下行隧道标识为该传输通道的隧道标识；若UPF与MB-UPF之间尚未建立传输通道，则第一下行隧道标识为UPF分配的隧道标识。更详细的描述可以参考现有技术，不再赘述。
另一种可能的实现方式，SMF向UPF发送N4消息，相应地，UPF接收来自SMF的N4消息，其中，N4消息用于询问是否建立过UPF至MB-UPF的传输通道；UPF向SMF发送N4消息的响应消息，相应地，SMF接收来自UPF的响应消息，其中响应消息中包括SSM信息；SMF向MB-SMF发送请求消息，相应地，MB-SMF接收来自SMF的请求消息，其中请求消息包括SSM信息；MB-SMF与MB-UPF交互建立UPF与MB-UPF之间的传输通道，在该过程中MB-UPF向MB-SMF提供用于多播的第二下行隧道标识；MB-SMF向SMF发送请求消息的响应消息，相应地，SMF接收来自MB-SMF的响应消息，其中响应消息包括第二下行隧道标识；SMF向UPF提供第二下行隧道标识。更详细的描述可以参考现有技术，不再赘述。
步骤603，SMF向UPF或MB-UPF发送eDRX缓存信息。
相应地，UPF或MB-SMF接收来自SMF的eDRX缓存信息。
其中，eDRX缓存信息用于缓存终端的多播数据。
可选地，eDRX缓存信息包括第三指示信息和终端进入eDRX的周期，其中第三指示信息用于指示停止终端的多播数据的传输并对终端的多播数据进行缓存。
可选地，eDRX缓存信息包括配置信息和终端进入eDRX的周期，其中配置信息用于配置UPF或MB-UPF以便UPF或MB-UPF对终端的多播数据进行缓存。
当SMF向UPF发送eDRX缓存信息时，可以认为是由UPF对终端的多播数据进行缓存。即MB-UPF可以通过UPF与MB-UPF之间的传输通道将终端的多播数据传输至UPF，并由UPF进行缓存。后续当终端重新变为可达状态时，UPF可以将缓存的数据发送至终端。
当SMF向MB-UPF发送eDRX缓存信息时，可以认为是由MB-UPF对终端的多播数据进行缓存。即MB-UPF可以对终端的多播数据进行缓存，后续当终端重新变为可达状态时，MB-UPF可以通过UPF与MB-UPF之间的传输通道将缓存的多播数据传输至UPF，在由UPF传输至终端。
需要指出的是，步骤603可以通过步骤602实现，例如，SMF通过发送给UPF的N4消息向UPF发送eDRX缓存信息，又例如，SMF通过发送给MB-SMF的请求消息向MB-SMF发送eDRX缓存信息，进而MB-SMF可以在与MB-UPF交互的过程中向MB-UPF发送eDRX缓存信息。步骤603也可以通过独立与步骤602的其他信令实现。
步骤604，SMF向接入网设备发送第九信息。
相应地，接入网设备接收来自SMF的第九信息。
其中，第九信息用于指示成功为终端配置非激活态下的eDRX。
后续，在接收到第九信息后，接入网设备可以发起RRC连接释放过程以及为终端配置eDRX。
需要说明的是，接入网设备与SMF之间的交互可以通过AMF，在此情况下，AMF接收到的信息和AMF发送的信息虽然都被称为第九信息，但AMF接收到的信息和AMF发送的信息的实现方式可以相同，也可以不同(例如通过不同的消息和/或信元)，不予限制。
这样，在终端加入多播会话的情况下，接入网设备可以将终端转化为非激活态以及为终端配置eDRX，并且由UPF或MB-UPF对终端的多播数据进行缓存，从而保障多播数据的传输。
可选地，在上述实施例的另一种场景下，在接收到第二信息后，由SMF对终端的多播数据进行缓存或由SMF通知MB-SMF对终端的多播数据进行缓存。
下面结合具体的例子对本申请的实施例进行详细描述。
在以下示例中，eDRX信息可以对应于上文的eDRX缓存信息。
示例1
图7是本申请的通信方法的一个示例。
在本示例中，接入网设备可以支持多播，也可以不支持多播。
步骤701，终端注册到网络，并与网络协商用于连接管理(connection management，CM)-空闲态(IDLE)的eDRX的参数。
具体地，当终端支持eDRX时，终端在发送给AMF的注册请求消息中携带用于指示终端支持eDRX的信息；如果允许终端进入eDRX状态，那么AMF在发送给终端的注册接受消息中携带用于指示允许终端进入eDRX的信息、以及寻呼时间窗口(paging time window，PTW)的信息。当终端不支持eDRX时，终端在发送给AMF的注册请求消息中携带用于指示终端不支持eDRX的信息。
步骤701更详细地描述可以参考现有技术，在此不再赘述。
步骤702，终端请求加入多播会话，相应地，核心网设备建立该多播会话的相关资源。
具体地，终端向核心网设备发送PDU会话修改请求消息或PDU会话建立请求消息，消息中携带终端请求加入的多播会话的标识；核心网设备根据终端请求加入的多播会话的标识生成该多播会话对应的上下文、以及可选的该多播会话对应的单播QoS流的信息，并将生成的信息发送至接入网设备；接入网设备根据接收到的信息，建立或修改多播会话对应的上下文、以及可选地建立单播上下文。
步骤702更详细地描述可以参考现有技术，在此不再赘述。
通过步骤702，SMF可以获知终端已加入多播会话。
步骤703，在终端加入多播会话后，SMF向AMF发送N11消息。
相应地，AMF接收来自SMF的N11消息。
其中，N11消息用于向AMF通知终端已加入多播会话。具体地，该N11消息包括终端加入的多播会话的标识(例如，临时多播组标识(temporary multicast group identifier，TMGI))。可选地，N11消息还包括指示信息#1，指示信息#1用于指示终端已加入该多播会话。
需要指出的是，当该N11消息不包括指示信息#1时，可以认为N11消息包括的多播会话的标识隐式地指示终端已加入该标识对应的多播会话。
还需要指出的是，SMF可以在终端加入的多播会话为激活态时才向AMF发送该N11消息，换句话说，N11消息可以隐示的指示多播会话为激活态。
步骤704，接入网设备向AMF上报接入网设备是否支持eDRX。
一种可能的实现方式，在接入网设备上电时，接入网设备向AMF上报其知否支持eDRX。例如，接入网设备在下一代应用协议(next generation application protocol，NGAP)设置请求消息(NGAP setup request)中携带接入网设备的eDRX能力信息，该eDRX能力信息用于指示接入网设备是否支持eDRX。
步骤704为可选步骤。
步骤705，AMF根据接入网设备是否支持eDRX、终端是否支持eDRX、以及终端是否已加入多播会话，确定是否可将终端转换为eDRX的非激活态(即RRC inactive with eDRX)。
具体地，当接入网设备不支持eDRX，和/或，终端不支持eDRX，和/或，终端已加入多播会话时，AMF确定终端不适用非激活态下的eDRX。当接入网设备支持eDRX、终端支持eDRX、且终端未加入多播会话时，AMF确定终端适用非激活态下的eDRX。
需要指出的是，若未执行步骤704，则AMF在确定是否可将终端转换为eDRX的非激活态时可以不考虑接入网设备是否支持eDRX。
步骤706，AMF向接入网设备发送指示信息#2。
相应地，接入网设备接收来自AMF的指示信息#2。
其中，指示信息#2用于指示终端是否适用非激活态下的eDRX。指示信息#2可以对应于上文的第一信息。
一种可能的实现方式，指示信息#2可以携带在RRC非激活态辅助信息(RRC inactive assistance information，RIAI)中。
步骤707，接入网设备根据指示信息#2，将或不将终端转换为eDRX的非激活态。
具体地，当指示信息#2用于指示终端不适用非激活态下的eDRX时，接入网设备不将终端转换为eDRX的非激活态。当指示信息#2用于指示终端适用非激活态下的eDRX时，接入网设备进一步结合其他信息(例如接入网设备是否支持eDRX(若未执行步骤704)、接入网设备的实现、和接入网设备当前的负载等)，确定将终端转换为eDRX的非激活态或不将终端转换为eDRX的非激活态。
这样，在本示例中，在终端已加入多播会话的情况下，接入网设备不将终端转换为eDRX的非激活态，有助于保障多播业务的传输。
示例2
图8是本申请的通信方法的另一个示例。
在本示例中，接入网设备支持多播。由于接入网设备支持多播，因此接入网设备知道终端是否已加入多播会话、以及多播会话的状态。
步骤801，终端注册到网络，并与网络协商用于CM-IDLE的eDRX的参数。
步骤802，终端请求加入多播会话，相应地，核心网设备建立该多播会话的相关资源。
步骤801～802可以参考步骤701～702，在此不再详述。
步骤803，接入网设备根据接入网设备是否支持eDRX、终端是否支持eDRX、以及终端是否已加入多播会话，将或不将终端转换为eDRX的非激活态。
一种可能的实现方式，当接入网设备不支持eDRX，和/或，终端不支持eDRX，和/或，终端已加入多播会话时，接入网设备不将终端转换为eDRX的非激活态。当接入网设备支持eDRX、终端支持eDRX、且终端未加入多播会话时，接入网设备可以将终端转换为eDRX的非激活态，但接入网设备是否将终端转换为eDRX的非激活态，还要看是否满足将终端转换为eDRX的非激活态需要满足的其他条件(例如，接入网设备的实现或接入网设备当前的负载等)时。
另一种可能的实现方式，接入网设备还可以进一步考虑终端加入的多播会话的状态。例如，当接入网设备不支持eDRX，和/或，终端不支持eDRX，和/或，终端已加入多播会话且该多播会话为激活态时，接入网设备不将终端转换为eDRX的非激活态；否则，接入网设备可以将终端转换为eDRX的非激活态，但接入网设备是否将终端转换为eDRX的非激活态，还要看是否满足将终端转换为eDRX的非激活态需要满足的其他条件(例如，接入网设备的实现或接入网设备当前的负载等)时。
这样，在本示例中，在终端已加入多播会话(可选的该多播会话为激活态)的情况下，接入网设 备不将终端转换为eDRX的非激活态，有助于保障多播业务的传输。
示例3
图9是本申请的通信方法的另一个示例。
步骤901，终端注册到网络，并与网络协商用于CM-IDLE的eDRX的参数。
步骤902，终端请求加入多播会话，相应地，核心网设备建立该多播会话的相关资源。
步骤901～902可以参考步骤701～702，在此不再详述。
步骤903，在终端加入多播会话后，SMF向AMF发送N11消息。
相应地，AMF接收来自SMF的N11消息。
其中，N11消息用于向AMF通知终端已加入多播会话。具体地，该N11消息包括终端加入的多播会话的标识(例如，TMGI)。可选地，N11消息还包括指示信息#1，指示信息#1用于指示终端已加入该多播会话。
需要指出的是，当该N11消息不包括指示信息#1时，可以认为N11消息包括的多播会话的标识隐式地指示终端已加入该标识对应的多播会话。
还需要指出的是，SMF可以在终端加入的多播会话为激活态时才向AMF发送该N11消息，换句话说，N11消息可以隐示的指示多播会话为激活态。
步骤904，接入网设备根据RIAI、以及其他可能的信息(例如接入网设备的实现或接入网设备当前的负载等)，决定将终端转换为eDRX的非激活态。
步骤905，在将终端转换为eDRX的非激活态之前，接入网设备向AMF发送N2消息。
相应地，AMF接收来自接入网设备的N2消息。
其中，该N2消息用于请求将终端转换为eDRX的非激活态，该消息中携带eDRX信息(例如，终端进入eDRX的周期等)。这样，在接收到该N2消息后，AMF根据该N2消息可以获知接入网设备计划将终端转换为eDRX的非激活态。
步骤904～905更详细的描述可以参考现有技术，在此不再详述。
步骤906，AMF根据步骤903中获得的信息(如TMGI和/或指示信息#1)确定终端不适用非激活态下的eDRX。
步骤907，AMF向接入网设备发送N2消息。
相应地，接入网设备接收来自AMF的N2消息。
其中，该N2消息用于拒绝将终端转换为eDRX的非激活态的请求。示例性地，该N2消息包括拒绝信息和拒绝原因，其中，拒绝信息用于指示拒绝将终端转换为eDRX的非激活态，拒绝原因包括终端已加入多播会话。
步骤908，接入网设备根据步骤907中的N2消息，不将终端转换为eDRX的非激活态。
这样，在本示例中，在终端已加入多播会话的情况下，接入网设备不将终端转换为eDRX的非激活态，有助于保障多播业务的传输。
示例4
图10是本申请的通信方法的另一个示例。
步骤1001，终端注册到网络，并与网络协商用于CM-IDLE的eDRX的参数。
步骤1002，终端请求加入多播会话，相应地，核心网设备建立该多播会话的相关资源。
步骤1001～1002可以参考步骤701～702，在此不再详述。
步骤1003，接入网设备根据RIAI、以及其他可能的信息(例如接入网设备的实现或接入网设备当前的负载等)，决定将终端转换为非激活态。
步骤1004，接入网设备向AMF发送N2消息。
相应地，AMF接收来自接入网设备的N2消息。
其中，该N2消息用于请求将终端转换为eDRX的非激活态，该消息中携带eDRX信息(例如，终端进入eDRX的周期等)。
这样，在接收到该N2消息后，AMF根据该N2消息可以获知接入网设备计划将终端转换为eDRX的非激活态，以便后续通知用户面处于激活态的PDU会话对应的SMF将终端转换为eDRX的非激活态。
步骤1003～1004更详细的描述可以参考现有技术，在此不再详述。
步骤1005，AMF向SMF发送N11消息。
相应地，SMF接收来自AMF的N11消息。
其中，N11消息用于请求将终端转换为eDRX的非激活态，该消息中携带eDRX信息(例如，终端进入eDRX的周期等)。
一种可能的实现方式，该N11消息为Nsmf_PDUSessionUpdateSMContext request。
步骤1006，SMF根据终端已加入多播会话，确定终端不适用非激活态下的eDRX。
其中，SMF可以通过步骤1002获知终端已加入多播会话。
步骤1007，SMF向AMF发送N11消息。
相应地，AMF接收来自SMF的N11消息。
其中，该N11消息用于拒绝将终端转换为eDRX的非激活态的请求。示例性地，该N11消息包括拒绝信息和拒绝原因，其中，拒绝信息用于拒绝将终端转换为eDRX的非激活态，拒绝原因包括终端已加入多播会话。
一种可能的实现方式，该N11消息为Nsmf_PDUSessionUpdateSMContext response。
步骤1008，若在步骤1004中AMF还向其他SMF发送了N11消息，则在接收到步骤1007中的N11消息后AMF向其他SMF发送N11消息。
其中，该N11消息用于撤回将终端转换为eDRX的非激活态的请求。示例性地，该N11消息中可以携带指示信息#3，指示信息#3用于指示停止将终端转换为eDRX的非激活态。
步骤1009，AMF向接入网设备发送N2消息。
相应地，接入网设备接收来自AMF的N2消息。
其中，该N2消息用于拒绝接入网设备将终端转换为eDRX的非激活态的请求。示例性地，该N2消息包括拒绝信息和拒绝原因，其中，拒绝信息用于拒绝将终端转换为eDRX的非激活态，拒绝原因包括终端已加入多播会话。
步骤1010，接入网设备根据步骤1009中的N2消息，不将终端转换为eDRX的非激活态。
这样，在本示例中，在终端已加入多播会话的情况下，接入网设备不将终端转换为eDRX的非激活态，有助于保障多播业务的传输。
示例5
图11是本申请的通信方法的另一个示例。
步骤1101，终端注册到网络，并与网络协商用于CM-IDLE的eDRX的参数。
步骤1102，终端请求加入多播会话，相应地，核心网设备建立该多播会话的相关资源。
步骤1101～1102可以参考步骤701～702，在此不再详述。
步骤1103，SMF向终端发送N1消息。
相应地，终端接收来自SMF的N1消息。
其中，该N1消息包括多播会话对应的多播业务的业务特性。这里的多播会话可以是终端加入的多播会话。多播业务的业务特性可以用于确定或指示该多播业务是否支持eDRX，例如，多播业务的业务特性可以包括多播业务是否支持eDRX、多播业务为时延敏感类型等。
一种可能的实现方式，N11消息可以是步骤1102中的消息，即步骤1103可以通过步骤1102来实现，或者说，步骤1103为步骤1102的一部分。例如，N11消息可以是多播会话加入请求消息的响应消息，如PDU会话修改指令(PDU session modification command)等，此时，多播业务的业务特性可以是该消息中的一个信元。
另一种可能的实现方式，N11消息可以是新增加的用于传输多播业务的业务特性的消息。
步骤1104，在满足以下条件时，终端向AMF发送注册请求消息，以便重新与网络协商终端的eDRX能力：
条件1，终端已加入多播会话；
条件2，在步骤1403中接收到的N1消息携带的多播业务的业务特性指示多播业务不支持eDRX；
条件3，之前与网络协商过用于CM-IDLE的eDRX的参数，并且接收到用于指示允许终端进入eDRX的信息、以及PTW的信息。
其中，注册请求消息不携带用于指示终端支持eDRX的信息或者携带用于指示终端不支持eDRX的信息。
需要指出的是，终端也可以不考虑条件2。
在此之后，由于终端已加入多播会话，因此在终端再次发起注册流程中不会携带用于指示终端支持eDRX的信息。当然，若终端离开了其加入的全部多播会话，则终端再次发起注册流程时可以携带用于指示终端支持eDRX的信息。
步骤1105，在接收到终端的注册请求消息后，AMF向接入网设备发送终端上下文更新消息。
相应地，接入网设备接收来自AMF的终端上下文更新消息。
其中，终端上下文更新消息不包括用于指示终端支持eDRX的信息，或者，终端上下文更新消息包括用于指示终端不支持eDRX的信息。例如，在RIAI信息中不携带UE specific extended idle mode DRX，或者，在RIAI信息中携带UE specific extended idle mode DRX，但UE specific extended idle mode DRX为特殊值。
一种可能的实现方式，在AMF向接入网设备发送终端上下文更新消息之前，AMF确定此前向接入网设备提供过RIAI信息。
另一种可能的实现方式，在AMF向接入网设备发送终端上下文更新消息之前，AMF确定此前向接入网设备提供过RIAI信息，且该RIAI信息包括用于指示允许终端进入eDRX的信息。
步骤1106，接入网设备根据更新后的终端上下文不将终端转换为eDRX的非激活态。
在以上示例1至示例5中，在终端已加入多播会话的情况下，接入网设备不会将终端转换为eDRX的非激活态。在以下的示例6和示例7中，在终端已加入多播会话的情况下，接入网设备可以将终端转换为eDRX的非激活态，多播数据缓存在核心网设备并在终端重新变为可达时才发送至终端。
示例6
在本示例中，在终端加入多播会话的情况下，接入网设备可以将终端转换为eDRX的非激活态，多播数据可以缓存在UPF。
图12是本申请的通信方法的另一个示例。
步骤1201，终端注册到网络，并与网络协商用于CM-IDLE的eDRX的参数。
步骤1202，终端请求加入多播会话，相应地，核心网设备建立该多播会话的相关资源。
步骤1201～1202可以参考步骤701～702，在此不再详述。
步骤1203，AMF向接入网设备发送N2消息。
相应地，接入网设备接收来自AMF的N2消息。
其中，N2消息包括RIAI。RIAI中携带用于将终端转换为非激活态时所需的信息，例如注册区域、周期注册时间、UE特定的扩展的空闲态DRX值(UE specific extended idle mode DRX values)等。
步骤1204，接入网设备根据RIAI、以及其他可能的信息(例如接入网设备的实现，UE的无线能力(UE Radio Capability)支持eDRX，或接入网设备当前的负载等)，决定将终端转换为RRC非激活态。
步骤1205，接入网设备向AMF发送N2消息。
相应地，AMF接收来自接入网设备的N2消息。
其中，N2消息中的包括eDRX信息(例如，终端进入eDRX的周期、eDRX指示、缓存时间等)。这样，在接收到该N2消息后，AMF根据该N2消息可以获知接入网设备计划(或准备)将终端转换为eDRX的非激活态，随后针对用户面处于激活态的PDU会话，AMF可以通知对应的SMF。
可选地，N2消息可以是UE通知(UE Notification)消息，也可以是RRC非激活态转换通知(RRC INACTIVE TRANSITION REPORT)，也可以是其他消息，本申请不做限定。
步骤1206，AMF向所述对应的SMF发送更新会话管理上下文请求消息(如Nsmf_PDUSessionUpdateSMContext request)。
相应地，SMF接收来自AMF的更新会话管理上下文请求消息。
其中，更新会话管理上下文请求消息中携带指示信息#4和eDRX信息，指示信息#4用于指示停止用户面传输并且对用户面的多播数据进行缓存。
此后，如果由SMF处理下行多播数据，那么SMF开始缓存下行多播数据。如果由MB-SMF处理 下行多播数据，那么SMF通知MB-SMF缓存下行多播数据。如果由UPF或MB-UPF处理下行多播数据，那么SMF可以继续执行步骤1207。
一种可能的实现方案是，指示信息#4可以是用户面挂起(UP Suspend)指示。
一种例子可以是，N2消息中包含了用户面处于激活态的PDU会话列表，AMF根据列表通知对应的SMF。
步骤1207，在接收到步骤1206中的更新会话管理上下文请求消息后，SMF触发建立MB-UPF到UPF的传输通道(或称转发通道、通道、转发隧道)。
一种可能的实现方式，若SMF为管理与终端的多播会话相关联的单播会话的SMF，则SMF判断：a)针对该终端，当前不存在MB-UPF到UPF的传输通道；和/或，b)SMF建立了MB-UPF到UPF的传输通道，但MB-UPF此时不向UPF发送数据(例如，MB-UPF被配置不向UPF发送数据)；和/或，c)终端当前驻留的接入网设备支持多播(例如，SMF从接入网设备接收的N2消息中，接收到“基站支持多播(NG-RAN supports MBS)”的指示信息)；SMF触发建立MB-UPF到UPF的传输通道。这里的“建立”可以指新建或修改。
建立MB-UPF到UPF的传输通道的步骤如步骤1208～1212
步骤1208，SMF向UPF发送N4消息(如N4会话修改请求消息)。
相应地，UPF接收来自SMF的N4消息。
其中，N4消息用于请求建立UPF至MB-UPF的传输通道，或者用于询问UPF是否建立过UPF至MB-UPF的传输通道。N4消息包括eDRX信息(buffer info for eDRX)、多播会话的标识(如TMGI)、可选的SSM等信息，其中eDRX信息用于缓存终端的多播数据。
可选地，N4消息还包括配置信息，配置信息用于配置的内容包括：a)多播数据的识别规则；b)多播数据的转发规则等。
步骤1209，UPF向SMF发送步骤1208中的N4消息的响应消息或数据包。
相应地，SMF接收来自UPF的响应消息或数据包。
其中，响应消息中包括下行隧道标识#1(如DL tunnel ID#1)。
具体地，在接收收到步骤1208中的N4消息后，UPF判断是否建立过UPF至MB-UPF的传输通道。若尚未建立UPF至MB-UPF的传输通道，则UPF可以返回下行隧道标识#1，或者根据SSM信息发送数据包。
可选地，UPF还可以在N4响应消息中包含下行隧道标识#1是否是新分配的。
步骤1210，SMF向MB-SMF发送N16mb消息。
相应地，MB-SMF接收来自SMF的N16mb消息。
其中，N16mb消息用于请求建立UPF至MB-UPF的传输通道。可选地，N16mb消息中包括下行隧道标识#1。
可选地，如果UPF在N4响应消息中包含下行隧道标识#1是新分配的，那么SMF可以向MB-SMF发送N16mb消息。
步骤1211，MB-SMF与MB-UPF进行N4mb会话修改流程。
在此过程中，MB-SMF可以将下行隧道标识#1提供给MB-UPF或者接收MB-UPF提供用于多播的下行隧道标识#2。
步骤1212，MB-SMF向SMF发送步骤1210中N16mb消息的响应消息。
相应地，SMF接收来自MB-SMF的响应消息。
可选地，响应消息中携带下行隧道标识#2。
可选地，若在步骤1208中N4消息不包括配置信息，则SMF在接收到响应消息后可以为UPF配置以下内容：a)多播数据的识别规则；b)多播数据的转发规则等。
可选地，若在响应消息中包括下行隧道标识#2，则SMF可以向UPF提供下行隧道标识#2。
步骤1213，SMF向AMF发送步骤1206中的N11消息的响应消息。
相应地，AMF接收来自SMF的响应消息。
步骤1214，AMF向接入网设备发送步骤1205中的N2消息的响应消息。
相应地，接入网设备接收来自AMF的响应消息。
步骤1215，接入网设备将终端转换为eDRX的RRC非激活态。
图13是传输多播数据的一个示意图。
图13所示的传输多播数据的示意图基于图12所示的传输方法，在终端已加入多播会话的情况下，接入网设备可以将终端转换为eDRX的非激活态。
如图13的(a)图所示，针对处于DRX的非激活态的终端(如终端1)，MB-UPF通过UPF与MB-UPF之间的传输通道将处于eDRX状态的终端1的多播数据传输至UPF，由UPF为终端1缓存多播数据。
如图13的(b)图所示，当终端重新变为可达时，UPF将缓存的多播数据发送至终端。
这样，在终端加入多播会话的情况下，接入网设备可以将终端转换为eDRX的非激活态，多播数据可以缓存在UPF，从而避免终端错过多播数据，有助于保障多播业务的传输。
示例7
在本示例中，在终端加入多播会话的情况下，接入网设备可以将终端转换为eDRX的非激活态，多播数据可以缓存在MB-UPF。
图14是本申请的通信方法的另一个示例。
步骤1401，终端注册到网络，并与网络协商用于CM-IDLE的eDRX的参数。
步骤1402，终端请求加入多播会话，相应地，核心网设备建立该多播会话的相关资源。
步骤1401～1402可以参考步骤701～702，在此不再详述。
步骤1403，AMF向接入网设备发送N2消息。
相应地，接入网设备接收来自AMF的N2消息。
其中，N2消息包括RIAI。RIAI中携带用于将终端转换为非激活态时所需的信息，例如注册区域、周期注册时间、UE特定的扩展的空闲态DRX值(UE specific extended idle mode DRX values)等。
步骤1404，接入网设备根据RIAI、以及其他可能的信息(例如接入网设备的实现，UE的无线能力(UE Radio Capability)支持eDRX，或接入网设备当前的负载等)，决定将终端转换为RRC非激活态。
步骤1405，接入网设备向AMF发送N2消息。
相应地，AMF接收来自接入网设备的N2消息。
其中，N2消息中的包括eDRX信息(例如，终端进入eDRX的周期、eDRX指示、缓存时间等)。这样，在接收到该N2消息后，AMF根据该N2消息可以获知接入网设备计划(或准备)将终端转换为eDRX的非激活态，随后针对用户面处于激活态的PDU会话，AMF可以通知对应的SMF。
可选地，N2消息可以是UE通知(UE Notification)消息，也可以是RRC非激活态转换通知(RRC INACTIVE TRANSITION REPORT)，也可以是其他消息，本申请不做限定。
步骤1406，AMF向所述对应的SMF发送更新会话管理上下文请求消息(如Nsmf_PDUSessionUpdateSMContext request)。
相应地，SMF接收来自AMF的更新会话管理上下文请求消息。
一种例子可以是，N2消息中包含了用户面处于激活态的PDU会话列表，AMF根据列表通知对应的SMF。
其中，更新会话管理上下文请求消息中携带指示信息#4和eDRX信息，指示信息#4用于指示停止用户面传输并且对用户面的多播数据进行缓存。
此后，如果由SMF处理下行多播数据，那么SMF开始缓存下行多播数据。如果由MB-SMF处理下行多播数据，那么SMF通知MB-SMF缓存下行多播数据。如果由UPF或MB-UPF处理下行多播数据，那么SMF可以继续执行步骤1407。
步骤1407，在接收到步骤1406中的更新会话管理上下文请求消息后，SMF触发建立MB-UPF到UPF的传输通道(或称转发通道、通道、转发隧道)。
一种可能的实现方式是，若SMF为管理与终端的多播会话相关联的单播会话的SMF，则SMF判断：a)针对该终端，当前不存在MB-UPF到UPF的传输通道；和/或，b)SMF建立了MB-UPF到UPF的传输通道，但MB-UPF此时不向UPF发送数据(例如，MB-UPF被配置不向UPF发送数据)；和/或，c)终端当前驻留的接入网设备支持多播(例如，SMF从接入网设备接收的N2消息中，接收到“基 站支持多播(NG-RAN supports MBS)”的指示信息)；SMF触发建立MB-UPF到UPF的传输通道。这里的“建立”可以指新建或修改。
步骤1407中的判断逻辑可以执行也可以不执行，不予限制。
建立MB-UPF到UPF的传输通道的步骤如步骤1408～1412
步骤1408，SMF向UPF发送N4消息(如N4会话修改请求消息)。
相应地，UPF接收来自SMF的N4消息。
其中，N4消息用于请求建立UPF至MB-UPF的传输通道，或者用于询问UPF是否建立过UPF至MB-UPF的传输通道。N4消息包括eDRX信息、多播会话的标识(如TMGI)、可选的SSM等信息，其中eDRX信息用于缓存终端的多播数据。
可选地，N4消息还包括配置信息，配置信息用于配置的内容包括：a)多播数据的识别规则；b)多播数据的转发规则等。
步骤1409，UPF向SMF发送步骤1408中的N4消息的响应消息或数据包。
相应地，SMF接收来自UPF的响应消息或数据包。
其中，响应消息中包括下行隧道标识#1(如DL tunnel ID#1)。
具体地，在接收收到步骤1408中的N4消息后，UPF判断是否建立过UPF至MB-UPF的传输通道。若尚未建立UPF至MB-UPF的传输通道，则UPF可以返回下行隧道标识#1，或者根据SSM信息发送数据包。
可选地，UPF还可以在N4响应消息中包含下行隧道标识#1是否是新分配的。
步骤1410，SMF向MB-SMF发送N16mb消息。
相应地，MB-SMF接收来自SMF的N16mb消息。
其中，N16mb消息用于请求建立UPF至MB-UPF的传输通道，N16mb消息中包括eDRX信息。可选地，N16mb消息中包括下行隧道标识#1。
可选地，如果UPF在N4响应消息中包含下行隧道标识#1是新分配的，那么SMF可以向MB-SMF发送N16mb消息。
步骤1411，MB-SMF与MB-UPF进行N4mb会话修改流程。
在此过程中，MB-SMF可以将eDRX信息提供给MB-UPF，并且将下行隧道标识#1提供给MB-UPF或者接收MB-UPF提供用于多播的下行隧道标识#2。
步骤1412，MB-SMF向SMF发送步骤1410中N16mb消息的响应消息。
相应地，SMF接收来自MB-SMF的响应消息。
可选地，响应消息中携带下行隧道标识#2。
可选地，若在步骤1408中N4消息不包括配置信息，则SMF在接收到响应消息后可以为UPF配置以下内容：a)多播数据的识别规则；b)多播数据的转发规则等。
可选地，若在响应消息中包括下行隧道标识#2，则SMF可以向UPF提供下行隧道标识#2。
步骤1413，SMF向AMF发送步骤1406中的N11消息的响应消息。
相应地，AMF接收来自SMF的响应消息。
步骤1414，AMF向接入网设备发送步骤1405中的N2消息的响应消息。
相应地，接入网设备接收来自AMF的响应消息。
步骤1415，接入网设备将终端转换为eDRX的RRC非激活态。
图15是传输多播数据的另一个示意图。
图15所示的传输多播数据的示意图基于图14所示的传输方法，在终端已加入多播会话的情况下，接入网设备可以将终端转换为eDRX的非激活态。
如图15的(a)图所示，针对处于DRX的非激活态的终端(如终端1)，由MB-UPF为处于eDRX状态的终端(如终端1)缓存多播数据。
如图15的(b)图所示，当终端重新变为可达时，MB-UPF通过UPF与MB-UPF之间的传输通道将缓存的多播数据传输至UPF，再由UPF发送至终端。
这样，在终端加入多播会话的情况下，接入网设备可以将终端转换为eDRX的非激活态，多播数据可以缓存在MB-UPF，从而避免终端错过多播数据，有助于保障多播业务的传输。此外，MB-UPF 缓存多播数据，缓存点比较高，有助于降低网络缓存的数据量。
上文结合图3至图15，详细描述了本申请提供的方法，下面将结合图16至图17，详细描述本申请的装置实施例。
可以理解的是，为了实现上述实施例中功能，图16或图17中的装置包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本申请中所公开的实施例描述的各示例的单元及方法步骤，本申请能够以硬件或硬件和计算机软件相结合的形式来实现。
图16和图17为本申请的实施例提供的可能的装置的结构示意图。这些装置可以用于实现上述方法实施例中核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元的功能，因此也能实现上述方法实施例所具备的有益效果。
如图16所示，装置1600包括收发单元1610和处理单元1620。
在一些实现方式中，当装置1600用于实现上述方法实施例中核心网设备的功能时，收发单元1610用于：获知终端已加入多播会话；发送第一信息，所述第一信息用于通知拒绝为所述终端配置非激活态下的eDRX，或者所述第一信息用于指示所述终端不适用非激活态下的eDRX。
可选地，收发单元1610具体用于：当以下条件中的至少一个被满足时，发送所述第一信息：为所述终端提供服务的接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件；其中，所述预设条件为：所述多播会话处于激活态、所述多播会话对应的多播业务不支持eDRX、或所述多播会话处于激活态且所述多播会话对应的多播业务不支持eDRX。
可选地，当所述第一信息用于通知拒绝为所述终端配置非激活态下的eDRX时，所述第一信息包括拒绝信息，所述拒绝信息用于指示拒绝为所述终端配置非激活态下的eDRX。
可选地，收发单元1610还用于：接收第二信息，所述第二信息用于请求为所述终端配置非激活态下的eDRX。
可选地，所述拒绝信息包括拒绝为所述终端配置非激活态下的eDRX的原因；其中，所述原因包括以下至少一个：所述终端已加入多播会话、为所述终端提供服务的接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件；其中，所述预设条件为：所述多播会话处于激活态、所述多播会话对应的多播业务不支持eDRX、或所述多播会话处于激活态且所述多播会话对应的多播业务不支持eDRX。
可选地，收发单元1610还用于：接收来自所述接入网设备的第三信息，所述第三信息用于指示所述接入网设备不支持eDRX。
可选地，所述核心网设备为接入和移动性管理功能网元或会话管理功能网元。
可选地，所述核心网设备为接入和移动性管理功能网元，收发单元1610还用于：接收来自会话管理功能的业务信息，所述业务信息用于指示所述多播会话对应的多播业务不支持eDRX。
可选地，所述业务信息包括所述多播业务的类型，所述类型为时延敏感类型。
可选地，所述核心网设备为接入和移动性管理功能网元，收发单元1610还用于：接收来自会话管理功能网元的第四信息，所述第四信息用于指示所述终端已加入多播会话。
在一些实现方式中，当装置1600用于实现上述方法实施例中接入网设备的功能时，收发单元1610用于：当确定将终端转换为非激活态时，向核心网设备发送第二信息，所述第二信息用于请求为所述终端配置非激活态下的eDRX；接收来自所述核心网设备的第一信息，所述第一信息用于通知拒绝为所述终端配置非激活态下的eDRX。处理单元1620用于根据所述第一信息，不为所述终端配置非激活态下的eDRX。
可选地，所述第一信息包括拒绝信息，所述拒绝信息用于指示拒绝为所述终端配置非激活态下的eDRX。
可选地，所述拒绝信息包括拒绝为所述终端配置非激活态下的eDRX的原因；其中，所述原因包括以下至少一个：所述终端已加入多播会话、所述接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件；其中，所述预设条件为：所述多播会话处于激活态、所述多播会话对应的多播业务不支持eDRX、或所述多播会话处于激活态且所述多播会话对应的多播业务不支持eDRX。
可选地，所述核心网设备为接入和移动性管理功能网元或会话管理功能网元。
在另一些实现方式中，当装置1600用于实现上述方法实施例中接入网设备的功能时，收发单元 1610用于：接收来自核心网设备的第一信息，所述第一信息用于指示终端不适用非激活态下的eDRX。处理单元1620用于：当确定将所述终端转换为非激活态时，根据所述第一信息，不为所述终端配置非激活态下的eDRX。
可选地，所述核心网设备为接入和移动性管理功能网元或会话管理功能网元。
在又一些实现方式中，当装置1600用于实现上述方法实施例中接入网设备的功能时，收发单元1610用于：获知终端已加入多播会话。处理单元1620用于：在确定将所述终端转换为非激活态时，不为所述终端配置非激活态下的eDRX。
可选地，处理单元1620具体用于：当以下条件中的至少一个被满足时，不为所述终端配置非激活态下的eDRX：所述接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件；其中，所述预设条件为：所述多播会话处于激活态、所述多播会话对应的多播业务不支持eDRX、或所述多播会话处于激活态且所述多播会话对应的多播业务不支持eDRX。
可选地，收发单元1610还用于：接收来自会话管理功能的业务信息，所述业务信息用于指示所述多播会话对应的多播业务不支持eDRX。
可选地，所述业务信息包括所述多播业务的类型，所述类型为时延敏感类型。
在一些实现方式中，当装置1600用于实现上述方法实施例中接入和移动性管理功能网元的功能时，收发单元1610用于：接收来自接入网设备的第二信息，所述第二信息用于请求为终端配置非激活态下的eDRX；向第一会话管理功能网元和第二会话管理功能网元发送所述第二信息，所述第一会话管理功能网元用于管理与所述终端的多播会话相关联的单播会话，所述第二会话管理功能网元用于管理与所述终端的多播会话不关联的单播会话；接收来自所述第一会话管理功能网元的第一信息，所述第一信息用于通知拒绝为所述终端配置非激活态下的eDRX；向所述接入网设备发送所述第一信息，和/或，向所述第二会话管理功能网元发送第五信息，所述第五信息用于触发所述第二会话管理功能网元停止为所述终端配置非激活态下的eDRX。
可选地，所述第一信息包括拒绝信息，所述拒绝信息用于指示拒绝为所述终端配置非激活态下的eDRX。
可选地，所述拒绝信息包括拒绝为所述终端配置非激活态下的eDRX的原因；其中，所述原因包括以下至少一个：所述终端已加入多播会话、所述接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件；其中，所述预设条件为：所述多播会话处于激活态、所述多播会话对应的多播业务不支持eDRX、或所述多播会话处于激活态且所述多播会话对应的多播业务不支持eDRX。
在一些实现方式中，当装置1600用于实现上述方法实施例中终端的功能时，收发单元1610用于：获知所述终端已加入多播会话，所述终端支持eDRX；向接入网设备发送第六信息，所述第六信息用于指示所述终端不支持eDRX。
可选地，收发单元1610具体用于：当以下条件中的至少一个被满足时，向所述接入网设备发送所述第六信息：接收到来自核心网设备的第一信息、所述接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件；其中，所述第一信息用于指示所述终端不适用非激活态下的eDRX，所述预设条件为：所述多播会话处于激活态、所述多播会话对应的多播业务不支持eDRX、或所述多播会话处于激活态且所述多播会话对应的多播业务不支持eDRX。
可选地，所述核心网设备为接入和移动性管理功能网元或会话管理功能网元。
可选地，收发单元1610还用于：接收来自会话管理功能的业务信息，所述业务信息用于指示所述多播会话对应的多播业务不支持eDRX。
可选地，所述业务信息包括所述多播业务的类型，所述类型为时延敏感类型。
可选地，在所述终端向接入网设备发送第六信息之前，收发单元1610还用于：向所述接入网设备发送第七信息，所述第七信息用于指示所述终端支持eDRX。
可选地，收发单元1610还用于：在所述终端离开所述终端已加入的全部多播会话后，向所述接入网设备发送第八信息，所述第八信息用于指示所述终端支持eDRX。
在一些实现方式中，当装置1600用于实现上述方法实施例中会话管理功能网元的功能时，收发单元1610用于：接收来自接入网设备的第二信息，所述第二信息用于请求为终端配置非激活态下的eDRX。处理单元1620用于：根据所述第二信息，建立单播用户面功能网元和多播用户面功能网元之间的传输 通道，所述传输通道用于传输所述终端的多播数据。收发单元1610还用于：向接入网设备发送第九信息，所述第九信息用于指示成功为所述终端配置非激活态下的eDRX。
可选地，收发单元1610还用于：向所述单播用户面功能网元或所述多播用户面功能网元发送eDRX缓存信息，所述eDRX缓存信息用于缓存所述多播数据。
在一些实现方式中，当装置1600用于实现上述方法实施例中多播用户面功能网元的功能时，收发单元1610用于：接收来自会话管理功能网元的eDRX缓存信息，所述eDRX缓存信息用于缓存终端的多播数据。处理单元1620用于：根据所述eDRX缓存信息，缓存所述终端的多播数据。
关于上述收发单元1610和处理单元1620更详细的描述，可参考上述方法实施例中的相关描述，在此不再说明。
如图17示，装置1700包括处理器1710。处理器1710与存储器1730耦合，存储器1730用于存储指令。当装置1700用于实现上文所述的方法时，处理器1710用于执行存储器1730中的指令，以实现上述处理单元1620的功能。
可选地，装置1700还包括存储器1730。
可选地，装置1700还包括接口电路1720。处理器1710和接口电路1720之间相互耦合。可以理解的是，接口电路1720可以为收发器或输入输出接口。当装置1700用于实现上文所述的方法时，处理器1710用于执行指令，以实现上述处理单元1620的功能，接口电路1720用于实现上述收发单元1610的功能。
示例性地，当装置1700为应用于核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元的芯片时，该芯片实现上述方法实施例中核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元的功能。该芯片从核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元中的其它模块(如射频模块或天线)接收信息，该信息是其他装置发送给核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元的；或者，该芯片向核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元中的其它模块(如射频模块或天线)发送信息，该信息是核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元发送给其他装置的。
本申请还提供一种通信装置，包括处理器，该处理器与存储器耦合，存储器用于存储计算机程序或指令和/或数据，处理器用于执行存储器存储的计算机程序或指令，或读取存储器存储的数据，以执行上文各方法实施例中的方法。可选地，处理器为一个或多个。可选地，该通信装置包括存储器。可选地，存储器为一个或多个。可选地，该存储器与该处理器集成在一起，或者分离设置。
本申请还提供一种计算机可读存储介质，其上存储有用于实现上述各方法实施例中由核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元执行的方法的计算机指令。
本申请还提供一种计算机程序产品，包含指令，该指令被计算机执行时以实现上述各方法实施例中由核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元执行的方法。
本申请还提供一种通信系统，该通信系统包括上文各实施例中的核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元中至少一个。
上述提供的任一种装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其它通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的方法步骤可以通过硬件的方式来实现，也可以由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器、闪存、只读 存储器、可编程只读存储器、可擦除可编程只读存储器、电可擦除可编程只读存储器、寄存器、硬盘、移动硬盘、只读光盘存储器(compact disc read-only memory，CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元中。当然，处理器和存储介质也可以作为分立组件存在于核心网设备、接入网设备、接入和移动性管理功能网元、终端、会话管理功能或多播用户面功能网元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序或指令可以从一个网站站点、计算机、服务器或数据中心通过有线或无线方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，数字视频光盘；还可以是半导体介质，例如，固态硬盘。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。
除非另有说明，本申请实施例所使用的所有技术和科学术语与本申请的技术领域的技术人员通常理解的含义相同。本申请中所使用的术语只是为了描述具体的实施例的目的，不是旨在限制本申请的范围。应理解，上述为举例说明，上文的例子仅仅是为了帮助本领域技术人员理解本申请实施例，而非要将申请实施例限制于所示例的具体数值或具体场景。本领域技术人员根据上文所给出的例子，显然可以进行各种等价的修改或变化，这样的修改和变化也落入本申请实施例的范围内。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (37)

  1. 一种通信方法，其特征在于，所述方法包括：
    核心网设备获知终端已加入多播会话；
    所述核心网设备发送第一信息，所述第一信息用于通知拒绝为所述终端配置非激活态下的延长非连续接收eDRX，或者所述第一信息用于指示所述终端不适用非激活态下的eDRX。
  2. 根据权利要求1所述的方法，其特征在于，所述核心网设备发送第一信息，包括：
    当以下条件中的至少一个被满足时，所述核心网设备发送所述第一信息：为所述终端提供服务的接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件；
    其中，所述预设条件为：所述多播会话处于激活态、所述多播会话对应的多播业务不支持eDRX、或所述多播会话处于激活态且所述多播会话对应的多播业务不支持eDRX。
  3. 根据权利要求1或2所述的方法，其特征在于，
    当所述第一信息用于通知拒绝为所述终端配置非激活态下的eDRX时，所述第一信息包括拒绝信息，所述拒绝信息用于指示拒绝为所述终端配置非激活态下的eDRX。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    所述核心网设备接收第二信息，所述第二信息用于请求为所述终端配置非激活态下的eDRX。
  5. 根据权利要求3或4所述的方法，其特征在于，
    所述拒绝信息包括拒绝为所述终端配置非激活态下的eDRX的原因；
    其中，所述原因包括以下至少一个：所述终端已加入多播会话、为所述终端提供服务的接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件；
    其中，所述预设条件为：所述多播会话处于激活态、所述多播会话对应的多播业务不支持eDRX、或所述多播会话处于激活态且所述多播会话对应的多播业务不支持eDRX。
  6. 根据权利要求2至5中任选一项所述的方法，其特征在于，所述方法还包括：
    所述核心网设备接收来自所述接入网设备的第三信息，所述第三信息用于指示所述接入网设备不支持eDRX。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，
    所述核心网设备为接入和移动性管理功能网元或会话管理功能网元。
  8. 根据权利要求7所述的方法，其特征在于，所述核心网设备为接入和移动性管理功能网元，所述方法还包括：
    所述接入和移动性管理功能网元接收来自会话管理功能的业务信息，所述业务信息用于指示所述多播会话对应的多播业务不支持eDRX。
  9. 根据权利要求8所述的方法，其特征在于，
    所述业务信息包括所述多播业务的类型，所述类型为时延敏感类型。
  10. 根据权利要求7至9中任一项所述的方法，其特征在于，所述核心网设备为接入和移动性管理功能网元，所述方法还包括：
    所述接入和移动性管理功能网元接收来自会话管理功能网元的第四信息，所述第四信息用于指示所述终端已加入多播会话。
  11. 一种通信方法，其特征在于，所述方法包括：
    当接入网设备确定将终端转换为非激活态时，所述接入网设备向核心网设备发送第二信息，所述第二信息用于请求为所述终端配置非激活态下的延长非连续接收eDRX；
    所述接入网设备接收来自所述核心网设备的第一信息，所述第一信息用于通知拒绝为所述终端配置非激活态下的eDRX；
    所述接入网设备根据所述第一信息，不为所述终端配置非激活态下的eDRX。
  12. 根据权利要求11所述的方法，其特征在于，
    所述第一信息包括拒绝信息，所述拒绝信息用于指示拒绝为所述终端配置非激活态下的eDRX。
  13. 根据权利要求12所述的方法，其特征在于，
    所述拒绝信息包括拒绝为所述终端配置非激活态下的eDRX的原因；
    其中，所述原因包括以下至少一个：所述终端已加入多播会话、所述接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件；
    其中，所述预设条件为：所述多播会话处于激活态、所述多播会话对应的多播业务不支持eDRX、或所述多播会话处于激活态且所述多播会话对应的多播业务不支持eDRX。
  14. 根据权利要求11至13中任一项所述的方法，其特征在于，
    所述核心网设备为接入和移动性管理功能网元或会话管理功能网元。
  15. 一种通信方法，其特征在于，所述方法包括：
    接入网设备接收来自核心网设备的第一信息，所述第一信息用于指示终端不适用非激活态下的延长非连续接收eDRX；
    当所述接入网设备确定将所述终端转换为非激活态时，所述接入网设备根据所述第一信息，不为所述终端配置非激活态下的eDRX。
  16. 根据权利要求15所述的方法，其特征在于，
    所述核心网设备为接入和移动性管理功能网元或会话管理功能网元。
  17. 一种通信方法，其特征在于，所述方法包括：
    接入和移动性管理功能网元接收来自接入网设备的第二信息，所述第二信息用于请求为终端配置非激活态下的延长非连续接收eDRX；
    所述接入和移动性管理功能网元向第一会话管理功能网元和第二会话管理功能网元发送所述第二信息，所述第一会话管理功能网元用于管理与所述终端的多播会话相关联的单播会话，所述第二会话管理功能网元用于管理与所述终端的多播会话不关联的单播会话；
    所述接入和移动性管理功能网元接收来自所述第一会话管理功能网元的第一信息，所述第一信息用于通知拒绝为所述终端配置非激活态下的eDRX；
    所述接入和移动性管理功能网元向所述接入网设备发送所述第一信息，和/或，向所述第二会话管理功能网元发送第五信息，所述第五信息用于触发所述第二会话管理功能网元停止为所述终端配置非激活态下的eDRX。
  18. 根据权利要求17所述的方法，其特征在于，
    所述第一信息包括拒绝信息，所述拒绝信息用于指示拒绝为所述终端配置非激活态下的eDRX。
  19. 根据权利要求18所述的方法，其特征在于，
    所述拒绝信息包括拒绝为所述终端配置非激活态下的eDRX的原因；
    其中，所述原因包括以下至少一个：所述终端已加入多播会话、所述接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件；
    其中，所述预设条件为：所述多播会话处于激活态、所述多播会话对应的多播业务不支持eDRX、或所述多播会话处于激活态且所述多播会话对应的多播业务不支持eDRX。
  20. 一种通信方法，其特征在于，所述方法包括：
    接入网设备获知终端已加入多播会话；
    在所述接入网设备确定将所述终端转换为非激活态时，所述接入网设备不为所述终端配置非激活态下的延长非连续接收eDRX。
  21. 根据权利要求20所述的方法，其特征在于，所述接入网设备不为所述终端配置eDRX，包括：
    当以下条件中的至少一个被满足时，所述接入网设备不为所述终端配置非激活态下的eDRX：所述接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件；
    其中，所述预设条件为：所述多播会话处于激活态、所述多播会话对应的多播业务不支持eDRX、或所述多播会话处于激活态且所述多播会话对应的多播业务不支持eDRX。
  22. 根据权利要求21所述的方法，其特征在于，所述方法还包括：
    所述接入网设备接收来自会话管理功能的业务信息，所述业务信息用于指示所述多播会话对应的多播业务不支持eDRX。
  23. 根据权利要求22所述的方法，其特征在于，
    所述业务信息包括所述多播业务的类型，所述类型为时延敏感类型。
  24. 一种通信方法，其特征在于，所述方法包括：
    终端获知所述终端已加入多播会话，所述终端支持延长非连续接收eDRX；
    所述终端向接入网设备发送第六信息，所述第六信息用于指示所述终端不支持eDRX。
  25. 根据权利要求24所述的方法，其特征在于，所述终端向接入网设备发送第六信息，包括：
    当以下条件中的至少一个被满足时，所述终端向所述接入网设备发送所述第六信息：接收到来自核心网设备的第一信息、所述接入网设备不支持eDRX、所述终端不支持eDRX、或所述多播会话满足预设条件；
    其中，所述第一信息用于指示所述终端不适用非激活态下的eDRX，所述预设条件为：所述多播会话处于激活态、所述多播会话对应的多播业务不支持eDRX、或所述多播会话处于激活态且所述多播会话对应的多播业务不支持eDRX。
  26. 根据权利要求25所述的方法，其特征在于，所述核心网设备为接入和移动性管理功能网元或会话管理功能网元。
  27. 根据权利要求25或26所述的方法，其特征在于，所述方法还包括：
    所述终端接收来自会话管理功能的业务信息，所述业务信息用于指示所述多播会话对应的多播业务不支持eDRX。
  28. 根据权利要求27所述的方法，其特征在于，
    所述业务信息包括所述多播业务的类型，所述类型为时延敏感类型。
  29. 根据权利要求24至28中任一项所述的方法，其特征在于，在所述终端向接入网设备发送第六信息之前，所述方法还包括：
    所述终端向所述接入网设备发送第七信息，所述第七信息用于指示所述终端支持eDRX。
  30. 根据权利要求24至29中任一项所述的方法，其特征在于，所述方法还包括：
    在所述终端离开所述终端已加入的全部多播会话后，所述终端向所述接入网设备发送第八信息，所述第八信息用于指示所述终端支持eDRX。
  31. 一种通信装置，其特征在于，包括：
    处理器，用于执行存储器中存储的计算机程序，以使得所述装置执行如权利要求1至10中任一项所述的方法，或者执行如权利要求11至14中任一项所述的方法，或者执行如权利要求15或16所述的方法，或者执行如权利要求17至19中任一项所述的方法，或者执行如权利要求20至23中任一项所述的方法，或者执行如权利要求24至30中任一项所述的方法。
  32. 根据权利要求31所述的装置，其特征在于，所述装置还包括所述存储器。
  33. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至10中任一项所述的方法，或者执行如权利要求11至14中任一项所述的方法，或者执行如权利要求15或16所述的方法，或者执行如权利要求17至19中任一项所述的方法，或者执行如权利要求20至23中任一项所述的方法，或者执行如权利要求24至30中任一项所述的方法。
  34. 一种计算机程序产品，其特征在于，所述计算机程序产品包括用于执行如权利要求1至10中任一项所述的方法的指令，或者包括执行如权利要求11至14中任一项所述的方法的指令，或者包括执行如权利要求15或16所述的方法的指令，或者包括执行如权利要求17至19中任一项所述的方法的指令，或者包括执行如权利要求20至23中任一项所述的方法的指令，或者包括执行如权利要求24至30中任一项所述的方法的指令。
  35. 一种通信系统，其特征在于，包括：接入网设备，所述接入网设备用于执行如权利要求11至16、20至23中任一项所述的方法。
  36. 根据权利要求35所述的通信系统，其特征在于，所述接入网设备用于执行如权利要求11至16中任一项所述的方法，所述通信系统还包括核心网设备，所述核心网设备用于执行如权利要求1至10中任一项所述的方法。
  37. 一种通信系统，其特征在于，包括：终端，所述终端用于执行如权利要求24至30中任一项所述的方法。
PCT/CN2023/111503 2022-08-09 2023-08-07 一种通信方法和通信装置 WO2024032555A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210952997.5A CN117641624A (zh) 2022-08-09 2022-08-09 一种通信方法和通信装置
CN202210952997.5 2022-08-09

Publications (1)

Publication Number Publication Date
WO2024032555A1 true WO2024032555A1 (zh) 2024-02-15

Family

ID=89850871

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/111503 WO2024032555A1 (zh) 2022-08-09 2023-08-07 一种通信方法和通信装置

Country Status (3)

Country Link
CN (1) CN117641624A (zh)
TW (1) TW202408256A (zh)
WO (1) WO2024032555A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108307507A (zh) * 2016-08-11 2018-07-20 株式会社Kt 用于接收多播数据的方法及其设备
CN113303025A (zh) * 2019-01-18 2021-08-24 苹果公司 基于受支持的蜂窝物联网(ciot)特征选择核心网络
CN114340043A (zh) * 2020-10-09 2022-04-12 华为技术有限公司 一种通信方法及设备
WO2022133992A1 (zh) * 2020-12-25 2022-06-30 北京小米移动软件有限公司 终端控制、信息处理方法及装置、通信设备及存储介质
WO2022141139A1 (zh) * 2020-12-30 2022-07-07 捷开通讯(深圳)有限公司 一种通信方法及用户设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108307507A (zh) * 2016-08-11 2018-07-20 株式会社Kt 用于接收多播数据的方法及其设备
CN113303025A (zh) * 2019-01-18 2021-08-24 苹果公司 基于受支持的蜂窝物联网(ciot)特征选择核心网络
CN114340043A (zh) * 2020-10-09 2022-04-12 华为技术有限公司 一种通信方法及设备
WO2022133992A1 (zh) * 2020-12-25 2022-06-30 北京小米移动软件有限公司 终端控制、信息处理方法及装置、通信设备及存储介质
WO2022141139A1 (zh) * 2020-12-30 2022-07-07 捷开通讯(深圳)有限公司 一种通信方法及用户设备

Also Published As

Publication number Publication date
CN117641624A (zh) 2024-03-01
TW202408256A (zh) 2024-02-16

Similar Documents

Publication Publication Date Title
CN112514422B (zh) 支持组通信的系统与方法
WO2022170819A1 (zh) 用于实现多播广播业务切换的方法及相关设备
US20230077191A1 (en) Method for implementing multicast broadcast service handover and related device
WO2022016948A1 (zh) 一种通信方法及装置
WO2022017285A1 (zh) 报文转发方法、装置及系统
US20230232196A1 (en) Data communication method and communication apparatus
US20230388863A1 (en) Communication method and apparatus
JP2023535041A (ja) データ送信方法、装置、およびシステム
WO2022033543A1 (zh) 一种中继通信方法及通信装置
WO2021163894A1 (zh) 一种基于中继的通信方法及装置
US20230371098A1 (en) Communication method, apparatus, and system
WO2022213799A1 (zh) 一种多播业务的通信方法及装置
WO2024032555A1 (zh) 一种通信方法和通信装置
WO2023000884A1 (zh) 多播会话处理方法、网络功能实体、装置及存储介质
WO2021147672A1 (zh) 会话处理方法及通信装置
AU2022278101A1 (en) Service data transmission method and communication apparatus
WO2023169225A1 (zh) 一种pin管理方法、通信装置及通信系统
WO2023207357A1 (zh) 一种通信方法和通信装置
WO2024074148A1 (zh) 通信方法、装置及系统
WO2023197737A1 (zh) 报文发送方法、pin管理方法、通信装置及通信系统
WO2023231032A1 (zh) 非激活态组播业务区域的确定方法、配置方法、及装置
WO2023066021A1 (zh) 一种通信方法、装置及设备
WO2023237046A1 (zh) 一种iab节点的移动性管理方法及相关设备
WO2023246427A1 (zh) 一种测距方法和通信装置
WO2023137579A1 (zh) 紧急业务的提供方法、装置、设备及存储介质

Legal Events

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

Ref document number: 23851776

Country of ref document: EP

Kind code of ref document: A1