WO2022017437A1 - 信息接收方法、发送方法、会话建立方法、装置和设备 - Google Patents

信息接收方法、发送方法、会话建立方法、装置和设备 Download PDF

Info

Publication number
WO2022017437A1
WO2022017437A1 PCT/CN2021/107764 CN2021107764W WO2022017437A1 WO 2022017437 A1 WO2022017437 A1 WO 2022017437A1 CN 2021107764 W CN2021107764 W CN 2021107764W WO 2022017437 A1 WO2022017437 A1 WO 2022017437A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
information
side device
resource information
pdu session
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2021/107764
Other languages
English (en)
French (fr)
Inventor
谢振华
张艳霞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Publication of WO2022017437A1 publication Critical patent/WO2022017437A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/10—Interfaces between hierarchically different network devices between terminal device and access point, i.e. wireless air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method for receiving information, a method for sending information, a method for establishing a session, an apparatus and a device.
  • a terminal can support Protocol Data Unit (Protocol Data Unit, PDU) sessions and multicast service data transmission.
  • PDU Protocol Data Unit
  • the terminal may switch, that is, switch from the source network side device to the target network side device, and the terminal can only switch the PDU session first, and then switch to the shared mode to obtain multicast air interface resources. It can be seen that at present, the efficiency of the terminal acquiring the multicast air interface resource is relatively low.
  • the present application provides an information receiving method, a sending method, a session establishing method, an apparatus and a device, which can solve the problem of low efficiency of a terminal in acquiring multicast air interface resources.
  • an embodiment of the present application provides a method for receiving resource information, which is applied to a terminal, including:
  • Resource information is received, where the resource information is used to indicate multicast air interface resources for the target network side device to transmit multicast service data.
  • an embodiment of the present application provides a method for sending resource information, which is applied to a target network side device, including:
  • an embodiment of the present application provides a session establishment method, which is applied to core network functions, including:
  • a multicast-related protocol data unit PDU session is established, wherein the multicast-related protocol data unit PDU session is associated with upstream channel resource information or specified flow identification information or specified service quality identification on the specified core network.
  • an embodiment of the present application provides an apparatus for receiving resource information, which is applied to a terminal, including:
  • a sending module configured to send a measurement report for handover to the source network side device
  • the first receiving module is configured to receive resource information, where the resource information is used to indicate multicast air interface resources for transmitting multicast service data by the target network side device.
  • an embodiment of the present application provides an apparatus for sending resource information, which is applied to a target network side device, including:
  • the reservation module is used to reserve multicast air interface resources according to the existence of multicast services in the terminal;
  • the first sending module is configured to send resource information to the terminal, where the resource information is used to instruct the target network side device to transmit multicast air interface resources for multicast service data.
  • an embodiment of the present application provides a session establishment apparatus, which is applied to core network functions, including:
  • the establishment module is configured to establish a multicast-related protocol data unit PDU session, wherein the multicast-related protocol data unit PDU session is associated with the specified core network upstream channel resource information or specified flow identification information or specified service quality identification.
  • an embodiment of the present application provides a terminal, including: a memory, a processor, and a program or instruction stored on the memory and executable on the processor, the program or instruction being executed by the processor When executed, the steps in the resource information receiving method provided by the embodiment of the present application are implemented.
  • an embodiment of the present application provides a network-side device, where the network-side device is a target network-side device, characterized in that it includes: a memory, a processor, and a device stored in the memory and available on the processor
  • a program or instruction running on the processor when the program or instruction is executed by the processor, implements the steps in the resource information sending method provided by the embodiment of the present application.
  • an embodiment of the present application provides a core network function, including: a memory, a processor, and a program or instruction stored in the memory and executable on the processor, the program or instruction being executed by the When executed by the processor, the steps in the session establishment method provided by the embodiment of the present application are implemented.
  • an embodiment of the present application provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the method for receiving resource information provided by the embodiment of the present application is implemented Alternatively, when the program or instruction is executed by the processor, the steps in the method for sending resource information provided by the embodiment of the present application are implemented, or when the program or instruction is executed by the processor, the step in the method for sending resource information provided by the embodiment of the present application is implemented. Steps in the session establishment method.
  • an embodiment of the present application provides a program product, the program product is stored in a non-volatile storage medium, and the program product is executed by at least one processor to realize the resource information reception provided by the embodiment of the present application
  • the steps in the method, or the program product is executed by at least one processor to implement the steps in the method for sending resource information provided by the embodiments of the present application
  • the program product is executed by at least one processor to implement the steps provided by the embodiments of the present application. steps in the session establishment method.
  • a measurement report for handover is sent to the source network side device; resource information is received, where the resource information is used to indicate the target network side device to transmit multicast air interface resources for multicast service data.
  • the terminal sends the measurement report to the source network side device, it can obtain the multicast air interface resources for the target network side device to transmit the multicast service data, thereby improving the efficiency of obtaining the multicast air interface resources.
  • FIG. 1 shows a block diagram of a wireless communication system to which an embodiment of the present application can be applied
  • FIG. 2 is a flowchart of a method for receiving resource information provided by an embodiment of the present application
  • FIG. 3 is a flowchart of a method for sending resource information provided by an embodiment of the present application.
  • FIG. 4 is a flowchart of a method for establishing a session provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of sending multicast service data according to an embodiment of the present application.
  • FIG. 6 is a structural diagram of an apparatus for receiving resource information provided by an embodiment of the present application.
  • FIG. 7 is a structural diagram of an apparatus for sending resource information provided by an embodiment of the present application.
  • FIG. 8 is a structural diagram of a session establishment apparatus provided by an embodiment of the present application.
  • FIG. 9 is a structural diagram of a terminal provided by an embodiment of the present application.
  • FIG. 10 is a structural diagram of a network side device provided by an embodiment of the present application.
  • FIG. 11 is a structural diagram of a core network function provided by an embodiment of the present application.
  • first, second and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and "first”, “second” distinguishes Usually it is a class, and the number of objects is not limited.
  • the first object may be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the associated objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies.
  • NR New Radio
  • NR terminology is used in most of the following description, although these techniques are also applicable to applications other than NR system applications, such as 6th generation ( 6th Generation, 6G) communication system.
  • FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied.
  • the wireless communication system includes a terminal 11 , a source network side device 12 , a target network side device 13 and a core network function 14 .
  • the terminal 11 may also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital computer Assistant (Personal Digital Assistant, PDA), PDA, Netbook, Ultra-mobile Personal Computer (UMPC), Mobile Internet Device (Mobile Internet Device, MID) or Vehicle-mounted Equipment (VUE), Pedestrian Terminal (PUE) , Terminal-side equipment such as a reduced capability terminal (RedCap UE), where the RedCap UE may include: wearable devices, industrial sensors, video surveillance equipment, etc., and the wearable devices include: bracelets, headphones, glasses, etc.
  • the source network side device 12 and the target network side device 13 may be a base station or a core network, where the base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station , radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, WLAN Access Ingress point, WiFi node, Transmitting Receiving Point (TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary, it should be noted that in In the embodiments of the present application, only the base station in the NR system is used as an example, but the specific type of the base station is not limited.
  • the core network function 14 may include at least one of the following: a mobility management entity (Mobility Management Entity, MME), an access mobility management function (Access Management Function, AMF), a session management function (Session Management Function, SMF), a user plane function ( User Plane Function, UPF), multicast session management function (multimedia broadcast Session Management Function, MB-SMF), multicast user plane function (multimedia broadcast User Plane Function, MB-UPF).
  • MME mobility management entity
  • AMF Access Management Function
  • SMF Session Management Function
  • UPF User Plane Function
  • UPF User Plane Function
  • multicast session management function multimedia broadcast Session Management Function
  • MB-UPF multicast user plane function
  • control signaling obtaining method e.g., sending method, apparatus, terminal, and network side device provided by the embodiments of the present application through specific embodiments and application scenarios with reference to the accompanying drawings.
  • FIG. 2 is a flowchart of a method for receiving resource information provided by an embodiment of the present application. The method is applied to a terminal, as shown in FIG. 2, and includes the following steps:
  • Step 201 Send a measurement report for handover to the source network side device.
  • the above measurement report may be a measurement report used for the terminal multi-source network side device to switch to the target network side device. And the above-mentioned target network side device may be selected by the source network side device.
  • the terminal sends a measurement report to the source network side device.
  • the source network side device After the source network side device receives the measurement report, it can select the target network side device and send a handover request message (such as a Handover Request message) to the target network side device.
  • a handover request message such as a Handover Request message
  • the above-mentioned handover request message may also carry PDU session related information, such as at least one of PDU Session ID (PDU Session ID), Flow Identifier (QFI), Quality of Service (QoS) related information, PDU session core network uplink channel information, etc. one.
  • PDU Session ID PDU Session ID
  • QFI Flow Identifier
  • QoS Quality of Service
  • Step 202 Receive resource information, where the resource information is used to indicate a multicast air interface resource for the target network side device to transmit multicast service data.
  • Step 202 may be to receive resource information sent by the target network side device through the source network side device, or through the core network function and the source network side device.
  • the above resource information may be sent through a handover command, which of course is not limited in this embodiment of the present application, for example, it may also be sent through a resetting message.
  • the multicast air interface resources used by the target network side device to transmit the multicast service data can be quickly obtained through the above steps, thereby improving the efficiency of obtaining the multicast air interface resources.
  • the switching efficiency of the multicast service can be improved.
  • the method further includes:
  • the idle state indication enter the idle state or stop sending the handover confirmation message to the target network side device.
  • the acquisition of the idle state indication may be obtained based on the above resource information, for example: the above resource information explicitly or implicitly indicates the above idle state indication.
  • the above idle state indication may be used to instruct the terminal to enter the idle state, so that after the terminal obtains the indication, it may enter the idle state or stop sending a handover confirmation message to the target network side device, so as to realize the reception of multicast service data in the idle state, Or in the case that the handover is not completed, the multicast service data is received.
  • the terminal may enter the connected state, or may send a handover confirmation message to the target network side device.
  • the obtaining the idle state indication includes at least one of the following:
  • the resource information does not include PDU session information.
  • the redirection message may be sent by the source network side device, and the redirection message may carry the resource information.
  • the above-mentioned target multicast service transmission mode information may be included in the above-mentioned resource information, and the above-mentioned target multicast service transmission mode information may be a point-to-multipoint transmission mode. Of course, this is not limited, for example: it may be predefined in the protocol. information on the transmission mode of multicast services.
  • the terminal when at least one of receiving the redirection message, receiving the target multicast service transmission mode information, and the resource information not including the PDU session information is satisfied, it may be determined that the terminal is instructed to enter the spatial state.
  • the above-mentioned idle state indication has two indication states, one of which indicates entering the idle state, and the other indicating not entering the idle state. For example, if the above resource information includes PDU session information, it indicates not to enter the idle state, or if the above resource information does not include information on the transmission mode of the target multicast service, it indicates not to enter the idle state, and so on.
  • the method further includes:
  • the multicast service data sent by the target network side device is received at the multicast air interface resource.
  • the terminal can receive multicast service data sent by the target network side device in the idle state.
  • the target network side device can send multicast service data to the terminal through a multicast shared channel or a dedicated channel.
  • this is not limited.
  • it can also receive the data sent by the target network side device in the idle state by other methods defined by the protocol. Multicast service data.
  • the switching efficiency can be improved, because there is no need to perform PDU session switching, and the power consumption of the terminal can also be saved.
  • a measurement report for handover is sent to the source network side device; resource information is received, where the resource information is used to indicate the target network side device to transmit multicast air interface resources for multicast service data.
  • the terminal sends the measurement report to the source network side device, it can obtain the multicast air interface resources for the target network side device to transmit the multicast service data, thereby improving the efficiency of obtaining the multicast air interface resources.
  • FIG. 3 is a flowchart of a method for sending resource information provided by an embodiment of the present application. The method is applied to a target network side device. As shown in FIG. 3, the method includes the following steps:
  • Step 301 Reserving multicast air interface resources according to the existence of multicast services in the terminal.
  • the above-mentioned reservation of the multicast air interface resource according to the situation that the terminal has the multicast service may be, when it is determined that the terminal has the multicast service, the multicast air interface resource is reserved.
  • Step 302 Send resource information to the terminal, where the resource information is used to instruct the target network side device to transmit multicast air interface resources for multicast service data.
  • the above steps can improve the efficiency of the terminal acquiring the multicast air interface resources.
  • the above-mentioned reservation of multicast air interface resources according to the existence of multicast services in the terminal includes:
  • Multicast air interface resources are reserved according to the PDU session information sent by the source network side device, and the PDU session information is used to indicate that the terminal has a multicast service.
  • the foregoing PDU session information may be used to indicate that the terminal has a multicast service, and the PDU session information may be used implicitly or explicitly to indicate that the terminal has a multicast service.
  • the multicast air interface resources are reserved, including:
  • Multicast air interface resources are reserved according to the specified core network uplink channel resource information or specified flow identification information or specified quality of service identifier (QoS Identifier, QI) included in the PDU session information.
  • QoS Identifier, QI quality of service identifier
  • the designated core network uplink channel resource information or designated flow identifier information or designated service quality identifier included in the above-mentioned PDU session information can determine that the terminal has a multicast service, and then reserve multicast air interface resources.
  • the above-mentioned designated QoS identifier can be the designated 5G QoS Identifier (5G QoS Identifier, 5QI) defined in the designated 5G system.
  • 5G QoS Identifier 5QI
  • 6G 6G
  • QoS identifier can be the designated service defined in the designated 6G system. Quality logo.
  • the core network function uses the specified core network uplink channel resource information, such as the core network uplink channel, during the process of establishing a multicast-related PDU session.
  • the resource information (CN UL Tunnel Info) is all 0s or all 1s, or uses the specified QoS flow identifier or the indicated QI to represent the multicast service.
  • the above-mentioned designated core network uplink channel resource information or designated flow identification information or designated service quality identification may be a protocol agreement, or pre-configured, etc., which is not limited, and the above designated core network uplink channel resource information or designated flow identification information Alternatively, the specified QoS identifier can also be understood as the specific core network uplink channel resource information or the specific flow identifier information or the specific QoS identifier.
  • the multicast air interface resources are reserved according to the PDU session information sent by the source network side device, there is no need to add other messages to reserve the multicast air interface resources, so as to save resource overhead.
  • the above method also includes:
  • An idle state indication is provided to the terminal.
  • the providing an idle state indication to the terminal includes at least one of the following:
  • the resource information does not include at least one item of PDU session information.
  • the method further includes:
  • the reserving multicast air interface resources includes:
  • Multicast air interface resources are reserved according to the pre-configured information.
  • the above-mentioned multi-play service information may be sent by the core network function, of course, this is not limited, for example: it may also be sent by the source network side device.
  • the above-mentioned multicast service information may include at least one item of a multicast service identifier, multicast service QoS information, and the like.
  • the foregoing reserving multicast air interface resources according to the multicast service information may be reserving multicast air interface resources matching the multicast service.
  • the above-mentioned reservation of multicast air interface resources according to the pre-configured information may be to reserve air interface multicast resources by using a pre-configured scheme based on the judgment that the terminal has a multicast service in the case that the multicast service information is not obtained.
  • the air interface resource information is reserved using the point-to-point transmission method by using pre-configured QoS information.
  • matching multicast air interface resources can be reserved for the terminal through the above two manners.
  • the method before reserving multicast air interface resources according to the multicast service information, the method further includes:
  • the multicast service information sent by the core network function is received, wherein the multicast service information is related to the PDU session information.
  • the above-mentioned PDU session information may include multicast related PDU session related information, wherein the multicast related PDU session may be a PDU session for receiving multicast service data.
  • the above-mentioned PDU session information may include at least one item of PDU session identifier, flow identifier, QoS-related information, and uplink channel information on the core network of the PDU session of the multicast service-related PDU session.
  • the core network function After the core network function receives the above-mentioned PDU session information, it can determine and send the above-mentioned multicast service information.
  • the above steps can improve the efficiency of the terminal in acquiring the multicast air interface resources, and can also improve the switching efficiency of the multicast service.
  • FIG. 4 is a flowchart of a session establishment method provided by an embodiment of the present application. The method is applied to a core network function, as shown in FIG. 4, and includes the following steps:
  • Step 401 establish a multicast-related PDU session, wherein the multicast-related protocol data unit PDU session is associated with the specified core network uplink channel resource information or specified flow identification information or specified service quality identification.
  • the above-mentioned multicast-related PDU session may be a PDU session that can be used to transmit multicast service data.
  • the multicast-related PDU session is used for the source network side device to send a multicast service to the terminal, and after the multicast PDU session is established, the method further includes:
  • a PDU session for transmitting a multicast service can be established, thereby improving the sending effect of the multicast service.
  • the method provided by the embodiment of the present application is described by taking the core network function as the source network side device to send the multicast service data using the multicast-related PDU session, the network side device being the gNB, and the core network function being the MB-SMF or MB-UPF. , as shown in Figure 5, including the following steps:
  • Step 1 Use the uplink channel resource information or QFI of the specific designated core network to indicate that there is a multicast service.
  • the core network function uses the specified core network uplink channel resource information in the process of establishing a multicast-related PDU session.
  • CN UL Tunnel Info is all 0 or all 1.
  • QFI QoS flow identifier
  • QoS information ie, quality of service identifier
  • Step 2 The UE sends a measurement report to the source base station (source gNB).
  • Step 3 The Source gNB decides to perform the handover operation, selects the target base station (target gNB), and sends a handover request message to the target base station.
  • a Handover Request message can carry PDU session-related information, such as PDU Session ID (PDU Session ID), Flow Identification (QFI), QoS-related information, and uplink channel information on the core network of the PDU session.
  • PDU Session ID PDU Session ID
  • QFI Flow Identification
  • QoS-related information QoS-related information
  • uplink channel information on the core network of the PDU session.
  • Step 4 The target gNB determines the multicast service of the terminal based on the received uplink channel resource information of the designated core network or the designated QoS flow identification information, and can obtain the relevant information of the PDU session related to the multicast service.
  • Step 5 The target gNB can send a session update request to the core network function (for example, sent to SMF through AMF), and the request can carry PDU session related information, for example: including multicast service related PDU session related information.
  • the core network function for example, sent to SMF through AMF
  • PDU session related information for example: including multicast service related PDU session related information.
  • Step 6 The core network function (such as SMF) obtains multicast service information based on the PDU session information, such as multicast service identifier, multicast service QoS information, etc., and sends the multicast service information to the target gNB (such as sent through AMF).
  • the core network function such as SMF
  • the target gNB such as sent through AMF.
  • Step 7 In the case of performing steps 5 to 6, the target gNB reserves the air interface multicast resources based on the multicast service information. In the case of not performing steps 5 to 6, the target gNB uses the pre-configured scheme to pre-configure based on the judgment of the multicast service. Reserving air interface multicast resources, for example, using pre-configured QoS information to reserve air interface resource information using point-to-point transmission.
  • Step 8 The target gNB sends the multicast air interface resource information to the terminal through the Source gNB (or through the core network function and the source base station).
  • the multicast air interface resource information may include an indication indicating whether the UE can enter an idle state. For example, a redirect message is sent to the terminal instead of a handover command to indicate that it can enter the idle state, or no multicast service related PDU session related information is sent to the UE, or a specified multicast data transmission mode is included, wherein the specified multicast data
  • the transmission mode may be a point-to-multipoint transmission mode, or the transmission mode may be indicated by the multicast air interface resource information of the point-to-multipoint transmission mode.
  • Step 9 The UE accesses the target gNB according to the received air interface resource information, and sends a handover confirmation message, such as a Handover Confirm (handover confirmation) message, to the target gNB, or the UE may enter the idle state based on the idle state indication without performing this step .
  • a handover confirmation message such as a Handover Confirm (handover confirmation) message
  • Step 10 It can be executed after step 7.
  • the target gNB sends a session update message to the core network function (for example, sent to SMF through AMF).
  • the message can carry the base station that established the multicast shared channel.
  • the side downlink receives resource information, and does not send multicast service-related PDU session-related information. If steps 5 to 6 are not performed, the message carries PDU session-related information, including multicast service-related PDU session-related information.
  • Step 11 The core network function can interact with the target gNB to establish a multicast shared channel in the case of receiving the relevant information about the PDU session related to the multicast service, that is, send the relevant information of the multicast service to the target gNB, and the relevant information of the multicast service can be Including multicast service information, such as service identifiers of multicast services and QoS flow identifiers. Further, the target gNB can update the multicast air interface resource information based on the multicast service related information, and notify the UE of the updated multicast air interface resource information, and the target gNB can also send the multicast shared channel base station side downlink to the core network function. Receive resource information.
  • multicast service information such as service identifiers of multicast services and QoS flow identifiers.
  • FIG. 6 is a structural diagram of an apparatus for receiving resource information provided by an embodiment of the present application.
  • the apparatus is applied to a terminal.
  • the apparatus for receiving resource information 600 includes:
  • a sending module 601, configured to send a measurement report for handover to a source network side device
  • the first receiving module 602 is configured to receive resource information, where the resource information is used to indicate multicast air interface resources for transmitting multicast service data by the target network side device.
  • the device further includes:
  • An execution module configured to enter an idle state or stop sending a handover confirmation message to the target network side device according to the idle state indication.
  • the obtaining the idle state indication includes at least one of the following:
  • the resource information does not include PDU session information.
  • the device further includes:
  • the second receiving module is configured to receive the multicast service data sent by the target network side device at the multicast air interface resource.
  • the resource information receiving apparatus can implement each process in the method embodiment of FIG. 2 , which is not repeated here to avoid repetition, and can improve the efficiency of obtaining multicast air interface resources.
  • the resource information receiving apparatus in this embodiment of the present application may be an apparatus, or may be a component, an integrated circuit, or a chip in a terminal.
  • FIG. 7 is a structural diagram of an apparatus for sending resource information provided by an embodiment of the present application.
  • the apparatus is applied to a target network side device.
  • the apparatus for sending resource information 700 includes:
  • Reservation module 701 configured to reserve multicast air interface resources according to the existence of multicast services in the terminal
  • the first sending module 702 is configured to send resource information to the terminal, where the resource information is used to instruct the target network side device to transmit multicast air interface resources for multicast service data.
  • the first sending module 702 is configured to reserve multicast air interface resources according to PDU session information sent by the source network side device, where the PDU session information is used to indicate that the terminal has a multicast service.
  • the first sending module 702 is configured to reserve multicast air interface resources according to the specified core network uplink channel resource information or specified flow identification information or specified quality of service identification included in the PDU session information.
  • the device further includes:
  • a module is provided for providing an idle state indication to the terminal.
  • the providing an idle state indication to the terminal includes at least one of the following:
  • the resource information does not include at least one item of PDU session information.
  • the device further includes:
  • the second sending module is configured to send multicast service data to the terminal according to the multicast air interface resource.
  • the reserved multicast air interface resources include:
  • Multicast air interface resources are reserved according to the pre-configured information.
  • the device further includes:
  • the third sending module is used to send the PDU session information to the core network function
  • a receiving module configured to receive the multicast service information sent by the core network function, wherein the multicast service information is related to the PDU session information.
  • the resource information sending apparatus provided in the embodiment of the present invention can implement each process in the method embodiment of FIG. 3 , which is not repeated here to avoid repetition, and can improve the efficiency of the terminal acquiring multicast air interface resources.
  • the apparatus for sending resource information in this embodiment of the present application may be an apparatus, or may be a component, an integrated circuit, or a chip in a target network-side device.
  • FIG. 8 is a structural diagram of a session establishment apparatus provided by an embodiment of the present application.
  • the apparatus is applied to a core network function, as shown in FIG. 8, including:
  • the establishment module 801 is configured to establish a multicast-related protocol data unit PDU session, wherein the multicast-related protocol data unit PDU session is associated with the specified core network upstream channel resource information or specified flow identification information or specified service quality identification.
  • the device further includes:
  • a receiving module configured to receive the PDU session information sent by the target network side device
  • a sending module configured to send multicast service information to the target network side device, wherein the multicast service information is related to the PDU session information.
  • the session establishment apparatus provided in the embodiment of the present invention can implement each process in the method embodiment of FIG. 4 , which is not repeated here to avoid repetition, and can improve the sending effect of the multicast service.
  • the session establishment apparatus in this embodiment of the present application may be an apparatus, and may also be a component, an integrated circuit, or a chip in a core network function.
  • FIG. 9 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
  • the terminal 900 includes but is not limited to: a radio frequency unit 901, a network module 902, an audio output unit 903, an input unit 904, a sensor 905, a display unit 906, a user input unit 907, an interface unit 908, a memory 909, and a processor 910 and other components .
  • the terminal 900 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 910 through a power management system, so as to manage charging, discharging, and power consumption through the power management system management and other functions.
  • a power source such as a battery
  • the structure of the electronic device shown in FIG. 9 does not constitute a limitation to the electronic device.
  • the electronic device may include more or less components than the one shown, or combine some components, or arrange different components, which will not be repeated here. .
  • the radio frequency unit 901 is configured to: send a measurement report for handover to the source network side device; and receive resource information, where the resource information is used to indicate multicast air interface resources for the target network side device to transmit multicast service data.
  • the radio frequency unit 901 or the processor 910 is used to:
  • the idle state indication enter the idle state or stop sending the handover confirmation message to the target network side device.
  • the obtaining the idle state indication includes at least one of the following:
  • the resource information does not include PDU session information.
  • the radio frequency unit 901 is further configured to:
  • the multicast service data sent by the target network side device is received at the multicast air interface resource.
  • This embodiment can improve the efficiency of acquiring multicast air interface resources.
  • an embodiment of the present invention further provides a terminal, including a processor 910, a memory 909, a program or instruction stored in the memory 909 and executable on the processor 910, the program or instruction being executed by the processor 910 During execution, each process of the foregoing resource information receiving method embodiment is implemented, and the same technical effect can be achieved. In order to avoid repetition, details are not described here.
  • FIG. 10 is a structural diagram of a network-side device provided by an embodiment of the present invention.
  • the network-side device is a target network-side device.
  • the network-side device 1000 includes: a processor 1001, a transceiver computer 1002, memory 1003 and bus interface, wherein:
  • Transceiver 1002 for:
  • the reservation of multicast air interface resources according to the existence of multicast services in the terminal includes:
  • Multicast air interface resources are reserved according to the PDU session information sent by the source network side device, and the PDU session information is used to indicate that the terminal has a multicast service.
  • reserving multicast air interface resources according to the PDU session information sent by the source network side device includes:
  • Multicast air interface resources are reserved according to the designated core network uplink channel resource information or designated flow identification information or designated service quality identification included in the PDU session information.
  • transceiver 1002 is also used to:
  • An idle state indication is provided to the terminal.
  • the transceiver 1002 providing the idle state indication to the terminal includes at least one of the following:
  • the resource information does not include at least one item of PDU session information.
  • the transceiver 1002 is further configured to:
  • the reserved multicast air interface resources include:
  • Multicast air interface resources are reserved according to the pre-configured information.
  • the transceiver 1002 is further used to:
  • the multicast service information sent by the core network function is received, wherein the multicast service information is related to the PDU session information.
  • This embodiment can improve the efficiency of the terminal acquiring multicast air interface resources.
  • the transceiver 1002 is used to receive and transmit data under the control of the processor 1001, and the transceiver 1002 includes at least two antenna ports.
  • the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1001 and various circuits of memory represented by memory 1003 linked together.
  • the bus architecture may also link together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be described further herein.
  • the bus interface provides the interface.
  • Transceiver 1002 may be a number of elements, including a transmitter and a receiver, that provide a means for communicating with various other devices over a transmission medium.
  • the bus interface may also be an interface capable of externally connecting a required device, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 1001 is responsible for managing the bus architecture and general processing, and the memory 1003 may store data used by the processor 1001 in performing operations.
  • an embodiment of the present invention further provides a network-side device, including a processor 1001, a memory 1003, a program or an instruction stored in the memory 1003 and executable on the processor 1001, the program or instruction being executed by the processor
  • a network-side device including a processor 1001, a memory 1003, a program or an instruction stored in the memory 1003 and executable on the processor 1001, the program or instruction being executed by the processor
  • FIG. 11 is a structural diagram of a core network function provided by an embodiment of the present invention.
  • the network side device 1100 includes: a processor 1101, a transceiver 1102, a memory 1103, and a bus interface, wherein :
  • the transceiver 1102 is configured to: establish a multicast-related protocol data unit PDU session, wherein the multicast-related protocol data unit PDU session is associated with designated core network upstream channel resource information or designated flow identification information or designated service quality identification.
  • the multicast-related PDU session is used for the source network side device to send the multicast service to the terminal.
  • the transceiver 1102 is further used for:
  • the sending effect of the multicast service can be improved.
  • the transceiver 1102 is used for receiving and transmitting data under the control of the processor 1101, and the transceiver 1102 includes at least two antenna ports.
  • the bus architecture may include any number of interconnected buses and bridges, in particular one or more processors represented by processor 1101 and various circuits of memory represented by memory 1103 linked together.
  • the bus architecture may also link together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be described further herein.
  • the bus interface provides the interface.
  • Transceiver 1102 may be a number of elements, including a transmitter and a receiver, that provide a means for communicating with various other devices over a transmission medium.
  • the bus interface may also be an interface capable of externally connecting a required device, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 1101 is responsible for managing the bus architecture and general processing, and the memory 1103 may store data used by the processor 1101 in performing operations.
  • an embodiment of the present invention further provides a core network function, including a processor 1101, a memory 1103, a program or instruction stored in the memory 1103 and run on the processor 1101, the program or instruction being executed by the processor
  • a core network function including a processor 1101, a memory 1103, a program or instruction stored in the memory 1103 and run on the processor 1101, the program or instruction being executed by the processor
  • Embodiments of the present application further provide a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps in the method for receiving resource information provided by the embodiment of the present application are implemented. , or, when the program or instruction is executed by the processor, the steps in the resource information sending method provided by the embodiment of the present application are implemented, or, when the program or the instruction is executed by the processor, the method for establishing a session provided by the embodiment of the present application is implemented steps in .
  • the embodiments of the present application further provide a program product, the program product is stored in a non-volatile storage medium, and the program product is executed by at least one processor to implement the method in the resource information receiving method provided by the embodiments of the present application. or, the program product is executed by at least one processor to implement the steps in the method for sending resource information provided by the embodiment of the present application, and the program product is executed by at least one processor to implement the session establishment provided by the embodiment of the present application. steps in the square.
  • the processor is the processor in the terminal or the network device described in the foregoing embodiment.
  • the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
  • An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used for running a program or an instruction to implement the above method for receiving resource information and resources.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip, or the like.
  • modules, units, sub-modules, sub-units, etc. can be implemented in one or more Application Specific Integrated Circuits (ASIC), Digital Signal Processing (DSP), digital signal processing equipment ( DSP Device, DSPD), Programmable Logic Device (Programmable Logic Device, PLD), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), general-purpose processor, controller, microcontroller, microprocessor, for in other electronic units or combinations thereof that perform the functions described herein.
  • ASIC Application Specific Integrated Circuits
  • DSP Digital Signal Processing
  • DSP Device digital signal processing equipment
  • PLD Programmable Logic Device
  • Field-Programmable Gate Array Field-Programmable Gate Array
  • FPGA Field-Programmable Gate Array
  • the method of the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is better implementation.
  • the technical solution of the present application can be embodied in the form of a software product in essence or in a part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, CD-ROM), including several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of this application.
  • a storage medium such as ROM/RAM, magnetic disk, CD-ROM

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种信息接收方法、发送方法、会话建立方法、装置和设备，包括：向源网络侧设备发送用于切换的测量报告；接收资源信息，所述资源信息用于指示目标网络侧设备传输多播业务数据的多播空口资源。

Description

信息接收方法、发送方法、会话建立方法、装置和设备
相关申请的交叉引用
本申请主张在2020年7月23日在中国提交的中国专利申请号No.202010718757.X的优先权，其全部内容通过引用包含于此。
技术领域
本申请涉及通信技术领域，尤其涉及一种信息接收方法、发送方法、会话建立方法、装置和设备。
背景技术
在一些通信系统(例如：5G系统)中，终端可以支持协议数据单元(Protocol Data Unit，PDU)会话和多播业务数据传输。然而，在实际应用中终端可能会发生切换，即从源网络侧设备切换至目标网络侧设备，且终端只能先切换PDU会话之后，再转换为共享模式，以获取到多播空口资源。可见，目前终端获取多播空口资源的效率比较低。
发明内容
本申请提供一种信息接收方法、发送方法、会话建立方法、装置和设备，能够解决终端获取多播空口资源的效率比较低的问题。
第一方面，本申请实施例提供一种资源信息接收方法，应用于终端，包括：
向源网络侧设备发送用于切换的测量报告；
接收资源信息，所述资源信息用于指示目标网络侧设备传输多播业务数据的多播空口资源。
第二方面，本申请实施例提供一种资源信息发送方法，应用于目标网络侧设备，包括：
依据终端存在多播业务的情况，预留多播空口资源；
向所述终端发送资源信息，所述资源信息用于指示所述目标网络侧设备 传输多播业务数据的多播空口资源。
第三方面，本申请实施例提供一种会话建立方法，应用于核心网功能，包括：
建立多播相关协议数据单元PDU会话，其中，所述多播相关协议数据单元PDU会话关联指定核心网上行通道资源信息或者指定流标识信息或者指定服务质量标识。
第四方面，本申请实施例提供一种资源信息接收装置，应用于终端，包括：
发送模块，用于向源网络侧设备发送用于切换的测量报告；
第一接收模块，用于接收资源信息，所述资源信息用于指示目标网络侧设备传输多播业务数据的多播空口资源。
第五方面，本申请实施例提供一种资源信息发送装置，应用于目标网络侧设备，包括：
预留模块，用于依据终端存在多播业务的情况，预留多播空口资源；
第一发送模块，用于向所述终端发送资源信息，所述资源信息用于指示所述目标网络侧设备传输多播业务数据的多播空口资源。
第六方面，本申请实施例提供一种会话建立装置，应用于核心网功能，包括：
建立模块，用于建立多播相关协议数据单元PDU会话，其中，所述多播相关协议数据单元PDU会话关联指定核心网上行通道资源信息或者指定流标识信息或者指定服务质量标识。
第七方面，本申请实施例提供一种终端，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的程序或者指令，所述程序或者指令被所述处理器执行时实现本申请实施例提供的资源信息接收方法中的步骤。
第八方面，本申请实施例提供一种网络侧设备，所述网络侧设备为目标网络侧设备，其特征在于，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的程序或者指令，所述程序或者指令被所述处理器执行时实现本申请实施例提供的资源信息发送方法中的步骤。
第九方面，本申请实施例提供一种核心网功能，包括：存储器、处理器及 存储在所述存储器上并可在所述处理器上运行的程序或者指令，所述程序或者指令被所述处理器执行时实现本申请实施例提供的会话建立方法中的步骤。
第十方面，本申请实施例提供一种可读存储介质，所述可读存储介质上存储有程序或指令，所述程序或指令被处理器执行时实现本申请实施例提供的资源信息接收方法中的步骤，或者，所述程序或指令被处理器执行时实现本申请实施例提供的资源信息发送方法中的步骤，或者，所述程序或指令被处理器执行时实现本申请实施例提供的会话建立方法中的步骤。
第十方面，本申请实施例提供一种程序产品，所述程序产品被存储在非易失的存储介质中，所述程序产品被至少一个处理器执行以实现本申请实施例提供的资源信息接收方法中的步骤，或者，所述程序产品被至少一个处理器执行以实现本申请实施例提供的资源信息发送方法中的步骤，所述程序产品被至少一个处理器执行以实现本申请实施例提供的会话建立方法中的步骤。
本申请实施例中，向源网络侧设备发送用于切换的测量报告；接收资源信息，所述资源信息用于指示目标网络侧设备传输多播业务数据的多播空口资源。这样终端向源网络侧设备发送完测量报告后，即可获取到目标网络侧设备传输多播业务数据的多播空口资源，从而提高获取多播空口资源的效率。
附图说明
图1示出本申请实施例可应用的一种无线通信系统的框图；
图2是本申请实施例提供的一种资源信息接收方法的流程图；
图3是本申请实施例提供的一种资源信息发送方法的流程图；
图4是本申请实施例提供的一种会话建立方法的流程图；
图5是本申请实施例提供的一种多播业务数据发送的示意图；
图6是本申请实施例提供的一种资源信息接收装置的结构图；
图7是本申请实施例提供的一种资源信息发送装置的结构图；
图8是本申请实施例提供的一种会话建立装置的结构图；
图9是本申请实施例提供的一种终端的结构图；
图10是本申请实施例提供的一种网络侧设备的结构图；
图11是本申请实施例提供的一种核心网功能的结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(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)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。然而，以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，尽管这些技术也可应用于NR系统应用以外的应用，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11、源网络侧设备12、目标网络侧设备13和核心网功能14。其中，终端11也可以称作终端设备或者用户终端(User Equipment，UE)，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop  Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)或车载设备(VUE)、行人终端(PUE)、能力下降终端(RedCap UE)等终端侧设备，其中，RedCap UE可以包括：穿戴设备、工业传感器、视频监控设备等，穿戴设备包括：手环、耳机、眼镜等。需要说明的是，在本申请实施例并不限定终端11的具体类型。
源网络侧设备12和目标网络侧设备13可以是基站或核心网，其中，基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例，但是并不限定基站的具体类型。
核心网功能14可以包括至少以下之一：移动管理实体(Mobility Management Entity，MME)、接入移动管理功能(Access Management Function，AMF)、会话管理功能(Session Management Function，SMF)、用户平面功能(User Plane Function，UPF)、多播会话管理功能(multimedia broadcast Session Management Function，MB-SMF)、多播用户平面功能(multimedia broadcast User Plane Function，MB-UPF)。
下面结合附图，通过具体的实施例及其应用场景对本申请实施例提供控制信令获取方法、发送方法、装置、终端和网络侧设备进行详细地说明。
请参见图2，图2是本申请实施例提供的一种资源信息接收方法的流程图，该方法应用于终端，如图2所示，包括以下步骤：
步骤201、向源网络侧设备发送用于切换的测量报告。
上述测量报告可以是用于终端多源网络侧设备切换至目标网络侧设备的测量报告。且上述目标网络侧设备可以是源网络侧设备选择的。
例如：终端向源网络侧设备发送测量报告，源网络侧设备接收到该测量 报告后，可以择目标网络侧设备，并向目标网络侧设备发送切换请求消息(比如Handover Request消息)。
进一步的，上述切换请求消息还可以携带PDU会话相关信息，比如PDU会话标识(PDU Session ID)、流标识(QFI)、服务质量(QoS)相关信息、PDU会话核心网上行通道信息等中的至少一项。
步骤202、接收资源信息，所述资源信息用于指示目标网络侧设备传输多播业务数据的多播空口资源。
步骤202可以是接收目标网络侧设备通过源网络侧设备，或者通过核心网功能和源网络侧设备发送的资源信息。
进一步的，上述资源信息可以是通过切换命令发送的，当然，对此本申请实施例不作限定，例如：还可以是通过重定消息发送的。
本申请实施例中，通过上述步骤可以实现在发送测量报告后，可以快速获取到目标网络侧设备传输多播业务数据的多播空口资源，从而提高多播空口资源获取的效率，进一步的，还可以提高多播业务的切换效率。
作为一种可选的实施方式，所述向源网络侧设备发送用于切换的测量报告之后，所述方法还包括：
获取空闲态指示；
依据所述空闲态指示，进入空闲态或停止向所述目标网络侧设备发送切换确认消息。
其中，获取空闲态指示可以是基于上述资源信息获取的，例如：上述资源信息显式或者隐式指示上述空闲态指示。
上述空闲态指示可以用于指示终端进入空闲态，从而终端获取该指示后，可以进入空闲态或停止向所述目标网络侧设备发送切换确认消息，以实现在空闲态下接收多播业务数据，或者在切换未完成的情况下，接收多播业务数据。
另外，如果指示终端不进入空闲态，则终端可以进入连接态，或者可以向所述目标网络侧设备发送切换确认消息。
可选的，所述获取空闲态指示包括如下至少一项：
接收重定向消息；
接收目标多播业务传输方式信息；
所述资源信息不包括PDU会话信息。
其中，上述重定向消息可以是源网络侧设备发送，该重定向消息可以携带上述资源信息。上述目标多播业务传输方式信息可以是上述资源信息中包含的，且上述目标多播业务传输方式信息可以是点到多点传输方式，当然，对此不作限定，例如：可以是协议中预定义的多播业务传输方式信息。
进一步，在接收重定向消息、接收目标多播业务传输方式信息和所述资源信息不包括PDU会话信息中至少一项满足时，可以确定指示终端进入空间态。
需要说明的是，在一些实施方式上述空闲态指示具备两种指示状态，一种指示进入空闲态，另一个指示不进入空闲态。例如：上述资源信息包括PDU会话信息，则指示不进入空闲态，或者上述资源信息不包括目标多播业务传输方式信息，则指示不进入空闲态等。
可选的，所述终端进入空闲态之后，所述方法还包括：
在所述多播空口资源接收所述目标网络侧设备发送的多播业务数据。
该实施方式中，可以实现终端在空闲态可以接收目标网络侧设备发送的多播业务数据。例如：目标网络侧设备可以通过多播共享通道或者专用通道向终端发送多播业务数据，当然，对此不作限定，例如：还可以通过协议定义的其他方式在空闲态接收目标网络侧设备发送的多播业务数据。
该实施方式中，由于在空闲态接收目标网络侧设备发送的多播业务数据，从而可以提高切换效率，因为不需要执行PDU会话切换，且还可以节约终端的功耗。
本申请实施例中，向源网络侧设备发送用于切换的测量报告；接收资源信息，所述资源信息用于指示目标网络侧设备传输多播业务数据的多播空口资源。这样终端向源网络侧设备发送完测量报告后，即可获取到目标网络侧设备传输多播业务数据的多播空口资源，从而提高获取多播空口资源的效率。
请参见图3，图3是本申请实施例提供的一种资源信息发送方法的流程图，该方法应用于目标网络侧设备，如图3所示，包括以下步骤：
步骤301、依据终端存在多播业务的情况，预留多播空口资源。
上述依据终端存在多播业务的情况，预留多播空口资源可以是，在确定终端存在多播业务时，预留多播空口资源。
步骤302、向所述终端发送资源信息，所述资源信息用于指示所述目标网络侧设备传输多播业务数据的多播空口资源。
其中，上述资源信息可以参见图2所示的实施例的相应说明，此处不作赘述。
本实施例中，通过上述步骤可以提高终端获取多播空口资源的效率。
作为一种可选的实施方式，上述依据终端存在多播业务的情况，预留多播空口资源，包括：
依据源网络侧设备发送的PDU会话信息，预留多播空口资源，所述PDU会话信息用于表示所述终端存在多播业务。
上述PDU会话信息用于表示所述终端存在多播业务可以是，该PDU会话信息隐式或者显式用于表示所述终端存在多播业务。
例如：上述依据源网络侧设备发送的PDU会话信息，预留多播空口资源，包括：
依据所述PDU会话信息中包括的指定核心网上行通道资源信息或指定流标识信息或者指定服务质量标识(QoS Identifier，QI)，预留多播空口资源。
其中，在上述PDU会话信息中包括的指定核心网上行通道资源信息或指定流标识信息或者指定服务质量标识可以确定上述终端存在多播业务，进而预留多播空口资源。
上述指定服务质量标识可以是指定5G系统中定义的指定5G服务质量标识(5G QoS Identifier，5QI)，当然，也可以应用于6G，则上述指定服务质量标识可以是指定6G系统中定义的指定服务质量标识。
该实施方式中，由于多播业务只有下行数据没有上行数据，从而核心网功能(比如SMF或UPF)在建立多播相关PDU会话过程中，使用指定核心网上行通道资源信息，比如核心网上行通道资源信息(CN UL Tunnel Info)为全0或全1，或使用指定QoS流标识或者指示QI来表示多播业务。
其中，上述指定核心网上行通道资源信息或指定流标识信息或者指定服务质量标识可以是协议约定，或者预先配置的等，对此不作限定，且上述指 定核心网上行通道资源信息或指定流标识信息或者指定服务质量标识也可以理解为特定核心网上行通道资源信息或特定流标识信息或特定服务质量标识。
上述实施方式中，由于依据源网络侧设备发送的PDU会话信息，预留多播空口资源，这样不需要增加其他消息来预留多播空口资源，以节约资源开销。
作为一种可选的实施方式，上述方法还包括：
向所述终端提供空闲态指示。
可选的，所述向所述终端提供空闲态指示包括如下至少一项：
发送重定向消息；
发送目标多播业务传输方式信息；
所述资源信息不包括PDU会话信息中的至少一项。
其中，上述空闲态指示可以参见图2所示的实施例的相应说明，此处不作限定。
作为一种可选的实施方式，所述向所述终端发送资源信息之后，所述方法还包括：
依据所述多播空口资源向所述终端发送多播业务数据。
其中，上述发送多播业务数据可以参见图2所示的实施例的相应说明，此处不作限定。
作为一种可选的实施方式，所述预留多播空口资源，包括：
依据多播业务信息，预留多播空口资源；或者
依据预配置信息，预留多播空口资源。
其中，上述多播放业务信息可以是核心网功能发送的，当然，对此不作限定，例如：也可以是源网络侧设备发送的。
上述多播业务信息可以包括多播业务标识、多播业务QoS信息等至少一项。
上述依据多播业务信息，预留多播空口资源可以是，预留与多播业务匹配的多播空口资源。
上述依据预配置信息，预留多播空口资源可以是，在未获取到多播业务信息的情况下，基于终端存在多播业务的判断使用预配置方案预留空口多播 资源。例如：比如采用预配置QoS信息使用点到点传输方式预留空口资源信息。
该实施方式中，通过上述两种方式可以实现为终端预留匹配的多播空口资源。
可选的，上述依据多播业务信息，预留多播空口资源之前，所述方法还包括：
向核心网功能发送PDU会话信息；
接收所述核心网功能发送的所述多播业务信息，其中，所述多播业务信息与所述PDU会话信息相关。
上述PDU会话信息可以包括多播相关PDU会话相关信息，其中，多播相关PDU会话可以是，用于接收多播业务数据的PDU会话。例如：上述PDU会话信息可以包括多播业务相关PDU会话的PDU会话标识、流标识、QoS相关信息、PDU会话核心网上行通道信息等至少一项。
当核心网功能接收到上述PDU会话信息后，可以确定并发送上述多播业务信息。
本实施例中，通过上述步骤可以提高终端获取多播空口资源的效率，且还可以提高多播业务的切换效率。
请参见图4，图4是本申请实施例提供的一种会话建立方法的流程图，该方法应用于核心网功能，如图4所示，包括以下步骤：
步骤401、建立多播相关PDU会话，其中，所述多播相关协议数据单元PDU会话关联指定核心网上行通道资源信息或者指定流标识信息或者指定服务质量标识。
上述多播相关PDU会话可以是，能够用于传输多播业务数据的PDU会话。
其中，上述指定核心网上行通道资源信息或者指定流标识信息或者指定服务质量标识可以参见图3所示实施例的相应说明，此处不作赘述。
可选的，所述多播相关PDU会话用于源网络侧设备向终端发送多播业务，所述建立多播PDU会话之后，所述方法还包括：
接收目标网络侧设备发送的PDU会话信息；
向所述目标网络侧设备发送多播业务信息，其中，所述多播业务信息与所述PDU会话信息相关。
其中，上述PDU会话信息和多播业务信息可以参见图3所示实施例的相应说明，此处不作赘述。
本实施例中，通过上述步骤可以实现建立用于传输多播业务的PDU会话，从而提高多播业务的发送效果。
下面以核心网功能通过源网络侧设备使用多播相关PDU会话发送多播业务数据，且网络侧设备为gNB、核心网功能为MB-SMF或者MB-UPF对本申请实施例提供的方法进行举例说明，如图5所示，包括以下步骤：
步骤1：使用特定指定核心网上行通道资源信息或者QFI指示存在多播业务。
由于多播业务只有下行数据没有上行数据，核心网功能(比如SMF或UPF)在建立多播相关PDU会话过程中，使用指定核心网上行通道资源信息，比如CN UL Tunnel Info为全0或全1，或使用指定QoS流标识(QFI)，比如某个指定值或某个指定范围内的值，或使用QoS信息(即服务质量标识)表示多播业务，比如使用动态的5QI配置(dynamic-5QI配置)，其中使用指定5QI值或指定范围的5QI值表示有多播业务。
步骤2：UE向源基站(source gNB)发送测量报告。
步骤3：Source gNB决定执行切换操作，选择目标基站(target gNB)，向目标基站发送切换请求消息。比如Handover Request消息，该消息可以携带PDU会话相关信息，比如PDU会话标识(PDU Session ID)、流标识(QFI)、QoS相关信息、PDU会话核心网上行通道信息等。
步骤4：target gNB基于收到的指定核心网上行通道资源信息或指定QoS流标识信息判断终端有多播业务，并可以获得多播业务相关PDU会话相关信息。
步骤5：target gNB可以向核心网功能发送会话更新请求(比如通过AMF发给SMF)，该请求可以携带PDU会话相关信息，例如：包括多播业务相关PDU会话相关信息。
步骤6：核心网功能(比如SMF)基于PDU会话信息获取多播业务信息， 比如多播业务标识，多播业务QoS信息等，并向target gNB发送多播业务信息(比如通过AMF发送)。
步骤7：执行步骤5～6的情况下，target gNB基于多播业务信息预留空口多播资源，不执行步骤5～6的情况下，target gNB基于有多播业务的判断使用预配置方案预留空口多播资源，比如采用预配置QoS信息使用点到点传输方式预留空口资源信息。
步骤8：target gNB通过Source gNB(也可以通过核心网功能和源基站)向终端发送多播空口资源信息。其中，该多播空口资源信息可以包括指示UE是否可以进入空闲态的指示。比如向终端发送重定向消息而非切换命令来指示可进入空闲态，或不发送多播业务相关PDU会话相关信息给UE，或包含指定的多播数据传输方式，其中，该指定的多播数据传输方式可以是点到多点传输方式，或可以通过点到多点传输方式的多播空口资源信息指示这种传输方式。
步骤9：UE依据收到的空口资源信息接入到target gNB，向target gNB发送切换确认消息，比如Handover Confirm(切换确认)消息，或者，UE可以基于空闲态指示进入空闲态而不执行此步骤。
步骤10：可以在步骤7之后执行，target gNB向核心网功能发送会话更新消息(比如通过AMF发送给SMF)，在执行了步骤5～6的情况下，消息可携带建立多播共享通道的基站侧下行接收资源信息，不发送多播业务相关PDU会话相关信息，在没执行步骤5～6的情况下，消息携带PDU会话相关信息，包括多播业务相关PDU会话相关信息。
步骤11：核心网功能在收到多播业务相关PDU会话相关信息的情况下，可以与target gNB交互建立多播共享通道，即向target gNB发送多播业务相关信息，该多播业务相关信息可以包括多播业务信息，例如：多播业务的业务标识、QoS流标识。进一步的，target gNB可基于多播业务相关信息更新多播空口资源信息，并将更新过的多播空口资源信息通知给UE，且target gNB还可以向核心网功能发送多播共享通道基站侧下行接收资源信息。
请参见图6，图6是本申请实施例提供的一种资源信息接收装置的结构图，该装置应用于终端，如图6所示，资源信息接收装置600包括：
发送模块601，用于向源网络侧设备发送用于切换的测量报告；
第一接收模块602，用于接收资源信息，所述资源信息用于指示目标网络侧设备传输多播业务数据的多播空口资源。
可选的，所述装置还包括：
获取模块，用于获取空闲态指示；
执行模块，用于依据所述空闲态指示，进入空闲态或停止向所述目标网络侧设备发送切换确认消息。
可选的，所述获取空闲态指示包括如下至少一项：
接收重定向消息；
接收目标多播业务传输方式信息；
所述资源信息不包括PDU会话信息。
可选的，所述装置还包括：
第二接收模块，用于在所述多播空口资源接收所述目标网络侧设备发送的多播业务数据。
本发明实施例提供的资源信息接收装置能够实现图2的方法实施例中的各个过程，为避免重复，这里不再赘述，且可以提高获取多播空口资源的效率果。
需要说明的是，本申请实施例中的资源信息接收装置可以是装置，也可以是终端中的部件、集成电路、或芯片。
请参见图7，图7是本申请实施例提供的一种资源信息发送装置的结构图，该装置应用于目标网络侧设备，如图7所示，资源信息发送装置700包括：
预留模块701，用于依据终端存在多播业务的情况，预留多播空口资源；
第一发送模块702，用于向所述终端发送资源信息，所述资源信息用于指示所述目标网络侧设备传输多播业务数据的多播空口资源。
可选的，所述第一发送模块702用于依据源网络侧设备发送的PDU会话信息，预留多播空口资源，所述PDU会话信息用于表示所述终端存在多播业务。
可选的，所述第一发送模块702用于依据所述PDU会话信息中包括的指 定核心网上行通道资源信息或指定流标识信息或者指定服务质量标识，预留多播空口资源。
可选的，所述装置还包括：
提供模块，用于向所述终端提供空闲态指示。
可选的，所述向所述终端提供空闲态指示包括如下至少一项：
发送重定向消息；
发送目标多播业务传输方式信息；
所述资源信息不包括PDU会话信息中的至少一项。
可选的，所述装置还包括：
第二发送模块，用于依据所述多播空口资源向所述终端发送多播业务数据。
可选的，所述预留多播空口资源，包括：
依据多播业务信息，预留多播空口资源；或者
依据预配置信息，预留多播空口资源。
可选的，所述装置还包括：
第三发送模块，用于向核心网功能发送PDU会话信息；
接收模块，用于接收所述核心网功能发送的所述多播业务信息，其中，所述多播业务信息与所述PDU会话信息相关。
本发明实施例提供的资源信息发送装置能够实现图3的方法实施例中的各个过程，为避免重复，这里不再赘述，且可以提高终端获取多播空口资源的效率果。
需要说明的是，本申请实施例中的资源信息发送装置可以是装置，也可以是目标网络侧设备中的部件、集成电路、或芯片。
请参见图8，图8是本申请实施例提供的一种会话建立装置的结构图，该装置应用于核心网功能，如图8所示，包括：
建立模块801，用于建立多播相关协议数据单元PDU会话，其中，所述多播相关协议数据单元PDU会话关联指定核心网上行通道资源信息或者指定流标识信息或者指定服务质量标识。
可选的，所述装置还包括：
接收模块，用于接收目标网络侧设备发送的PDU会话信息；
发送模块，用于向所述目标网络侧设备发送多播业务信息，其中，所述多播业务信息与所述PDU会话信息相关。
本发明实施例提供的会话建立装置能够实现图4的方法实施例中的各个过程，为避免重复，这里不再赘述，且可以提高多播业务的发送效果。
需要说明的是，本申请实施例中的会话建立装置可以是装置，也可以是核心网功能中的部件、集成电路、或芯片。
图9为实现本申请实施例的一种终端的硬件结构示意图。
该终端900包括但不限于：射频单元901、网络模块902、音频输出单元903、输入单元904、传感器905、显示单元906、用户输入单元907、接口单元908、存储器909、以及处理器910等部件。
本领域技术人员可以理解，终端900还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器910逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图9中示出的电子设备结构并不构成对电子设备的限定，电子设备可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
射频单元901用于：向源网络侧设备发送用于切换的测量报告；接收资源信息，所述资源信息用于指示目标网络侧设备传输多播业务数据的多播空口资源。
可选的，所述向源网络侧设备发送用于切换的测量报告之后，射频单元901或者处理器910用于：
获取空闲态指示；
依据所述空闲态指示，进入空闲态或停止向所述目标网络侧设备发送切换确认消息。
可选的，所述获取空闲态指示包括如下至少一项：
接收重定向消息；
接收目标多播业务传输方式信息；
所述资源信息不包括PDU会话信息。
可选的，所述终端进入空闲态之后，射频单元901还用于：
在所述多播空口资源接收所述目标网络侧设备发送的多播业务数据。
本实施例可以提高获取多播空口资源的效率。
可选的，本发明实施例还提供一种终端，包括处理器910，存储器909，存储在存储器909上并可在所述处理器910上运行的程序或指令，该程序或指令被处理器910执行时实现上述资源信息接收方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
参见图10，图10是本发明实施例提供的一种网络侧设备的结构图，该网络侧设备为目标网络侧设备，如图10所示，该网络侧设备1000包括：处理器1001、收发机1002、存储器1003和总线接口，其中：
收发机1002，用于：
依据终端存在多播业务的情况，预留多播空口资源；
向所述终端发送资源信息，所述资源信息用于指示所述目标网络侧设备传输多播业务数据的多播空口资源。
可选的，所述依据终端存在多播业务的情况，预留多播空口资源，包括：
依据源网络侧设备发送的PDU会话信息，预留多播空口资源，所述PDU会话信息用于表示所述终端存在多播业务。
可选的，所述依据源网络侧设备发送的PDU会话信息，预留多播空口资源，包括：
依据所述PDU会话信息中包括的指定核心网上行通道资源信息或指定流标识信息或者指定服务质量标识，预留多播空口资源。
可选的，收发机1002还用于：
向所述终端提供空闲态指示。
收发机1002所述向所述终端提供空闲态指示包括如下至少一项：
发送重定向消息；
发送目标多播业务传输方式信息；
所述资源信息不包括PDU会话信息中的至少一项。
可选的，所述向所述终端发送资源信息之后，收发机1002还用于：
依据所述多播空口资源向所述终端发送多播业务数据。
可选的，所述预留多播空口资源，包括：
依据多播业务信息，预留多播空口资源；或者
依据预配置信息，预留多播空口资源。
可选的，所述依据多播业务信息，预留多播空口资源之前，收发机1002还用于：
向核心网功能发送PDU会话信息；
接收所述核心网功能发送的所述多播业务信息，其中，所述多播业务信息与所述PDU会话信息相关。
本实施例可以提高终端获取多播空口资源的效率。
其中，收发机1002，用于在处理器1001的控制下接收和发送数据，所述收发机1002包括至少两个天线端口。
在图10中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1001代表的一个或多个处理器和存储器1003代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1002可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。针对不同的用户设备，总线接口还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器1001负责管理总线架构和通常的处理，存储器1003可以存储处理器1001在执行操作时所使用的数据。
优选的，本发明实施例还提供一种网络侧设备，包括处理器1001，存储器1003，存储在存储器1003上并可在所述处理器1001上运行的程序或者指令，该程序或者指令被处理器1001执行时实现上述资源信息发送方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
参见图11，图11是本发明实施例提供的一种核心网功能的结构图，如图11所示，该网络侧设备1100包括：处理器1101、收发机1102、存储器1103和总线接口，其中：
收发机1102，用于：建立多播相关协议数据单元PDU会话，其中，所述多播相关协议数据单元PDU会话关联指定核心网上行通道资源信息或者指 定流标识信息或者指定服务质量标识。
可选的，所述多播相关PDU会话用于源网络侧设备向终端发送多播业务，所述建立多播PDU会话之后，收发机1102还用于：
接收目标网络侧设备发送的PDU会话信息；
向所述目标网络侧设备发送多播业务信息，其中，所述多播业务信息与所述PDU会话信息相关。
本实施例，可以提高多播业务的发送效果。
其中，收发机1102，用于在处理器1101的控制下接收和发送数据，所述收发机1102包括至少两个天线端口。
在图11中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1101代表的一个或多个处理器和存储器1103代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1102可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。针对不同的用户设备，总线接口还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器1101负责管理总线架构和通常的处理，存储器1103可以存储处理器1101在执行操作时所使用的数据。
优选的，本发明实施例还提供一种核心网功能，包括处理器1101，存储器1103，存储在存储器1103上并可在所述处理器1101上运行的程序或者指令，该程序或者指令被处理器1101执行时实现上述会话建立方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，所述程序或指令被处理器执行时实现本申请实施例提供的资源信息接收方法中的步骤，或者，所述程序或指令被处理器执行时实现本申请实施例提供的资源信息发送方法中的步骤，或者，所述程序或指令被处理器执行时实现本申请实施例提供的会话建立方法中的步骤。
本申请实施例还提供一种程序产品，所述程序产品被存储在非易失的存 储介质中，所述程序产品被至少一个处理器执行以实现本申请实施例提供的资源信息接收方法中的步骤，或者，所述程序产品被至少一个处理器执行以实现本申请实施例提供的资源信息发送方法中的步骤，所述程序产品被至少一个处理器执行以实现本申请实施例提供的会话建立方中的步骤。
其中，所述处理器为上述实施例中所述的终端或者网络设备中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述资源信息接收方法、资源信息发送方法或者信息确定方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片、系统芯片、芯片系统或片上系统芯片等。
可以理解的是，本公开描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，模块、单元、子模块、子单元等可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processing，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本申请所述功能的其它电子单元或其组合中。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包 括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (30)

  1. 一种资源信息接收方法，应用于终端，其中包括：
    向源网络侧设备发送用于切换的测量报告；
    接收资源信息，所述资源信息用于指示目标网络侧设备传输多播业务数据的多播空口资源。
  2. 如权利要求1所述的方法，其中，所述向源网络侧设备发送用于切换的测量报告之后，所述方法还包括：
    获取空闲态指示；
    依据所述空闲态指示，进入空闲态或停止向所述目标网络侧设备发送切换确认消息。
  3. 如权利要求2所述的方法，其中，所述获取空闲态指示包括如下至少一项：
    接收重定向消息；
    接收目标多播业务传输方式信息；
    所述资源信息不包括PDU会话信息。
  4. 如权利要求2所述的方法，其中，所述终端进入空闲态之后，所述方法还包括：
    在所述多播空口资源接收所述目标网络侧设备发送的多播业务数据。
  5. 一种资源信息发送方法，应用于目标网络侧设备，包括：
    依据终端存在多播业务的情况，预留多播空口资源；
    向所述终端发送资源信息，所述资源信息用于指示所述目标网络侧设备传输多播业务数据的多播空口资源。
  6. 如权利要求5所述的方法，其中，所述依据终端存在多播业务的情况，预留多播空口资源，包括：
    依据源网络侧设备发送的PDU会话信息，预留多播空口资源，所述PDU会话信息用于表示所述终端存在多播业务。
  7. 如权利要求6所述的方法，其中，所述依据源网络侧设备发送的PDU会话信息，预留多播空口资源，包括：
    依据所述PDU会话信息中包括的指定核心网上行通道资源信息或指定流标识信息或指定服务质量标识，预留多播空口资源。
  8. 如权利要求5所述的方法，其中，所述方法还包括：
    向所述终端提供空闲态指示。
  9. 如权利要求8所述的方法，其中，所述向所述终端提供空闲态指示包括如下至少一项：
    发送重定向消息；
    发送目标多播业务传输方式信息；
    所述资源信息不包括PDU会话信息中的至少一项。
  10. 如权利要求5所述的方法，其中，所述向所述终端发送资源信息之后，所述方法还包括：
    依据所述多播空口资源向所述终端发送多播业务数据。
  11. 如权利要求5所述的方法，其中，所述预留多播空口资源，包括：
    依据多播业务信息，预留多播空口资源；或者
    依据预配置信息，预留多播空口资源。
  12. 如权利要求11所述的方法，其中，所述依据多播业务信息，预留多播空口资源之前，所述方法还包括：
    向核心网功能发送PDU会话信息；
    接收所述核心网功能发送的所述多播业务信息，其中，所述多播业务信息与所述PDU会话信息相关。
  13. 一种会话建立方法，应用于核心网功能，包括：
    建立多播相关协议数据单元PDU会话，其中，所述多播相关协议数据单元PDU会话关联指定核心网上行通道资源信息或者指定流标识信息或者指定服务质量标识。
  14. 如权利要求13所述的方法，其中，所述多播相关PDU会话用于源网络侧设备向终端发送多播业务，所述建立多播PDU会话之后，所述方法还包括：
    接收目标网络侧设备发送的PDU会话信息；
    向所述目标网络侧设备发送多播业务信息，其中，所述多播业务信息与 所述PDU会话信息相关。
  15. 一种资源信息接收装置，应用于终端，包括：
    发送模块，用于向源网络侧设备发送用于切换的测量报告；
    第一接收模块，用于接收资源信息，所述资源信息用于指示目标网络侧设备传输多播业务数据的多播空口资源。
  16. 如权利要求15所述的装置，其中，所述装置还包括：
    获取模块，用于获取空闲态指示；
    执行模块，用于依据所述空闲态指示，进入空闲态或停止向所述目标网络侧设备发送切换确认消息。
  17. 一种资源信息发送装置，应用于目标网络侧设备，包括：
    预留模块，用于依据终端存在多播业务的情况，预留多播空口资源；
    第一发送模块，用于向所述终端发送资源信息，所述资源信息用于指示所述目标网络侧设备传输多播业务数据的多播空口资源。
  18. 如权利要求17所述的装置，其中，所述发送模块用于依据源网络侧设备发送的PDU会话信息，预留多播空口资源，所述PDU会话信息用于表示所述终端存在多播业务。
  19. 如权利要求17所述的装置，其中，所述装置还包括：
    提供模块，用于向所述终端提供空闲态指示。
  20. 一种会话建立装置，应用于核心网功能，包括：
    建立模块，用于建立多播相关协议数据单元PDU会话，其中，所述多播相关协议数据单元PDU会话关联指定核心网上行通道资源信息或者指定流标识信息或者指定服务质量标识。
  21. 如权利要求20所述的装置，其中，所述装置还包括：
    接收模块，用于接收目标网络侧设备发送的PDU会话信息；
    发送模块，用于向所述目标网络侧设备发送多播业务信息，其中，所述多播业务信息与所述PDU会话信息相关。
  22. 一种终端，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的程序或者指令，所述程序或者指令被所述处理器执行时实现如权利要求1至4中任一项所述的资源信息接收方法中的步骤。
  23. 一种网络侧设备，所述网络侧设备为目标网络侧设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的程序或者指令，所述程序或者指令被所述处理器执行时实现如权利要求5至12中任一项所述的资源信息发送方法中的步骤。
  24. 一种核心网功能，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的程序或者指令，所述程序或者指令被所述处理器执行时实现如权利要求13至14中任一项所述的会话建立方法中的步骤。
  25. 一种可读存储介质，所述可读存储介质上存储有程序或指令，所述程序或指令被处理器执行时实现如权利要求1至4中任一项所述的资源信息接收方法中的步骤，或者，所述程序或指令被处理器执行时实现如权利要求5至12中任一项所述的资源信息发送方法中的步骤，或者，所述程序或指令被处理器执行时实现如权利要求13至14中任一项所述的会话建立方法中的步骤。
  26. 一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如权利要求1至4中任一项所述的资源信息接收方法，或者，实现如权利要求5至12中任一项所述的资源信息发送方法，或者，实现如权利要求13至14中任一项所述的会话建立方法。
  27. 一种计算机程序产品，所述计算机程序产品被至少一个处理器执行以实现如权利要求1至4中任一项所述的资源信息接收方法，或者，实现如权利要求5至12中任一项所述的资源信息发送方法，或者，实现如权利要求13至14中任一项所述的会话建立方法。
  28. 一种终端，所述终端被配置成用于执行如权利要求1-4中任一项所述的资源信息接收方法。
  29. 一种网络侧设备，所述网络侧设备被配置成用于执行如权利要求5至12中任一项所述的资源信息发送方法。
  30. 一种核心网功能，所述核心网功能被配置成用于执行如权利要求13至14中任一项所述的会话建立方法。
PCT/CN2021/107764 2020-07-23 2021-07-22 信息接收方法、发送方法、会话建立方法、装置和设备 Ceased WO2022017437A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010718757.XA CN113973266B (zh) 2020-07-23 2020-07-23 信息接收方法、发送方法、会话建立方法、装置和设备
CN202010718757.X 2020-07-23

Publications (1)

Publication Number Publication Date
WO2022017437A1 true WO2022017437A1 (zh) 2022-01-27

Family

ID=79585390

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/107764 Ceased WO2022017437A1 (zh) 2020-07-23 2021-07-22 信息接收方法、发送方法、会话建立方法、装置和设备

Country Status (2)

Country Link
CN (1) CN113973266B (zh)
WO (1) WO2022017437A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116980836A (zh) * 2022-04-22 2023-10-31 大唐移动通信设备有限公司 业务处理方法、装置、终端设备及网络设备
US12495457B2 (en) * 2020-08-06 2025-12-09 Zte Corporation Signaling for multicast broadcast services

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102316418A (zh) * 2010-07-02 2012-01-11 中兴通讯股份有限公司 一种多媒体广播多播业务连续性的实现方法和装置
US20180160342A1 (en) * 2016-12-02 2018-06-07 Ofinno Technologies, Llc Handover Procedure for a UE with V2X Services
CN113498132A (zh) * 2020-04-03 2021-10-12 维沃移动通信有限公司 移动性管理方法、源基站、目标基站及终端设备

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100571208C (zh) * 2006-04-20 2009-12-16 中兴通讯股份有限公司 一种实现多播/广播业务的资源预留方法
US8451795B2 (en) * 2007-08-08 2013-05-28 Qualcomm Incorporated Handover in a wireless data packet communication system that avoid user data loss
WO2010139088A1 (zh) * 2009-06-01 2010-12-09 上海贝尔股份有限公司 服务续传方法、用户设备和基站
CN104812087A (zh) * 2014-01-24 2015-07-29 北京三星通信技术研究有限公司 支持组业务传输的方法、装置及系统
CN105530667A (zh) * 2014-09-28 2016-04-27 中兴通讯股份有限公司 终端的业务连续性处理方法及装置
CN109257827B (zh) * 2016-09-30 2020-09-18 华为技术有限公司 通信方法、装置、系统、终端和接入网设备
CN108024253B (zh) * 2016-11-04 2021-04-09 华为技术有限公司 一种通信方法以及终端、接入网设备、核心网设备
CN113784417A (zh) * 2017-01-09 2021-12-10 华为技术有限公司 一种会话管理方法及装置
CN108696905B (zh) * 2017-02-20 2023-06-13 中兴通讯股份有限公司 一种无线资源的管理方法及装置
CN110831076B (zh) * 2018-08-10 2023-07-14 大唐移动通信设备有限公司 一种pdu会话的处理方法及设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102316418A (zh) * 2010-07-02 2012-01-11 中兴通讯股份有限公司 一种多媒体广播多播业务连续性的实现方法和装置
US20180160342A1 (en) * 2016-12-02 2018-06-07 Ofinno Technologies, Llc Handover Procedure for a UE with V2X Services
CN113498132A (zh) * 2020-04-03 2021-10-12 维沃移动通信有限公司 移动性管理方法、源基站、目标基站及终端设备

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Mobility for NR MBS", 3GPP DRAFT; R2-2101171, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic meeting; 20210125 - 20210205, 14 January 2021 (2021-01-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051972834 *
HUAWEI, HISILICON: "KI#7, New Solution: Inter-RAN node MBS Session Handover", 3GPP DRAFT; S2-2003966, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Elbonia; 20200601 - 20200612, 22 May 2020 (2020-05-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051889974 *
HUAWEI, HISILICON: "MBS Session Management", 3GPP DRAFT; S2-2000489, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Incheon, South Korea; 20200113 - 20200117, 7 January 2020 (2020-01-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051842554 *
VIVO: "KI #1, New Sol: Multicast session leg addition due to UE mobility", 3GPP DRAFT; S2-2004105, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting ;20200601 - 20200612, 22 May 2020 (2020-05-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051890112 *
VIVO: "KI #7, New Sol: Delivery method change due to UE mobility", 3GPP DRAFT; S2-2004331, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting ;20200601 - 20200612, 29 May 2020 (2020-05-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051892267 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12495457B2 (en) * 2020-08-06 2025-12-09 Zte Corporation Signaling for multicast broadcast services
CN116980836A (zh) * 2022-04-22 2023-10-31 大唐移动通信设备有限公司 业务处理方法、装置、终端设备及网络设备

Also Published As

Publication number Publication date
CN113973266B (zh) 2023-12-19
CN113973266A (zh) 2022-01-25

Similar Documents

Publication Publication Date Title
US10980072B2 (en) Method and device for performing communication configuration
US10764805B2 (en) Signal strength measurement method and device
CN113766670A (zh) 一种pdu会话激活方法、寻呼方法及其装置
US9445343B2 (en) Systems for switching modes in wireless sessions
US11012215B2 (en) Information transmission method, terminal device and network device
JP2018527838A (ja) ネットワーク指示の処理装置、方法及び通信システム
WO2022111402A1 (zh) 通信指示方法、装置及网络侧设备
WO2022206663A1 (zh) Pdu会话建立方法、相关设备及可读存储介质
WO2022017437A1 (zh) 信息接收方法、发送方法、会话建立方法、装置和设备
WO2022042440A1 (zh) 用户面数据的传输方法和网络节点
CN110087269B (zh) 用户设备接入网络的方法和接入设备
CN113810956B (zh) 切换多播业务的方法及设备
CN111108785A (zh) 用于无线网络的网络切片特定寻呼周期
CN113950042A (zh) 识别方法、发送方法及相关设备
US20230164645A1 (en) Handover method and apparatus, and communications device
CN113973268B (zh) 数据接收方法、发送方法、资源更新方法、装置和设备
WO2022028541A1 (zh) 切换方法、装置及相关设备
CN114513757B (zh) 信息获取方法、指示方法、装置、相关设备和存储介质
CN114449543B (zh) 辅助信息获取方法、配置方法、终端和网络设备
US20260040186A1 (en) Apparatus, method and computer program
CN115243401B (zh) 业务处理方法、装置、系统、可读取存储介质和电子设备
CN114071591B (zh) 多播业务实现方法及装置、通信设备
WO2022022568A1 (zh) 数据传输方法、装置、核心网设备及接入网侧设备
US20190116528A1 (en) Communication method, core network device, access network device, terminal device, and communication system
KR20250043543A (ko) 정보 처리 방법, 장치, 통신 디바이스 및 저장 매체

Legal Events

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

Ref document number: 21846056

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21846056

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 21846056

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 01/08/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 21846056

Country of ref document: EP

Kind code of ref document: A1