Shared channel management method, device, core network node and access network node
By acquiring MBS capability information from access network nodes through core network nodes and managing the establishment of shared channels, the problem of invalid core network establishment was solved, and the optimal utilization of resources was achieved.
Patent Information
- Application Number
- CN202110497329.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2021-04-27
- Filing Date
- 2021-05-07
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2041-05-07
AI Technical Summary
The core network may initiate unnecessary shared channel establishment processes due to unknown base station support, resulting in a waste of communication resources.
Core network nodes manage the establishment of shared channels and avoid unnecessary processes by obtaining multicast broadcast service (MBS) capability information from access network nodes.
Effective management of shared channel establishment can avoid resource waste and improve communication efficiency.
Smart Images

Figure CN115250433B_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of communications, and in particular relates to a shared channel management method, device, core network node and access network node. Background Art
[0002] The New Radio (NR) R17 version can support the provision of Multicast Broadcast Service (MBS). At present, in order to support MBS, base stations and core network equipment can establish a shared channel (shared tunnel, which can be understood as the data channel is shared by multiple terminals) to transmit MBS service data. The radio access network (RAN) side can provide multicast services through multicast bearers, and specifically can provide MBS services in point-to-point (PTP) and point-to-multipoint (PTM) modes. Among them, PTM is a point-to-multipoint transmission mode, which can be understood as RAN using the same wireless resources to transmit multicast service data to multiple terminals, and PTP is a point-to-point transmission mode, which can be understood as RAN using terminal-specific wireless resources to transmit multicast service data to specific terminals.
[0003] Currently, the core network can actively trigger the establishment of a shared channel with the base station (for example, the establishment of a shared data channel for broadcast services). Since the core network cannot know whether the base station supports the establishment of a shared channel, the establishment of the shared channel initiated may fail sometimes. It can also be understood that the core network may initiate an unnecessary shared channel establishment process. Summary of the invention
[0004] The embodiments of the present application provide a shared channel management method, device, core network node and access network node, which can solve the problem in the prior art that the core network may initiate unnecessary shared channel establishment processes, resulting in waste of communication resources.
[0005] In a first aspect, a shared channel management method is provided, comprising:
[0006] The first core network node obtains multicast broadcast service MBS capability information of at least one access network node;
[0007] The MBS capability information is used for the management of shared channel establishment.
[0008] In a second aspect, a shared channel management method is provided, comprising:
[0009] The second core network node obtains the MBS capability information of the access network node, and initiates or refuses to initiate a shared channel establishment request based on the MBS capability information of the access network node; or,
[0010] 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 message for rejecting establishment of the shared channel sent by the first core network node.
[0011] In a third aspect, a shared channel management method is provided, including:
[0012] Upon receiving the MBS capability acquisition request information sent by the first core network node, the access network node sends the multicast broadcast service MBS capability information to the first core network node; or
[0013] The access network node sends capability indication information to the first core network node, where the capability indication information is used to assist the first core network node in determining MBS capability information.
[0014] In a fourth aspect, a shared channel management device is provided, which is applied to a first core network node, including:
[0015] An acquisition module, configured to acquire multicast broadcast service MBS capability information of at least one access network node;
[0016] The MBS capability information is used for the management of shared channel establishment.
[0017] In a fifth aspect, a core network node is provided, which is a first core network node, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the shared channel management method as described in the first aspect.
[0018] In a sixth aspect, a core network node is provided, the core network node being a first core network node, comprising a processor and a communication interface, wherein the processor is configured to obtain multicast broadcast service MBS capability information of at least one access network node;
[0019] The MBS capability information is used for the management of shared channel establishment.
[0020] In a seventh aspect, a shared channel management device is provided, which is applied to a second core network node, including:
[0021] A second execution module is configured to obtain MBS capability information of an access network node, and initiate or refuse to initiate a shared channel establishment request based on the MBS capability information of the access network node; or
[0022] A request for establishing a shared channel of an access network node is sent to a first core network node, and a message for rejecting establishment of a shared channel sent by the first core network node is received.
[0023] In an eighth aspect, a core network node is provided, which is a second core network node, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the shared channel management method as described in the second aspect.
[0024] In a ninth aspect, a core network node is provided, the core network node being a second core network node, comprising a processor and a communication interface, wherein the communication interface is used to obtain MBS capability information of an access network node, and initiate or refuse to initiate a shared channel establishment request based on the MBS capability information of the access network node; or,
[0025] A request for establishing a shared channel of an access network node is sent to a first core network node, and a message for rejecting establishment of a shared channel sent by the first core network node is received.
[0026] In a tenth aspect, a shared channel management device is provided, which is applied to an access network node, including:
[0027] a capability sending module, configured to send the multicast broadcast service MBS capability information to the first core network node upon receiving the MBS capability acquisition request information sent by the first core network node; or
[0028] Sending capability indication information to the first core network node, where the capability indication information is used to assist the first core network node in determining MBS capability information.
[0029] In the eleventh aspect, an access network node is provided, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the shared channel management method as described in the third aspect.
[0030] In a twelfth aspect, an access network node is provided, comprising a processor and a communication interface, wherein the communication interface is used to send 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
[0031] Sending capability indication information to the first core network node, where the capability indication information is used to assist the first core network node in determining MBS capability information.
[0032] In the thirteenth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect, the second aspect or the third aspect are implemented.
[0033] In a fourteenth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instructions to implement the steps of the method described in the first aspect, the second aspect, or the third aspect.
[0034] In a fifteenth aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a non-volatile storage medium, and the program / program product is executed by at least one processor to implement the steps of the method described in the first aspect or the third aspect.
[0035] In the embodiment of the present application, the first core network node manages the establishment of the shared channel by acquiring the MBS capability information of the access network node, thereby ensuring that the core network can establish an effective shared channel and avoiding waste of communication resources. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] Figure 1 This is one of the flow charts of the shared channel management method according to an embodiment of the present application;
[0037] Figure 2 This is one of the flow charts of the shared channel management device according to an embodiment of the present application;
[0038] Figure 3 is a structural block diagram of a core network node in an embodiment of the present application;
[0039] Figure 4 This is the second flow chart of the shared channel management method according to the embodiment of the present application;
[0040] Figure 5 It is a flowchart of a multicast service channel management method according to an embodiment of the present application;
[0041] Figure 6 This is the second flow chart of the shared channel management device according to the embodiment of the present application;
[0042] Figure 7 This is the third flow chart of the shared channel management method according to the embodiment of the present application;
[0043] Figure 8 This is the third flow chart of the shared channel management device according to the embodiment of the present application;
[0044] Fig. 9 is a structural block diagram of an access network node in an embodiment of the present application;
[0045] Fig.10 It is a structural block diagram of the communication device of an embodiment of the present application. DETAILED DESCRIPTION
[0046] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.
[0047] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally represents that the objects associated with each other are in an "or" relationship.
[0048] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in 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 often used interchangeably, and the described technology can be used for the above-mentioned systems and radio technologies as well as for other systems and radio technologies. The following description describes a new radio (NR) system for example purposes, and NR terms are used in most of the following descriptions, but these technologies can also be applied to applications other than NR system applications, such as the 6th Generation (6G) communication system.
[0049] The shared channel management method, device, core network node and access network node provided in the embodiments of the present application are described in detail below with reference to the accompanying drawings through some embodiments and their application scenarios.
[0050] like Figure 1 As shown, an embodiment of the present application provides a shared channel management method, including:
[0051] Step 101: A first core network node obtains MBS capability information of at least one access network node.
[0052] It should be noted that by adding the MBS capability information of the access network node, the MBS capability information is used for the management of shared channel establishment, thereby ensuring that the shared channel is associated with the MBS capability information of the access network node, and avoiding the core network node from initiating an invalid shared channel establishment process as much as possible.
[0053] It should be further noted that, optionally, after step 101, the shared channel management method may further include:
[0054] Based on the MBS capability information of the access network node, performing a first operation;
[0055] It should be noted that in the embodiment of the present application, the first core network node can obtain the 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 to say, the first core network node can obtain whether each access network node among all access network nodes supports MBS, and then perform the first operation based on this.
[0056] Optionally, the first operation may include at least one of the following:
[0057] A11. Indicating MBS capability information of the access network node to the second core network node;
[0058] It should be noted that, since the first core network node can obtain the MBS capability information of all access network nodes, and the shared channel establishment request sent by the second core network node is for one or several access network nodes, the first core network node can only send the MBS capability information of the access network nodes that need to establish a shared channel when sending the MBS capability information of the access network nodes; 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 can 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 can also actively send the MBS capability information of the access network node to the second core network node, for example, the first core network node can send the MBS capability information of each access network node to the second core network node in turn.
[0059] A12. Respond to the shared channel establishment request sent by the second core network node.
[0060] The specific behaviors under each operation are described in detail below.
[0061] For A11,
[0062] Optionally, A11 may be implemented in at least one of the following ways:
[0063] A111. The first core network node sends the MBS capability information of the access network node to the second core network node;
[0064] That is to say, in this manner, the first core network node directly sends the MBS capability information of the access network node to the second core network node.
[0065] A112. The first core network node sends the MBS capability information of the access network node to the second core network node through the third core network node;
[0066] That is to say, in this way, the first core network node does not directly send the MBS capability information of the access network node to the second core network node, but can send the MBS capability information with the help of the third core network node (i.e., other core network nodes except the first core network node and 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 message additionally carries the MBS capability information of the access network node. Exemplarily, the terminal initiates a request message for joining the MBS service reception through the access network node, and after the first core network node (such as AMF) receives the request message, the request message additionally carries the MBS capability information of the access network node. After the second core network node (such as MB-SMF) receives the request message for joining the MBS service reception carrying the MBS capability information of the access network node, it determines whether to initiate a shared channel establishment request based on the MBS capability information of the access network node. As a specific implementation, after the first core network node (such as AMF) obtains the MBS capability information of the access network node, it indicates the MBS capability information of the access network node to the third core network node (such as SMF), and the third core network node then indicates the MBS capability information of the access network node to the second core network node (such as MB-SFM).
[0067] Further, under this operating 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 refuses to initiate a shared channel establishment request based on the MBS capability information of the access network node; that is, when the access network node does not support MBS, the second core network node refuses to initiate a shared channel establishment request to the access network node; or, when the access network node supports MBS, the second core network node initiates a shared channel establishment request to the access network node.
[0068] It should also be noted that, in one case, the second core network node can receive the MBS capability information of the access network node indicated by the first core network node. In this case, the second core network node does not need to obtain the MBS capability information of the access network node by itself; in another case, the second core network node can also determine the MBS capability information of the access network node based on the service information already established between the second core network node and the access network node. In this case, the second core network node needs to obtain the MBS capability information of the access network node by itself.
[0069] For A12,
[0070] Optionally, A12 may be implemented in at least one of the following ways:
[0071] A121. Receive a shared channel establishment request sent by the second core network node, and accept or reject the shared channel establishment request based on the MBS capability information of the access network node;
[0072] It should be noted that the further optional implementation process under this method is:
[0073] A1211. When the MBS capability information indicates that the access network node does not support MBS, reject the shared channel establishment request;
[0074] In the case where 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 by the first core network node when it is determined 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 initiating a shared channel establishment request to the access network node.
[0075] For example, the second core network node sends a shared channel establishment request message to the first core network node to request to establish a shared channel with access network node 1. When the first core network node determines that access network node 1 does not support MBS, the first core network node refuses to establish a shared channel. After receiving the shared channel establishment rejection message, the second core network node determines that access network node 1 does not support MBS capabilities, and therefore no longer requests to establish a data sharing channel with access network node 1 subsequently.
[0076] A1212. When the MBS capability information indicates that the access network node supports MBS, accept the shared channel establishment request;
[0077] In the case where 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.
[0078] A122. Receive a shared channel establishment request sent by the second core network node, and send a group notification message or a single terminal paging message to the access network node based on the MBS capability information of the access network node and the status of the terminal;
[0079] The terminal determines based on the shared channel establishment request.
[0080] It should be noted here that the group notification message is used to notify the terminal to access the network, and the single terminal paging is also used to notify the terminal to access the network.
[0081] It should be noted that the further optional implementation process under this method is:
[0082] 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;
[0083] A1222. When the MBS capability information indicates that the access network node supports MBS and the terminal is in an idle state, send a group notification to the access network node.
[0084] It should also be noted that step 101 in the embodiment of the present application may be implemented in one of the following ways:
[0085] B11. 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;
[0086] That is to say, the MBS capability information under this method is sent based on the request of the first core network node. The first core network node needs to know which access network node or nodes have MBS capability information, and can send MBS capability acquisition request information to these access network nodes. 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.
[0087] For example, the first core network node sends MBS capability acquisition request information to the access network node A, and the access network node A feeds back capability acquisition response information to the first core network node, where the capability acquisition response information carries the MBS capability information.
[0088] B12. 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 according to the capability indication information;
[0089] For example, as an implementation, the access network node may carry the capability indication information of the access network node during the process of initiating establishment of the NG interface between the access network node and the first core network node.
[0090] It should also be noted that the MBS capability information in this manner is actively sent to the first core network node indirectly or directly by the access network node. Direct sending means that the capability indication is the MBS capability information, and indirect sending means that the capability indication carries multiple information, 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 based on the capability indication information.
[0091] For example, when the capability indication information is MBS capability information, the NG setup request message carries the MBS capability information that the access network node supports MBS, or carries the MBS capability information that the access network node does not support MBS capability, or the access network node does not carry the MBS capability information. It can be understood that when the access network node does not carry the MBS capability information, the first core network node can assume that the access network node does not support MBS.
[0092] It should also be noted that, optionally, the first core network node mentioned in the embodiment of the present application can be a mobility management function (AMF) entity; the second core network node is a management node of a shared channel, for example, it can be a multicast broadcast session management function (MB-SMF) entity.
[0093] The following takes the AMF entity and the MB-SMF entity as examples to illustrate the specific implementation of this application as follows:
[0094] Implementation method 1: The AMF entity obtains the 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 access network node A supports MBS based on the MBS capability information of access network node A. If access network node A supports MBS, a shared channel establishment request is initiated. If access network node A does not support MBS, the shared channel establishment request is rejected.
[0095] It should be noted that the first implementation method is to manage the establishment of shared channels from the perspective of the MB-SMF entity, that is, the MB-SMF entity only establishes shared channels with access network nodes that support MBS, thereby avoiding unnecessary shared channel establishment processes and reducing signaling overhead.
[0096] Implementation method two: The AMF entity obtains the MBS capability information of at least one access network node. When receiving a shared channel establishment request sent by the MB-SMF entity to the access network node B, the AMF entity determines whether to accept or reject the shared channel establishment request based on the MBS capability information of the access network node B. When the access network node B supports MBS, the shared channel establishment request is accepted and a shared channel establishment request message is sent to the access network node B. If the access network node B does not support MBS, the shared channel establishment request is rejected and a shared channel establishment rejection message is sent to the MB-SMF entity.
[0097] It should be noted that this implementation method is different from implementation method 1 in that the AMF entity does not send the MBS capability information to the MB-SMF entity. In other words, the MB-SMF entity still directly sends the shared channel establishment request, and the AMF entity determines whether to allow the shared channel establishment request. This implementation method can also avoid unnecessary shared channel establishment processes and reduce signaling overhead.
[0098] It should be noted that the embodiments of the present application can enable the core network node to learn the MBS capability of the access network node, thereby avoiding the subsequent initiation of unnecessary shared channel establishment processes and thus the waste of communication resources.
[0099] It should be noted that the shared channel management method provided in the embodiment of the present application can be executed by a shared channel management device, or a control module in the shared channel management device for executing the shared channel management method. In the embodiment of the present application, the shared channel management device provided in the embodiment of the present application is described by taking the execution of the shared channel management method by the shared channel management device as an example.
[0100] like Figure 2As shown, the embodiment of the present application provides a shared channel management device 200, including:
[0101] An acquisition module 201 is used to acquire MBS capability information of at least one access network node;
[0102] The MBS capability information is used for the management of shared channel establishment.
[0103] Optionally, after the acquiring module 201 acquires the multicast broadcast service MBS capability information of at least one access network node, the method further includes:
[0104] A first execution module, configured to execute a first operation based on the MBS capability information of the access network node;
[0105] The first operation includes at least one of the following:
[0106] indicating MBS capability information of the access network node to the second core network node;
[0107] Respond to the shared channel establishment request sent by the second core network node.
[0108] Optionally, the MBS capability information indicates whether the access network node supports MBS or does not support MBS.
[0109] Optionally, the implementation of responding to the shared channel establishment request sent by the second core network node includes at least one of the following:
[0110] receiving a shared channel establishment request sent by the second core network node, and accepting or rejecting the shared channel establishment request based on the MBS capability information of the access network node;
[0111] receiving a shared channel establishment request sent by the second core network node, and sending a group notification message or a single terminal paging message to the access network node based on the MBS capability information of the access network node and the state of the terminal;
[0112] The terminal determines based on the shared channel establishment request.
[0113] Optionally, the implementation method of accepting or rejecting the shared channel establishment request based on the MBS capability information of the access network node includes:
[0114] When the MBS capability information indicates that the access network node does not support MBS, rejecting the shared channel establishment request;
[0115] When the MBS capability information indicates that the access network node supports MBS, the shared channel establishment request is accepted.
[0116] Optionally, in the case of accepting the shared channel establishment request, the shared channel management device further includes:
[0117] The first sending module is used to send a shared channel establishment request message to the access network node.
[0118] Optionally, in the case of rejecting the shared channel establishment request, the shared channel management device further includes:
[0119] The second sending module is used to send a shared channel establishment rejection message to the second core network node.
[0120] Optionally, the implementation method of sending a group notification message or a single terminal paging message to the access network node based on the MBS capability information of the access network node and the state of the terminal includes:
[0121] 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;
[0122] When the MBS capability information indicates that the access network node supports MBS and the terminal is in an idle state, a group notification is sent to the access network node.
[0123] Optionally, the group notification message is used to notify the terminal to access the network.
[0124] Optionally, the single terminal paging is used to notify the terminal to access the network.
[0125] Optionally, the acquisition module 201 is used to:
[0126] 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
[0127] 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 according to the capability indication information.
[0128] Optionally, the implementation method of indicating the MBS capability information of the access network node to the second core network node includes:
[0129] The first core network node sends the MBS capability information of the access network node to the second core network node;
[0130] The first core network node sends the MBS capability information of the access network node to the second core network node through the third core network node.
[0131] It should be noted that by indicating the MBS capability information of at least one access network node to the second core network node, or responding to the shared channel establishment request sent by the second core network node, it is ensured that the core network can establish an effective shared channel and avoid waste of communication resources.
[0132] The shared channel management device in the embodiment of the present application can be a device, a device or electronic device with an operating system, or a component, an integrated circuit, or a chip in an electronic device. The device or electronic device is mainly a non-mobile terminal. Exemplarily, the non-mobile terminal can be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.
[0133] The shared channel management device provided in the embodiment of the present application can achieve Figure 1 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.
[0134] The embodiment of the present application further provides a core network node, wherein the core network node is a first core network node, including a processor and a communication interface, and the processor is used to:
[0135] Acquire multicast broadcast service MBS capability information of at least one access network node;
[0136] The MBS capability information is used for the management of shared channel establishment.
[0137] This core network node embodiment corresponds to the first core network node side method embodiment described above, and each implementation process and implementation method of the above method embodiment can be applied to this core network node embodiment and can achieve the same technical effect. Specifically, Figure 3 A schematic diagram of the hardware structure of a core network node for implementing an embodiment of the present application.
[0138] The core network node 300 includes an antenna 301, a radio frequency device 302, and a baseband device 303. The antenna 301 is connected to the radio frequency device 302. In the uplink direction, the radio frequency device 302 receives information through the antenna 301 and sends the received information to the baseband device 303 for processing. In the downlink direction, the baseband device 303 processes the information to be sent and sends it to the radio frequency device 302. The radio frequency device 302 processes the received information and sends it out through the antenna 301.
[0139] The above-mentioned frequency band processing device may be located in the baseband device 303 . The method executed by the core network node in the above embodiment may be implemented in the baseband device 303 . The baseband device 303 includes a processor 304 and a memory 305 .
[0140] The baseband device 303 may include, for example, at least one baseband board on which a plurality of chips are arranged. Figure 3 As shown, one of the chips is, for example, a processor 304, which is connected to a memory 305 to call a program in the memory 35 to execute the core network node operation shown in the above method embodiment.
[0141] The baseband device 303 may further include a network interface 306 for exchanging information with the radio frequency device 302 . The interface may be, for example, a common public radio interface (CPRI).
[0142] Specifically, the access network node of the embodiment of the present invention further includes: instructions or programs stored in the memory 305 and executable on the processor 304, and the processor 304 calls the instructions or programs in the memory 305 to execute. Figure 2 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.
[0143] Preferably, an embodiment of the present application also provides a core network node, which is a first core network node, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When the program or instruction is executed by the processor, each process of an embodiment of a shared channel management method applied to the first core network node side is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0144] The embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by the processor, each process of the embodiment of the shared channel management method applied to the first core network node side is implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here. Among them, the computer-readable storage medium, such as a read-only memory (Read-Only Memory, referred to as ROM), a random access memory (Random Access Memory, referred to as RAM), a disk or an optical disk, etc.
[0145] like Figure 4 As shown, the embodiment of the present application also provides a shared channel management method, including:
[0146] Step 401: The second core network node obtains MBS capability information of the access network node, and initiates or refuses to initiate a shared channel establishment request based on the MBS capability information of the access network node; or
[0147] 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 message for rejecting establishment of the shared channel sent by the first core network node.
[0148] Optionally, the MBS capability information indicates whether the access network node supports MBS or does not support MBS.
[0149] Optionally, the shared channel establishment rejection message is sent by the first core network node according to MBS capability information of the access network node when it is determined that the access network node does not support MBS.
[0150] Optionally, the initiating or refusing to initiate a shared channel establishment request based on the MBS capability information of the access network node includes:
[0151] In a case where the access network node does not support MBS, the second core network node refuses to initiate a request to establish a shared channel to the access network node; or
[0152] In a case where the access network node supports MBS, the second core network node initiates a request to the access network node to establish a shared channel.
[0153] Optionally, after receiving the shared channel establishment rejection message sent by the first core network node, the method further includes:
[0154] It is determined that the access network node does not support MBS, and a request to establish a shared channel to the access network node is rejected.
[0155] Optionally, the second core network node acquires MBS capability information of the access network node, including at least one of the following:
[0156] Receiving MBS capability information of the access network node indicated by the first core network node;
[0157] Based on the service information that has been established between the second core network node and the access network node, the MBS capability information of the access network node is determined.
[0158] It should be noted that all descriptions about the second core network node in the above embodiments are applicable to this embodiment and can achieve the same technical effects as the above embodiments, and will not be repeated here.
[0159] like Figure 5 As shown, the embodiment of the present application also provides a multicast service channel management method, including:
[0160] Step 501: The second core network node refuses to initiate a request to establish a shared channel based on the existence of a storage record of the information of the access network node; or, the second core network node initiates a request to establish a shared channel based on the existence of a storage record of the information of the access network node; or, the second core network node indicates the establishment of a shared channel or refuses to indicate the establishment of a shared channel based on the status of the multicast session; or, the second core network node indicates the establishment of a unicast channel based on the existence of an access network node that does not support multicast in the multicast session; or, the second core network node refuses to indicate the establishment of a unicast channel based on the absence of an access network node that does not support multicast in the multicast session.
[0161] Optionally, the stored record is used to indicate that the access network node has joined the multicast session.
[0162] Optionally, when the state of the multicast session is an activated state, establishment of a shared channel is indicated.
[0163] Optionally, when the state of the multicast session is an inactive state, the establishment of the shared channel is refused.
[0164] Optionally, the instructing establishment of a shared channel includes:
[0165] Sending, through the first core network function, an instruction to establish a shared channel to the access network node; or
[0166] Send a request to establish a shared channel to the access network node.
[0167] Optionally, the rejecting the establishment of the shared channel includes:
[0168] Sending, through the first core network function, an indication of refusing to establish a shared channel to the access network node; or
[0169] The request to establish a shared channel sent to the access network node is rejected.
[0170] Optionally, the instructing establishment of a unicast channel includes:
[0171] An instruction to establish a unicast channel is sent to the first core network function.
[0172] Optionally, the rejecting the establishment of the indication unicast channel includes:
[0173] Sending an indication to the first core network function to refuse to establish a unicast channel; or
[0174] Refuse to send an instruction to the first core network function to establish a unicast channel.
[0175] Optionally, the instruction to establish a unicast channel is further used to:
[0176] Instruct the first core network function to send multicast service information associated with a unicast channel to the access network node.
[0177] It should be noted that all descriptions about the second core network node in the above embodiments are applicable to this embodiment and can achieve the same technical effects as the above embodiments, and will not be repeated here.
[0178] like Figure 6 As shown, the embodiment of the present application further provides a shared channel management device 600, which is applied to the second core network node, including:
[0179] The second execution module 601 is configured to obtain MBS capability information of an access network node, and initiate or refuse to initiate a shared channel establishment request based on the MBS capability information of the access network node; or
[0180] A request for establishing a shared channel of an access network node is sent to a first core network node, and a message for rejecting establishment of a shared channel sent by the first core network node is received.
[0181] Optionally, the MBS capability information indicates whether the access network node supports MBS or does not support MBS.
[0182] Optionally, the shared channel establishment rejection message is sent by the first core network node according to MBS capability information of the access network node when it is determined that the access network node does not support MBS.
[0183] Optionally, the second execution module 601 executes an implementation method of initiating or refusing to initiate a shared channel establishment request based on the MBS capability information of the access network node, including:
[0184] In a case where the access network node does not support MBS, the second core network node refuses to initiate a request to establish a shared channel to the access network node; or
[0185] In a case where the access network node supports MBS, the second core network node initiates a request to the access network node to establish a shared channel.
[0186] Optionally, after the second execution module 601 receives the shared channel establishment rejection message sent by the first core network node, the method further includes:
[0187] The determination module is used to determine that the access network node does not support MBS, and refuse to initiate a request to establish a shared channel to the access network node.
[0188] Optionally, the implementation manner of acquiring the MBS capability information of the access network node includes at least one of the following:
[0189] Receiving MBS capability information of the access network node indicated by the first core network node;
[0190] Based on the service information that has been established between the second core network node and the access network node, the MBS capability information of the access network node is determined.
[0191] 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 waste of communication resources.
[0192] The shared channel management device in the embodiment of the present application can be a device, a device or electronic device with an operating system, or a component, an integrated circuit, or a chip in an electronic device. The device or electronic device is mainly a non-mobile terminal. Exemplarily, the non-mobile terminal can be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.
[0193] The shared channel management device provided in the embodiment of the present application can achieve Figure 4 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.
[0194] Preferably, an embodiment of the present application also provides a core network node, which is a second core network node, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When the program or instruction is executed by the processor, each process of an embodiment of a shared channel management method applied to the second core network side is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0195] An embodiment of the present application also provides a computer-readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the shared channel management method embodiment applied to the second core network side are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0196] The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0197] The embodiment of the present application further provides a core network node, where the core network node is a second core network node, including a processor and a communication interface, where the communication interface is used to:
[0198] Acquire MBS capability information of the access network node, and initiate or refuse to initiate a shared channel establishment request based on the MBS capability information of the access network node; or,
[0199] A request for establishing a shared channel of an access network node is sent to a first core network node, and a message for rejecting establishment of a shared channel sent by the first core network node is received.
[0200] The second core network node embodiment corresponds to the method embodiment on the second core network node side described above. Each implementation process and implementation method of the method embodiment described above can be applied to the second core network node embodiment and can achieve the same technical effect.
[0201] Specifically, the embodiment of the present application further provides a core network node. The specific structure of the core network node can be seen in Figure 3, and the core network node is a second core network node.
[0202] Specifically, the core network node of the embodiment of the present application includes: instructions or programs stored in the memory and executable on the processor, and the processor calls the instructions or programs in the memory to execute Figure 6 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.
[0203] The embodiment of the present application further provides a multicast service channel management device, which is applied to a second core network node, including:
[0204] A third execution module is configured to refuse to initiate a shared channel establishment request based on the existence of a storage record of information about the access network node; or
[0205] Initiate a request to establish a shared channel based on the absence of storage records for the information of the access network node; or
[0206] 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,
[0207] Based on the existence of an access network node that does not support multicast in the multicast session, instructing the establishment of a unicast channel; or,
[0208] Based on the fact that there is no access network node that does not support multicast in the multicast session, the establishment of the unicast channel is refused.
[0209] Optionally, the stored record is used to indicate that the access network node has joined the multicast session.
[0210] Optionally, when the third execution module executes the instruction to establish a shared channel or refuse to indicate the establishment of a shared channel based on the state of the multicast session, it is used to implement:
[0211] When the state of the multicast session is active, it indicates the establishment of a shared channel; or
[0212] When the state of the multicast session is an inactive state, the establishment of the shared channel is rejected.
[0213] Optionally, the third execution module executes the establishment of an indication shared channel to implement:
[0214] Sending, through the first core network function, an instruction to establish a shared channel to the access network node; or
[0215] Send a request to establish a shared channel to the access network node.
[0216] Optionally, the third execution module executes establishment of a rejection indication shared channel, to implement:
[0217] Sending, through the first core network function, an indication of refusing to establish a shared channel to the access network node; or
[0218] The request to establish a shared channel sent to the access network node is rejected.
[0219] Optionally, the third execution module executes the establishment of an indication unicast channel to implement:
[0220] An instruction to establish a unicast channel is sent to the first core network function.
[0221] Optionally, the third execution module executes establishment of a rejection indication unicast channel, to implement:
[0222] Sending an indication to the first core network function to refuse to establish a unicast channel; or
[0223] Refuse to send an instruction to the first core network function to establish a unicast channel.
[0224] Optionally, the instruction to establish a unicast channel is further used to:
[0225] Instruct the first core network function to send multicast service information associated with a unicast channel to the access network node.
[0226] The multicast service channel management device in the embodiment of the present application can be a device, a device or electronic device with an operating system, or a component, an integrated circuit, or a chip in an electronic device. The device or electronic device is mainly a non-mobile terminal. Exemplarily, the non-mobile terminal can be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.
[0227] The multicast service channel management device provided in the embodiment of the present application can achieve Figure 5 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.
[0228] Preferably, an embodiment of the present application also provides a core network node, which is a second core network node, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When the program or instruction is executed by the processor, each process of an embodiment of a multicast service channel management method applied to the second core network side is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0229] An embodiment of the present application also provides a computer-readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of an embodiment of a multicast service channel management method applied to the second core network side is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0230] The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0231] The embodiment of the present application further provides a core network node, where the core network node is a second core network node, including a processor and a communication interface, where the processor is used to:
[0232] Reject the request to establish a shared channel based on the existence of a storage record of the information of the access network node; or
[0233] Initiate a request to establish a shared channel based on the absence of storage records for the information of the access network node; or
[0234] 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,
[0235] Based on the existence of an access network node that does not support multicast in the multicast session, instructing the establishment of a unicast channel; or,
[0236] Based on the fact that there is no access network node that does not support multicast in the multicast session, the establishment of the unicast channel is refused.
[0237] The second core network node embodiment corresponds to the method embodiment on the second core network node side described above. Each implementation process and implementation method of the method embodiment described above can be applied to the second core network node embodiment and can achieve the same technical effect.
[0238] Specifically, the embodiment of the present application further provides a core network node. The specific structure of the core network node can be seen in Figure 3, and the core network node is a second core network node.
[0239] Specifically, the core network node of the embodiment of the present application includes: instructions or programs stored in the memory and executable on the processor. The processor calls the instructions or programs in the memory to execute the methods executed by the modules shown above and achieves the same technical effect. To avoid repetition, it will not be described here.
[0240] like Figure 7 As shown, the embodiment of the present application also provides a shared channel management method, including:
[0241] Step 701: upon receiving MBS capability acquisition request information sent by a first core network node, the access network node sends multicast broadcast service MBS capability information to the first core network node; or
[0242] The access network node sends capability indication information to the first core network node, where the capability indication information is used to assist the first core network node in determining MBS capability information.
[0243] Optionally, the MBS capability information indicates whether the access network node supports MBS or does not support MBS.
[0244] It should be noted that all descriptions about the access network node in the above embodiments are applicable to this embodiment and can achieve the same technical effects as the above embodiments, and will not be repeated here.
[0245] like Figure 8 As shown, the embodiment of the present application further provides a shared channel management device 800, which is applied to an access network node, including:
[0246] The capability sending module 801 is configured to send the multicast broadcast service MBS capability information to the first core network node upon receiving the MBS capability acquisition request information sent by the first core network node; or
[0247] Sending capability indication information to the first core network node, where the capability indication information is used to assist the first core network node in determining MBS capability information.
[0248] Optionally, the MBS capability information indicates whether the access network node supports MBS or does not support MBS.
[0249] 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 waste of communication resources.
[0250] The shared channel management device in the embodiment of the present application can be a device, a device or electronic device with an operating system, or a component, an integrated circuit, or a chip in an electronic device. The device or electronic device is mainly a non-mobile terminal. Exemplarily, the non-mobile terminal can be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.
[0251] The shared channel management device provided in the embodiment of the present application can achieve Figure 6 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.
[0252] The embodiment of the present application further provides an access network node, including a processor and a communication interface, where the communication interface is used to:
[0253] Upon receiving the MBS capability acquisition request information sent by the first core network node, the access network node sends the multicast broadcast service MBS capability information to the first core network node; or
[0254] The access network node sends capability indication information to the first core network node, where the capability indication information is used to assist the first core network node in determining MBS capability information.
[0255] The access network node embodiment corresponds to the above-mentioned access core network node side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to the access network node embodiment and can achieve the same technical effect. Specifically, Fig. 9 A schematic diagram of the hardware structure of an access network node for implementing an embodiment of the present application.
[0256] The core network node 900 includes an antenna 901, a radio frequency device 902, and a baseband device 903. The antenna 901 is connected to the radio frequency device 902. In the uplink direction, the radio frequency device 902 receives information through the antenna 901 and sends the received information to the baseband device 903 for processing. In the downlink direction, the baseband device 903 processes the information to be sent and sends it to the radio frequency device 902. The radio frequency device 902 processes the received information and sends it out through the antenna 901.
[0257] The frequency band processing device may be located in the baseband device 903 . The method performed by the network-side device in the above embodiment may be implemented in the baseband device 903 . The baseband device 903 includes a processor 904 and a memory 905 .
[0258] The baseband device 903 may include, for example, at least one baseband board on which a plurality of chips are arranged. Fig. 9 As shown, one of the chips is, for example, a processor 904, which is connected to a memory 905 to call a program in the memory 905 to execute the core network node operations shown in the above method embodiment.
[0259] The baseband device 903 may further include a network interface 906 for exchanging information with the radio frequency device 902 . The interface may be, for example, a common public radio interface (CPRI for short).
[0260] Specifically, the core network node of the embodiment of the present invention further includes: an instruction or program stored in the memory 905 and executable on the processor 904, and the processor 904 calls the instruction or program in the memory 905 to execute Figure 8 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.
[0261] Preferably, an embodiment of the present application also provides an access network node, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When the program or instruction is executed by the processor, each process of an embodiment of a shared channel management method applied to the access network node side is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.
[0262] The embodiment of the present application also 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 applied to the access network node side is implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here. Among them, the computer-readable storage medium is such as a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc.
[0263] Optional, such as Fig.10As shown, the embodiment of the present application also provides a communication device 1000, including a processor 1001, a memory 1002, and a program or instruction stored in the memory 1002 and executable on the processor 1001. For example, when the communication device 1000 is a core network node, the program or instruction is executed by the processor 1001 to implement the various processes of the above-mentioned shared channel management method embodiment applied to the first core network node or the second core network node side, and can achieve the same technical effect. When the communication device 1000 is an access network node, the program or instruction is executed by the processor 1001 to implement the various processes of the above-mentioned shared channel management method embodiment applied to the access network node side, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0264] The terminal involved in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called a user equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.
[0265] The access network node involved in the embodiments of the present application can be a base station (Base Transceiver Station, BTS) in Global System of Mobile communication (GSM) or Code Division Multiple Access (CDMA), or a base station (NodeB, NB) in Wideband Code Division Multiple Access (WCDMA), or an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a base station in the future 5G network, etc., which is not limited here.
[0266] The network side device and the terminal can each use one or more antennas for multi-input multi-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the form and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can be diversity transmission, precoding transmission or beamforming transmission, etc.
[0267] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned shared channel management method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0268] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0269] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.
[0270] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a network device to execute the methods described in each embodiment of the present application.
[0271] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.
Claims
1. A shared channel management method, It is characterized in that include: The first core network node obtains multicast broadcast service MBS capability information of at least one access network node; Among them, MBS capability information is used for management of shared channel establishment; After the first core network node learns the multicast broadcast service MBS capability information of at least one access network node, the method further includes: Based on the MBS capability information of the access network node, performing a first operation; The first operation includes: Responding to the shared channel establishment request sent by the second core network node; The responding to the shared channel establishment request sent by the second core network node includes at least one of the following: receiving a shared channel establishment request sent by the second core network node, and accepting or rejecting the shared channel establishment request based on the MBS capability information of the 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 message to the access network node based on the MBS capability information of the access network node and the state of the terminal, wherein the terminal is determined based on the shared channel establishment request; The sending of a group notification message or a single terminal paging message to the access network node based on the MBS capability information of the access network node and the state of the terminal includes: 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; When the MBS capability information indicates that the access network node supports MBS and the terminal is in an idle state, sending a group notification to the access network node; Among them, the first core network node is a mobile management function AMF entity, and the second core network node is a multicast broadcast session management function MB-SMF entity.
2. The method according to claim 1, It is characterized in that The MBS capability information indicates whether the access network node supports MBS or does not support MBS.
3. The method according to claim 1, It is characterized in that The accepting or rejecting the shared channel establishment request based on the MBS capability information of the access network node includes at least one of the following: When the MBS capability information indicates that the access network node does not support MBS, rejecting the shared channel establishment request; When the MBS capability information indicates that the access network node supports MBS, the shared channel establishment request is accepted.
4. The method according to claim 3, It is characterized in that In the case of accepting the shared channel establishment request, the method further includes: Send a shared channel establishment request message to the access network node.
5. The method according to claim 3, It is characterized in that In the case of rejecting the shared channel establishment request, the method further includes: Send a shared channel establishment rejection message to the second core network node.
6. The method according to claim 1 or 2, It is characterized in that The group notification message is used to notify the terminal to access the network.
7. The method according to claim 1 or 2, It is characterized in that The single terminal paging is used to notify the terminal to access the network.
8. The method according to claim 1, It is characterized in that The first core network node acquires the multicast broadcast service MBS capability information of at least one access network node, including: 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 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 according to the capability indication information.
9. A shared channel management method, It is characterized in that include: 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 message for rejecting establishing a shared channel sent by the first core network node, where the message for rejecting establishing a shared channel is sent by the first core network node when it is determined that the access network node does not support MBS based on the MBS capability information of the access network node; Among them, the first core network node is a mobile management function AMF entity, and the second core network node is a multicast broadcast session management function MB-SMF entity.
10. The method according to claim 9, It is characterized in that The MBS capability information indicates whether the access network node supports MBS or does not support MBS.
11. The method according to claim 9, It is characterized in that After receiving the shared channel establishment rejection message sent by the first core network node, the method further includes: It is determined that the access network node does not support MBS, and a request to establish a shared channel to the access network node is rejected.
12. A shared channel management device, applied to a first core network node, It is characterized in that include: An acquisition module, configured to acquire multicast broadcast service MBS capability information of at least one access network node; Among them, MBS capability information is used for management of shared channel establishment; After the acquisition module acquires the multicast broadcast service MBS capability information of at least one access network node, the method further includes: A first execution module, configured to execute a first operation based on the MBS capability information of the access network node; The first operation includes: Responding to the shared channel establishment request sent by the second core network node; The implementation of responding to the shared channel establishment request sent by the second core network node includes at least one of the following: receiving a shared channel establishment request sent by the second core network node, and accepting or rejecting the shared channel establishment request based on the MBS capability information of the 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 message to the access network node based on the MBS capability information of the access network node and the state of the terminal, wherein the terminal is determined based on the shared channel establishment request; The implementation method of sending a group notification message or a single terminal paging message to the access network node based on the MBS capability information of the access network node and the status of the terminal includes: 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; When the MBS capability information indicates that the access network node supports MBS and the terminal is in an idle state, sending a group notification to the access network node; Among them, the first core network node is a mobile management function AMF entity, and the second core network node is a multicast broadcast session management function MB-SMF entity.
13. A core network node, wherein the core network node is a first core network node, It is characterized in that It includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the shared channel management method as described in any one of claims 1 to 8.
14. A shared channel management device, applied to a second core network node, It is characterized in that include: a second execution module, configured to send a request for establishing a shared channel of the access network node to the first core network node, and receive a message for rejecting establishing a shared channel sent by the first core network node, wherein the message for rejecting establishing a shared channel is sent by the first core network node when it is determined that the access network node does not support MBS based on the MBS capability information of the access network node; Among them, the first core network node is a mobile management function AMF entity, and the second core network node is a multicast broadcast session management function MB-SMF entity.
15. A core network node, wherein the core network node is a second core network node, It is characterized in that It includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the shared channel management method as described in any one of claims 9 to 11.
16. A readable storage medium, It is characterized in that The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the shared channel management method according to any one of claims 1 to 11 are implemented.
