Shared channel management method, first core network node and second core network node

Abstract

The present application discloses a shared channel management method, device, core network node and access network node, which belong to the field of communications technology. In an embodiment of the shared channel management method of the present application, a first core network node obtains multicast broadcast service (MBS) capability information of at least one access network node (101), where the MBS capability information is used to manage the establishment of a shared channel.

Description

[Technical field]

[0001] The present application relates to the field of communications, and in particular to a shared channel management method, device, core network node and access network node. [Background technology]

[0002] New Radio (NR) R17 version can support the provision of a Multicast Broadcast Service (MBS). Currently, to support MBS, a base station and a core network device can establish a shared channel (shared tunnel, this data channel may be understood as being common to multiple terminals) for transmitting MBS service data. Meanwhile, a Radio Access Network (RAN) side can provide a multicast service through a multicast bearer, and specifically, can provide an MBS service in two ways, Point to Point (PTP) and Point to Multipoint (PTM). Here, PTM is a point-to-multipoint transmission method, which may be understood as a case where a RAN transmits multicast service data to multiple terminals using the same radio resource, and PTP is a point-to-point transmission method, which may be understood as a case where a RAN transmits multicast service data to a specific terminal using a radio resource dedicated to the terminal.

[0003] Currently, the core network can actively trigger the establishment of a shared channel with a base station (e.g., the establishment of a shared data channel for a broadcast service). It may be understood that the core network may fail to establish an initiated shared channel because it cannot obtain whether the base station supports the establishment of a shared channel, and the core network may initiate an unnecessary shared channel establishment process.

[0004] In an ideal backhaul line, scheduling information and feedback information of user equipment (UE) can be exchanged in real time between multiple transmission reception points (TRPs). In addition to being able to schedule multiple physical downlink shared channels (PDSCHs) by the above-mentioned multiple downlink control information (DCIs), a PDSCH can also be scheduled by a single DCI. The following transmission methods are included:

[0005] (1) Space Division Multiplexing (SDM): Different data layers of the same Transport Block (TB) are from different TRP’s Non-Coherent Joint Transmission (NCJT).

[0006] (2) Frequency Division Multiplexing (FDM): The same redundancy version (RV) of the same TB is mapped to different frequency domain resources and emitted from different TRPs, or different RVs of the same TB are mapped to different frequency domain resources and emitted from different TRPs.

[0007] (3) Time division multiplexing (TDM): Multiple repetitions of different RVs of the same TB, e.g. within one slot or across multiple slots, are from different TRPs.

[0008] In this case, Acknowledgement / Negative Acknowledgement (ACK / NACK) feedback and Channel State Information (CSI) report can be fed back to any one of the TRPs.

[0009] However, conventional CSI report mappings are primarily designed for one measurement hypothesis and cannot support various measurement hypotheses well. Summary of the Invention [Problem to be solved by the invention]

[0010] The embodiments of the present application provide a shared channel management method, device, core network node and access network node that can solve the problem in the prior art that the core network may initiate an unnecessary shared channel establishment process, resulting in a waste of communication resources. [Means for solving the problem]

[0011] According to a first aspect, there is provided a method for shared channel management, the method comprising: The first core network node acquires multicast broadcast service (MBS) capability information of at least one access network node; Here, the MBS capability information is used to manage the establishment of a shared channel.

[0012] According to a second aspect, there is provided a method for shared channel management, the method comprising: A second core network node obtains MBS capability information of an access network node, and initiates or rejects a shared channel establishment request based on the MBS capability information of the access network node; or The second core network node sends a request for establishing a shared channel of the access network node to the first core network node, and receives a shared channel establishment rejection message sent by the first core network node.

[0013] According to a third aspect, there is provided a method of shared channel management, the method comprising: When receiving MBS capability acquisition request information sent by the first core network node, the access network node sends multicast broadcast service MBS capability information to the first core network node; or The access network node may transmit capability indication information to a first core network node, the capability indication information being used to assist the first core network node in making a decision on the MBS capability information.

[0014] According to a fourth aspect, there is provided a method for managing a multicast service channel, the method comprising: the second core network node rejects the initiation of the shared channel establishment request if there is a stored record in the information of the access network node; or the second core network node initiates a shared channel establishment request if there is no stored record in the information of the access network node; or The second core network node instructs the establishment of a shared channel or refuses to instruct the establishment of a shared channel based on a state of the multicast session; or The second core network node instructs the establishment of a unicast channel when an access network node that does not support multicast is present in the multicast session; or The second core network node may refuse to instruct the establishment of a unicast channel if there are no access network nodes that do not support multicast for the multicast session.

[0015] According to a fifth aspect, there is provided a shared channel management apparatus for use in a first core network node, the apparatus comprising: Including an acquisition module for acquiring multicast broadcast service (MBS) capability information of at least one access network node; Here, the MBS capability information is used to manage the establishment of a shared channel.

[0016] According to a sixth aspect, there is provided a core network node, the core network node being a first core network node, comprising a processor, a memory, and a program or instructions stored in the memory and operable to run on the processor, the program or instructions realizing the steps of the shared channel management method described in the first aspect when executed by the processor.

[0017] According to a seventh aspect, there is provided a core network node, the core network node being a first core network node, comprising: a processor and a communication interface, the processor being adapted to obtain multicast broadcast service (MBS) capability information of at least one access network node; Here, the MBS capability information is used to manage the establishment of a shared channel.

[0018] According to an eighth aspect, there is provided a shared channel management apparatus for use in a second core network node, the apparatus comprising: Obtaining MBS capability information of an access network node, and initiating or rejecting the initiation of a shared channel establishment request based on the MBS capability information of the access network node; or A second execution module is included for sending a shared channel establishment request of the access network node to a first core network node and receiving a shared channel establishment reject message sent by the first core network node.

[0019] According to a ninth aspect, there is provided a core network node, the core network node being a second core network node, comprising a processor, a memory and a program or instructions stored in the memory and operable to run on the processor, the program or instructions realising the steps of the shared channel management method described in the second aspect when executed by the processor.

[0020] According to a tenth aspect, there is provided a core network node, the core network node being a second core network node, comprising: a processor and a communication interface, wherein the communication interface is adapted to: obtain MBS capability information of an access network node; and based on the MBS capability information of the access network node, initiate or reject the initiation of a shared channel establishment request; or It is used for sending a shared channel establishment request of the access network node to a first core network node, and for receiving a shared channel establishment rejection message sent by the first core network node.

[0021] According to an eleventh aspect, there is provided a shared channel management apparatus for use in an access network node, the apparatus comprising: Sending multicast / broadcast service MBS capability information to the first core network node when receiving MBS capability acquisition request information sent by the first core network node; or A capability sending module is included for sending capability indication information to a first core network node, the capability indication information being used to assist the first core network node to make a decision on the MBS capability information.

[0022] According to a twelfth aspect, there is provided an access network node comprising a processor, a memory and a program or instructions stored in the memory and operable to run on the processor, the program or instructions, when executed by the processor, realising the steps of the shared channel management method according to the third aspect.

[0023] According to a thirteenth aspect, there is provided an access network node, the access network node including: a processor and a communication interface, wherein the communication interface is configured to, when receiving MBS capability acquisition request information sent by a first core network node, send multicast broadcast service MBS capability information to the first core network node; or It is used for sending capability indication information to a first core network node, and the capability indication information is used for assisting the first core network node to make a decision on the MBS capability information.

[0024] According to a fourteenth aspect, there is provided a multicast service channel management device for use in a second core network node, the device comprising: If there is a stored record in the access network node's information, reject the initiation of the shared channel establishment request; or Initiating a shared channel establishment request if there is no stored record in the access network node's information; or Instructing the establishment of a shared channel or refusing to instruct the establishment of a shared channel based on the state of the multicast session, or Indicate the establishment of a unicast channel if there are access network nodes in the multicast session that do not support multicast, or A third execution module is included for refusing to instruct establishment of a unicast channel if there is no access network node that does not support multicast in the multicast session.

[0025] According to a fifteenth aspect, there is provided a core network node, the core network node being a second core network node, comprising a processor, a memory, and a program or instructions stored in the memory and operable to run on the processor, the program or instructions realizing the steps of the multicast service channel management method described in the fourth aspect when executed by the processor.

[0026] According to a sixteenth aspect, there is provided a core network node, the core network node being a second core network node and comprising a processor and a communications interface, wherein the processor: If there is a stored record in the access network node's information, reject the initiation of the shared channel establishment request; or Initiating a shared channel establishment request if there is no stored record in the access network node's information; or Instructing the establishment of a shared channel or refusing to instruct the establishment of a shared channel based on the state of the multicast session, or Indicate the establishment of a unicast channel if there are access network nodes in the multicast session that do not support multicast, or It is used to refuse to direct the establishment of a unicast channel if there are no access network nodes in the multicast session that do not support multicast.

[0027] According to a seventeenth aspect, there is provided a readable storage medium having a program or instructions stored thereon which, when executed by a processor, effectuates steps of the method of the first, second, third or fourth aspect.

[0028] According to an eighteenth aspect, there is provided a chip, the chip including a processor and a communication interface, the communication interface coupled to the processor, the processor running a program or instructions and adapted to implement steps of the method of the first, second, third or fourth aspect.

[0029] According to a nineteenth aspect, there is provided a computer program / program product, the computer program / program product being stored on a non-volatile storage medium, the computer program / program product being executed by at least one processor to implement the steps of the method according to the first, second, third or fourth aspect.

[0030] According to a twentieth aspect, an embodiment of the present application provides a communications device, configured to perform the steps of the method according to the first aspect, configured to perform the steps of the method according to the second aspect, configured to perform the steps of the method according to the third aspect or configured to perform the steps of the method according to the fourth aspect. Effect of the Invention

[0031] In an embodiment of the present application, the first core network node manages the establishment of a shared channel by obtaining MBS capability information of the access network node, thereby ensuring that the core network can establish an effective shared channel and avoiding the waste of communication resources. [Brief description of the drawings]

[0032] [Figure 1] 1 is a flowchart of a shared channel management method according to an embodiment of the present application; [Diagram 2] 1 is a structural block of a shared channel management device according to an embodiment of the present application; [Diagram 3] FIG. 2 is a structural block diagram of a core network node in an embodiment of the present application; [Figure 4]2 is a second flowchart of a shared channel management method according to an embodiment of the present application. [Diagram 5] 2 is a flowchart of a multicast service channel management method according to an embodiment of the present application; [Figure 6] 1 is a structural block of a shared channel management device according to an embodiment of the present application; [Figure 7] 3 is a third flowchart of a shared channel management method according to an embodiment of the present application. [Figure 8] 1 is a structural block of a shared channel management device according to an embodiment of the present application; [Figure 9] FIG. 2 is a structural block diagram of an access network node in an embodiment of the present application; [Figure 10] FIG. 2 is a structural block diagram of a communication device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0033] The following clearly describes the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present application are all within the scope of protection of the present application.

[0034] The terms "first," "second," etc. in the specification and claims of the present application are intended to distinguish between similar objects and are not intended to describe a particular order or sequence. It is to be understood that the terms so used are interchangeable where appropriate, such that the embodiments of the present application may be performed in other orders than those shown or described herein, and that the objects distinguished by "first" and "second" are generally of the same type and do not limit the number of objects, e.g., the first object may be one or more. Note that "and / or" in the specification and claims refers to at least one of the objects connected, and the character " / " generally refers to an "or" relationship between the related objects.

[0035] It should be noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be applied to other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of the present application are always used interchangeably, and the techniques described may be used in the above-mentioned systems and radio technologies, or in other systems and radio technologies. Although the following description describes a New Radio (NR) system for illustrative purposes and uses NR terminology in most of the description below, these techniques may be applied to applications other than NR system applications, such as 6th Generation (6G) communication systems.

[0036] In the following, the shared channel management method, device, core network node and access network node according to the embodiments of the present application will be described in detail through several embodiments and application scenarios thereof in conjunction with the drawings.

[0037] As shown in FIG. 1 , an embodiment of the present application provides a shared channel management method, The method includes the step 101, in which a first core network node obtains multicast broadcast service (MBS) capability information of at least one access network node; It should be noted that by adding the MBS capability information of the access network node used to manage the shared channel establishment, it is possible to ensure that the shared channel is related to the MBS capability information of the access network node, and to avoid the core network node from initiating an invalid shared channel establishment flow as much as possible.

[0038] It should be further explained that, optionally, after step 101, the shared channel management method includes: The method may further include performing a first operation based on the MBS capability information of the access network node; It should be noted that in an embodiment of the present application, a first core network node can obtain MBS capability information of at least one access network node, and the MBS capability information is used to indicate that the access network node supports MBS or does not support MBS, that is, the first core network node can obtain whether each access network node among all access network nodes supports MBS, and perform a first operation based on this.

[0039] Optionally, the first operation may include at least one of the following: A11, indicating MBS capability information of the access network node to a second core network node; It should be noted that the first core network node can obtain the MBS capability information of all access network nodes, but since the shared channel establishment request sent by the second core network node is for one or several access network nodes, when the first core network node transmits the MBS capability information of the access network nodes, it may only transmit the MBS capability information of the access network nodes that need to establish a shared channel. For example, when the second core network node needs to create a shared channel between access network node 1 and access network node 2, the second core network node may send an MBS capability information acquisition request to the first core network node to obtain the MBS capability information of access network node 1 and access network node 2. Of course, the first core network node may actively transmit the MBS capability information of the access network nodes to the second core network node. For example, the first core network node may transmit the MBS capability information of each access network node to the second core network node alternately.

[0040] A12, respond to a shared channel establishment request sent by a second core network node.

[0041] The specific actions for each operation will be described in detail below.

[0042] About A11: Optionally, A11 may be implemented in at least one of the following ways: A111, the first core network node sends MBS capability information of the access network node to a second core network node; That is, in such a manner, the first core network node directly sends the MBS capability information of the access network node to the second core network node.

[0043] A112, the first core network node sends the MBS capability information of the access network node to a second core network node via a third core network node; That is, in this manner, the first core network node may transmit the MBS capability information of the access network node via a third core network node (i.e., other core network nodes than the first core network node and the second core network node) instead of directly transmitting the MBS capability information of the access network node to the second core network node. For example, as an example, when the first core network node receives a message whose message destination is the second core network node, the first core network node additionally carries the MBS capability information of the access network node in the message. Exemplarily, the terminal initiates a request message to join MBS service reception via an access network node, and the first core network node (e.g., Access and Mobility Management Function, AMF) additionally carries the MBS capability information of the access network node in the request message after receiving the request message. The second core network node (e.g., Multicast Broadcast Session Management Function, MB-SMF) determines whether to initiate a shared channel establishment request based on the MBS capability information of the access network node after receiving the request message to join MBS service reception carrying the MBS capability information of the access network node. In a specific implementation, after a first core network node (e.g., AMF) learns the MBS capability information of an access network node, it indicates the MBS capability information of the access network node to a third core network node (e.g., SMF), and the third core network node further indicates the MBS capability information of the access network node to a second core network node (e.g., MB-SFM).

[0044] Further, in such an operation mode, optionally, after receiving the MBS capability information of the access network node indicated by the first core network node, the second core network node initiates or rejects the initiation of a shared channel establishment request based on the MBS capability information of the access network node, i.e., if the access network node does not support MBS, the second core network node rejects the initiation of a shared channel establishment request to the access network node, or if the access network node supports MBS, the second core network node initiates a shared channel establishment request to the access network node.

[0045] It should be further explained that in some cases, the second core network node may receive the MBS capability information of the access network node indicated by the first core network node, in such a case, the second core network node does not need to acquire the MBS capability information of the access network node by itself; in another case, the second core network node may determine the MBS capability information of the access network node based on service information already established between the second core network node and the access network node, in such a case, the second core network node needs to acquire the MBS capability information of the access network node by itself.

[0046] Regarding A12, Optionally, A12 may be implemented in at least one of the following ways: A121, receiving a shared channel establishment request sent by the second core network node, and accepting or rejecting the shared channel establishment request according to MBS capability information of an access network node; It should be noted that a further selective realization process in this manner is as follows.

[0047] A1211, if the MBS capability information indicates that the access network node does not support MBS, rejecting the shared channel establishment request; When the first core network node rejects the shared channel establishment request, the first core network node needs to send a shared channel establishment rejection message to the second core network node, that is, the shared channel establishment rejection message is sent when the first core network node determines that the access network node does not support MBS based on the MBS capability information of the access network node. After receiving the shared channel establishment rejection message, the second core network node determines that the access network node does not support MBS, and rejects to initiate a shared channel establishment request to the access network node.

[0048] For example, a second core network node sends a shared channel establishment request message to a first core network node to request the establishment of a shared channel with access network node 1, and when the first core network node determines that the access network node 1 does not support MBS, it rejects the establishment of the shared channel; and after receiving the shared channel establishment rejection message, the second core network node determines that the access network node 1 does not support MBS capability and therefore subsequently does not request the establishment of a data shared channel with access network node 1.

[0049] A1212, if the MBS capability information indicates that the access network node supports MBS, accept the shared channel establishment request; If the first core network node accepts the shared channel establishment request, the first core network node directly sends a shared channel establishment request message to the access network node to establish the shared channel.

[0050] A122, receiving a shared channel establishment request sent by the second core network node, and sending a group notification message or a single terminal paging to the access network node according to the MBS capability information of the access network node and the state of the terminal; Here, the terminal is determined based on the shared channel establishment request.

[0051] It should be noted here that the group notification message is used to notify that a terminal has accessed the network, and the single terminal paging is also used to notify that a terminal has accessed the network.

[0052] It should be noted that a further selective realization process in this manner is as follows.

[0053] A1221, when the MBS capability information indicates that the access network node does not support MBS and the terminal is in an idle state, sending a single terminal paging to the access network node; A1222, when the MBS capability information indicates that the access network node supports MBS and the terminal is in an idle state, a group advertisement message to the access network node.

[0054] It should be further explained that step 101 in the embodiment of the present application may adopt one of the following implementation manners.

[0055] B11, sending MBS capability acquisition request information to the at least one access network node; receiving MBS capability information fed back by the at least one access network node according to the MBS capability acquisition request information; That is, in this manner, the MBS capability information is transmitted based on a request from the first core network node, and when the first core network node needs to obtain the MBS capability information of which or which access network nodes, it can send MBS capability acquisition request information to these access network nodes, and after receiving the MBS capability acquisition request information sent by the first core network node, the access network node feeds back the MBS capability information to the first core network node.

[0056] For example, a first core network node sends MBS capability acquisition request information to an access network node A, and the access network node A feeds back capability acquisition response information to the first core network node, in which the MBS capability information is carried.

[0057] B12, receiving capability indication information sent by at least one access network node, and determining MBS capability information of the at least one access network node according to the capability indication information; For example, in one implementation, an access network node may convey capability indication information of the access network node during the initiation of an NG interface establishment process between the access network node and a first core network node.

[0058] It should be further explained that the MBS capability information in this manner is actively sent by the access network node to the first core network node indirectly or directly, where direct sending means that the capability indication is the MBS capability information, and indirect sending means that various information is carried in the capability indication, one of which is the MBS capability information, or the capability indication can indirectly reflect the MBS capability information, for example, the access network node sends the capability indication information, and the first core network node can infer the MBS capability information according to the capability indication information.

[0059] For example, when the capability indication information is MBS capability information, the NG setup request message carries MBS capability information that the access network node supports MBS, or carries MBS capability information that the access network node does not support MBS capability, or the access network node does not carry MBS capability information. It can be understood that, when the access network node does not carry MBS capability information, the first core network node may silently assume that the access network node does not support MBS.

[0060] It should be further explained that, optionally, the first core network node mentioned in the embodiments of the present application may be an Access and Mobility Management Function (AMF) entity, and the second core network node may be a shared channel management node, for example a Multicast Broadcast Session Management Function (MB-SMF) entity.

[0061] Below, using AMF entities and MB-SMF entities as examples, the specific implementation of this application is described by way of example as follows:

[0062] Implementation method 1: an AMF entity obtains MBS capability information of at least one access network node, and the AMF entity sends the MBS capability information of access network node A to the MB-SMF entity. When the MB-SMF entity needs to establish a shared channel with access network node A, it first determines whether the access network node A supports MBS based on the MBS capability information of access network node A, if the access network node A supports MBS, it initiates a shared channel establishment request, and if the access network node A does not support MBS, it rejects the initiation of the shared channel establishment request.

[0063] It should be noted that the implementation method 1 manages the shared channel establishment from the perspective of the MB-SMF entity, i.e., the MB-SMF entity only establishes a shared channel with an access network node that supports MBS, thereby avoiding unnecessary shared channel establishment flows and reducing signaling overhead.

[0064] Implementation method 2: an AMF entity obtains MBS capability information of at least one access network node. When receiving a shared channel establishment request with access network node B sent by the MB-SMF entity, the AMF entity determines whether to accept or reject the shared channel establishment request based on the MBS capability information of access network node B. If the access network node B supports MBS, it accepts the shared channel establishment request and sends a shared channel establishment request message to the access network node B; if the access network node B does not support MBS, it rejects the shared channel establishment request and sends a shared channel establishment rejection message to the MB-SMF entity.

[0065] It should be noted that the difference between this implementation method and implementation method 1 is that the AMF entity does not send the capability information of the MBS to the MB-SMF entity, that is, the MB-SMF entity directly sends a shared channel establishment request, and the AMF entity decides whether to accept this shared channel establishment request. This implementation method can also avoid unnecessary shared channel establishment flows and reduce signaling overhead.

[0066] It should be noted that embodiments of the present application may enable a core network node to acquire the MBS capability of an access network node, thereby avoiding initiating subsequent unnecessary shared channel establishment flows that would result in a waste of communication resources.

[0067] It should be noted that in the shared channel management method according to the embodiment of the present application, the execution body can be a shared channel management device or a control module for executing the shared channel management method in the shared channel management device. In the embodiment of the present application, the execution of the shared channel management method by the shared channel management device is taken as an example to describe the shared channel management device according to the embodiment of the present application.

[0068] As shown in FIG. 2, an embodiment of the present application provides a shared channel management device 200, including an acquisition module 201 for acquiring multicast / broadcast service (MBS) capability information of at least one access network node; Here, the MBS capability information is used to manage the establishment of a shared channel.

[0069] Optionally, after the acquiring module 201 learns the multicast / broadcast service (MBS) capability information of at least one access network node, Further comprising a first execution module for performing a first operation based on the MBS capability information of the access network node; Here, the first operation is: indicating MBS capability information of the access network node to a second core network node; and responding to a shared channel establishment request transmitted by the second core network node.

[0070] Optionally, the MBS capability information indicates that the access network node supports MBS or does not support MBS.

[0071] Optionally, the implementation of responding to the shared channel establishment request sent by the second core network node includes: receiving a shared channel establishment request sent by the second core network node, and accepting or rejecting the shared channel establishment request based on MBS capability information of an access network node; receiving a shared channel establishment request sent by the second core network node; and sending a group notification message or a single terminal paging to the access network node based on the MBS capability information of the access network node and a state of the terminal; Here, the terminal is determined based on the shared channel establishment request.

[0072] Optionally, the implementation of accepting or rejecting the shared channel establishment request based on the MBS capability information of the access network node may include: rejecting the shared channel establishment request if the MBS capability information indicates that the access network node does not support MBS; If the MBS capability information indicates that the access network node supports MBS, accepting the shared channel establishment request.

[0073] Optionally, when accepting the shared channel establishment request, the shared channel management device: It further includes a first sending module for sending a shared channel establishment request message to the access network node.

[0074] Optionally, when rejecting the shared channel establishment request, the shared channel management device: The second sending module further includes a second sending module for sending a shared channel establishment rejection message to a second core network node.

[0075] Optionally, the above-mentioned implementation manner of sending a group notification message or a single terminal paging to the access network node according to the MBS capability information of the access network node and the status of the terminal includes: If the MBS capability information indicates that the access network node does not support MBS and the terminal is in an idle state, sending a single terminal paging to the access network node; If the MBS capability information indicates that the access network node supports MBS and the terminal is in an idle state, a group advertisement message and transmitting the same to the access network node.

[0076] Optionally, the group announcement message is used to announce that a terminal has accessed the network.

[0077] Optionally, the single terminal paging is used to notify a terminal that it has accessed the network.

[0078] Optionally, the acquisition module 201 includes: Sending MBS capability acquisition request information to the at least one access network node, and receiving MBS capability information fed back by the at least one access network node based on the MBS capability acquisition request information; or It is used to receive capability indication information sent by at least one access network node, and determine MBS capability information of the at least one access network node based on the capability indication information.

[0079] Optionally, the implementation manner of indicating the MBS capability information of the access network node to the second core network node includes: the first core network node sending MBS capability information of the access network node to a second core network node; Or, The first core network node sends the MBS capability information of the access network node to a second core network node via a third core network node.

[0080] It should be noted that, based on the MBS capability information of at least one access network node, the MBS capability information of the access network node is indicated to a second core network node, or a shared channel establishment request sent by the second core network node is responded to, thereby ensuring that the core network can establish an effective shared channel and avoiding waste of communication resources.

[0081] The shared channel management device in the embodiment of the present application may be a device or electronic device having an operating system, or may be a component, integrated circuit, or chip in an electronic device. This device or electronic device is mainly a non-mobile terminal. Illustratively, the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a deposit and withdrawal machine, or a self-service machine, etc., and the embodiment of the present application is not specifically limited.

[0082] The shared channel management device according to the embodiment of the present application can realize each process realized by the embodiment of the method in FIG. 1 and achieve the same technical effects, and will not be described further here in order to avoid repetition of description.

[0083] An embodiment of the present application further provides a core network node, wherein the core network node is a first core network node, and includes a processor and a communication interface, wherein the processor: for obtaining multicast / broadcast service (MBS) capability information of at least one access network node; Here, the MBS capability information is used to manage the establishment of a shared channel.

[0084] This embodiment of the core network node corresponds to the embodiment of the method at the first core network node side, and the implementation processes and realization manners of the above-mentioned embodiment of the method can be applied to this embodiment of the core network node, and the same technical effects can be achieved. Specifically, Figure 3 is a schematic diagram of the hardware structure of the core network node of the embodiment of the present application.

[0085] The core network node 300 includes an antenna 301, a radio frequency device 302, and a baseband device 303. The antenna 301 and the radio frequency device 302 are connected. In the uplink direction, the radio frequency device 302 receives information via the antenna 301 and transmits the received information to the baseband device 303 for processing. In the downlink direction, the baseband device 303 processes the information to be transmitted and transmits it to the radio frequency device 302, and the radio frequency device 302 sends out the received information via the antenna 301 after processing it.

[0086] The above frequency band processing device may be located in a baseband device 303, and the method performed by the core network node in the above embodiments may be implemented in the baseband device 303, which includes a processor 304 and a memory 305.

[0087] The baseband device 303 may, for example, include at least one baseband board, on which multiple chips are installed, and as shown in FIG. 3, one of the chips is, for example, a processor 304, connected to a memory 305, and calls the program in the memory 305 to perform the operations of the core network node shown in the above method embodiments.

[0088] The baseband device 303 may further include a network interface 306, which is used to exchange information with the radio frequency device 302, and which is, for example, a common public radio interface (abbreviated as CPRI).

[0089] Specifically, the core network node of an embodiment of the present invention further includes instructions or programs stored in memory 305 and capable of running on processor 304, and processor 304 can call instructions or programs in memory 305 to execute the method performed by each module shown in FIG. 2 and achieve the same technical effect, which will not be described further here in order to avoid repetition.

[0090] Preferably, the embodiment of the present application further provides a core network node, the core network node being a first core network node, including a processor, a memory, and a program or instruction stored in the memory and operable on the processor, the program or instruction being executed by the processor to realize each process of the embodiment of the shared channel management method used on the first core network node side, and achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0091] The embodiment of the present application further provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, each process of the embodiment of the shared channel management method used in the first core network node side can be realized and the same technical effect can be achieved. In order to avoid repetition, no further description will be given here. Here, the said computer-readable storage medium is, for example, a read-only memory (abbreviated as ROM), a random access memory (abbreviated as RAM), a magnetic disk or an optical disk.

[0092] As shown in FIG. 4, an embodiment of the present application further provides a shared channel management method, A second core network node obtains MBS capability information of the access network node, and initiates or rejects the initiation of a shared channel establishment request according to the MBS capability information of the access network node; or The method includes step 401, in which a second core network node sends a request for establishing a shared channel of an access network node to a first core network node, and receives a shared channel establishment rejection message sent by the first core network node.

[0093] Optionally, the MBS capability information indicates that the access network node supports MBS or does not support MBS.

[0094] Optionally, the shared channel establishment reject message is sent when the first core network node determines, based on MBS capability information of an access network node, that the access network node does not support MBS.

[0095] Optionally, the initiating or denying the initiation of a shared channel establishment request based on the MBS capability information of the access network node comprises: refusing the second core network node to initiate a request to establish a shared channel to the access network node if the access network node does not support MBS; or If the access network node supports MBS, the second core network node initiates a request to the access network node to establish a shared channel.

[0096] Optionally, after receiving the shared channel establishment rejection message sent by the first core network node, The method further includes determining that the access network node does not support MBS and refusing to initiate a request to establish a shared channel to the access network node.

[0097] Optionally, the second core network node obtaining MBS capability information of an access network node includes: receiving MBS capability information of an access network node indicated by a first core network node; and determining MBS capability information of the access network node based on service information already established between the second core network node and an access network node.

[0098] It should be noted that all the descriptions related to the second core network node in the above embodiment also apply to this embodiment, and can achieve the same technical effects as the above embodiment, and will not be further described here.

[0099] As shown in FIG. 5, an embodiment of the present application further provides a multicast service channel management method, The method includes step 501, in which the second core network node refuses to initiate a shared channel establishment request if a memory record exists in the information of the access network node, or the second core network node initiates a shared channel establishment request if a memory record does not exist in the information of the access network node, or the second core network node instructs establishment of a shared channel or refuses to instruct establishment of a shared channel based on a state of the multicast session, or the second core network node instructs establishment of a unicast channel if an access network node that does not support multicast exists in the multicast session, or the second core network node refuses to instruct establishment of a unicast channel if an access network node that does not support multicast exists in the multicast session.

[0100] Optionally, the stored record is used to indicate that an access network node has already participated in a multicast session.

[0101] Optionally, when the state of the multicast session is in an activated state, it indicates the establishment of a shared channel.

[0102] Optionally, refusing to indicate establishment of a shared channel when the state of the multicast session is in a deactivated state.

[0103] Optionally, the step of instructing the establishment of the shared channel further comprises: sending, by a first core network function, an indication to an access network node to establish a shared channel; or Sending a request to establish a shared channel to an access network node.

[0104] Optionally, said refusing to instruct establishment of a shared channel may include: sending, by a first core network function, an indication to an access network node to reject establishment of the shared channel; or Refusing to send a request to establish a shared channel to the access network node.

[0105] Optionally, the step of instructing the establishment of the unicast channel further comprises: Sending an instruction to a first core network function to establish a unicast channel.

[0106] Optionally, the refusal to instruct establishment of a unicast channel may include: sending an indication to a first core network function to reject the establishment of the unicast channel; or Refusing to send an instruction to establish a unicast channel to the first core network function.

[0107] Optionally, the instructions for establishing a unicast channel may further include: It is used to instruct the first core network function to transmit multicast service information related to the unicast channel to the access network node.

[0108] It should be noted that all the descriptions related to the second core network node in the above embodiment also apply to this embodiment, and can achieve the same technical effects as the above embodiment, and will not be further described here.

[0109] As shown in FIG. 6 , an embodiment of the present application further provides a shared channel management device 600 for use in a second core network node, Obtaining MBS capability information of an access network node, and initiating or rejecting the initiation of a shared channel establishment request based on the MBS capability information of the access network node; or The access network node includes a second execution module 601 for sending a shared channel establishment request to a first core network node, and receiving a shared channel establishment rejection message sent by the first core network node.

[0110] Optionally, the MBS capability information indicates that the access network node supports MBS or does not support MBS.

[0111] Optionally, the shared channel establishment reject message is sent when the first core network node determines, based on MBS capability information of an access network node, that the access network node does not support MBS.

[0112] Optionally, the second execution module 601 executes initiating or refusing to initiate a shared channel establishment request according to the MBS capability information of the access network node in a manner that: refusing the second core network node to initiate a request to establish a shared channel to the access network node if the access network node does not support MBS; or If the access network node supports MBS, the second core network node initiates a request to the access network node to establish a shared channel.

[0113] Optionally, after the second execution module 601 receives a shared channel establishment rejection message sent by the first core network node, The access network node further includes a determining module for determining that the access network node does not support MBS and refusing to initiate a request to establish a shared channel to the access network node.

[0114] Optionally, the implementation of obtaining MBS capability information of an access network node includes: receiving MBS capability information of an access network node indicated by a first core network node; and determining MBS capability information of the access network node based on service information already established between the second core network node and an access network node.

[0115] It should be noted that the embodiments of the present application can ensure that the core network can establish an effective shared channel and avoid the waste of communication resources.

[0116] The shared channel management device in the embodiment of the present application may be a device, may be a device or electronic device having an operating system, may be a component, an integrated circuit, or a chip in an electronic device. The device or electronic device is mainly a non-mobile terminal. Illustratively, the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a deposit payment machine or a self-service machine, etc., and the embodiment of the present application is not specifically limited.

[0117] The shared channel management device according to the embodiment of the present application can realize each process realized by the embodiment of the method of FIG. 4 and achieve the same technical effect, and will not be described further here in order to avoid repetition of description.

[0118] Preferably, the embodiment of the present application further provides a core network node, the core network node being a second core network node, including a processor, a memory, and a program or instruction stored in the memory and operable on the processor, the program or instruction being executed by the processor to realize each process of the embodiment of the shared channel management method used on the second core network side, and achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0119] The embodiment of the present application further provides a computer-readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, each process of the embodiment of the shared channel management method used on the second core network side can be realized, and the same technical effect can be achieved. In order to avoid repetition, no further description will be given here.

[0120] Here, the computer-readable storage medium is, for example, a read-only memory (abbreviated as ROM), a random access memory (abbreviated as RAM), a magnetic disk, or an optical disk.

[0121] An embodiment of the present application further provides a core network node, wherein the core network node is a second core network node, and includes a processor and a communication interface, and the communication interface: Obtaining MBS capability information of an access network node, and initiating or rejecting the initiation of a shared channel establishment request based on the MBS capability information of the access network node; or It is used for sending a shared channel establishment request of the access network node to a first core network node, and for receiving a shared channel establishment rejection message sent by the first core network node.

[0122] This second core network node embodiment corresponds to the above-mentioned second core network node side method embodiment, and each implementation process and realization manner of the above-mentioned method embodiment can be applied to this second core network node embodiment and can achieve the same technical effects.

[0123] Specifically, the embodiment of the present application further provides a core network node, the specific structure of which is as follows: figure 3, this core network node is the second core network node.

[0124] Specifically, the core network node of the embodiments of the present application includes instructions or programs that are stored in a memory and can run on a processor, and the processor can call the instructions or programs in the memory to execute the methods performed by each module shown in FIG. 6 and achieve the same technical effect, which will not be described further here in order to avoid repetition.

[0125] An embodiment of the present application further provides a multicast service channel management device for use in a second core network node, If there is a stored record in the access network node's information, reject the initiation of the shared channel establishment request; or Initiating a shared channel establishment request if there is no stored record in the access network node's information; or Instructing the establishment of a shared channel or refusing to instruct the establishment of a shared channel based on the state of the multicast session, or Indicate the establishment of a unicast channel if there are access network nodes in the multicast session that do not support multicast, or A third execution module is included for refusing to instruct establishment of a unicast channel if there is no access network node that does not support multicast in the multicast session.

[0126] Optionally, the stored record is used to indicate that an access network node has already participated in a multicast session.

[0127] Optionally, when the third execution module executes instructing the establishment of a shared channel or refusing to instruct the establishment of a shared channel based on a state of a multicast session, indicating establishment of a shared channel when the state of the multicast session is in an activated state; or It is used to realize refusal to instruct the establishment of a shared channel when the state of the multicast session is in a deactivated state.

[0128] Optionally, the third execution module executing to instruct the establishment of a shared channel includes: sending, by a first core network function, an indication to an access network node to establish a shared channel; or It is used to realize sending a request to establish a shared channel to an access network node.

[0129] Optionally, the third execution module executes refusing to instruct the establishment of a shared channel. sending, by a first core network function, an indication to an access network node to reject establishment of the shared channel; or It is used to realize refusal to send a request to establish a shared channel to an access network node.

[0130] Optionally, the third execution module executes instructing the establishment of a unicast channel. It is used to realize sending an instruction to establish a unicast channel to a first core network function.

[0131] Optionally, the third execution module executes refusing to instruct the establishment of a unicast channel. sending an indication to a first core network function to reject the establishment of the unicast channel; or It is used to realize refusal to send an instruction to establish a unicast channel to the first core network function.

[0132] Optionally, the instructions for establishing a unicast channel may further include: It is used to instruct the first core network function to transmit multicast service information related to the unicast channel to the access network node.

[0133] The multicast service channel management device in the embodiment of the present application may be a device, may be a device or electronic device having an operating system, may be a component, an integrated circuit, or a chip in an electronic device. The device or electronic device is mainly a non-mobile terminal. Illustratively, the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a deposit payment machine or a self-service machine, etc., and the embodiment of the present application is not specifically limited.

[0134] The multicast service channel management device according to the embodiment of the present application can realize each process realized by the embodiment of the method of Figure 5 and achieve the same technical effect, and will not be described further here in order to avoid repetition of description.

[0135] Preferably, the embodiment of the present application further provides a core network node, the core network node being a second core network node, including a processor, a memory, and a program or instruction stored in the memory and operable on the processor, the program or instruction being executed by the processor to realize each process of the embodiment of the multicast service channel management method used on the second core network side, and achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0136] The embodiment of the present application further provides a computer-readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, each process of the embodiment of the multicast service channel management method used in the second core network side can be realized, and the same technical effect can be achieved. In order to avoid repetition, no further description will be given here.

[0137] Here, the computer-readable storage medium is, for example, a read-only memory (abbreviated as ROM), a random access memory (abbreviated as RAM), a magnetic disk, or an optical disk.

[0138] An embodiment of the present application further provides a core network node, wherein the core network node is a second core network node, and includes a processor and a communication interface, wherein the processor: If there is a stored record in the access network node's information, reject the initiation of the shared channel establishment request; or Initiating a shared channel establishment request if there is no stored record in the access network node's information; or Instructing the establishment of a shared channel or refusing to instruct the establishment of a shared channel based on the state of the multicast session, or Indicate the establishment of a unicast channel if there are access network nodes in the multicast session that do not support multicast, or It is used to refuse to direct the establishment of a unicast channel if there are no access network nodes in the multicast session that do not support multicast.

[0139] This second core network node embodiment corresponds to the above-mentioned second core network node side method embodiment, and each implementation process and realization manner of the above-mentioned method embodiment can be applied to this second core network node embodiment and can achieve the same technical effects.

[0140] Specifically, the embodiment of the present application further provides a core network node, the specific structure of which can be seen in Figure 3, and this core network node is a second core network node.

[0141] Specifically, the core network node of the embodiments of the present application includes instructions or programs that are stored in a memory and can run on a processor, and the processor can call the instructions or programs in the memory to execute the methods performed by each module described above and achieve the same technical effect, which will not be described further here in order to avoid repetition.

[0142] As shown in FIG. 7, an embodiment of the present application further provides a shared channel management method, When receiving MBS capability acquisition request information sent by the first core network node, the access network node sends multicast broadcast service MBS capability information to the first core network node; or The method includes a step 701 in which an access network node sends capability indication information to a first core network node, the capability indication information being used to assist the first core network node to make a decision on MBS capability information.

[0143] Optionally, the MBS capability information indicates that the access network node supports MBS or does not support MBS.

[0144] It should be noted that all the descriptions related to the access network node in the above embodiment also apply to this embodiment, and the same technical effects as the above embodiment can be achieved, and will not be further described here.

[0145] As shown in FIG. 8 , an embodiment of the present application further provides a shared channel management device 800 for use in an access network node, comprising: Sending multicast / broadcast service MBS capability information to the first core network node when receiving MBS capability acquisition request information sent by the first core network node; or The present invention includes a capability sending module 801 for sending capability indication information to a first core network node, the capability indication information being used to assist the first core network node to make a decision on MBS capability information.

[0146] Optionally, the MBS capability information indicates that the access network node supports MBS or does not support MBS.

[0147] It should be noted that the embodiments of the present application can ensure that the core network can establish an effective shared channel and avoid the waste of communication resources.

[0148] The shared channel management device in the embodiment of the present application may be a device, may be a device or electronic device having an operating system, may be a component, an integrated circuit, or a chip in an electronic device. The device or electronic device is mainly a non-mobile terminal. Illustratively, the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a deposit payment machine or a self-service machine, etc., and the embodiment of the present application is not specifically limited.

[0149] The shared channel management device according to the embodiment of the present application can realize each process realized by the embodiment of the method of FIG. 6 and achieve the same technical effect, and will not be described further here in order to avoid repetition of description.

[0150] An embodiment of the present application further provides an access network node, comprising: a processor and a communication interface, the communication interface comprising: When receiving MBS capability acquisition request information sent by the first core network node, the access network node sends multicast broadcast service MBS capability information to the first core network node; or The access network node is used to send capability indication information to a first core network node, and the capability indication information is used to assist the first core network node to make a decision on the MBS capability information.

[0151] This access network node embodiment corresponds to the above-mentioned access core network node side method embodiment, and each implementation process and realization manner of the above-mentioned method embodiment can be applied to this access network node embodiment, and the same technical effect can be achieved. Specifically, Figure 9 is a hardware structural schematic diagram of the access network node of the embodiment of the present application.

[0152] The access network node 900 includes an antenna 901, a radio frequency device 902, and a baseband device 903. The antenna 901 and the radio frequency device 902 are connected. In the uplink direction, the radio frequency device 902 receives information via the antenna 901 and transmits the received information to the baseband device 903 for processing. In the downlink direction, the baseband device 903 processes the information to be transmitted and transmits it to the radio frequency device 902, and the radio frequency device 902 sends out the received information via the antenna 901 after processing it.

[0153] The above frequency band processing device may be located in a baseband device 903, and the method performed by the network side equipment in the above embodiments may be implemented in the baseband device 903, which includes a processor 904 and a memory 905.

[0154] The baseband device 903 may, for example, include at least one baseband board, on which multiple chips are installed, and as shown in FIG. 9, one of the chips is, for example, a processor 904, connected to a memory 905, and calls the program in the memory 905 to perform the operations of the core network node shown in the above method embodiments.

[0155] The baseband device 903 may further include a network interface 906, which is used to exchange information with the radio frequency device 902, and which is, for example, a common public radio interface (abbreviated as CPRI).

[0156] Specifically, the access network node of the embodiment of the present invention further includes instructions or programs stored in memory 905 and capable of running on processor 904, and processor 904 can call the instructions or programs in memory 905 to execute the method performed by each module shown in FIG. 8 and achieve the same technical effect, which will not be described further here in order to avoid repetition.

[0157] Preferably, the embodiment of the present application further provides an access network node, including a processor, a memory, and a program or instruction stored in the memory and operable on the processor, which, when executed by the processor, can realize each process of the embodiment of the shared channel management method used on the access network node side, and achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0158] The embodiments of the present application further provide a computer-readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, each process of the embodiment of the shared channel management method used in the access network node side can be realized, and the same technical effect can be achieved. In order to avoid repetition, no further description will be given here. Here, the computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0159] Optionally, as shown in Fig. 10, the embodiment of the present application further provides a communication device 1000, including a processor 1001, a memory 1002, and a program or instruction stored in the memory 1002 and operable on the processor 1001, for example, when the communication device 1000 is a core network node, when the program or instruction is executed by the processor 1001, each process of the embodiment of the shared channel management method used on the first core network node or the second core network node side can be realized, and the same technical effect can be achieved. When the communication device 1000 is an access network node, when the program or instruction is executed by the processor 1001, each process of the embodiment of the shared channel management method used on the access network node side can be realized, and the same technical effect can be achieved. In order to avoid repetition, no further description will be given here.

[0160] The terminal according to the embodiment of the present application may refer to a device that provides voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing device connected to a wireless modem. The name of the terminal device may vary depending on the system, for example, in a 5G system, the terminal device may be called a user equipment. The wireless terminal device may communicate with one or more core networks (Core Networks, CN) through a wireless access network, and the wireless terminal device may be a mobile terminal device, such as a mobile phone (also called a "cellular" phone) and a computer with a mobile terminal device, such as a mobile, pocket, handheld, computer-embedded or vehicle-mounted mobile device, which exchanges language and / or data with the wireless access network. For example, Personal Communication Service (PCS) telephones, cordless telephones, Session Initiated Protocol (SIP) telephones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), and other devices. The wireless terminal device may also be called a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal, an access terminal, a user terminal, a user agent, or a user device, and is not limited to the embodiments of this application.

[0161] The access network node in the embodiments of the present application may be a base station (abbreviated as BTS) in Global System of Mobile communication (abbreviated as GSM (registered trademark)) or Code Division Multiple Access (abbreviated as CDMA), a base station (abbreviated as Node B, NB) in Wideband Code Division Multiple Access (abbreviated as WCDMA (registered trademark)), an evolved base station (abbreviated as Evolved Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a base station in a future 5th Generation mobile communication (5G) network, and is not limited thereto.

[0162] Between the network side device and the terminal, multiple input multiple output (MIMO) transmission can be performed using one or multiple antennas, and the MIMO transmission may be single user MIMO (SU-MIMO) or multiple user MIMO (MU-MIMO). Depending on the form and number of antenna combinations, the MIMO transmission may be two-dimensional multiple input multiple output (2D-MIMO), three-dimensional multiple input multiple output (3D-MIMO), full-dimensional multiple input multiple output (FD-MIMO) or massive-MIMO, and may be diversity transmission, precoding transmission, beamforming transmission, etc.

[0163] The embodiments of the present application further provide a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, the processor is used to run a program or instruction to realize each process of the above method embodiments, and can achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0164] It should be understood that the chips referred to in the embodiments of the present application may be referred to as system level chips, system chips, chip systems, or systems on chips.

[0165] The embodiments of the present application provide a computer program / program product, the computer program / program product being stored in a non-volatile storage medium, and the computer program / program product being executed by at least one processor to realize each process of the above method embodiments and achieve the same technical effects. In order to avoid repetition, no further description will be given here.

[0166] It should be explained that in this specification, the terms "comprise", "include", or any other variants thereof are intended to cover the non-exclusive "comprise", whereby a process, method, article, or apparatus that includes a set of elements includes not only those elements, but also other elements not expressly listed or inherent to such process, method, article, or apparatus. In the absence of further limitations, an element limited by the phrase "comprises a" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes this element. It should be pointed out that the scope of the method and apparatus in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may include performing functions in an essentially simultaneous manner or in reverse order based on the functions involved, for example, the described method can be performed in a different order than described, and various steps can be added, omitted, or combined. Also, features described with reference to some examples can be combined in other examples.

[0167] From the above description of the embodiments, it is clear to those skilled in the art that the methods of the above embodiments can be realized in the form of software and a necessary general-purpose hardware platform. Of course, they can also be realized in hardware, but in many cases the former is a more preferable embodiment. In light of this understanding, the technical proposal of the present application may be substantially embodied in the form of a software product, or a portion of the contribution to the prior art may be embodied in the form of a software product. This computer software product is stored in a storage medium (e.g., ROM / RAM, magnetic disk, optical disk) and includes some instructions for causing a network device to execute the methods described in each embodiment of the present application.

[0168] The above describes the embodiments of the present application in conjunction with the drawings, but the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not limiting. Those skilled in the art can take the suggestions of this application and make many forms without departing from the spirit and scope of the claims of this application, all of which belong to the protection scope of this application. CROSS-REFERENCE TO RELATED APPLICATIONS

[0169] This application claims priority from Chinese Patent Application No. 202110460704.7 filed in China on April 27, 2021 and Chinese Patent Application No. 202110497329.3 filed in China on May 7, 2021, the entire contents of which are incorporated herein by reference.

Claims

1. A shared channel management method, comprising: The first core network node acquires multicast broadcast service (MBS) capability information of at least one access network node; The MBS capability information is used to manage the establishment of a shared channel; After the first core network node knows the MBS capability information of at least one access network node, performing a first operation based on the MBS capability information of the access network node; The first operation includes: Responding to a shared channel establishment request transmitted by the second core network node; Responding to a shared channel establishment request transmitted by the second core network node includes: receiving a shared channel establishment request sent by the second core network node, rejecting the shared channel establishment request if the MBS capability information indicates that the access network node does not support MBS, and accepting the shared channel establishment request if the MBS capability information indicates that the access network node supports MBS; When the shared channel establishment request is accepted, the shared channel management method includes: sending a shared channel establishment request message to the access network node; When the shared channel establishment request is rejected, the shared channel management method includes: and transmitting a shared channel establishment rejection message to the second core network node. How to manage shared channels.

2. The shared channel management method described in claim 1, wherein the first core network node is an Access and Mobility Management Function AMF entity, and the second core network node is a Multicast Broadcast Session Management Function MB-SMF entity.

3. A shared channel management method, comprising: The first core network node acquires multicast broadcast service (MBS) capability information of at least one access network node; The MBS capability information is used to manage the establishment of a shared channel; After the first core network node knows the MBS capability information of at least one access network node, performing a first operation based on the MBS capability information of the access network node; The first operation includes: Responding to a shared channel establishment request transmitted by the second core network node; Responding to the shared channel establishment request sent by the second core network node includes receiving the shared channel establishment request sent by the second core network node, and sending a group notification message or a single terminal paging to the access network node based on the MBS capability information of the access network node and a state of the terminal, the terminal being determined based on the shared channel establishment request; Sending a group notification message or a single terminal paging to the access network node based on the MBS capability information of the access network node and a state of the terminal, sending a single-terminal paging to the access network node if the MBS capability information indicates that the access network node does not support MBS and the terminal is in an idle state; If the MBS capability information indicates that the access network node supports MBS and the terminal is in an idle state, sending a group advertisement message to the access network node.

4. The shared channel management method described in claim 3, wherein the first core network node is an Access and Mobility Management Function AMF entity, and the second core network node is a Multicast Broadcast Session Management Function MB-SMF entity.

5. The first operation further comprises: indicating MBS capability information of the access network node to the second core network node; The method of claim 3 , further comprising:

6. The shared channel management method according to claim 3 , wherein the MBS capability information indicates that the access network node supports MBS or does not support MBS.

7. The first core network node obtaining multicast / broadcast service (MBS) capability information of at least one access network node includes: Sending MBS capability acquisition request information to the at least one access network node, and receiving MBS capability information fed back by the at least one access network node based on the MBS capability acquisition request information; or The method for managing a shared channel according to claim 3, comprising: receiving capability indication information transmitted by at least one access network node; and determining MBS capability information of the at least one access network node based on the capability indication information.

8. Indicating MBS capability information of the access network node to the second core network node includes: the first core network node sending MBS capability information of the access network node to the second core network node; or The shared channel management method according to claim 5, further comprising: the first core network node transmitting the MBS capability information of the access network node to the second core network node via a third core network node.

9. A shared channel management method, comprising: A second core network node sends a request for establishing a shared channel of an access network node to a first core network node, and receives a shared channel establishment rejection message sent by the first core network node; The shared channel establishment rejection message is sent when the first core network node determines, based on the multicast broadcast service (MBS) capability information of the access network node, that the access network node does not support MBS. How to manage shared channels.

10. The shared channel management method described in claim 9, wherein the first core network node is an Access and Mobility Management Function AMF entity and the second core network node is a Multicast Broadcast Session Management Function MB-SMF entity.

11. The MBS capability information indicates that the access network node supports MBS or does not support MBS. The shared channel management method according to claim 9.

12. After receiving a shared channel establishment rejection message sent by the first core network node, 10. The method of claim 9, further comprising: determining that the access network node does not support MBS and refusing to initiate a request to establish a shared channel to the access network node.

13. A first core network node comprising a processor, a memory, and a program or instructions stored in the memory and operable on the processor, the program or instructions, when executed by the processor, realizing the steps of the shared channel management method described in claim 1 or claim 2.

14. A first core network node comprising a processor, a memory, and a program or instructions stored in the memory and operable on the processor, wherein when the program or instructions are executed by the processor, the first core network node realizes steps of a shared channel management method described in any one of claims 3 to 8.

15. A second core network node comprising a processor, a memory, and a program or instructions stored in the memory and operable to run on the processor, the second core network node realizing the steps of a shared channel management method according to any one of claims 9 to 12 when the program or instructions are executed by the processor.

Images