Communication control method and apparatus, and communication device and storage medium

Abstract

The present disclosure relates to the technical field of communications, and particularly relates to a communication control method and apparatus, and a communication device and a storage medium. The communication control method comprises: receiving a first message sent by a network device; and determining a processing mode for a multicast service configuration on the basis of the first message. On the basis of the present disclosure, a terminal can receive a first message from a network device, and then determine a processing mode for a multicast service configuration on the basis of the first message. On this basis, it can be ensured that the terminal can determine how to process the multicast service configuration, thereby avoiding the situation where a problem occurs in an operation of the terminal when same has not clearly determined how to process the multicast service configuration.

Description

Communication control method, device, communication equipment and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a communication control method, a communication control apparatus, a terminal, a network device, a communication device, and a storage medium. Background Art

[0002] In some communication scenarios, a terminal can perform multicast services with a network device, for example, a terminal can receive multicast services. The network device can activate or deactivate the multicast services, but deactivating the multicast services presents some technical challenges that need to be addressed.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a communication control method, apparatus, communication device, and storage medium to solve technical problems in related technologies.

[0005] According to a first aspect of an embodiment of the present disclosure, a communication control method is proposed, the method comprising: receiving a first message sent by a network device, and determining a processing method for a multicast service configuration according to the first message.

[0006] According to a second aspect of an embodiment of the present disclosure, a communication control method is proposed, the method comprising: sending a first message to a terminal, wherein the first message is used by the terminal to determine a processing method for multicast service configuration.

[0007] According to the third aspect of an embodiment of the present disclosure, a terminal is proposed, comprising: one or more processors; a memory coupled to the one or more processors, wherein the memory stores executable instructions, and when the executable instructions are executed by the one or more processors, the terminal executes the communication control method described in the first aspect.

[0008] According to the fourth aspect of an embodiment of the present disclosure, a network device is proposed, comprising: one or more processors; a memory coupled to the one or more processors, wherein the memory stores executable instructions, and when the executable instructions are executed by the one or more processors, the network device executes the communication control method described in the second aspect.

[0009] According to a fifth aspect of an embodiment of the present disclosure, a communication control device is proposed, including: a transceiver module for receiving a first message sent by a network device; and a processing module for determining a processing method for a multicast service configuration based on the first message.

[0010] According to a sixth aspect of an embodiment of the present disclosure, a communication control device is proposed, including: a transceiver module, configured to send a first message to a terminal, wherein the first message is used by the terminal to determine a processing method for a multicast service configuration.

[0011] According to the seventh aspect of an embodiment of the present disclosure, a communication device is proposed, comprising: one or more processors; wherein the processor is used to call instructions so that the communication device executes the communication control method described in any one of the first aspect and the second aspect.

[0012] According to an eighth aspect of an embodiment of the present disclosure, a communication system is proposed, comprising a terminal and a network device, wherein the terminal is configured to implement the communication control method described in the first aspect, and the network device is configured to implement the communication control method described in the second aspect.

[0013] According to a ninth aspect of an embodiment of the present disclosure, a storage medium is proposed, wherein the storage medium stores instructions. When the instructions are executed on a communication device, the communication device executes the communication control method described in any one of the first and second aspects.

[0014] According to an embodiment of the present disclosure, a terminal can determine how to handle a multicast service configuration based on a first message received from a network device. This ensures that the terminal can determine how to handle the multicast service configuration, avoiding operational issues when the terminal does not clearly determine how to handle the multicast service configuration. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0016] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0017] FIG2 is an interactive schematic diagram showing a communication control method according to an embodiment of the present disclosure.

[0018] FIG3 is a schematic flowchart showing a communication control method according to an embodiment of the present disclosure.

[0019] FIG4 is a schematic flowchart showing a communication control method according to an embodiment of the present disclosure.

[0020] FIG5 is a schematic block diagram of a communication control device according to an embodiment of the present disclosure.

[0021] FIG6 is a schematic block diagram of a communication control device according to an embodiment of the present disclosure.

[0022] FIG7 is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure.

[0023] FIG8 is a schematic diagram of the structure of a chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0024] Embodiments of the present disclosure provide a communication control method, apparatus, communication device, and storage medium.

[0025] In a first aspect, an embodiment of the present disclosure proposes a communication control method, the method comprising: receiving a first message sent by a network device, and determining a processing method for a multicast service configuration according to the first message.

[0026] In the above embodiment, the terminal can determine how to handle the multicast service configuration based on the first message received from the network device. This ensures that the terminal can determine how to handle the multicast service configuration, avoiding operational problems when the terminal does not clearly determine how to handle the multicast service configuration.

[0027] In conjunction with some embodiments of the first aspect, in some embodiments, the first message is used to instruct the terminal to deactivate the multicast service session.

[0028] In combination with some embodiments of the first aspect, in some embodiments, determining a processing method for the multicast service configuration according to the first message includes at least one of the following:

[0029] The first message provides a first multicast service configuration, and the first multicast service configuration is stored;

[0030] The first message does not provide the first multicast service configuration, and the first operation is performed.

[0031] In conjunction with some embodiments of the first aspect, in some embodiments, storing the first multicast service configuration includes at least one of the following:

[0032] The terminal has stored a second multicast service configuration, and the first multicast service configuration is used to overwrite the second multicast service configuration; or,

[0033] When the terminal has stored a second multicast service configuration, and the second multicast service configuration is the same as the first multicast service configuration, retaining the first multicast service configuration or retaining the second multicast service configuration; or,

[0034] The terminal does not store the second multicast service configuration, but stores the first multicast service configuration.

[0035] In the above embodiment, when the first multicast service configuration is provided in the first message, the terminal will eventually store the multicast service configuration. Accordingly, when the subsequent network device activates the multicast service, the terminal can receive the multicast service based on the stored multicast service configuration, which is conducive to ensuring the continuity of receiving the multicast service and further conducive to ensuring good communication quality.

[0036] In combination with some embodiments of the first aspect, in some embodiments, the first operation includes: releasing the second multicast service configuration stored by the terminal, or retaining the second multicast service configuration stored by the terminal.

[0037] In combination with some embodiments of the first aspect, in some embodiments, the first operation is performed according to at least one of the following: a multicast service field; a protocol agreement; or a network device indication.

[0038] In combination with some embodiments of the first aspect, in some embodiments, the performing of the first operation includes: releasing the second multicast service configuration when the multicast service field corresponds to the first requirement code.

[0039] In combination with some embodiments of the first aspect, in some embodiments, the performing of the first operation includes: the multicast service field corresponds to a second requirement code, and determining to release or retain the second multicast service configuration according to a protocol agreement or a network device instruction.

[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the first message is used to provide a first multicast service configuration, and the second message is used to provide a second multicast service configuration.

[0041] In combination with some embodiments of the first aspect, in some embodiments, the first message and the second message are of the same type, or the first message and the second message are of different types.

[0042] In combination with some embodiments of the first aspect, in some embodiments, the type includes at least one of the following: a broadcast message, and proprietary signaling.

[0043] In combination with some embodiments of the first aspect, in some embodiments, the broadcast message includes at least one of the following: system information; a multicast service control channel message; or a paging message.

[0044] In a second aspect, an embodiment of the present disclosure proposes a communication control method, the method comprising: sending a first message to a terminal, wherein the first message is used by the terminal to determine a processing method for multicast service configuration.

[0045] In the above embodiment, the network device can send a first message to the terminal. The first message can be used by the terminal to determine how to handle the multicast service configuration. After receiving the first message from the network device, the terminal can determine how to handle the multicast service configuration based on the first message. This ensures that the terminal can determine how to handle the multicast service configuration, avoiding operational issues when the terminal does not clearly determine how to handle the multicast service configuration.

[0046] In combination with some embodiments of the second aspect, in some embodiments, the first message is used to instruct the terminal to deactivate the multicast service session.

[0047] In conjunction with some embodiments of the second aspect, in some embodiments, the first message is used by the terminal to determine a processing method for the multicast service configuration, including at least one of the following:

[0048] The first message provides a first multicast service configuration, and the terminal stores the first multicast service configuration;

[0049] The first message does not provide the first multicast service configuration, and the terminal performs a first operation.

[0050] In conjunction with some embodiments of the second aspect, in some embodiments, storing the first multicast service configuration includes at least one of the following:

[0051] The terminal has stored a second multicast service configuration, and the first multicast service configuration is used to overwrite the second multicast service configuration; or,

[0052] When the terminal has stored a second multicast service configuration, and the second multicast service configuration is the same as the first multicast service configuration, retaining the first multicast service configuration or retaining the second multicast service configuration; or

[0053] The terminal does not store the second multicast service configuration, but stores the first multicast service configuration.

[0054] In the above embodiment, when the first multicast service configuration is provided in the first message, the terminal can eventually store the multicast service configuration. Accordingly, when the subsequent network device activates the multicast service, the terminal can receive the multicast service based on the stored multicast service configuration, which is conducive to ensuring the continuity of receiving the multicast service and further conducive to ensuring good communication quality.

[0055] In conjunction with some embodiments of the second aspect, in some embodiments, the first operation includes: releasing the second multicast service configuration stored by the terminal, or retaining the second multicast service configuration stored by the terminal.

[0056] In combination with some embodiments of the second aspect, in some embodiments, the first operation is performed according to at least one of the following: a multicast service field; a protocol agreement; or a network device indication.

[0057] In conjunction with some embodiments of the second aspect, in some embodiments, the first operation includes: releasing the second multicast service configuration when the multicast service field corresponds to the first requirement code.

[0058] In conjunction with some embodiments of the second aspect, in some embodiments, the first operation includes: the multicast service field corresponds to a second requirement code, and the terminal determines to release or retain the second multicast service configuration according to a protocol agreement or an instruction from a network device.

[0059] In conjunction with some embodiments of the second aspect, in some embodiments, the first message is used to provide a first multicast service configuration, and the second message is used to provide a second multicast service configuration.

[0060] In conjunction with some embodiments of the second aspect, in some embodiments, the first message and the second message are of the same type, or the first message and the second message are of different types.

[0061] In conjunction with some embodiments of the second aspect, in some embodiments, the type includes at least one of the following: a broadcast message, and proprietary signaling.

[0062] In conjunction with some embodiments of the second aspect, in some embodiments, the broadcast message includes at least one of the following: system information; a multicast service control channel message; or a paging message.

[0063] In a third aspect, an embodiment of the present disclosure proposes a terminal comprising: one or more processors; a memory coupled to the one or more processors, the memory storing executable instructions, which, when executed by the one or more processors, enables the terminal to execute the communication control method described in any one of the first aspect and the optional embodiments of the first aspect.

[0064] In a fourth aspect, an embodiment of the present disclosure proposes a network device, comprising: one or more processors; a memory coupled to the one or more processors, the memory storing executable instructions, which, when executed by the one or more processors, enables the network device to execute the communication control method described in any one of the second aspect and the optional embodiments of the second aspect.

[0065] In a fifth aspect, an embodiment of the present disclosure proposes a communication control device, comprising: a transceiver module for receiving a first message sent by a network device; and a processing module for determining a processing method for a multicast service configuration based on the first message.

[0066] In a sixth aspect, an embodiment of the present disclosure proposes a communication control device, comprising: a transceiver module, configured to send a first message to a terminal, wherein the first message is used by the terminal to determine a processing method for a multicast service configuration.

[0067] In the seventh aspect, an embodiment of the present disclosure proposes a communication device, which includes: one or more processors; one or more memories for storing instructions; wherein the processor is used to call the instructions so that the communication device executes the communication control method described in the first and second aspects, and the optional embodiments of the first and second aspects.

[0068] In the eighth aspect, an embodiment of the present disclosure proposes a communication system, which includes: a terminal and a network device; wherein the terminal is configured to execute the method described in the first aspect and the optional embodiment of the first aspect, and the network device is configured to execute the method described in the second aspect and the optional embodiment of the second aspect.

[0069] In the ninth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first and second aspects, and the optional embodiments of the first and second aspects.

[0070] In a tenth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the first and second aspects, and the optional embodiments of the first and second aspects.

[0071] In an eleventh aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the methods described in the first and second aspects, and the optional embodiments of the first and second aspects.

[0072] It is understandable that the above-mentioned terminals, network devices, communication control devices, communication devices, communication systems, storage media, program products, and computer programs are all used to execute the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0073] The present disclosure provides a communication control method, apparatus, communication device, and storage medium. In some embodiments, the terms "communication control method," "information processing method," and "communication method" are interchangeable; the terms "communication control apparatus," "information processing apparatus," and "communication apparatus" are interchangeable; and the terms "information processing system," "communication system," and "communication system" are interchangeable.

[0074] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional embodiments in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional embodiments of other embodiments.

[0075] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0076] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0077] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular form, such as "a", "an", "the", "above", "said", "aforementioned", "this", etc., may mean "one and only one", or "one or more", "at least one", etc.

[0078] For example, when using articles such as “a”, “an”, and “the” in English in translation, the noun following the article can be understood as a singular expression or a plural expression.

[0079] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0080] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0081] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0082] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0083] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restrictions on the position, order, priority, quantity or content of the description objects. For the statement of the description objects, please refer to the description in the context of the claims or embodiments, and no unnecessary restrictions should be constituted due to the use of prefixes.

[0084] For example, if the description object is "field," the ordinal number preceding "field" in "first field" and "second field" does not restrict the position or order of the "fields." "First" and "second" do not restrict whether the modified "fields" are in the same message, nor do they restrict the order of the "first field" and "second field." For another example, if the description object is "level," the ordinal number preceding "level" in "first level" and "second level" does not restrict the priority of the "levels." For another example, the number of description objects is not restricted by the ordinal number and can be one or more. For example, in the case of "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the description object is "device," "first device" and "second device" can be the same or different devices, and their types can be the same or different. For another example, if the description object is "information," "first information" and "second information" can be the same or different information, and their content can be the same or different.

[0085] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0086] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0087] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0088] In some embodiments, devices and the like can be interpreted as physical or virtual, and their names are not limited to those in the embodiments.

[0089] The recorded names, "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject" and other terms can be used interchangeably.

[0090] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0091] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0092] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0093] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0094] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0095] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0096] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0097] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0098] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0099] As shown in FIG1 , a communication system 100 includes a terminal 101 and a network device 102 , wherein the network device includes at least one of the following: an access network device and a core network device.

[0100] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0101] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0102] In some embodiments, a core network device may be a device including one or more network elements, or may be multiple devices or device groups, each including all or part of the one or more network elements. The network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0103] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0104] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0105] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0106] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0107] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0108] FIG2 is an interactive schematic diagram showing a communication control method according to an embodiment of the present disclosure.

[0109] As shown in FIG2 , the communication control method may include the following steps:

[0110] Step S201: The network device sends a first message to the terminal.

[0111] In some embodiments, the terminal receives a first message sent by the network device.

[0112] In some embodiments, the first message is used by the terminal to determine a processing method for the multicast service configuration.

[0113] In some embodiments, the first message is used to instruct the terminal to deactivate the multicast service session.

[0114] Step S202: The terminal determines a processing method for the multicast service configuration according to the first message.

[0115] In some embodiments, the terminal determines, based on the first message, a processing method for the multicast service configuration, including at least one of the following:

[0116] The first message provides a first multicast service configuration, and the first multicast service configuration is stored;

[0117] The first message does not provide the first multicast service configuration, and the first operation is performed.

[0118] In some embodiments, the terminal stores the first multicast service configuration, including at least one of the following:

[0119] The terminal has stored the second multicast service configuration and the second multicast service configuration is overwritten by the first multicast service configuration; or, if the terminal has stored the second multicast service configuration and the second multicast service configuration is the same as the first multicast service configuration, the first multicast service configuration is retained or the second multicast service configuration is retained; or, if the terminal does not store the second multicast service configuration, the first multicast service configuration is stored.

[0120] In some embodiments, when the multicast service field of the terminal corresponds to the first requirement code, the second multicast service configuration released includes at least one of the following: a second multicast service provided by a broadcast message; a second multicast service provided by proprietary signaling.

[0121] For example, when the multicast service field of the terminal corresponds to the first requirement code, the terminal releases the second multicast service configuration, for example, the second multicast service configuration provided by the MCCH message can be released. This release method is the same as that agreed in the existing protocol, so this processing method for the second multicast service does not require adjusting the existing protocol.

[0122] For example, when the multicast service field of the terminal corresponds to the first requirement code, the second multicast service configuration is released. For example, the second multicast service configuration provided by the proprietary signaling can be released. This release method is different from the method agreed upon in the existing protocol, so this method of handling the second multicast service can be achieved by adjusting the existing protocol (for example, adjusting the description of the multicast service field in the existing protocol or modifying the existing protocol process description).

[0123] In some embodiments, the first operation includes: releasing the second multicast service configuration stored by the terminal, or retaining the second multicast service configuration stored by the terminal.

[0124] For example, when the requirement code corresponding to the multicast service field is the second requirement code, and the protocol stipulates that the second multicast service configuration needs to be released in this case, the terminal may release the second multicast service configuration.

[0125] For example, when the requirement code corresponding to the multicast service field is the second requirement code, and the protocol agreement (such as setting the protocol description of the multicast service field or modifying the existing protocol process description) requires retaining the second multicast service configuration in this case, then the terminal can retain the second multicast service configuration.

[0126] For example, when the requirement code corresponding to the multicast service field is the second requirement code, and the network device indicates that the second multicast service configuration needs to be released in this case, the terminal may release the second multicast service configuration.

[0127] For example, when the requirement code corresponding to the multicast service field is the second requirement code, and the network device indicates that the second multicast service configuration needs to be retained in this case, the terminal may retain the second multicast service configuration.

[0128] In some embodiments, the first operation is performed according to at least one of the following: a multicast service field; a protocol agreement; and a network device indication.

[0129] In some embodiments, the terminal performs a first operation, including: corresponding to the first requirement code in the multicast service field, releasing the second multicast service configuration.

[0130] In some embodiments, the terminal performs a first operation, including: corresponding to the second requirement code in the multicast service field, and determining to release or retain the second multicast service configuration according to a protocol agreement or an instruction of a network device.

[0131] In some embodiments, the first message is used to provide a first multicast service configuration, and the second message is used to provide a second multicast service configuration.

[0132] In some embodiments, the first message and the second message are of the same type, or the first message and the second message are of different types.

[0133] In some embodiments, the type includes at least one of: a broadcast message, proprietary signaling.

[0134] In some embodiments, the broadcast message includes at least one of the following: system information; multicast service control channel message; paging message.

[0135] In some embodiments, the dedicated signaling includes at least one of the following: radio resource control signaling, downlink control information; and media access control elements.

[0136] The communication method involved in the embodiments of the present disclosure may include at least one of steps S201 and S202. For example, step S201 may be implemented as an independent embodiment, step S202 may be implemented as an independent embodiment, and steps S201+S202 may be implemented as independent embodiments, but are not limited thereto.

[0137] In some embodiments, steps S201 and S202 may be performed in an interchangeable order or simultaneously.

[0138] In some embodiments, step S201 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0139] In some embodiments, step S202 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0140] In some embodiments, reference may be made to other optional embodiments described before or after the description corresponding to FIG. 2 .

[0141] In some embodiments, the terminal can receive a multicast service, for example, according to a multicast service configuration, where the multicast service configuration may also be referred to as a Point to Multipoint (PTM) configuration.

[0142] For example, a multicast service may be identified by at least one of the following: a temporary mobile group identity (TMGI), a multicast broadcast service session identifier (MBS Session ID), and a multicast broadcast service quality of service flow identifier (MBS QoS flow ID), where MBS stands for multicast broadcast service and QoS stands for quality of service.

[0143] In some embodiments, the multicast service may be sent in a multicast manner, and the terminal may receive the multicast service sent in a multicast manner by the network device according to the multicast service configuration in a connected (CONNECTED) state.

[0144] In some embodiments, the multicast service may be sent in a broadcast manner, and the terminal may receive the multicast service sent by the network device in a broadcast manner according to the multicast service configuration in a connected state or a non-connected state.

[0145] The non-connected state includes at least one of the following: an idle state and an inactive state.

[0146] In some embodiments, the terminal may receive the multicast service configuration via dedicated signaling in a connected state, and then receive the multicast service according to the multicast service configuration. In some embodiments, the terminal may receive the multicast service configuration via a broadcast message in a non-connected state, and then receive the multicast service according to the multicast service configuration.

[0147] For example, the multicast service configuration includes MBS configuration, and the broadcast message may include a multicast service control channel (eg, MBS Transmission Channel, MCCH) message.

[0148] In some embodiments, the network device can deactivate the multicast service, and the terminal can stop listening to the Group Radio Network Temporary Indentifier (G-RNTI) to stop receiving the multicast service. However, the handling method for multicast service configuration has not yet been determined.

[0149] In a first aspect, embodiments of the present disclosure provide a communication control method. Figure 3 is a schematic flow chart illustrating a communication control method according to an embodiment of the present disclosure. The communication control method illustrated in this embodiment can be executed by a terminal.

[0150] As shown in FIG3 , the communication control method may include the following steps:

[0151] In step S301, a first message sent by a network device is received;

[0152] In step S302, a processing method for the multicast service configuration is determined according to the first message.

[0153] It should be noted that the embodiment shown in FIG. 3 can be implemented independently or in combination with at least one other embodiment in the present disclosure. The specific selection can be made as needed and the present disclosure does not limit it.

[0154] In some embodiments, the terminal may determine how to handle the multicast service configuration based on a first message received from the network device. This ensures that the terminal can determine how to handle the multicast service configuration, thereby avoiding operational problems when the terminal does not clearly determine how to handle the multicast service configuration.

[0155] In some embodiments, the multicast service in the embodiments of the present disclosure may include a non-connected multicast service, such as an inactive multicast service. Of course, it is not limited thereto, and may also include a connected multicast service, an idle multicast service, etc.

[0156] In some embodiments, a processing method for the multicast service configuration is determined according to the first message, wherein the multicast service configuration includes at least one of the following: a first multicast service configuration carried in the first message; a second multicast service configuration stored in the terminal.

[0157] For example, the terminal may determine, based on the first message, how to process the first multicast service configuration provided in the first message; for example, the terminal may determine, based on the first message, how to process the second multicast service configuration stored in the terminal.

[0158] In some embodiments, the first message is used to instruct the terminal to deactivate the multicast service session.

[0159] When the terminal determines according to the first message that the multicast service session needs to be deactivated, the terminal may stop monitoring the G-RNTI, thereby stopping receiving the multicast service, and may also determine a processing method for the multicast service configuration according to the first message.

[0160] In some embodiments, determining, according to the first message, a processing manner for the multicast service configuration includes at least one of the following:

[0161] The first message provides a first multicast service configuration, and the first multicast service configuration is stored;

[0162] The first message does not provide the first multicast service configuration, and the first operation is performed.

[0163] For example, the terminal determines the processing manner of the multicast service configuration according to the first message, and may store the first multicast service configuration provided in the first message when the first multicast service configuration is provided in the first message.

[0164] For example, the terminal determines the processing mode of the multicast service configuration according to the first message, and may perform the first operation when the first multicast service configuration is not provided in the first message.

[0165] In some embodiments, storing the first multicast service configuration includes at least one of the following: the terminal has stored the second multicast service configuration, and the second multicast service configuration is overwritten by the first multicast service configuration; or, the terminal has stored the second multicast service configuration, and when the second multicast service configuration is the same as the first multicast service configuration, retaining the first multicast service configuration or retaining the second multicast service configuration; or, the terminal has not stored the second multicast service configuration, and stores the first multicast service configuration.

[0166] In some embodiments, when the first multicast service configuration is provided in the first message, the terminal may store the first multicast service configuration. It may also be further considered whether the terminal has stored the second multicast service configuration.

[0167] For example, when a terminal has stored a second multicast service configuration, the terminal may overwrite the second multicast service configuration with the first multicast service configuration, for example, by storing the first multicast service configuration and releasing the second multicast service configuration. For example, storing the first multicast service configuration may be described as setting up the first multicast service configuration, and releasing the second multicast service configuration may be described as releasing the second multicast service configuration.

[0168] For example, when the terminal has stored a second multicast service configuration, and the stored second multicast service configuration is the same as the first multicast service configuration provided by the first message, the terminal can retain the first multicast service configuration and further release the second multicast service configuration; or, the terminal retains the second multicast service configuration and ignores the first multicast service configuration. Since the second multicast service configuration is the same as the first multicast service configuration, this situation can also be regarded as retaining the first multicast service configuration.

[0169] For example, when the terminal does not store the second multicast service configuration, the terminal may store the first multicast service configuration carried by the first message.

[0170] It can be seen that in the above embodiment, when the first multicast service configuration is provided in the first message, the terminal will eventually store the multicast service configuration. Accordingly, when the subsequent network device activates the multicast service, the terminal can receive the multicast service based on the stored multicast service configuration, which is conducive to ensuring the continuity of receiving the multicast service, and further conducive to ensuring good communication quality.

[0171] In some embodiments, the first operation includes: releasing the second multicast service configuration stored by the terminal, or retaining the second multicast service configuration stored by the terminal.

[0172] In some embodiments, if the first multicast service configuration is not provided in the first message, the terminal performs a first operation, which may be, for example, releasing the second multicast service configuration stored by the terminal, or retaining the second multicast service configuration stored by the terminal. Whether to release or retain the second multicast service configuration stored by the terminal will be described in detail in subsequent embodiments.

[0173] In some embodiments, the first operation is performed according to at least one of the following: a multicast service field; a protocol agreement; and a network device indication.

[0174] In some embodiments, when the first multicast service configuration is not provided in the first message, the terminal may perform the first operation based on at least one of a multicast service field, a protocol agreement, and a network device indication.

[0175] For example, the terminal may perform the first operation based on the multicast service field, the multicast service field and a protocol, or the multicast service field and a network device, and the present disclosure does not limit this. The following describes several exemplary embodiments of the terminal performing the first operation.

[0176] In some embodiments, performing the first operation includes: corresponding to the first requirement code in the multicast service field, releasing the second multicast service configuration stored in the terminal.

[0177] For example, the terminal may perform the first operation based on the multicast service field. The terminal may first determine the need code corresponding to the multicast service field. When the need code corresponding to the multicast service field is determined to be the first need code, for example, the first need code includes need R, the terminal may release the second multicast service configuration.

[0178] It should be noted that the requirement code corresponding to the multicast service field can be the requirement code corresponding to the multicast service configuration field, for example, the requirement code corresponding to at least one information element (IE) in the multicast service configuration field. Each optional information element must be associated with a requirement code to determine the terminal's behavior when the information element is not provided.

[0179] In some embodiments, when the multicast service field of the terminal corresponds to the first requirement code, the second multicast service configuration released includes at least one of the following: a second multicast service provided by a broadcast message; a second multicast service provided by proprietary signaling.

[0180] For example, when the multicast service field of the terminal corresponds to the first requirement code, the terminal releases the second multicast service configuration, for example, the second multicast service configuration provided by the MCCH message can be released. This release method is the same as that agreed in the existing protocol, so this processing method for the second multicast service does not require adjusting the existing protocol.

[0181] For example, when the multicast service field of the terminal corresponds to the first requirement code, the second multicast service configuration is released. For example, the second multicast service configuration provided by the proprietary signaling can be released. This release method is different from the method agreed upon in the existing protocol, so this method of handling the second multicast service can be achieved by adjusting the existing protocol (for example, adjusting the description of the multicast service field in the existing protocol or modifying the existing protocol process description).

[0182] In some embodiments, performing the first operation includes: the multicast service field corresponds to the second requirement code, and the terminal determines to release or retain the second multicast service configuration stored in the terminal according to a protocol agreement or an instruction of a network device.

[0183] For example, the terminal may perform the first operation based on the multicast service field. The terminal may first determine the need code corresponding to the multicast service field. When it is determined that the need code corresponding to the multicast service field is a second need code, for example, the second need code includes need S, the terminal may release the second multicast service configuration or retain the second multicast service configuration.

[0184] For example, when the requirement code corresponding to the multicast service field is the second requirement code, and the protocol stipulates that the second multicast service configuration needs to be released in this case, the terminal may release the second multicast service configuration.

[0185] For example, when the requirement code corresponding to the multicast service field is the second requirement code, and the protocol agreement (such as setting the protocol description of the multicast service field or modifying the existing protocol process description) requires retaining the second multicast service configuration in this case, then the terminal can retain the second multicast service configuration.

[0186] For example, when the requirement code corresponding to the multicast service field is the second requirement code, and the network device indicates that the second multicast service configuration needs to be released in this case, the terminal may release the second multicast service configuration.

[0187] For example, when the requirement code corresponding to the multicast service field is the second requirement code, and the network device indicates that the second multicast service configuration needs to be retained in this case, the terminal may retain the second multicast service configuration.

[0188] It should be noted that, regardless of whether the first message provides the first multicast service configuration, the first message still contains the multicast service configuration field. However, the value of the multicast service field may be different when the first multicast service configuration is provided or not.

[0189] In some embodiments, the first message is used to provide a first multicast service configuration, and the second message is used to provide a second multicast service configuration.

[0190] In some embodiments, the first message and the second message are of the same type, or the first message and the second message are of different types.

[0191] In some embodiments, the type includes at least one of: a broadcast message, proprietary signaling.

[0192] In some embodiments, the broadcast message includes at least one of the following: system information; a multicast traffic control channel MCCH message; or a paging message. The system information may include, for example, a system information block (SIB), which may be an existing SIB or a newly defined SIB.

[0193] In some embodiments, the dedicated signaling includes at least one of the following: Radio Resource Control (RRC) signaling, Downlink Control Information (DCI); and Media Access Control Control Element (MAC CE).

[0194] For example, the first message may be an MCCH message for providing a first multicast service configuration, and the second message may be RRC signaling for providing a second multicast service configuration. For example, the first message may be an MCCH message for providing a first multicast service configuration, and the second message may also be an MCCH message for providing a second multicast service configuration. The two MCCH messages may be MCCH messages received at different times.

[0195] In a second aspect, embodiments of the present disclosure provide a communication control method. Figure 4 is a schematic flow chart illustrating a communication control method according to an embodiment of the present disclosure. The communication control method illustrated in this embodiment can be executed by a network device.

[0196] As shown in FIG4 , the communication control method may include the following steps:

[0197] In step S401, a first message is sent to a terminal, wherein the first message is used by the terminal to determine a processing method for multicast service configuration.

[0198] In some embodiments, a network device may send a first message to a terminal. The first message may be used by the terminal to determine how to handle the multicast service configuration. After receiving the first message from the network device, the terminal may determine how to handle the multicast service configuration based on the first message. This ensures that the terminal can determine how to handle the multicast service configuration, avoiding operational issues when the terminal does not clearly determine how to handle the multicast service configuration.

[0199] In some embodiments, the multicast service in the embodiments of the present disclosure may include a non-connected multicast service, such as an inactive multicast service. Of course, it is not limited thereto, and may also include a connected multicast service, an idle multicast service, etc.

[0200] In some embodiments, the first message is used by the terminal to determine a processing method for the multicast service configuration, wherein the multicast service configuration includes at least one of the following: a first multicast service configuration carried in the first message; a second multicast service configuration stored in the terminal.

[0201] For example, the terminal may determine, based on the first message, how to process the first multicast service configuration provided in the first message; for example, the terminal may determine, based on the first message, how to process the second multicast service configuration stored in the terminal.

[0202] In some embodiments, the first message is used to instruct the terminal to deactivate the multicast service session.

[0203] When the terminal determines according to the first message that the multicast service session needs to be deactivated, the terminal may stop monitoring the G-RNTI, thereby stopping receiving the multicast service, and may also determine a processing method for the multicast service configuration according to the first message.

[0204] In some embodiments, the first message is used by the terminal to determine a processing method for the multicast service configuration, including at least one of the following:

[0205] The first message provides a first multicast service configuration, and the terminal stores the first multicast service configuration;

[0206] The first message does not provide the first multicast service configuration, and the terminal performs the first operation.

[0207] For example, the first message is used by the terminal to determine a processing method for the multicast service configuration. When the first multicast service configuration is provided in the first message, the terminal stores the first multicast service configuration provided in the first message.

[0208] For example, the first message is used by the terminal to determine how to process the multicast service configuration. If the first multicast service configuration is not provided in the first message, the terminal performs the first operation. The implementation of the first operation will be described in subsequent embodiments and will not be described here.

[0209]

[0210] In some embodiments, storing the first multicast service configuration includes at least one of the following:

[0211] The terminal has stored the second multicast service configuration, and the first multicast service configuration is used to overwrite the second multicast service configuration; or,

[0212] If the terminal has stored the second multicast service configuration and the second multicast service configuration is the same as the first multicast service configuration, retain the first multicast service configuration or retain the second multicast service configuration; or,

[0213] The terminal does not store the second multicast service configuration, but stores the first multicast service configuration.

[0214] In some embodiments, when the first multicast service configuration is provided in the first message, the terminal may store the first multicast service configuration. It may also be further considered whether the terminal has stored the second multicast service configuration.

[0215] For example, when a terminal has stored a second multicast service configuration, the terminal may overwrite the second multicast service configuration with the first multicast service configuration, for example, by storing the first multicast service configuration and releasing the second multicast service configuration. For example, storing the first multicast service configuration may be described as setting up the first multicast service configuration, and releasing the second multicast service configuration may be described as releasing the second multicast service configuration.

[0216] For example, when the terminal has stored a second multicast service configuration, and the stored second multicast service configuration is the same as the first multicast service configuration provided by the first message, the terminal can retain the first multicast service configuration and further release the second multicast service configuration; or, the terminal retains the second multicast service configuration and ignores the first multicast service configuration. Since the second multicast service configuration is the same as the first multicast service configuration, this situation can also be regarded as retaining the first multicast service configuration.

[0217] For example, when the terminal does not store the second multicast service configuration, the terminal may store the first multicast service configuration carried by the first message.

[0218] It can be seen that in the above embodiment, when the first multicast service configuration is provided in the first message, the terminal can eventually store the multicast service configuration. Accordingly, when the subsequent network device activates the multicast service, the terminal can receive the multicast service based on the stored multicast service configuration, which is conducive to ensuring the continuity of receiving the multicast service, and further conducive to ensuring good communication quality.

[0219] In some embodiments, the first operation includes: releasing the second multicast service configuration stored by the terminal, or retaining the second multicast service configuration stored by the terminal.

[0220] In some embodiments, if the first multicast service configuration is not provided in the first message, the terminal performs a first operation, which may be, for example, releasing the second multicast service configuration stored by the terminal, or retaining the second multicast service configuration stored by the terminal. Whether to release or retain the second multicast service configuration stored by the terminal will be described in detail in subsequent embodiments.

[0221] In some embodiments, the first operation is performed according to at least one of the following: a multicast service field; a protocol agreement; and a network device indication.

[0222] In some embodiments, when the first multicast service configuration is not provided in the first message, the terminal may perform the first operation based on at least one of a multicast service field, a protocol agreement, and a network device indication.

[0223] For example, the terminal may perform the first operation based on the multicast service field, the multicast service field and a protocol, or the multicast service field and a network device, and the present disclosure does not limit this. The following describes several exemplary embodiments of the terminal performing the first operation.

[0224] In some embodiments, the first operation includes: the multicast service field corresponds to the first requirement code, and the terminal releases the second multicast service configuration stored therein.

[0225] For example, the terminal may perform the first operation based on the multicast service field. The terminal may first determine the need code corresponding to the multicast service field. When the need code corresponding to the multicast service field is determined to be the first need code, for example, the first need code includes need R, the terminal may release the second multicast service configuration.

[0226] It should be noted that the requirement code corresponding to the multicast service field can be the requirement code corresponding to the multicast service configuration field, for example, the requirement code corresponding to at least one information element (IE) in the multicast service configuration field. Each optional information element must be associated with a requirement code to determine the terminal's behavior when the information element is not provided.

[0227] In some embodiments, when the multicast service field of the terminal corresponds to the first requirement code, the second multicast service configuration released includes at least one of the following: a second multicast service provided by a broadcast message; a second multicast service provided by proprietary signaling.

[0228] For example, when the multicast service field of the terminal corresponds to the first requirement code, the terminal releases the second multicast service configuration, for example, the second multicast service configuration provided by the MCCH message can be released. This release method is the same as that agreed in the existing protocol, so this processing method for the second multicast service does not require adjusting the existing protocol.

[0229] For example, when the multicast service field of the terminal corresponds to the first requirement code, the second multicast service configuration is released. For example, the second multicast service configuration provided by the proprietary signaling can be released. This release method is different from the method agreed upon in the existing protocol, so this method of handling the second multicast service can be achieved by adjusting the existing protocol (for example, adjusting the description of the multicast service field in the existing protocol or modifying the existing protocol process description).

[0230] In some embodiments, the first operation includes: the multicast service field corresponds to the second requirement code, and the terminal determines to release or retain the second multicast service configuration stored in the terminal according to a protocol agreement or an instruction of a network device.

[0231] For example, the terminal may perform the first operation based on the multicast service field. The terminal may first determine the need code corresponding to the multicast service field. When it is determined that the need code corresponding to the multicast service field is a second need code, for example, the second need code includes need S, the terminal may release the second multicast service configuration or retain the second multicast service configuration.

[0232] For example, when the requirement code corresponding to the multicast service field is the second requirement code, and the protocol stipulates that the second multicast service configuration needs to be released in this case, the terminal may release the second multicast service configuration.

[0233] For example, when the requirement code corresponding to the multicast service field is the second requirement code, and the protocol agreement (such as setting the protocol description of the multicast service field or modifying the existing protocol process description) requires retaining the second multicast service configuration in this case, then the terminal can retain the second multicast service configuration.

[0234] For example, when the requirement code corresponding to the multicast service field is the second requirement code, and the network device indicates that the second multicast service configuration needs to be released in this case, the terminal may release the second multicast service configuration.

[0235] For example, when the requirement code corresponding to the multicast service field is the second requirement code, and the network device indicates that the second multicast service configuration needs to be retained in this case, the terminal may retain the second multicast service configuration.

[0236] It should be noted that, regardless of whether the first message provides the first multicast service configuration, the first message still contains the multicast service configuration field. However, the value of the multicast service field may be different when the first multicast service configuration is provided or not.

[0237] In some embodiments, the first message is used to provide a first multicast service configuration, and the second message is used to provide a second multicast service configuration.

[0238] In some embodiments, the first message and the second message are of the same type, or the first message and the second message are of different types.

[0239] In some embodiments, the type includes at least one of: a broadcast message, proprietary signaling.

[0240] In some embodiments, the broadcast message includes at least one of the following: system information; a multicast traffic control channel MCCH message; a paging message. The system information may include, for example, a system information block (SIB), which may be an existing SIB or a newly defined SIB.

[0241] In some embodiments, the dedicated signaling includes at least one of the following: radio resource control (RRC) signaling, downlink control information (DCI); and medium access control element (MAC CE).

[0242] For example, the first message may be an MCCH message for providing a first multicast service configuration, and the second message may be RRC signaling for providing a second multicast service configuration. For example, the first message may be an MCCH message for providing a first multicast service configuration, and the second message may also be an MCCH message for providing a second multicast service configuration. The two MCCH messages may be MCCH messages received at different times.

[0243] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0244] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0245] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0246] Corresponding to the aforementioned embodiments of the communication control method, the present disclosure also provides embodiments of a terminal, a network device, and a communication control apparatus.

[0247] An embodiment of the present disclosure also proposes a terminal, comprising: one or more processors; a memory coupled to the one or more processors, wherein the memory stores executable instructions, and when the executable instructions are executed by the one or more processors, the terminal executes the communication control method described in any one of the first aspect and the optional embodiments of the first aspect.

[0248] The embodiments of the present disclosure further provide a communication control device. FIG5 is a schematic block diagram of a communication control device according to an embodiment of the present disclosure. As shown in FIG5 , the communication control device includes a transceiver module 501 and a processing module 502 .

[0249] In some embodiments, the transceiver module is used to receive a first message sent by a network device; and the processing module is used to determine a processing method for the multicast service configuration according to the first message.

[0250] In some embodiments, the first message is used to instruct the terminal to deactivate the multicast service session.

[0251] In some embodiments, the processing module is configured to:

[0252] The first message provides a first multicast service configuration, and the first multicast service configuration is stored;

[0253] The first message does not provide the first multicast service configuration, and the first operation is performed.

[0254] In some embodiments, the processing module is configured to:

[0255] The terminal has stored a second multicast service configuration, and the first multicast service configuration is used to overwrite the second multicast service configuration; or,

[0256] When the terminal has stored a second multicast service configuration, and the second multicast service configuration is the same as the first multicast service configuration, retaining the first multicast service configuration or retaining the second multicast service configuration; or

[0257] The terminal does not store the second multicast service configuration, but stores the first multicast service configuration.

[0258] In some embodiments, the first operation includes: releasing the second multicast service configuration stored by the terminal, or retaining the second multicast service configuration stored by the terminal.

[0259] In some embodiments, the first operation is performed according to at least one of the following: a multicast service field; a protocol agreement; and a network device indication.

[0260] In some embodiments, the performing of the first operation includes: the multicast service field corresponds to the first requirement code, and the second multicast service configuration is released.

[0261] In some embodiments, the performing of the first operation includes: the multicast service field corresponds to a second requirement code, and the terminal determines to release or retain the second multicast service configuration according to a protocol agreement or an instruction of a network device.

[0262] In some embodiments, the first message is used to provide a first multicast service configuration, and the second message is used to provide a second multicast service configuration.

[0263] In some embodiments, the first message and the second message are of the same type, or the first message and the second message are of different types.

[0264] In some embodiments, the type includes at least one of the following: a broadcast message, a proprietary signaling.

[0265] In some embodiments, the broadcast message includes at least one of the following: system information; multicast service control channel message; paging message.

[0266] It should be noted that the terminal may include the above-mentioned transceiver module and processing module, and may also include other modules, such as a storage module, a display module, etc., and the present disclosure does not limit this.

[0267] An embodiment of the present disclosure also proposes a network device, comprising: one or more processors; a memory coupled to the one or more processors, wherein the memory stores executable instructions, and when the executable instructions are executed by the one or more processors, the network device executes the communication control method described in any one of the second aspect and the optional embodiments of the second aspect.

[0268] The embodiments of the present disclosure further provide a communication control device. FIG6 is a schematic block diagram of a communication control device according to an embodiment of the present disclosure. As shown in FIG6 , the communication control device includes a transceiver module 601 .

[0269] In some embodiments, the transceiver module is used to send a first message to the terminal, wherein the first message is used by the terminal to determine a processing method for the multicast service configuration.

[0270] In some embodiments, the first message is used to instruct the terminal to deactivate the multicast service session.

[0271] In some embodiments, the first message is used by the terminal to determine a processing method for the multicast service configuration, including at least one of the following:

[0272] The first message provides a first multicast service configuration, and the terminal stores the first multicast service configuration;

[0273] The first message does not provide the first multicast service configuration, and the terminal performs a first operation.

[0274] In some embodiments, storing the first multicast service configuration includes at least one of the following:

[0275] The terminal has stored a second multicast service configuration and overwrites the second multicast service configuration with the first multicast service configuration; or, if the terminal has stored a second multicast service configuration and the second multicast service configuration is the same as the first multicast service configuration, retain the first multicast service configuration or retain the second multicast service configuration; or, if the terminal does not store the second multicast service configuration, stores the first multicast service configuration.

[0276] In some embodiments, the first operation includes: releasing the second multicast service configuration stored by the terminal, or retaining the second multicast service configuration stored by the terminal.

[0277] In some embodiments, the first operation is performed according to at least one of the following: a multicast service field; a protocol agreement; and a network device indication.

[0278] In some embodiments, the first operation includes: the multicast service field corresponds to a first requirement code, and the second multicast service configuration is released.

[0279] In some embodiments, the first operation includes: the multicast service field corresponds to a second requirement code, and the terminal determines to release or retain the second multicast service configuration according to a protocol agreement or an instruction from a network device.

[0280] In some embodiments, the first message is used to provide a first multicast service configuration, and the second message is used to provide a second multicast service configuration.

[0281] In some embodiments, the first message and the second message are of the same type, or the first message and the second message are of different types.

[0282] In some embodiments, the type includes at least one of the following: a broadcast message, a proprietary signaling.

[0283] In some embodiments, the broadcast message includes at least one of the following: system information; multicast service control channel message; paging message.

[0284] It should be noted that the network device may include the above-mentioned transceiver module, and may also include other modules, such as a storage module, a processing module, etc., and this disclosure does not limit this.

[0285] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can be referred to the partial description of the method embodiment. The device embodiment described above is merely illustrative, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Those of ordinary skill in the art can understand and implement it without paying any creative work.

[0286] An embodiment of the present disclosure also proposes a communication device, comprising: one or more processors; wherein the processor is used to call instructions to enable the communication device to execute any one of the communication control methods described in the first aspect, the second aspect, the optional embodiment of the first aspect, and the optional embodiment of the second aspect.

[0287] An embodiment of the present disclosure also proposes a communication system, including a terminal and a network device, wherein the terminal is configured to implement the communication control method described in any one of the first aspect and the optional implementation of the first aspect, and the network device is configured to implement the communication control method described in any one of the second aspect and the optional implementation of the second aspect.

[0288] An embodiment of the present disclosure also proposes a storage medium storing instructions. When the instructions are executed on a communication device, the communication device executes the communication control method described in any one of the first aspect, the second aspect, the optional embodiment of the first aspect, and the optional embodiment of the second aspect.

[0289] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0290] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above units or modules are realized by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by software called by the processor, and the rest by hardware circuits.

[0291] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0292] Figure 7 is a schematic diagram of the structure of a communication device 7100 proposed in an embodiment of the present disclosure. Communication device 7100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 7100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0293] As shown in Figure 7, the communication device 7100 includes one or more processors 7101. The processor 7101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The processor 7101 is used to call instructions to enable the communication device 7100 to perform any of the above methods.

[0294] In some embodiments, the communication device 7100 further includes one or more memories 7102 for storing instructions. Optionally, all or part of the memories 7102 may be located outside the communication device 7100.

[0295] In some embodiments, the communication device 7100 further includes one or more transceivers 7103. When the communication device 7100 includes one or more transceivers 7103, the communication steps such as sending and receiving in the above method are performed by the transceiver 7103, and the other steps are performed by the processor 7101.

[0296] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0297] Optionally, the communication device 7100 further includes one or more interface circuits 7104, which are connected to the memory 7102. The interface circuits 7104 may be configured to receive signals from the memory 7102 or other devices, and may be configured to send signals to the memory 7102 or other devices. For example, the interface circuits 7104 may read instructions stored in the memory 7102 and send the instructions to the processor 7101.

[0298] The communication device 7100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 7100 described in the present disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 7 . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0299] FIG8 is a schematic diagram of the structure of a chip 8200 according to an embodiment of the present disclosure. If the communication device 7100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 8200 shown in FIG8 , but the present disclosure is not limited thereto.

[0300] The chip 8200 includes one or more processors 8201, and the processor 8201 is used to call instructions so that the chip 8200 executes any of the above methods.

[0301] In some embodiments, the chip 8200 further includes one or more interface circuits 8202, which are connected to the memory 8203. The interface circuit 8202 can be used to receive signals from the memory 8203 or other devices, and can be used to send signals to the memory.

[0302] 8203 or other devices to send signals. For example, the interface circuit 8202 can read the instructions stored in the memory 8203 and send the instructions to the processor 8201. Optionally, the terms interface circuit, interface, transceiver pin, transceiver, etc. can be used interchangeably.

[0303] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0304] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 7100, the communication device 7100 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

[0305] The present disclosure also provides a program product, which, when executed by the communication device 7100, enables the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0306] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A communication control method, characterized in that: The method comprises: receiving a first message sent by a network device; A processing method for multicast service configuration is determined according to the first message.

2. The method according to claim 1, characterized in that The first message is used to instruct the terminal to deactivate the multicast service session.

3. The method according to claim 1 or 2, characterized in that: The determining, according to the first message, a processing method for the multicast service configuration includes at least one of the following: The first message provides a first multicast service configuration, and the first multicast service configuration is stored; The first message does not provide the first multicast service configuration, and the first operation is performed.

4. The method according to claim 3, characterized in that: The storing of the first multicast service configuration includes at least one of the following: The terminal has stored the second multicast service configuration, and the first multicast service configuration is used to overwrite the second multicast service configuration; or, When the terminal has stored the second multicast service configuration and the second multicast service configuration is the same as the first multicast service configuration, retaining the first multicast service configuration or retaining the second multicast service configuration; or, The terminal does not store the second multicast service configuration, but stores the first multicast service configuration.

5. The method according to claim 3, characterized in that: The first operation includes: Release the second multicast service configuration stored in the terminal, or, The second multicast service configuration stored in the terminal is retained.

6. The method according to claim 3, characterized in that The first operation is performed according to at least one of the following: Multicast service field; Agreement; Network device indication.

7. The method according to claim 6, characterized in that The performing of the first operation includes: The multicast service field corresponds to the first requirement code and releases the second multicast service configuration stored in the terminal.

8. The method according to claim 6, characterized in that The performing of the first operation includes: The multicast service field corresponds to the second requirement code, and determines whether to release or retain the second multicast service configuration stored in the terminal according to the protocol agreement or the network device instruction.

9. The method according to any one of claims 1 to 8, characterized in that The first message is used to provide a first multicast service configuration, and the second message is used to provide a second multicast service configuration.

10. The method according to claim 9, characterized in that The first message and the second message are of the same type, or the first message and the second message are of different types.

11. The method according to claim 10, characterized in that The types include at least one of the following: Broadcast messages, proprietary signaling.

12. The method according to claim 11, characterized in that The broadcast message includes at least one of the following: System information; Multicast service control channel message; Paging message.

13. A communication control method, characterized in that: The method comprises: A first message is sent to a terminal, wherein the first message is used by the terminal to determine a processing method for multicast service configuration.

14. The method according to claim 13, characterized in that The first message is used to instruct the terminal to deactivate the multicast service session.

15. The method according to claim 13 or 14, characterized in that The first message is used by the terminal to determine a processing method for multicast service configuration, including at least one of the following: The first message provides a first multicast service configuration, and the terminal stores the first multicast service configuration; The first message does not provide a first multicast service configuration, and the terminal performs a first operation.

16. The method according to claim 15, characterized in that The storing of the first multicast service configuration includes at least one of the following: The terminal has stored a second multicast service configuration, and the second multicast service configuration is overwritten by the first multicast service configuration; or, When the terminal has stored a second multicast service configuration, and the second multicast service configuration is the same as the first multicast service configuration, retaining the first multicast service configuration or retaining the second multicast service configuration; or, The terminal does not store the second multicast service configuration, but stores the first multicast service configuration.

17. The method according to claim 15, characterized in that The first operation includes: releasing the second multicast service configuration stored in the terminal, or, The second multicast service configuration stored in the terminal is retained.

18. The method according to claim 15, characterized in that The first operation is performed according to at least one of the following: Multicast service field; Agreement; Network device indication.

19. The method according to claim 18, characterized in that The first operation includes: the multicast service field corresponds to the first requirement code, and the second multicast service configuration stored in the terminal is released.

20. The method according to claim 18, characterized in that The first operation includes: the multicast service field corresponds to a second requirement code, and the terminal determines to release or retain the second multicast service configuration stored in the terminal according to a protocol agreement or an instruction of a network device.

21. The method according to any one of claims 13 to 20, characterized in that The first message is used to provide a first multicast service configuration, and the second message is used to provide a second multicast service configuration.

22. The method according to claim 21, characterized in that The first message and the second message are of the same type, or the first message and the second message are of different types.

23. The method according to claim 22, characterized in that The types include at least one of the following: Broadcast messages, proprietary signaling.

24. The method according to claim 23, characterized in that The broadcast message includes at least one of the following: System information; Multicast service control channel message; Paging message.

25. A terminal, characterized in that: include: one or more processors; A memory coupled to the one or more processors, wherein executable instructions are stored in the memory, and when the one or more processors execute the executable instructions, the terminal executes the communication control method according to any one of claims 1 to 12.

26. A network device, characterized in that: include: one or more processors; A memory coupled to the one or more processors, wherein executable instructions are stored in the memory, and when the one or more processors execute the executable instructions, the network device executes the communication control method according to any one of claims 13 to 24.

27. A communication control device, characterized in that: include: A transceiver module, used for receiving a first message sent by a network device; A processing module is used to determine a processing method for multicast service configuration according to the first message.

28. A communication control device, characterized in that: include: The transceiver module is used to send a first message to a terminal, wherein the first message is used by the terminal to determine a processing method for multicast service configuration.

29. A communication device, characterized in that: include: one or more processors; The processor is used to call instructions so that the communication device executes the communication control method described in any one of claims 1-12 and 13-24.

30. A communication system, characterized in that: It comprises a terminal and a network device, wherein the terminal is configured to implement the communication control method according to any one of claims 1 to 12, and the network device is configured to implement the communication control method according to any one of claims 13 to 24.

31. A storage medium storing instructions, characterized in that: When the instruction is executed on the communication device, the communication device is caused to execute the communication control method according to any one of claims 1-12 and 13-24.

Images