Patent Application
20230319905
The present application relates to the field of wireless communication technologies, and particularly to an MBS data communication method, a network side apparatus, and a network side device.
The existing 4G MBMS (Multimedia Broadcast Multicast Service) technology mainly includes following three modes.
In this mode, the MCE (Multi-cell/multicast Coordination Entity) sends an MBMS session start request to the CN (Core Network). The CN sends an MBMS session start response to the MCE. The MCE decides to use the SC-PTM for the MBMS holder. The MCE sends an MBMS session start request to the eNB (Evolved Node B). The eNB sends an MBMS session start response to the MCE. The eNB triggers a UE (User Equipment) to receive the service data of the SC-PTM.
In the above process, the interested UE only needs to read the SC-MCCH (Single Cell-MBMS Control Channel) information and learn the scheduling information of the SC-MTCH (Single Cell-MBMS 1 Channel), to receive the MBMS service in the idle state or connected state.
The UE receives the MBMS service in the unicast mode through a PDU (Protocol Data Unit) session establishment process. This mode requires the UE to establish a session process in the connected state, and the unicast communication of the MBMS service can only be completed through the traditional unicast PDU session establishment process.
The 4G network node E-UTRAN may determine that some UEs that are receiving the MBMS service in the PTP (Point To Point) mode need to switch to the PTM (Point To Multiploint) mode for data reception, where the PTM mode refers to the communication mode of MBSFN. Then, the E-UTRAN sends an RRC signaling message to notify these UEs. If the UE decides to terminate the data reception of the PTP, the UE sends a signaling message again to notify the E-UTRAN. Finally, the UE completes the transition from the PTP mode to the MBSFN mode.
It can be seen that the current 4G MBMS technology only allows the UE to switch to the statically planned target cell, and there are only two kinds of terminal’s reception requirements: connected state and idle state. The 5G NR, as a new generation radio access technology network, also has requirements for multicast/broadcast services. In one embodiment, there are in-active UEs under the 5G architecture. In order to enable these UEs also to maintain the continuity of reception of the MBS (Multimedia Broadcast Service), a new enhancement technology needs to be adopted to expand the current MBS service communication mechanism.
The present application provides an MBS service data communication method, and a network side apparatus and device, to solve the problem of how to ensure the continuity of the UE’s reception of the MBS service in the in-active state.
According to some embodiments of the present application, an MBS service data communication method is provided, which is applied to a network side device of a target cell and includes:
sending a UE context request message to a source cell and obtaining MBS session context related information from the source cell for a UE in an in-active state that moves to the target cell, and performing MBS data communication after the target cell establishes an MBS session context.
In one embodiment the MBS data communication is performed through a common forwarding channel with the source cell and/or an N3 channel with a core network.
In one embodiment performing the MBS data communication, includes:
In one embodiment performing the MBS data communication, includes:
In one embodiment obtaining the MBS session context related information from the source cell, includes:
In one embodiment the method further includes:
receiving an RRC connection resume request message indicating establishment of the MBS session context sent by the in-active UE when the UE determines that the target cell cannot meet an MBS session requirement.
In one embodiment performing the MBS data communication through the common forwarding channel with the source cell, includes:
In one embodiment the common forwarding address request process initiated to the source cell is a process of indicating a reused UE-associated XN-U address, or a newly defined non-UE-associated process.
In one embodiment the method further includes: initiating an MBS session context release process to release the common forwarding channel.
In one embodiment performing the MBS data communication through the N3 channel with the core network, includes:
In one embodiment the method further includes:
releasing the common forwarding channel after determining that the N3 channel is established and after receiving an end indication sent by the source cell on the common forwarding channel if the common forwarding channel currently exists.
According to some embodiments of the present application, an MBS service data communication method, applied to a network side device of a source cell, includes:
In one embodiment the method further includes: establishing a common forwarding channel with the target cell and transmitting MBS data, and the target cell sends the MBS data to the UE.
In one embodiment sending the MBS session context related information to the target cell, includes:
In one embodiment establishing the common forwarding channel with the target cell and transmitting the MBS data, includes:
In one embodiment the common forwarding address request process is a process of indicating a reused UE-associated XN-U address, or a newly defined non-UE-associated process.
The method further includes:
initiating an MBS session context release process to release the common forwarding channel.
According to some embodiments of the present application, a network side device is provided, including: a memory and a processor;
In one embodiment the processor is further configured to perform the MBS data communication through a common forwarding channel with the source cell and/or an N3 channel with a core network.
In one embodiment the processor performs the MBS data communication, including:
In one embodiment the processor performs the MBS data communication, including:
In one embodiment the processor obtains the MBS session context related information from the source cell, including:
In one embodiment the processor is further configured to:
receive an RRC connection resume request message indicating establishment of the MBS session context sent by the in-active UE when the UE determines that the target cell cannot meet an MBS session requirement.
In one embodiment the processor performs the MBS data communication through the common forwarding channel with the source cell, including:
In one embodiment the common forwarding address request process initiated to the source cell is a process of indicating a reused UE-associated XN-U address, or a newly defined non-UE-associated process.
In one embodiment the processor is further configured to:
initiate an MBS session context release process to release the common forwarding channel.
In one embodiment the processor performs the MBS data communication through the N3 channel with the core network, including:
In one embodiment the processor is further configured to:
release the common forwarding channel after determining that the N3 channel is established and after receiving an end indication sent by the source cell on the common forwarding channel if the common forwarding channel currently exists.
According to some embodiments of the present application, a network side device is provided, including: a memory and a processor;
In one embodiment the processor is further configured to: establish a common forwarding channel with the target cell and transmit MBS data, and the target cell sends the MBS data to the UE.
In one embodiment the processor sends the MBS session context related information to the target cell, including:
In one embodiment the processor establishes the common forwarding channel with the target cell and transmits the MBS data, including:
In one embodiment the common forwarding address request process is a process of indicating a reused UE-associated XN-U address, or a newly defined non-UE-associated process.
In one embodiment the processor is further configured to:
initiate an MBS session context release process to release the common forwarding channel.
According to some embodiments of the present application, a network side apparatus is provided, including:
In one embodiment the network side apparatus further includes:
In one embodiment the MBS data communication device performs the MBS data communication, including:
In one embodiment the MBS data communication device performs the MBS data communication, including:
In one embodiment the MBS context obtaining device obtains the MBS session context related information from the source cell, including:
In one embodiment the MBS context obtaining device is further configured to:
receive an RRC connection resume request message indicating establishment of the MBS session context sent by the in-active UE when the UE determines that the target cell cannot meet an MBS session requirement.
In one embodiment the MBS data forwarding device performs the MBS data communication through the common forwarding channel with the source cell, including:
In one embodiment the common forwarding address request process initiated to the source cell is a process of indicating a reused UE-associated XN-U address, or a newly defined non-UE-associated process.
In one embodiment the network side apparatus further includes:
a channel release device configured to initiate an MBS session context release process to release the common forwarding channel.
In one embodiment performing the MBS data communication through the N3 channel with the core network, includes:
The channel establishment device is further configured to:
release the common forwarding channel after determining that the N3 channel is established and after receiving an end indication sent by the source cell on the common forwarding channel if the common forwarding channel currently exists.
According to some embodiments of the present application, a network side apparatus is provided, including:
In one embodiment the network side apparatus further includes:
In one embodiment the MBS context sending device sends the MBS session context related information to the target cell, including:
In one embodiment the MBS communication device is configured to:
In one embodiment the common forwarding address request process is a process of indicating a reused UE-associated XN-U address, or a newly defined non-UE-associated process.
In one embodiment the network side apparatus further includes:
a forwarding channel release device configured to initiate an MBS session context release process to release the common forwarding channel.
According to some embodiments of the present application, there is provided a chip, which is coupled to a memory in a device, and the chip invokes program instructions stored in the memory when running, to implement the above various embodiments of the present application and any possible method involved in the various aspects.
According to some embodiments of the present application, there is provided a computer readable storage medium storing program instructions, which, when executed on a computer, cause the computer to perform the above various embodiments of the present application and any possible method involved in the various aspects.
According to some embodiments of the present application, there is provided a computer program product which, when running on an electronic device, causes the electronic device to implement the above various embodiments of the present application and any possible method involved in the various embodiments.
The MBS service data communication method and the network side device and apparatus provided in the present application have the following beneficial effects.
Compared with the existing 4G MBMS technology, the solution provided by the present application allows the UE in the in-active state to trigger a new MBS context establishment process to transmit the MBS data at a new 5G RAN target node, to ensure the continuity of the MBS service communication in the in-active state dynamically and flexibly.
In order to illustrate the embodiments of the present application more clearly, the accompanying figures which need to be used in describing the embodiments will be introduced below briefly. The accompanying figures described below are only some embodiments of the present application.
In order to make the embodiments of the present application clearer, the present application will be further illustrated below in details with reference to the accompanying figures. The described embodiments are merely a part of the embodiments of the present application but not all the embodiments.
The existing 4G MBMS technology mainly includes following three modes.
1) For the SC-PTM mode, as shown in
Step 1: the CN sends an MBMS session start request to the MCE.
Step 1a: the MCE sends an MBMS session start response to the CN.
Step 2: the MCE decides to use the SC-PTM for the MBMS holder.
Step 3: the MCE sends an MBMS session start request to the eNB.
Step 3a: the eNB sends an MBMS session start response to the MCE.
Step 4: the eNB triggers the UE to perform the single-cell point to multipoint.
In this process, the interested UE only needs to read the SC-MCCH information and learn the scheduling information of the SC-MTCH, to receive the MBMS service in the idle state or connected state.
2) The process of receiving the MBMS service in unicast mode, as shown in
Step 1: the UE sends a PDU session establishment request to the AMF.
Step 2: the AMF sends a PDU session resource establishment request to the gNB.
Step 3: the gNB sends the RRC reconfiguration information to the UE.
Step 4: the UE reconstructs the data radio bearer.
Step 5: the UE sends the RRC reconfiguration complete to the gNB.
Step 6: the gNB sends a PDU session resource establishment response to the AMF.
Step 7: the gNB, UPF and UE perform the uplink data update.
The MBMS service can only complete the unicast communication of the MBMS service through the traditional unicast PDU session establishment process.
3) The process of bearer conversion from 4G MBSFN to unicast, as shown in
In the above process, the 4G network node E-UTRAN may determine that some UEs that are receiving the MBMS service in the PTP mode need to switch to the PTM mode for data reception, where the PTM mode refers to the communication mode of MBSFN. Step 1: the E-UTRAN sends an RRC signaling message to notify the corresponding UE that the MBMS service in the PTP mode is converted into being sent in the PTM mode, and sends the relevant information of the PTM mode. Step 2: the UE responds to the above message. Step 3: if the UE decides to terminate the data reception of the PTP, the UE sends a signaling message again to notify the E-UTRAN. For example, the UE notifies the E-UTRAN to stop sending the MBMS service in the PTP mode. Step 4: the E-UTRAN responds to the above message. Finally, the UE completes the transition from the PTP mode to the MBSFN mode.
The existing 4G MBMS technology only allows the UE to switch to the statically planned target cell, and there are only two kinds of terminal’s reception requirements: connected state and idle state. In this way, the receiving of the MBMS service by the UE in the in-active state is bound to be limited under the 5G NR architecture.
Based on the above problem, embodiments of the present application provide a solution for MBS service data communication. When a UE in the in-active state moves to a new target cell, if the target cell does not have the MBS service context in which the UE is interested, the UE is allowed to trigger the establishment of the corresponding MBS context in the target cell by initiating an RRC resume process, and the target cell can perform the MBS service communication for the UE based on the established context.
Embodiments of the present application further provide another solution for MBS service data communication. On the basis of establishing the corresponding MBS context in the target cell, the target cell establishes and maintains the data communication channel of the MBS session in two ways according to different situations. One way is that the target cell establishes a common forwarding channel with the source cell, and the other way is that the target cell establishes an N3 channel with the core network. In one embodiment, both of the two channels are established, and the N3 channel is maintained for M3 data communication after the common forwarding channel is released.
The embodiments of the two solutions will be illustrated in detail below.
As shown in
In this embodiment, the way for the above-mentioned MBS service data communication system to achieve the MBS service communication is a way of performing the MBS data communication by resuming the MBS session context.
In one embodiment, the first network side device is further configured to establish a common forwarding channel with the target cell and transmit the MBS data, and the target cell sends the MBS data to the UE.
The second network side device is further configured to establish a common forwarding channel with the target cell and transmit the MBS data, and the target cell sends the MBS data to the UE.
In this embodiment, the way for the above-mentioned MBS service data communication system to achieve the MBS service communication is a way of performing the MBS data communication through the common forwarding channel.
In one embodiment, the first network side device in the MBS service data communication system provided in the embodiment of the present application is further configured to perform the MBS data communication through an N3 channel with the core network.
The system further includes: a third network side device configured to establish an N3 channel with the target cell for transmitting the MBS data to the in-active UE; and send the MBS data to the target cell through the N3 channel, and the target cell sends the MBS data to the in-active UE.
In this embodiment, the way for the above-mentioned MBS service data communication system to achieve the MBS service communication is a way of performing the MBS data communication through the N3 channel.
In one embodiment, as shown in
In this embodiment, the way for the above-mentioned MBS service data communication system to achieve the MBS service communication is a way of performing the MBS data communication through the common forwarding channel and N3 channel.
In the embodiments of the present application, the user terminal UE may refer to an access terminal, a user unit, a user station, a mobile radio station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-carried device, a wearable device, a mobile station in the 5G network, or a subscription device in the future evolved Public Land Mobile Network (PLMN) network, etc.
The first/second network side device may be a generation Node B (gNB) in the 5G system, or may be a Base Transceiver Station (BTS) in the Global System of Mobile communication (GSM) system or Code Division Multiple Access (CDMA), or may be a NodeB (NB) in the Wideband Code Division Multiple Access (WCDMA) system, or may be an evolutional Node B (eNB or eNodeB) in the Long Term Evolution (LTE) system, etc.
The third network side device may be a UPF entity in the 5G system.
The ways for the MBS service data communication system to achieve the MBS service communication will be illustrated in detail below.
The first way: a way of performing the MBS data communication by resuming the MBS session context.
When a UE in the in-active state moves to a new target cell, if the target cell does not have the MBS service context in which the UE is interested, the UE is allowed to initiate an RRC resume process.
In one embodiment, the UE in the in-active state moves to the target cell, determines that the target cell cannot meet the MBS session requirement, and sends an RRC connection resume request message to the first network side device. The first network side device receives the RRC connection resume request message carrying the indication information similar to “MBS session establishment” to indicate the establishment of the MBS session context send by the UE in the in-active state when determining that the target cell cannot meet the MBS session requirement.
The Resume Cause in the indication information “RRC resume request message” carries indication information similar to “MBS session establishment”; or
The indication information “RRC resume request message” carries a list of MBS session services that the UE is interested in.
After receiving the RRC connection resume request message, the first network side device determines that it needs to establish an MBS session context in the target cell according to the indication. The first network side device initiates an MBS context resume process to the second network side device of the source cell, and obtains the related information of the MBS session service context to be established through this process. For example, the first network side device sends a UE context request message to the source cell, indicates through the UE context request message that the source cell needs to return the corresponding MBS session service context related information, and receives a UE context response message returned by the source cell, where the UE context response message carries the MBS session service context related information.
In one embodiment, the UE context request message sent by the source cell carries the MBS session context list information existing in the target cell. After receiving the UE context request message, the target cell determines the MBS session services existing in the source cell, determines which MBS services the source cell does not have according to the context related information of the existing MBS session services saved by itself, to send the new MBS service session context information to the source cell. That is, the UE context request message sent to the source cell carries the new MBS service session context related information that does not exist in the target cell.
In one embodiment, the UE context request message sent by the source cell to the target cell does not carry any MBS service session related information, but indicates that the target cell needs to return the MBS service session context information, where the indication method may be explicit or implicit indication. After receiving the UE context request message, the target cell feeds back the session context related information of all the MBS services stored locally. That is, the UE context response message returned by the target cell carries the session context related information of all the MBS services related to the UE.
In one embodiment, the UE context request message sent by the source cell carries the MBS session context list information expected by the UE. After receiving the UE context request message, the target cell locally queries the MBS service session context related information expected by the UE and sends it to the source cell. That is, the UE context response message sent by the target cell to the source cell carries the MBS service session context related information expected by the UE.
After obtaining the MBS session service related context information, the target cell establishes the MBS session context in the target cell according to the MBS session service related context information. After the target cell establishes the MBS session context, the MBS data communication may be performed in any of the following ways.
After establishing the MBS session context, the target cell configures the MBS resource for MBS session service data communication and sends it to the UE through an RRC connection message. After receiving the RRC connection message, the UE enters the connected state and returns an RRC connection complete message to the target cell. The target cell receives the RRC connection complete message returned by the UE and transmits the MBS data to the UE in the connected state.
After establishing the MBS session context, the target cell configures the MBS resource, and sends the configured MBS resource to the UE through an RRC connection release message or an RRC reject message if the target cell wants the UE to enter to the in-active state to receive the MBS data. The UE enters the in-active state after receiving the RRC connection release message or RRC reject message. The target cell transmits the MBS data to the UE in the in-active state.
The detailed flow of the way of performing the MBS data communication by resuming the MBS session context is given below in conjunction with the flowchart, as shown in
Step 601: a UE in the in-active state receives some MBS session services in the source cell.
Step 602: the UE moves to a new target cell and determines that the target cell does not have an MBS session context that the UE is interested in, and then the UE initiates an RRC resume process.
In one embodiment, the UE sends an RRC connection resume request message (RRC resume request message) to the target cell (or network entity), where the Resume Cause in the message carries indication information similar to “MBS session establishment”.
Step 603: the target cell receives the RRC connection resume request message, parses out the source serving node, and prepares to send a UE context request message to the source serving node to initiate a UE context request process.
After receiving the above RRC connection resume request message, the target cell determines the MBS session context that has existed in the current target serving node, and sends the UE context request message to the source cell, where this message is allowed to carry the MBS session context service list information that has existed in the current target service node.
The target cell may parse out the corresponding source serving node according to the I-RNTI in the RRC connection resume request message.
Step 604: the source cell receives the UE context request message, and returns a UE context response message carrying the new MBS session service context related information not stored in the source cell to the target cell.
After receiving the UE context request message, the source cell determines the MBS session service context related information that has existed in the target cell, and determines the MBS session services that need to be established at the new target node in combination with the locally-stored MBS context related information of interest to the UE. Correspondingly, the returned UE context response message carries the context related information of the new MBS sessions that need to be established by the target cell, including at least the QOS profile, multicast address and other information corresponding to these MBS sessions.
Step 605: the target cell receives the UE context response message returned by the source cell, and starts the establishment of the MBS session context according to the MBS session service related information in the message.
The MBS session context may include information such as corresponding QOS profile and multicast address, and can be added to the corresponding N3 channel multicast communication group later if necessary.
Step 606: the target cell decides, for the UE, whether to use the MRB or DRB to transmit the corresponding MBS session service, and executes step 607 or step 607a.
Step 607: the target cell sends an RRC resume message to the UE, configures the corresponding DRB resource or MRB, and uses the configured resource for MBS data communication.
Step 608: the UE returns an RRC resume complete message to the target cell after receiving the RRC resume message, and starts preparing to receive the corresponding MBS session service according to the configuration.
Step 607a: the target cell returns an RRC release or RRC reject message carrying the corresponding resource configuration to the UE.
The message explicitly or implicitly indicates “entering the in-active state” to receive the MBS session. If the MRB resource is configured and the UE is expected to continue to receive data in the in-active state, the target cell returns the RRC release or RRC reject message carrying the corresponding resource configuration to the UE.
Step 608a: the UE enters the in-active state, and prepares to receive the corresponding MBS session service according to the corresponding configuration.
It should be noted that, during the implementations, the content of the UE context request/response message involved in the above process may be changed. For example, the UE context response message returned by the source cell carries all the MBS session context related information that the UE is interested in, at least including information such as QOS profile and multicast address corresponding to these MBS sessions. In one embodiment, the UE context request message sent by the target cell carries the MBS session context list information expected by the UE, and the UE context response message returned by the source cell carries the MBS service session context related information expected by the UE. The other processes are the same as above, and the specific processes will not be repeated here.
The second way: a way of performing the MBS data communication through the common forwarding channel.
When the UE in the in-active state moves to a new target cell, as one embodiment: the UE in the in-active state moves to the target cell and determines that the target cell cannot meet the MBS session requirement, and the target cell obtains the MBS session context related information from the source cell by sending a UE context request message to the source cell; after establishing the MBS session context, the target cell indicates the expected MBS session context list information to the source cell by initiating a common forwarding address request process to the second network side device of the source cell; and the source cell establishes a common forwarding channel with the target cell and transmits the MBS data, and the target cell sends the MBS data to the UE. For example, the target cell receives the MBS data sent by the source cell on the common forwarding channel according to the expected MBS session context list information, and sends the MBS data to the UE.
The above-mentioned common forwarding address request process initiated by the target cell to the source cell may be, but not limited to, a process of indicating a reused UE-associated XN-U address, or a newly defined non-UE-associated address communication process.
In one embodiment the target cell triggers the common forwarding address request process to the source cell. The request contains the MBS session service list information, that the local cell does not have and that is expected to be established, to be indicated to the common forwarding channel with the source cell, and the MBS session service list information that is expected to be established may be of per MBS session. Next, the source cell configures the MBS resource, enables the forwarding operation of the corresponding MBS session data packet on the common forwarding channel, and sends the MBS data to the UE according to the MBS data sent by the expected MBS session context list information.
After that, the target cell (or the network entity) is allowed to maintain this channel to transmit the MBS service data in this cell. At any time, the target cell or the source cell can actively initiate the context release process of the MBS session, the corresponding forwarding channel is also released, and the MBS data is transmitted to the UE in the in-active state.
The third way: a way of performing the MBS data communication through the N3 channel.
When the UE in the in-active state moves to a new target cell, one embodiment: the UE in the in-active state moves to the target cell, determines that the target cell cannot meet the MBS session requirement, and obtains the MBS session context related information from the source cell by sending a UE context request message to the source cell; after establishing the MBS session context, the target cell triggers an N3 channel establishment process with the second network side device; the source cell establishes an N3 channel with the target cell for transmitting the MBS data to the UE in the in-active state, and sends the MBS data to the target cell through the N3 channel; and the target cell sends the MBS data to the UE in the in-active state.
In one embodiment, the N3 channel establishment process is a reused UE-associated path switching process, or a newly defined non-UE-associated MBS session establishment request process. The MBS data sent by the UPF is received through the N3 channel, and the MBS data is sent to the UE.
The fourth way: a way of performing the MBS data communication through the common forwarding channel and N3 channel.
When the UE in the in-active state moves to a new target cell, as in some embodiments: the UE in the in-active state moves to the target cell, determines that the target cell cannot meet the MBS session requirement, and obtains the MBS session context related information from the source cell by sending a UE context request message to the source cell; and after establishing the MBS session context, the target cell triggers a process of initiating a common forwarding address request to the second network side device of the source cell and an N3 channel establishment process with the third network side device.
The establishment of the common forwarding channel and the establishment of the N3 channel can be triggered at the same time, or the establishment of the common forwarding channel is triggered before the establishment of the N3 channel is triggered. The detailed process of establishing the common forwarding channel and N3 channel and transmitting the MBS data can refer to the description in the above-mentioned embodiments and will not be repeated here.
It is necessary to note that the common forwarding channel is released after determining that the N3 channel is established and after receiving an end indication sent by the source cell on the common forwarding channel if the common forwarding channel currently exists. The process is: if the target cell has previously or simultaneously initiated the common forwarding address request process to the second network side device, the source cell enables the forwarding operation of the corresponding MBS session data packet on the common forwarding channel, and sends the MBS data to the UE according to the MBS data sent by the expected MBS session context list information. Subsequently, after receiving the end marker indication on the forwarding channel from the source cell, the target cell releases the common forwarding channel established for this MBS session, receives the MBS data sent by the UPF through the N3 channel, and sends the MBS data to the UE.
The system architectures and service scenarios described in the embodiments of the present application are intended to illustrate the embodiments of the present application more clearly, and do not constitute a limitation on the embodiments of the present application. With the evolution of system architectures and the emergence of new service scenarios, the embodiments of the present application are also applicable to similar problems.
Referring to
Step 701: sending a UE context request message to a source cell and obtaining the MBS session context related information from the source cell for an in-active UE that moves to a target cell.
Step 702: performing MBS data communication after the target cell establishes an MBS session context.
In one embodiment the method further includes:
In one embodiment performing the MBS data communication, includes:
In one embodiment performing the MBS data communication, includes:
In one embodiment obtaining the MBS session context related information from the source cell, includes:
In one embodiment the method further includes:
receiving an RRC connection resume request message indicating establishment of the MBS session context sent by the in-active UE when determining that the target cell cannot meet an MBS session requirement.
In one embodiment performing the MBS data communication through the common forwarding channel with the source cell, includes:
In one embodiment the common forwarding address request process initiated to the source cell is a process of indicating a reused UE-associated XN-U address, or a newly defined non-UE-associated process.
In one embodiment the method further includes:
initiating an MBS session context release process to release the common forwarding channel.
In one embodiment performing the MBS data communication through the N3 channel with the core network, includes:
In one embodiment the method further includes:
releasing the common forwarding channel after determining that the N3 channel is established and after receiving an end indication sent by the source cell on the common forwarding channel if the common forwarding channel currently exists.
Embodiments of the present application further provide an MBS service data communication method, applied to a network side device of a target cell. The process, as shown in
Step 801: receiving a context request message sent by the target cell for an in-active UE.
Step 802: sending the MBS session context related information to the target cell, and the target cell establishes an MBS session context and performs MBS data communication.
In one embodiment the method further includes:
obtaining the MBS session context related information from a source cell by sending a UE context request message to the source cell, and transmitting the MBS data through a common forwarding channel after the target cell establishes the MBS session context, and the target cell sends the MBS data to the UE.
In one embodiment sending the MBS session context related information to the target cell, includes:
In one embodiment establishing the common forwarding channel with the target cell and transmitting the MBS data, includes:
In one embodiment the common forwarding address request process is a process of indicating a reused UE-associated XN-U address, or a newly defined non-UE-associated process.
The method further includes:
initiating an MBS session context release process to release the common forwarding channel.
Embodiments of the present application further provide an MBS service data communication method, applied to a core network device. The process, as shown in
Step 901: establishing an N3 channel with a target cell for transmitting the MBS data to an in-active UE. The target cell completes the establishment of the MBS session context through RRC connection resume.
Step 902: sending the MBS data to the target cell through the N3 channel, and the target cell sends the MBS data to the in-active UE.
In one embodiment establishing the N3 channel with the target cell for transmitting the MBS data to the in-active UE, includes:
The above MBS service data communication method provided by the embodiments of the present application and the MBS service data communication solution in the MBS service data communication system provided by the above embodiments, and various implementations of the MBS service data communication solution provided by the above embodiments may be applied to the MBS service data communication method in the embodiments, which will not be repeated here.
Embodiments of the present application provide a network side device, which may be a base station of a target cell, as shown in
The processor 1000 is responsible for managing the bus architecture and general processing, and the memory 1001 may store the data used by the processor 1000 when performing the operations. The transceiver 1002 is configured to receive and send the data under the control of the processor 1000.
The bus architecture may include any numbers of interconnected buses and bridges, and link various circuits of one or more processors represented by the processor 1000 and the memory represented by the memory 1001. The bus architecture may further link various other circuits such as peripheral device, voltage regulator and power management circuit, which are all well known in the art and thus will not be further described again herein. The bus interface provides an interface. The processor 1000 is responsible for managing the bus architecture and general processing, and the memory 1001 may store the data used by the processor 1000 when performing the operations.
The procedure disclosed by the embodiments of the present application may be applied in the processor 1000 or implemented by the processor 1000. In the implementation process, each step of the signal processing flow may be completed by the integrated logic circuit of hardware or the instruction in the form of software in the processor 1000. The processor 1000 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or perform each method, step and logical block diagram disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in combination with the embodiments of the present application may be directly completed by a hardware processor, or completed by a combination of hardware and software devices in the processor. The software devices may be located in the random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable read only memory, register and other mature storage medium in the art. The storage medium is located in the memory 1001, and the processor 1000 reads the information in the memory 1001 and completes the steps of the signal processing flow in combination with its hardware.
For example, the processor 1000 is configured to read the program in the memory 1001 to:
send a UE context request message to a source cell and obtain MBS session context related information from the source cell for an in-active UE that moves to a target cell, and perform MBS data communication after the target cell establishes an MBS session context.
In one embodiment the processor is further configured to:
establish a common forwarding channel with the source cell and/or an N3 channel with a core network for MBS data communication.
In one embodiment the processor performs the MBS data communication, including:
In one embodiment the processor performs the MBS data communication, including:
In one embodiment the processor obtains the MBS session context related information from the source cell, including:
In one embodiment the processor is further configured to:
receive an RRC connection resume request message indicating establishment of the MBS session context sent by the in-active UE when determining that the target cell cannot meet an MBS session requirement.
In one embodiment the processor performs the MBS data communication through the common forwarding channel with the source cell, including:
In one embodiment the common forwarding address request process initiated to the source cell is a process of indicating a reused UE-associated XN-U address, or a newly defined non-UE-associated process.
In one embodiment the processor is further configured to:
initiate an MBS session context release process to release the common forwarding channel.
In one embodiment the processor performs the MBS data communication through the N3 channel with the core network, including:
In one embodiment the processor is further configured to:
release the common forwarding channel after determining that the N3 channel is established and after receiving an end indication sent by the source cell on the common forwarding channel if the common forwarding channel currently exists.
Embodiments of the present application further provide a network side device, which may be a base station of a source cell. As shown in
The processor 1100 is responsible for managing the bus architecture and general processing, and the memory 1101 may store the data used by the processor 1100 when performing the operations. The transceiver 1102 is configured to receive and send the data under the control of the processor 1100.
The bus architecture may include any numbers of interconnected buses and bridges, and link various circuits of one or more processors represented by the processor 1100 and the memory represented by the memory 1101. The bus architecture may further link various other circuits such as peripheral device, voltage regulator and power management circuit, which are all well known in the art and thus will not be further described again herein. The bus interface provides an interface. The processor 1100 is responsible for managing the bus architecture and general processing, and the memory 1101 may store the data used by the processor 1100 when performing the operations.
The procedure disclosed by the embodiment of the present application may be applied in the processor 1100 or implemented by the processor 1100. In the implementation process, each step of the signal processing flow may be completed by the integrated logic circuit of hardware or the instruction in the form of software in the processor 1100. The processor 1100 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or perform each method, step and logical block diagram disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in combination with the embodiments of the present application may be directly completed by a hardware processor, or completed by a combination of hardware and software devices in the processor. The software devices may be located in the random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable read only memory, register and other mature storage medium in the art. The storage medium is located in the memory 1101, and the processor 1100 reads the information in the memory 1101 and completes the steps of the signal processing flow in combination with its hardware.
For example, the processor 1100 is configured to read the program in the memory 1101 to:
In one embodiment the processor is further configured to:
establish a common forwarding channel with the target cell and transmit MBS data, and the target cell sends the MBS data to the UE.
In one embodiment the processor sends the MBS session context related information to the target cell, including:
In one embodiment the processor establishes the common forwarding channel with the target cell and transmits the MBS data, including:
In one embodiment the common forwarding address request process is a process of indicating a reused UE-associated XN-U address, or a newly defined non-UE-associated process.
In one embodiment the processor is further configured to:
initiate an MBS session context release process to release the common forwarding channel.
Embodiments of the present application further provide a network side device, which may be an entity device (such as UPF) of the core network. As shown in
The processor 1200 is responsible for managing the bus architecture and general processing, and the memory 1201 may store the data used by the processor 1200 when performing the operations. The transceiver 1202 is configured to receive and send the data under the control of the processor 1200.
The bus architecture may include any numbers of interconnected buses and bridges, and link various circuits of one or more processors represented by the processor 1200 and the memory represented by the memory 1201. The bus architecture may further link various other circuits such as peripheral device, voltage regulator and power management circuit, which are all well known in the art and thus will not be further described again herein. The bus interface provides an interface. The processor 1200 is responsible for managing the bus architecture and general processing, and the memory 1201 may store the data used by the processor 1200 when performing the operations.
The procedure disclosed by the embodiment of the present application may be applied in the processor 1200 or implemented by the processor 1200. In the implementation process, each step of the signal processing flow may be completed by the integrated logic circuit of hardware or the instruction in the form of software in the processor 1200. The processor 1200 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or perform each method, step and logical block diagram disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in combination with the embodiments of the present application may be directly completed by a hardware processor, or completed by a combination of hardware and software devices in the processor. The software devices may be located in the random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable read only memory, register and other mature storage medium in the art. The storage medium is located in the memory 1201, and the processor 1200 reads the information in the memory 1201 and completes the steps of the signal processing flow in combination with its hardware.
For example, the processor 1200 is configured to read the program in the memory 1201 to:
In one embodiment the processor establishes the N3 channel with the target cell for transmitting the MBS data to the in-active UE, including:
Embodiments of the present application further provide a network side apparatus, which is applied to a target cell, as shown in
In one embodiment the network side apparatus further includes:
In one embodiment the MBS data communication device performs the MBS data communication, including:
In one embodiment the MBS data communication device performs the MBS data communication, including:
In one embodiment the MBS context obtaining device obtains the MBS session context related information from the source cell, including:
In one embodiment the MBS context obtaining device is further configured to:
receive an RRC connection resume request message indicating establishment of the MBS session context sent by the in-active UE when determining that the target cell cannot meet an MBS session requirement.
In one embodiment the MBS data forwarding device performs the MBS data communication through the common forwarding channel with the source cell, including:
In one embodiment the common forwarding address request process initiated to the source cell is a process of indicating a reused UE-associated XN-U address, or a newly defined non-UE-associated process.
In one embodiment the network side apparatus further includes:
a channel release device configured to initiate an MBS session context release process to release the common forwarding channel.
In one embodiment performing the MBS data communication through the N3 channel with the core network, includes:
The channel establishment device is further configured to:
release the common forwarding channel after determining that the N3 channel is established and after receiving an end indication sent by the source cell on the common forwarding channel if the common forwarding channel currently exists.
Embodiments of the present application further provide a network side apparatus, which is applied to a source cell. As shown in
In one embodiment the MBS context sending device sends the MBS session context related information to the target cell, including:
In one embodiment the MBS communication device is configured to:
In one embodiment the common forwarding address request process is a process of indicating a reused UE-associated XN-U address, or a newly defined non-UE-associated process.
In one embodiment the network side apparatus further includes:
a forwarding channel release device configured to initiate an MBS session context release process to release the common forwarding channel.
Embodiments of the present application further provide a network side apparatus, which is applied to a core network entity. As shown in
In one embodiment the N3 channel establishment device is configured to establish the N3 channel through an N3 channel establishment process triggered by the target cell. The N3 channel establishment process is a reused UE-associated path switching process, or a newly defined non-UE-associated MBS session establishment request process.
The above network side device/network side apparatus provided by the embodiments of the present application and the network side device in the MBS service data communication system provided by the above embodiments, and various implementations of the network side device provided in the above embodiments may be applied to the network side device/network side apparatus in the embodiments for implementation, which will not be repeated here.
Embodiments of the present disclosure further provide a computer readable storage medium including instructions, which, when executed on a computer, cause the computer to execute the MBS service data communication method provided by the above-mentioned embodiments.
For the convenience and simplicity of description, the specific working processes of the above-mentioned devices and devices can refer to the corresponding processes in the method embodiments described above, and the detailed description thereof will be omitted here.
In the several embodiments provided by the present application, it should be understood that the disclosed system, devices and methods may be implemented in other manners. For example, the device embodiments described above are only schematic, for example, the division of the devices is merely a logical function division. In an actual implementation, there may be other division manners, for example, of the devices or components may be combined or integrated to another system, or some features may be ignored or not performed. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be implemented through the indirect coupling or communication connection between some interfaces, devices or devices, and may be in the electrical or other forms.
The devices described as separate components may or may not be physically separated, and the components displayed as devices may or may not be physical devices, that is, may be located in one place or may be distributed onto multiple network devices. Some or all of the devices may be selected according to the actual needs to achieve the objects of the solutions of the embodiments.
In addition, the functional devices in each embodiment of the present application may be integrated into one processing device, or each device may exist alone physically, or two or more devices may be integrated into one device. The above-mentioned integrated devices can be implemented in the form of hardware, or can be implemented in the form of software functional devices. When the integrated device is implemented in the form of software functional device and sold or used as an independent product, it may be stored in a computer readable storage medium.
The above embodiments may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, they may be implemented in the form of a computer program product in whole or in part.
The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from a computer readable storage medium to another computer readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server or data center to another website, computer, server or data center in a wired (e.g., coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) way. The computer readable storage medium may be any available medium that can be stored by a computer, or a data storage device such as server or data center that is integrated with one or more available media. The available medium may be a magnetic medium (for example, floppy disk, hard disk, magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, Solid State Disk (SSD)), etc.
The embodiments of the present application are introduced in detail above, specific examples are used in the present application to illustrate the principles and embodiments of the present application, and the description of the above embodiments is only used to help the understanding of the methods of the present application and the core ideas thereof; and at the same time, modifications on the specific embodiments and the application scope can be made according to the ideas of the present application. In summary, the content of this specification should not be construed as a limitation on the present application.
The embodiments of the present application can provide methods, systems and computer program products. Thus the present application can take the form of hardware embodiments alone, software embodiments alone, or embodiments combining the software and hardware aspects. Also the present application can take the form of computer program products implemented on one or more computer usable storage mediums (including but not limited to magnetic disk memories, CD-ROMs, optical memories and the like) containing computer usable program codes therein.
The present application is described by reference to the flow charts and/or the block diagrams of the methods, the devices (systems) and the computer program products according to the present application. It should be understood that each process and/or block in the flow charts and/or the block diagrams, and a combination of processes and/or blocks in the flow charts and/or the block diagrams can be implemented by the computer program instructions. These computer program instructions may be provided to a general-purpose computer, a dedicated computer, an embedded processor, or a processor of another programmable data processing device to produce a machine, and an apparatus for implementing the functions specified in one or more processes of the flow charts and/or one or more blocks of the block diagrams is produced by the instructions executed by the computer or the processor of another programmable data processing device.
These computer program instructions may also be stored in a computer readable memory which may guide the computer or another programmable data processing device to operate in a particular way, and the instructions stored in the computer readable memory produce a manufacture including the instruction apparatus which implements the functions specified in one or more processes of the flow charts and/or one or more blocks of the block diagrams.
These computer program instructions may also be loaded onto the computer or another programmable data processing device, and a series of operation steps are performed on the computer or another programmable device to produce the computer-implemented processing. Thus the instructions executed on the computer or another programmable device provide steps for implementing the functions specified in one or more processes of the flow charts and/or one or more blocks of the block diagrams.
| Number | Date | Country | Kind |
|---|---|---|---|
| 202010820157.4 | Aug 2020 | CN | national |
The present application is a U.S. National Stage of International Application No. PCT/CN2021/100708, filed on Jun. 17, 2021, which claims the priority from Chinese Patent Application No. 202010820157.4, filed with the China National Intellectual Property Administration (CNIPA) on Aug. 14, 2020 and entitled “MBS Data Communication Method, and Network Side Apparatus and Device”, the entire contents of which are hereby incorporated by reference.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/CN2021/100708 | 6/17/2021 | WO |
