WO2022151155A1 - 信息传输方法及通信装置 - Google Patents

信息传输方法及通信装置 Download PDF

Info

Publication number
WO2022151155A1
WO2022151155A1 PCT/CN2021/071767 CN2021071767W WO2022151155A1 WO 2022151155 A1 WO2022151155 A1 WO 2022151155A1 CN 2021071767 W CN2021071767 W CN 2021071767W WO 2022151155 A1 WO2022151155 A1 WO 2022151155A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
slice
network element
unit
bearer unit
Prior art date
Application number
PCT/CN2021/071767
Other languages
English (en)
French (fr)
Inventor
孙海洋
朱方园
李岩
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN202180088636.4A priority Critical patent/CN116711458A/zh
Priority to PCT/CN2021/071767 priority patent/WO2022151155A1/zh
Publication of WO2022151155A1 publication Critical patent/WO2022151155A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices

Definitions

  • the present application relates to the field of communication technologies, and in particular, to an information transmission method and a communication device.
  • Network slicing is to virtualize multiple end-to-end networks based on a common hardware through slicing technology. Each network has different network functions and adapts to different types of service requirements.
  • single network slice selection assistance information (S-NSSAI) is used to identify a network slice.
  • the radio access network A radio access network (RAN) node is configured with a remapping S-NSSAI list, where the S-NSSAI list includes identifiers of slice resources of various resource types configured for the network slice. If the slice resources of a certain resource type configured for network slicing on the RAN are insufficient, some slice resources of other resource types can be used to ensure service continuity. If the same charging method in the prior art is used for charging, fairness will be affected.
  • the embodiments of the present application provide an information transmission method and a communication device, which can realize fair charging.
  • an embodiment of the present application provides an information transmission method, where the method may be performed by a first access network device, or may be performed by a component (for example, a processor, a chip, or a chip) of the first access network device system, etc.) to execute.
  • the information transmission method may include: the first access network device determines that the resource type of the slice resource used by the first bearer unit changes.
  • the granularity of the first bearer unit may be session granularity, or may also be QoS flow granularity, or may also be network slice granularity.
  • the change of the resource type of the slice resource used by the first bearer unit may refer to: a session in which the resource type of the used slice resource is changed in the first bearer unit or QoS flow.
  • the resource type of the slice resource may be determined by the identifier of the subgroup in the S-NSSAI list configured for the network slice. The identifiers of different subgroups in the S-NSSAI list are used to identify slice resources of different resource types serving the network slice.
  • the first access network device may schedule slice resources of different resource types in the S-NSSAI list corresponding to the network slice for different sessions or different QoS flows in the network slice, or may schedule the same resources in the S-NSSAI list corresponding to the network slice.
  • a sliced resource of resource type may be used to schedule slice resources of different resource types in the S-NSSAI list corresponding to the network slice for different sessions or different QoS flows in the network slice, or may schedule the same resources in the S-NSSAI list corresponding to the network slice.
  • the first access network device In response to a change in the resource type of the slice resource used by the first bearer unit, the first access network device notifies the first network element.
  • the first bearer unit is a network slice
  • the first access network device may determine the number of sessions whose resource types are changed in the network slice or the number of QoS flows and the number of all sessions included in the network slice. or the ratio between the number of QoS flows, and notify the first network element of the ratio.
  • the first network element determines that the resource type of the slice resource used by the first bearer unit has changed according to the notification, and notifies the charging network element that the resource type of the slice resource used by the second bearer unit has changed, so that the charging network element can change the resource type of the slice resource used by the second bearer unit.
  • a charging mode corresponding to the changed resource type of the second bearer unit is determined.
  • the second bearing unit is a subset of the first bearing unit, or the first bearing unit is a subset of the second bearing unit, or the first bearing unit and the second bearing unit are the same.
  • the first network element can sense that the resource type of the slice resource used by the first bearer unit has changed, and notify the charging network element of the resource type of the slice resource used by the second bearer unit If a change occurs, the charging network element perceives the change of the resource type, so that the charging method corresponding to the changed resource type is used for charging, so as to realize fair charging.
  • the notification manner of the first access network device notifying the first network element may be that the first access network device sends first information to the first network element, where the first information may be used to indicate the first network element.
  • the resource type of the slice resource used by a bearer unit changes, or the first information may be used to indicate the changed resource type of the slice resource used by the first bearer unit.
  • the number of resource types may include two, and the first access network device may notify the first network element through the first information that the resource type of the slice resource used by the first bearer unit changes, and the first network element That is, the resource type of the slice resource used by the changed first bearer unit can be determined.
  • the first access network device can notify the first network element that the resource type of the slice resource used by the first bearer unit has changed in various ways, thereby facilitating the first network element to determine the changed first bearer unit The resource type of the tile resource used.
  • the first access network device when the access network device through which the user plane connection of the first bearer unit passes is switched from the second access network device to the first access network device, the first access network device
  • the resource type of the slice resource corresponding to the first bearer unit may be received from the second access network device, where the resource type is the resource type of the slice resource scheduled by the second access network device for the first bearer unit.
  • the first access network device further determines the resource type of the slice resource scheduled by the first access network device for the first bearer unit, and according to the received resource type of the slice resource corresponding to the first bearer unit and the first The access network device determines whether the resource type of the slice resource used by the first bearer unit changes for the resource type of the slice resource scheduled by the first bearer unit.
  • the first access network device can determine whether the resource type of the slice resource used by the first bearer unit changes.
  • the first bearer unit is one of a session, a QoS flow or a network slice.
  • the first access network device may receive indication information from the first network element, and in response to the indication information, the resource type of the slice resource used by the first access network device in the first bearer unit occurs. In case of change, the first network element is notified.
  • the first network element can indicate to the first access network device the bearer unit that needs to be reported, thereby facilitating the first access network device to report in a targeted manner and saving network transmission resources.
  • the indication information may be used to instruct the first access network device to notify the first network element when the resource type of the slice resource used by the first bearer unit changes; or, the indication information may be used for instructing the subscription of the first access network device to the resource type change event of the first bearer unit.
  • the first network element may be an access and mobility management function (AMF) or a session management function (SMF).
  • AMF access and mobility management function
  • SMF session management function
  • an embodiment of the present application provides an information transmission method, where the method may be performed by a first network element, or may be performed by a component of the first network element (for example, a processor, a chip, or a chip system, etc.) .
  • the information transmission method may include: the first network element determines that the resource type of the slice resource used by the first bearer unit changes, and in response to the change of the resource type of the slice resource used by the first bearer unit, the first network element notifies the computer The resource type of the slice resource used by the second bearer unit of the fee network element changes.
  • the first bearing unit is a subset of the second bearing unit, or the second bearing unit is a subset of the first bearing unit, or the first bearing unit and the second bearing unit
  • the carrying unit is the same.
  • the manner in which the first network element notifies the charging network element may be that the first network element sends slice resource information to the charging network element, where the slice resource information is used to indicate the resource type of the slice resource used by the second bearer unit If the change occurs, or the slice resource information indicates the resource type of the slice resource used by the changed second bearer unit.
  • the first network element when the first network element perceives that the type of slice resources used by the first bearer unit has changed, the first network element notifies the charging network element of the slice resources used by the second bearer unit The type changes, so that the charging network element perceives the change of the resource type, and adopts the charging method corresponding to the changed resource type to perform charging, so as to realize charging fairness.
  • the way for the first network element to determine that the resource type of the slice resource used by the first bearer unit has changed may be: the first network element receives a notification from the access network device, and determines the first network element according to the notification.
  • the resource type of the slice resource used by a bearer unit changes.
  • the notification may indicate that the resource type of the slice resource used by the first bearer unit has changed, or the notification may indicate the changed resource type of the slice resource used by the first bearer unit.
  • the first network element can quickly determine that the resource type of the slice resource used by the first bearer unit has changed through the notification received from the access network device.
  • the way for the first network element to determine that the resource type of the slice resource used by the first bearer unit has changed may be: the access network device through which the user plane connection of the first bearer unit passes is determined by the first bearer unit.
  • the first network element receives first resource state information from the first access network device, where the first resource state information is used to indicate that the first access network device is The resource type of the slice resource scheduled by the first bearer unit.
  • the first network element receives second resource state information from the second access network device, where the second resource state information is used to indicate the resource type of the slice resource scheduled by the second access network device for the first bearer unit.
  • the first network element may determine, according to the first resource state information and the second resource state information, that the resource type of the slice resource used by the first bearer unit has changed.
  • the first network element determines whether the resource type of the slice resource used by the first bearer unit changes.
  • the first bearer unit is one of a session, a QoS flow or a network slice.
  • the second bearer unit is one of a network slice, a session or a QoS flow.
  • the second bearer unit is one of a network slice, a session, a QoS flow or a service.
  • the granularity reported by the first network element to the charging network element can be selected in various ways.
  • the method further includes: the first network element receives first indication information from the charging network element, and in response to the first indication information, the first network element in the first bearer unit uses the slice resource When the resource type is changed, the slice resource information is sent to the charging network element.
  • the charging network element can indicate to the first network element the bearer unit that needs to be reported, thereby facilitating the first network element to report in a targeted manner and saving network transmission resources.
  • the first indication information is used to instruct the first network element to notify the charging network element when the resource type of the slice resource used by the second bearer unit changes; or, the first indication information may be It is used to instruct the charging network element to subscribe the first network element to the resource type change event of the second bearer unit.
  • the method may further include: in response to the first indication information received by the first network element from the charging network element, the first network element may send second indication information to the access network device,
  • the access network device may refer to an access network device to which the terminal device is connected.
  • the second indication information may be used to instruct the access network device to notify the first network element when the resource type of the slice resource used by the first bearer unit changes.
  • the charging network element subscribes to the first network element for the resource type change event of the second bearer unit
  • the first network element subscribes to the access network device for the resource type change event of the first bearer unit
  • the access network equipment can report to the bearer unit in a targeted manner, saving network transmission resources.
  • an embodiment of the present application provides an information transmission method, where the method may be executed by a charging network element, or may be executed by a component of the charging network element (for example, a processor, a chip, or a chip system, etc.) .
  • the information transmission method may include: the charging network element receives slice resource information from the first network element, where the slice resource information is used to indicate that the resource type of the slice resource used by the first bearer unit changes, or the slice resource information indicates that the change The resource type of the slice resource used by the subsequent first bearer unit.
  • the charging network element determines, for the first bearer unit, a charging processing manner corresponding to the changed resource type of the slice resource used by the first bearer unit.
  • the first A network element may determine the resource type of the slice resource used by the changed first bearer unit according to the slice resource information.
  • the charging network element can perceive that the resource type of the slice resource used by the bearer unit has changed, and thus use the charging method corresponding to the changed resource type to perform charging, so as to realize fair charging .
  • the method further includes: the charging network element sends indication information to the first network element, where the indication information is used to indicate the resource type of the slice resource used by the first network element in the first bearer unit In the case of changes, the charging network element is notified.
  • the charging network element instructs the first network element to report the resource type change event of the bearer unit in a targeted manner, thereby saving network transmission resources.
  • an embodiment of the present application provides an information transmission method, where the method may be performed by a first access network device, or may be performed by a component (for example, a processor, a chip, or a chip) of the first access network device. system, etc.) to execute.
  • the information transmission method may include: the first access network device determines that the access network device through which the user plane connection of the first bearer unit passes is switched.
  • the first access network device may be the access network device through which the user plane connection of the first bearer unit passes before the handover, that is, the source access network device, or the first access network device may also be the handover After that, the access network device through which the user plane of the first bearer unit is connected, that is, the target access network device.
  • the first access network device In response to the handover of the access network device through which the user plane connection of the first bearer unit passes, the first access network device sends resource status information to the first network element, where the resource status information is used to indicate the first access network device The resource type of the slice resource scheduled for the first bearer unit.
  • the access network device through which the user plane connection of the first bearer unit passes is switched, and the source access network device and the target access network device will perform the scheduling of the first bearer unit.
  • the resource type of the slice resource is reported to the first network element, so that the first network element can determine whether the resource type of the slice resource used by the first bearer unit has changed.
  • the method may further include: the first access network device receives indication information from the first network element; in response to the indication information, the first access network device is on the user plane of the first bearer unit When the access network device through which the connection passes is switched, the resource status information is sent to the first network element.
  • the indication information is used to instruct the first access network device to notify the first network element when the resource type of the slice resource used by the first bearer unit changes.
  • the first access network device can determine, according to the indication information, the resource state information that needs to be reported to the bearer unit of the first network element, so as to report in a targeted manner and save transmission resources.
  • an embodiment of the present application provides a communication apparatus, where the communication apparatus may be a first access network device, or may be a component of the first access network device (for example, a processor, a chip, or a chip system, etc.) , the communication device may include a transceiver unit and a processing unit;
  • a processing unit configured to determine that the resource type of the slice resource used by the first bearer unit has changed
  • a transceiver unit configured to notify the first network element in response to a change in the resource type of the slice resource used by the first bearer unit.
  • the transceiver unit is specifically configured to send first information to the first network element, where the first information is used to indicate that the resource type of the slice resource used by the first bearer unit changes, or the The first information is used to indicate the changed resource type of the slice resource used by the first bearer unit.
  • the transceiver unit is further configured to receive the resource type of the slice resource corresponding to the first bearer unit from the second access network device;
  • the processing unit is further configured to determine the resource type of the slice resource scheduled by the first access network device for the first bearer unit.
  • the first bearer unit is one of a session, a quality of service QoS flow or a network slice.
  • the transceiver unit is further configured to receive indication information from the first network element
  • the transceiver unit is further configured to, in response to the indication information, notify the first network element when the resource type of the slice resource used by the first bearer unit changes.
  • the indication information is used to instruct the first access network device to notify the first network element when the resource type of the slice resource used by the first bearer unit changes .
  • the first network element is an access and mobility management function AMF network element or a session management function SMF network element.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a first network element or a component of the first network element (for example, a processor, a chip, or a chip system, etc.).
  • the communication device may include a transceiver unit and a processing unit;
  • a processing unit configured to determine that the resource type of the slice resource used by the first bearer unit has changed
  • a transceiver unit configured to send slice resource information to the charging network element in response to a change in the resource type of the slice resource used by the first bearer unit, where the slice resource information is used to indicate the size of the slice resource used by the second bearer unit The resource type is changed, or the slice resource information indicates the resource type of the slice resource used by the changed second bearer unit;
  • the first bearing unit is a subset of the second bearing unit, or the second bearing unit is a subset of the first bearing unit, or the first bearing unit and the second bearing unit
  • the carrying unit is the same.
  • the transceiver unit is further configured to receive a notification from an access network device
  • the processing unit is specifically configured to determine, according to the notification, that the resource type of the slice resource used by the first bearer unit has changed.
  • the transceiver unit is further configured to receive first resource status information from a first access network device, where the first resource status information is used to indicate that the first access network device is the the resource type of the slice resource scheduled by the first bearer unit;
  • the transceiver unit is further configured to receive second resource state information from a second access network device, where the second resource state information is used to indicate the slice resource scheduled by the second access network device for the first bearer unit resource type;
  • the processing unit is specifically configured to determine, according to the first resource state information and the second resource state information, that the resource type of the slice resource used by the first bearer unit has changed.
  • the first bearer unit is one of a session, a quality of service QoS flow or a network slice.
  • the second bearer unit is one of a network slice, a session or a QoS flow
  • the second bearer unit is one of a network slice, a session, a QoS flow or a service.
  • the transceiver unit is further configured to receive first indication information from the charging network element
  • the transceiver unit is further configured to, in response to the first indication information, send slice resource information to the charging network element in the case that the resource type of the slice resource used by the first bearer unit changes.
  • the first indication information is used to instruct the first network element to notify the charging network element when the resource type of the slice resource used by the second bearer unit changes .
  • the transceiver unit is further configured to, in response to the first indication information, send second indication information to the access network device, where the second indication information is used to indicate the access network device In the case that the resource type of the slice resource used by the first bearer unit changes, the first network element is notified.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a charging network element or a component of the charging network element (for example, a processor, a chip, or a chip system, etc.).
  • the communication device may include a transceiver unit and a processing unit;
  • a transceiver unit configured to receive slice resource information from the first network element, where the slice resource information is used to indicate that the resource type of the slice resource used by the first bearer unit has changed, or the slice resource information indicates that the changed first The resource type of the slice resource used by the bearer unit;
  • a processing unit configured to determine, for the first bearer unit, a charging processing manner corresponding to the changed resource type of the slice resource used by the first bearer unit.
  • the transceiver unit is further configured to send indication information to the first network element, where the indication information is used to indicate the slice resource used by the first network element in the first bearer unit In the case that the resource type of the device is changed, the charging network element is notified.
  • an embodiment of the present application provides a communication apparatus, where the communication apparatus may be a first access network device, or may be a component of the first access network device (for example, a processor, a chip, or a chip system, etc.) , the communication device may include a transceiver unit and a processing unit;
  • a processing unit configured to determine that the access network device through which the user plane connection of the first bearer unit passes is switched
  • a transceiver unit configured to send resource status information to the first network element in response to a handover of the access network device through which the user plane connection of the first bearer unit passes, where the resource status information is used to indicate the first access network device
  • the resource type of the slice resource scheduled by an access network device for the first bearer unit is used to indicate the first access network device.
  • the first access network device may be the access network device through which the user plane connection of the first bearer unit passes before the handover, that is, the source access network device, or the first access network device may also be the handover After that, the access network device through which the user plane of the first bearer unit is connected, that is, the target access network device.
  • the transceiver unit is further configured to receive indication information from the first network element
  • the transceiver unit is further configured to, in response to the indication information, send resource status information to the first network element when the access network device through which the user plane connection of the first bearer unit passes is switched.
  • the indication information is used to instruct the first access network device to notify the first network element when the resource type of the slice resource used by the first bearer unit changes.
  • an embodiment of the present application provides a communication apparatus, including a processor.
  • the processor is coupled to the memory and can be used to execute instructions in the memory to implement the method of any one of the first to fourth aspects above.
  • the communication device further includes a memory.
  • the communication device further includes a communication interface, and the processor is coupled to the communication interface.
  • an embodiment of the present application provides a processor, including: an input circuit, an output circuit, and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor performs the method of any one of the first to fourth aspects.
  • the above-mentioned processor may be one or more chips
  • the input circuit may be input pins
  • the output circuit may be output pins
  • the processing circuit may be transistors, gate circuits, flip-flops and various logic circuits, etc. .
  • the input signal received by the input circuit may be received and input by, for example, but not limited to, a receiver
  • the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by a transmitter
  • the circuit can be the same circuit that acts as an input circuit and an output circuit at different times.
  • the embodiments of the present application do not limit the specific implementation manners of the processor and various circuits.
  • an embodiment of the present application provides a processing apparatus, including a processor and a memory.
  • the processor is used for reading instructions stored in the memory, and can receive signals through the receiver and transmit signals through the transmitter, so as to perform the method of any one of the first to fourth aspects.
  • processors there are one or more processors and one or more memories.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor.
  • the memory can be a non-transitory memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip, or can be separately set in different On the chip, the embodiment of the present application does not limit the type of the memory and the setting manner of the memory and the processor.
  • ROM read only memory
  • sending information may be a process of outputting information from the processor
  • receiving information may be a process of receiving information by the processor.
  • the data output by the processor can be output to the transmitter, and the input data received by the processor can be from the receiver.
  • the transmitter and the receiver may be collectively referred to as a transceiver.
  • the processing device in the above eighth aspect may be one or more chips.
  • the processor in the processing device may be implemented by hardware or by software.
  • the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, implemented by reading software codes stored in a memory, which can Integrated in the processor, can be located outside the processor, independent existence.
  • an embodiment of the present application provides a computer program product, where the computer program product includes: a computer program (also referred to as code, or instruction), which, when the computer program is executed, causes a computer to execute the above-mentioned The method of any one of the first to fourth aspects.
  • a computer program also referred to as code, or instruction
  • the embodiments of the present application provide a computer-readable storage medium, where the computer-readable storage medium stores a computer program (also referred to as code, or instruction) when it runs on a computer, causing the computer to The method of any one of the first to fourth aspects above is performed.
  • a computer program also referred to as code, or instruction
  • an embodiment of the present application provides a communication system, including the foregoing first network element and a charging network element.
  • the communication system may further include an access network device.
  • a fifteenth aspect provides a chip system
  • the chip system includes a processor and an interface, and the processor is used to call and run a computer program (also referred to as code, or instruction) stored in the memory from the memory, so as to realize the first
  • a computer program also referred to as code, or instruction
  • the chip system further includes a memory, and the memory is used for saving necessary program instructions and data.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • FIGS. 2a and 2b are schematic diagrams of network slicing provided by an embodiment of the present application.
  • 3a-3e are schematic diagrams of application scenarios provided by embodiments of the present application.
  • FIG. 5 is a schematic flowchart of another information transmission method provided by an embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a communication device provided by the present application.
  • FIG. 7 is a schematic block diagram of another communication apparatus provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a chip provided by an embodiment of the present application.
  • the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: long term evolution (long term evolution, LTE) system, universal mobile telecommunication system (universal mobile telecommunication system, UMTS), fifth generation (5th generation, 5G) system, new radio (NR), and other new systems that appear with the development of technology.
  • LTE long term evolution
  • UMTS universal mobile telecommunication system
  • 5th generation, 5G fifth generation
  • NR new radio
  • the technical solutions of the embodiments of this application can be applied to various scenarios.
  • the technical solutions of the embodiments of this application can be used in a network architecture based on a service interface, or It is used in reference point-based network architecture, and can also be applied to roaming scenarios or non-roaming scenarios, etc.
  • FIG. 1a and FIG. 1b it is a 5G network architecture diagram in a non-roaming scenario provided by an embodiment of the present application.
  • Figure 1a is a 5G network architecture based on reference points in a non-roaming scenario
  • Figure 1b is a 5G network architecture based on a service interface in a non-roaming scenario.
  • FIG. 1c-FIG. 1f it is a 5G network architecture diagram in a roaming scenario provided by an embodiment of the present application.
  • Figure 1c is a 5G network architecture diagram based on a service interface in a local breakout (LBO) roaming scenario
  • Figure 1d is a reference point-based 5G network architecture diagram in an LBO roaming scenario
  • Figure 1e is a home routing (home routed) 5G network architecture diagram based on service interface in roaming scenario
  • Figure 1f is the 5G network architecture diagram based on reference point in home routing roaming scenario.
  • the access network is used to implement functions related to wireless access, and mainly includes an access network (AN) device 102.
  • the access network device includes a radio access network (RAN) device and other devices connected through an air interface. connected devices (such as WiFi).
  • the core network mainly includes the following key logical network elements: user plane function (user plane function) 103, access and mobility management function (AMF) 105, session management function (session management function) 106, policy Control function (policy control function, PCF) 107, unified data management function (unified data management) 109.
  • the system 100 may also include one or more of a user equipment (UE) 101 , a data network (DN) 104 and an application function (AF) 108 .
  • UE user equipment
  • DN data network
  • AF application function
  • the interfaces between the network elements are shown in Figure 1a. It should be understood that a service-based interface may also be used for communication between network elements.
  • Terminal devices may communicate with one or more core networks (CNs) via AN devices.
  • a terminal device may be referred to as an access terminal, terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless network device, user agent, or user equipment.
  • the 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 wireless communication capable Devices, computing devices or other devices connected to wireless modems, in-vehicle devices, wearable devices or the Internet of Things, end devices in vehicle networks, and any form of end device in future networks, etc.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • An AN device is a device that accesses a terminal device to a wireless network, and may specifically be a base station.
  • the base station may include various forms of base stations, such as: a macro base station, a micro base station (also called a small station), a relay station, an access point, and the like.
  • a macro base station such as: a macro base station, a micro base station (also called a small station), a relay station, an access point, and the like.
  • AP access point
  • WLAN wireless local area network
  • GSM global system for mobile communications
  • code division multiple access code division multiple access
  • CDMA Code Division Multiple access
  • base station base transceiver station, BTS
  • WCDMA wideband code division multiple access
  • NodeB base station
  • NB can also be an evolved base station in LTE (Evolved Node B, eNB or eNodeB), or relay station or access point, or in-vehicle devices, wearable devices, and the next generation Node B (gNB) in 5G systems or future evolution of public land mobile networks (public land mobile network, PLMN) base station in the network, etc.
  • LTE evolved Node B, eNB or eNodeB
  • gNB next generation Node B
  • 5G systems public land mobile networks
  • PLMN public land mobile network
  • UDM has functions such as managing user contract data and generating user authentication information.
  • AMF is mainly responsible for UE registration management, UE connection management, UE reachability management, UE access authorization and access authentication, UE security functions, UE mobility management, and network slice selection. , SMF selection and other functions.
  • the AMF acts as the anchor point of the N1/N2 interface signaling connection and provides the SMF with the routing of N1/N2 interface session management (session management, SM) messages, and maintains and manages the state information of the UE.
  • AMF is a mobility management network element in the 5G system.
  • SMF is mainly responsible for all control plane functions of UE session management, including UPF selection and control, network interconnection protocol (IP) address allocation and management, session quality of service (QoS) management, from PCF Obtain policy and charging control (policy and charging control, PCC) policy, etc.
  • IP network interconnection protocol
  • QoS session quality of service
  • PCC policy and charging control
  • the SMF also acts as a termination point for the SM part of a non-access stratum (NAS) message.
  • NAS non-access stratum
  • PCF has functions such as providing policy rules to control plane functional entities.
  • AF which may be an application server, may belong to an operator or a third party.
  • UPF is mainly responsible for processing user packets, such as forwarding, charging, etc., and can be used as an anchor point for protocol data unit (PDU) session connection, that is, PDU session anchor (PSA session anchor, PSA). ), responsible for UE data packet filtering, data transmission/forwarding, rate control, generation of charging information, user plane QoS processing, uplink transmission authentication, transmission level verification, downlink data packet buffering, and downlink data notification triggering, etc.
  • PDU session anchor PDU session anchor
  • the UPF can also act as a branch point for a multi-homed PDU session.
  • the DN a network that provides data transmission services for users, such as IP Multi-media service (IMS), Internet, etc.
  • the DN can include an application server (AS), which is a software framework that provides an application running environment and is used to provide applications with services such as security, data, transaction support, load balancing, and large-scale distributed system management.
  • AS application server
  • the UE obtains the application message by communicating with the AS. It should be noted that the above-mentioned AF is the control plane of the AS.
  • a communication system to which the information transmission method of the embodiment of the present application can be applied may include more or less network elements or devices.
  • the device or network element in FIG. 1a may be hardware, software divided by functions, or a combination of the above two.
  • the devices or network elements in FIG. 1a may communicate with each other through other devices or network elements.
  • Network slicing is to virtualize multiple end-to-end networks on the basis of a common hardware through slicing technology.
  • Each network has different network functions and adapts to different types of service requirements.
  • Various industries have various requirements for network functions, but these requirements can be parsed into requirements for network functions such as network bandwidth, number of connections, delay, and reliability.
  • the 5G standard also summarizes the requirements of different services for network functions into three typical scenarios, enhanced mobile broadband (eMBB) services, massive machine type communication (mMTC) services and ultra-reliable and low-latency communications (Ultra-reliable and Low Latency Communications, URLLC) services.
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communication
  • URLLC ultra-reliable and low-latency communications
  • the types of network slices corresponding to these three typical scenarios are eMBB slices, mMTC slices, and uRLLC slices.
  • FIG. 2b the schematic diagram of the 5G network slicing architecture is shown in the figure.
  • an eMBB slicing network is virtualized using the physical resources for the public Internet business, and then the smart meter reading of some manufacturers in the vertical industry is used.
  • a mMTC slicing network is virtualized by using physical resources.
  • the two slicing networks provide services for different business scenarios. Different slicing networks correspond to different physical resources, thereby realizing resource isolation between slicing networks.
  • S-NSSAI is used to identify a network slice.
  • S-NSSAI includes two parts: slice/service type (SST) and slice differentiator (SD).
  • SST refers to the expected network slicing behavior in terms of features and services.
  • the standard value range of SST is 1, 2, and 3.
  • the value 1 indicates the eMBB slice type
  • 2 indicates the URLLC slice type
  • 3 indicates the mMTC slice type.
  • SD is optional information used to supplement SST to distinguish multiple network slices of the same slice/service type.
  • the SST and SD parts are combined to represent a slice type and multiple slices of the same slice type.
  • S-NSSAI is 0x01000000, 0x02000000, and 0x03000000, which represent eMBB type slices, uRLLC type slices, and mMTC type slices, respectively.
  • the S-NSSAI values of 0x01000001 and 0x01000002 indicate eMBB type slices, serving user group 1 and user group 2 respectively, that is, identifying two specific network slices respectively.
  • the RAN node is pre-configured with a remapping policy by an operation administration and maintenance (OAM) network element.
  • OAM operation administration and maintenance
  • the granularity of the remapping policy is per network slice, that is, for each supported S-NSSAI, the RAN node is configured with a possible remapping list.
  • the remapping list includes multiple subgroups, and different subgroups can be used to identify different resource types.
  • Slice resources For example, the remapping list configured for S-NSSAI 1 is (S-NSSAI 1a, S-NSSAI 1b).
  • S-NSSAI 1a and S-NSSAI 1b can be respectively identified as slice resources of two resource types of the network slice service corresponding to S-NSSAI 1.
  • the slice resources of different subgroups can be mapped to each other, that is, when the slice resources of a certain subgroup are insufficient, the slice resources of another subgroup can be used.
  • S-NSSAI 1 as an example, if the slice resources of S-NSSAI 1a on the RAN are insufficient, part of the slice resources of S-NSSAI 1b can be used (S-NSSAI 1b still has surplus resources).
  • the resource types of sliced resources include but are not limited to shared resources (shared resources), priority resources (priortized resources) or dedicated resources (dedicated resources).
  • S-NSSAI-1a and S-NSSAI-1b are just an example of resource identifiers, which do not mean that the resource only serves S-NSSAI1.
  • the slice resource identified by S-NSSAI-1b can be the priority resource of S-NSSAI2, that is, if the slice resource identified by S-NSSAI-1b is guaranteed to be used by S-NSSAI2, if there are idle resources available for other S-NSSAI use.
  • the slice resources identified by S-NSSAI-1b may be shared resources, that is, different S-NSSAIs can use the slice resources identified by the S-NSSAI-1b, but there is no guarantee that the S-NSSAI-1b will be used when needed. - There are free resources in the slice resource identified by NSSAI-1b.
  • the resource processing methods may be different.
  • S-NSSAI1 As an example.
  • the RAN schedules the slice resources identified by S-NSSAI 1a, and the resource processing is better (for example, S-NSSAI-1a is a dedicated resource of S-NSSAI-1, and S-NSSAI-1 does not When used, it cannot be used by other S-NSSAIs); and the scheduling of slice resources identified by S-NSSAI1b is slightly worse.
  • S-NSSAI 1b slice resources to serve network slices.
  • resource processing methods may lead to differences in QoS. For example, if the resource processing is better, the network delay will be smaller, the bandwidth will be higher, and correspondingly, the user experience will be better. Different resource processing methods may also have other processing differences, such as data packet scheduling methods, etc., which will not be repeated here.
  • the bearer unit in this embodiment of the present application may refer to a transmission unit for transmitting data.
  • the bearer unit may be one of a session, a quality of service (quality of service, QoS) flow, a network slice, or a service.
  • a network slice can be associated with multiple sessions, and a session can include multiple QoS flows.
  • a session can also include multiple services.
  • a service may refer to a specific service data flow (service data flow, SDF), or may be one or more service data flows identified by a charging key (charging key). Among them, one or more service data streams identified by the same charging key are charged in the same manner.
  • the first bearing unit and the second bearing unit in the embodiment of the present application may be used to distinguish different granularities, or the granularity of the first bearing unit and the second bearing unit may be the same.
  • the first bearer unit may be the same bearer unit as the second bearer unit, for example, the first bearer unit and the second bearer unit are the same network slice.
  • the RAN in FIG. 3a-FIG. 3e may be a The RAN in the network architecture shown in Fig. 1a-Fig. 1f
  • the UE in Fig. 3a-Fig. 3e may be the UE in the network architecture shown in Fig. 1a-Fig. 1f.
  • RAN1 and RAN2 belong to the same registration area (RA).
  • RA registration area
  • the UE moves from the coverage of RAN1 to the coverage of RAN2, that is, the RAN accessed by the UE is switched from RAN1 to RAN2.
  • RAN1 and RAN2 configure slice resources of different resource types for a specific network slice (eg, network slice 1 ), for example, configure a remapping list for this network slice 1 .
  • the resource type of the slice resource scheduled by RAN1 for network slice 1 of the UE and the resource type of the slice resource scheduled by RAN2 for network slice 1 of the UE are changed.
  • RAN1 schedules resources for network slice 1 of the UE to process better slice resources, while RAN2 is congested, that is, more UEs use the slice resources of network slice 1.
  • the resource processing If the better slice resources are insufficient, the RAN2 can schedule resources for the UE's network slice 1 to handle slightly worse slice resources.
  • the resource type of slice resources of one or more sessions in network slice 1 or one or more QoS flows in network slice 1 may also change. For example, RAN2 schedules some sessions in network slice 1. Resources handle slightly less tiled resources.
  • the RAN2 determines that the resource type of the slice resource used by the first bearer unit has changed, and then notifies the AMF or SMF of the change of the resource type, and further, the AMF or SMF reports the change to the CHF or PCF for distinction Billing to achieve billing fairness.
  • the first bearer unit may be the above-mentioned network slice 1, or may be a part of the session in the network slice 1, or may be part of the QoS flow included in the session.
  • the reporting granularity may be based on the corresponding network element. Determined by subscription granularity.
  • RAN1 and RAN2 belong to different RAs, RAN1 belongs to RA1, and RAN2 belongs to RA2.
  • the UE moves, the UE moves from the coverage of RAN1 to the coverage of RAN2, that is, the RAN accessed by the UE is switched from RAN1 to RAN2.
  • the resource type of the slice resource scheduled by RAN1 for network slice 1 of the UE and the resource type of the slice resource scheduled by RAN2 for network slice 1 of the UE may change.
  • RAN2 may notify the AMF or SMF of the change of the resource type, and further, the AMF or SMF may report the change to the CHF or PCF for differential charging. For details, refer to the description of scenario 1, which is not repeated here.
  • Scenario 3 as shown in Figure 3c, RAN1 and RAN2 belong to different RAs, RAN1 belongs to RA1, RAN2 belongs to RA2, or RAN1 and RAN2 may belong to the same RA.
  • the UE moves, the UE moves from the coverage of RAN1 to the coverage of RAN2, and then from the coverage of RAN2 to the coverage of RAN1, that is, the RAN the UE accesses is switched from RAN1 to RAN2, and then from RAN2 to RAN1, optionally, if RAN1 and RAN2 belong to different RAs, scenario 3 may be a scenario of switching back to RAN1 based on scenario 2.
  • scenario 3 may be a scenario of switching back to RAN1 based on scenario 1.
  • the resource type of the slice resource scheduled by RAN2 for network slice 1 of the UE and the resource type of the slice resource scheduled by RAN1 for network slice 1 of the UE may change. For example, if RAN2 is congested, that is, there are more UEs using the slice resources of network slice 1. Among the slice resources configured by RAN2 for network slice 1, the slice resources with better resource processing are insufficient, then RAN2 can schedule the network slice 1 of the UE. Resources handle slightly less tiled resources. However, the RAN1 is not congested, even if there are fewer UEs using the slice resources of the network slice 1, the RAN1 can schedule resources for the network slice 1 to process more optimal slice resources.
  • resource type of slice resources of one or more sessions in network slice 1 or one or more QoS flows in network slice 1 may also change.
  • RAN1 schedules some sessions in network slice 1.
  • Resource handles better sliced resources.
  • the AMF or SMF when RAN1 determines that the resource type of the slice resource used by the first bearer unit has changed, the AMF or SMF is notified of the change of the resource type, and further, the AMF or SMF reports the change to the CHF or PCF for distinction. Billing to achieve billing fairness.
  • the first bearer unit may be the above-mentioned network slice 1, or may be a part of the session in the network slice 1, or may be part of the QoS flow included in the session.
  • the reporting granularity may be based on the corresponding network element. Determined by subscription granularity.
  • RAN1 and RAN2 are the master station and slave station in a dual-connectivity (DC) scenario
  • RAN2 (slave station) is the resource type of the slice resource scheduled by the UE's network slice 1 subject to change.
  • RAN2 may change from non-congested to congested, that is, when RAN2 is not congested, it schedules resources for the UE's network slice 1 to handle better slice resources, while when RAN2 is relatively congested, that is, UEs using network slice 1's slice resources More, RAN2 can schedule resources for the UE's network slice 1 to handle slightly worse slice resources.
  • the resource type of slice resources of one or more sessions in network slice 1 or one or more QoS flows in network slice 1 may also change.
  • RAN2 schedules some sessions in network slice 1. Resources handle slightly less tiled resources. It should be noted that RAN2 may also change from congested to non-congested. When RAN2 is congested, RAN2 can schedule resources for the UE's network slice 1 to handle slightly worse slice resources, and when RAN2 is not congested, RAN2 is the UE's network slice. Network slice 1 schedules resources to handle more optimal slice resources.
  • the RAN2 determines that the resource type of the slice resource used by the first bearer unit has changed, and then notifies the AMF or SMF of the change of the resource type, and further, the AMF or SMF reports the change to the CHF or PCF for distinction Billing to achieve billing fairness.
  • the first bearer unit may be the above-mentioned network slice 1, or may be a part of the session in the network slice 1, or may be part of the QoS flow included in the session.
  • the reporting granularity may be based on the corresponding network element. Determined by subscription granularity.
  • the UE accesses RAN1, and the UE is in a non-mobile scenario, and the resource type of the slice resource scheduled by RAN1 for the UE's network slice 1 may change.
  • RAN1 may change from non-congested to congested, or from non-congested to congested, and the resource type of the slice resource scheduled by RAN1 for network slice 1 of UE1 may change.
  • RAN1 can schedule resources for network slice 1 of the UE to handle better slice resources
  • RAN1 can schedule resources for network slice 1 of the UE to handle slightly worse slice resources.
  • the resource type of slice resources of one or more sessions in network slice 1 or one or more QoS flows in network slice 1 may also change. For example, RAN1 schedules some sessions in network slice 1. Resources handle slightly less tiled resources.
  • the AMF or SMF when RAN1 determines that the resource type of the slice resource used by the first bearer unit has changed, the AMF or SMF is notified of the change of the resource type, and further, the AMF or SMF reports the change to the CHF or PCF for distinction. Billing to achieve billing fairness.
  • the first bearer unit may be the above-mentioned network slice 1, or may be a part of the session in the network slice 1, or may be part of the QoS flow included in the session.
  • the reporting granularity may be based on the corresponding network element. Determined by subscription granularity.
  • the access network device may determine that the resource type of the slice resource used by the first bearer unit is changed, and the The change of the resource type is notified to the first network element, which is further reported by the first network element to the charging network element for charging at the granularity of the second bearer unit.
  • FIG. 5 may show that in a handover scenario, the first access network device and the second access network device report resource status information to the first network element, respectively, and the first network element is based on the first access network device and the second access network device.
  • the resource status information reported by the network device determines that the resource type of the slice resource used by the first bearer unit has changed, and the change of the resource type is notified to the first network element, which is further reported by the first network element with the granularity of the second bearer unit.
  • Charge the billing network element Exemplarily, in the embodiments shown in FIG. 4 and FIG. 5 , the first network element may be AMF or SMF, and the charging network element may be CHF or PCF. The specific steps of the embodiments shown in FIG. 4 and FIG. 5 are respectively introduced below.
  • FIG. 4 is a schematic flowchart of an information transmission method according to an embodiment of the present application
  • FIGS. 1 a to 1 e may be examples of network architectures to which the information transmission method is applied.
  • 3a to 3e may be examples of scenarios to which the information transmission method is applied.
  • the method may include: S102-S106, and optionally, may further include one or both of a subscription process and a handover process.
  • the subscription process may include S100 and S101, and the handover process may include S10 and S11.
  • the execution sequence of each step is not limited in this embodiment of the present application.
  • the information transmission method of the embodiment of the present application includes but is not limited to the following steps:
  • the charging network element sends first indication information to the first network element.
  • the charging network element may subscribe the first network element to the resource type change event of the second bearer unit.
  • the charging network element sends the first indication information to the first network element, where the first indication information can be used to indicate that the first network element changes when the resource type of the slice resource used by the second bearer unit changes, Send slice resource information to the charging network element; or, the first indication information may be used to instruct the charging network element to subscribe the second bearer unit to the first network element; or, the first indication information may be used to indicate that the second bearer When the resource type of the slice resource used by the unit changes, it needs to be reported to the charging network element; or the first indication information can be used to indicate to the first network element when the resource type of the slice resource used by the second bearer unit changes Notify the charging network element.
  • the first indication information may be sent to the first network element through a subscription request.
  • the charging network element may simultaneously send the second bearer unit identifier (such as S-NSSAI, QoS flow identifier, service data flow template, PDU session identifier, etc.) and the first indication information, representing the second bearer unit's identifier.
  • the first indication information may be an indication used to indicate that the resource type is changed to be reported. It can be understood that, the identifier of the second bearing unit may also be in the first indication information, which is not limited in this application.
  • the granularity of the second bearer unit may be network slice granularity, that is, when the resource type of the slice resource used by one or more network slices changes, it needs to be reported to the charging network element; the granularity of the second bearer unit is also It can be session granularity, that is, when the resource type of slice resources used by one or more sessions changes, it needs to be reported to the charging network element; the granularity of the second bearer unit can also be QoS flow granularity, that is, when a certain or When the resource type of the slice resources used by multiple QoS flows changes, it needs to be reported to the charging network element; optionally, the granularity of the second bearer unit may also be the service granularity, for example, if the first network element is SMF, the second The granularity of the second bearer unit may be the service granularity, that is, when the resource type of the slice resource used by one or more services changes, it needs to be reported to the charging network element.
  • the second bearing unit may also be of other granularity, which is not limited in this application.
  • the first network element is an AMF network element
  • the second bearer unit may be one of a session or a network slice.
  • the first network element is an SMF network element
  • the second bearer unit may be one of a network slice, a session, a QoS flow or a service.
  • the service granularity may refer to a specific SDF, or may be one or more service data streams identified by a charging key. Generally, the charging processing methods of the service data streams identified by the same charging key are the same.
  • the CHF may also subscribe to the first network element through the PCF. For example, the CHF subscribes to the PCF for resource type change events. After receiving the subscription, the PCF subscribes the resource type change event of the second bearer unit to the first network element.
  • the granularity of the subscription of the CHF to the PCF and the granularity of the subscription of the PCF to the first network element may be the same or different.
  • the SMF can bind the service data flow with subscription requirements to the same QoS flow. , that is, SMF binds service data streams with different subscription requirements (such as those with and without subscription requirements, or the specific content of subscriptions are different, etc.) to different QoS streams.
  • the processing rules are the same, and the processing rules include the same way of changing resource types of service data flows belonging to the same QoS flow.
  • the PCF can send the policy and charging control (policy and charging control, PCC) rules carrying the binding parameters to the SMF, and the PCC rules have a corresponding relationship with the service data flow.
  • policy and charging control policy and charging control
  • PCC policy and charging control
  • the above-mentioned first indication information may also be sent to the SMF through a PCC rule, and optionally, the above-mentioned first indication information may be used as a binding parameter.
  • the SMF After the SMF receives the PCC rule, when the binding parameters in the PCC rule are exactly the same as the binding parameters of the current QoS flow, the SMF binds the PCC rule to the QoS flow, that is, the service data flow corresponding to the PCC rule is bound by the SMF. Bind to this QoS flow.
  • SMF can create a new QoS flow according to the binding parameters in the PCC rule, and bind the PCC rule to the new QoS flow.
  • the binding parameter in the PCC rule is the same as the binding parameter of the current QoS flow, which may mean that the indication information in the PCC rule is the same as the one bound to the current QoS flow.
  • the indication information in other PCC rules of the QoS flow is the same, that is, the SMF binds all PCC rules with the same indication information to the same QoS flow.
  • the SMF may send second indication information to the first access network device, where the second indication information may be used to indicate that the QoS flow needs to be reported when the resource type of the QoS flow changes.
  • a first network element sends second indication information to a first access network device in response to the first indication information.
  • the first network element may subscribe to the first access network device for the resource type change event of the first bearer unit. That is, after receiving the first indication information of the charging network element, the first network element sends second indication information to the first access network device in response to the first indication information.
  • the second indication information may also be called slice resources Information change reporting indication, the second indication information can be used to instruct the first access network device to notify the first network element when the resource type of the slice resource used by the first bearer unit changes; or, the second indication The information may be used to instruct the first network element to subscribe the first bearer unit to the first access network device.
  • the first network element may send the first bearer unit identifier (such as S-NSSAI, QoS flow identifier, service data flow template, PDU session identifier, etc.) and second indication information at the same time, representing the first bearer unit's identifier.
  • the second indication information may be an indication used to indicate that the resource type is changed to be reported. It can be understood that, the first bearing unit identifier may also be in the second indication information, which is not limited in this application.
  • the granularity of the first bearer unit may be network slice granularity, that is, when the resource type of the slice resource used by one or more network slices changes, it needs to be reported to the first network element; the granularity of the second bearer unit is also It can be session granularity, that is, when the resource type of slice resources used by one or more sessions changes, it needs to be reported to the first network element; the granularity of the second bearer unit can also be QoS flow granularity, that is, when a certain or When the resource type of the slice resource used by the multiple QoS flows changes, it needs to be reported to the first network element. It can be understood that, the first bearing unit may also be of other granularity, which is not limited in this application.
  • the granularity of the first bearing unit and the granularity of the second bearing unit may be the same or different. If the granularity of the first bearer unit is the same as the granularity of the second bearer unit, the first bearer unit and the second bearer unit may be the same, for example, the charging network element may indicate to the first network element the slice resources used in network slice 1 When the resource type of the network slice 1 changes, the charging network element is notified, and the first network element may indicate to the first access network device that the resource type of the slice resource used by the network slice 1 changes to notify the first network element. .
  • the first bearing unit may be a subset of the second bearing unit, or the second bearing unit may be a subset of the first bearing unit.
  • the second bearer unit may be network slice 1
  • the first bearer unit may be a session in network slice 1, that is, the first bearer unit is a subset of the second bearer unit
  • the charging network element may indicate to the first network element
  • the second bearer unit is a subset of the first bearer unit.
  • the resources of the slice resources used by all bearer units included in the first bearer unit The types may all be the same, or the resource types of the slice resources used by all the bearer units included in the first bearer unit may be changed.
  • the charging network element completes the subscription of the resource type change event of the second bearer unit to the first network element, and the first network element completes the resource type change event of the first bearer unit to the first access network device. subscription.
  • the first access network device may be an access network device to which the terminal device is connected.
  • the subscription event (including the subscribed bearer unit) of the first network element to the first access network device can be used as The context is transferred to the switched access network device, or the subscription event may not be delivered, but the first network element re-subscribes the resource type change event to the switched access network device.
  • the process in which the first network element subscribes to the first access network device that is, as shown in step S101).
  • the subscription event (including the subscribed bearer unit) of the charging network element to the first network element can also be passed as a context to the first network element after the switch.
  • the subscription event may not be delivered, but the charging network element subscribes the resource type change event to the switched first network element again.
  • the charging network element subscribes to the first network element in the foregoing embodiment. process (that is, as shown in step S100).
  • the first access network device determines that the resource type of the slice resource used by the first bearer unit changes.
  • the first network element subscribes the resource type change event of the first bearer unit to the first access network device.
  • the first bearer unit may be a network slice, or may also be a session in a network slice, or may also be a QoS flow of a session in a network slice, or the like.
  • the OAM may pre-configure slice resources of multiple resource types for the network slice service in the first access network device.
  • a remapping list is configured in the first access network device, and the remapping list includes multiple subgroups, and different subgroups can be used to identify slice resources of different resource types.
  • S-NSSAI 1 identifies network slice 1
  • the remap list configured for S-NSSAI 1 is (S-NSSAI 1a, S-NSSAI 1b).
  • S-NSSAI 1a and S-NSSAI 1b can respectively identify slice resources of two resource types served by network slice 1.
  • the slice resources corresponding to S-NSSAI 1a are priority resources
  • the slice resources corresponding to S-NSSAI 1b are shared resources.
  • the first access network device may schedule slice resources of different resource types corresponding to the network slice for different sessions in the network slice.
  • the first access network device may also Schedule slice resources of the same resource type for different sessions within a network slice.
  • the first access network device may also schedule slice resources of different resource types for different QoS flows in the same session, or, in the case that slice resources of a certain resource type are sufficient, the first access network device may also be Different QoS flows schedule slice resources of the same resource type. It can be understood that the first access network device may schedule resources for sessions or QoS flows in the network slice preferentially to process slice resources of a resource type with better resource processing.
  • Slice resources of lesser resource handling resource types can be scheduled to sessions or QoS flows within a network slice.
  • the following uses the session granularity as an example to illustrate the resource status diagram of the first access network device scheduling slice resources for sessions in the network slice. As shown in Table 1, the first access network device schedules the slice resources corresponding to S-NSSAI 1a for session 1 , schedule the slice resource corresponding to S-NSSAI 1b for session 2.
  • the first access network device may also maintain context of other granularities, such as QoS flow identifier and corresponding slice resource status, or S-NSSAI. and the corresponding slice resource status.
  • the method for determining that the resource type of the slice resource used by the first bearer unit is changed by the first access network device may include, but is not limited to, the following two optional implementation manners:
  • the state transition of the first access network device causes the resource type of the slice resource used by the first bearer unit to change.
  • the first access network device accessed by the terminal device may be converted from a congested state to a non-congested state.
  • the number of terminal devices changes from more to less, and the resource type of the slice resource scheduled by the first bearer unit of the first access network device may change.
  • the first access network device is the first bearer of the terminal device.
  • the slice resource scheduled by the unit may be switched from the slice resource with slightly poor resource processing to the slice resource with better resource processing.
  • the first access network device accessed by the terminal device may be converted from a non-congested state to a congested state.
  • the number of terminal devices changes from a small number to a large number, and the resource type of the slice resources scheduled by the first bearer unit of the first access network device for the terminal device may change.
  • the first access network device is the first bearer of the terminal device.
  • the slice resource scheduled by the unit may be switched from a slice resource with better resource processing to a slice resource with slightly poor resource processing.
  • the above-mentioned first bearer unit may be a network slice, or may be a session in a network slice, or may also be a QoS flow of a session in a network slice, or the like. It should be noted that, if the first bearer unit is a network slice, the change of the resource type of the slice resource used by the network slice may mean that there is a session or QoS flow whose resource type is changed in the network slice.
  • the switching of the access network device through which the user plane connection of the first bearer unit passes is switched from the second access network device to the first access network device, resulting in the change of slice resources used by the first bearer unit.
  • the resource type has changed.
  • the terminal device moves from the coverage of the second access network device to the coverage of the first access network device, that is, The access network device accessed by the terminal device is switched from the second access network device to the first access network device.
  • the access network device through which the user plane of the first bearer unit of the terminal device is connected is The second access network device is switched to the first access network device.
  • the resource type of the slice resource scheduled by the second access network device for the first bearer unit of the terminal device may be different from the resource type of the slice resource scheduled by the first access network device for the first bearer unit of the terminal device.
  • the second access network device may change the resource type of the slice resource corresponding to the first bearer unit.
  • the resource type of the slice resource is sent to the first access network device, so that the first access network device can determine whether the resource type of the slice resource scheduled for the first bearer unit of the terminal device has changed.
  • the first access network device receives the resource type of the slice resource corresponding to the first bearer unit from the second access network device.
  • the second access network device may send the resource type of the slice resource corresponding to the first bearer unit to the first access network device through the context, where the resource type of the slice resource corresponding to the first bearer unit is the resource type of the slice resource corresponding to the first bearer unit.
  • the network access device is the resource type of the slice resource scheduled by the first bearer unit.
  • the first bearer unit may be a bearer unit subscribed by the first network element to the second access network device. It can be understood that, the first network element can subscribe the second access network device to one or more first bearer units associated with one or more network slices, and then the second access network device can subscribe to the first access network device.
  • the device sends the resource type of the slice resources corresponding to one or more first bearer units associated with one or more network slices.
  • the first bearer unit is used as an example for the following description.
  • the second connection A context example of the resource type of the slice resource scheduled by the network access device for each session, wherein S-NSSAI 2 identifies network slice 2, and the second access network device schedules the corresponding S-NSSAI 2a for session 3 in network slice 2 Slice resources:
  • the second access network device may also maintain context of other granularities, such as QoS flow identifier and corresponding slice resource status, or S-NSSAI. and the corresponding slice resource status.
  • the second access network device may transfer the context to the first access network device through the Xn interface; or, the second access network device may transfer the context to the first access network device via the core network (such as AMF). access equipment.
  • the core network such as AMF
  • the first access network device determines the resource type of the slice resource scheduled by the first access network device for the first bearer unit.
  • the first access network device may determine the resource type of the slice resource scheduled for the first bearer unit according to the congestion state of the first access network device. Exemplarily, if the number of terminal devices accessing the first access network device and using the network slice (for example, network slice 1) is relatively large, the first access network device schedules resources for the first bearer unit to process a bit. poor slicing resources; if the number of terminal devices accessing the first access network device and using the network slicing is relatively small, and the slicing resources with better resource processing are sufficient, the first bearer unit can be scheduled for better resource processing slice resource.
  • the network slice for example, network slice 1
  • the first access network device may be based on the resource type of the slice resource scheduled by the second access network device for the first bearer unit and the resource type of the slice resource scheduled by the first access network device for the first bearer unit. Resource type, to determine whether the resource type of the slice resource used by the first bearer unit has changed.
  • the first access network device notifies the first network element in response to a change in the resource type of the slice resource used by the first bearer unit.
  • the first access network device determines that the resource type of the slice resource used by the first bearer unit has changed, and notifies the first network element. Specifically, the first access network device may notify the first network element in various ways. For example, the first access network device may send first information to the first network element. Optionally, the first information may be The resource type used to indicate the slice resource used by the first bearer unit changes. For example, the resource types corresponding to network slices include two types. If the resource type of the slice resource initially used by the first bearer unit is known, the first access The network device may indicate to the first network element that the resource type is changed, and the first network element may obtain the changed resource type of the slice resource used by the first bearer unit.
  • the first information may be used to indicate the changed resource type of the slice resource used by the first bearer unit.
  • the first access network The device indicates to the first network element the resource type of the slice resource used by the changed first bearer unit.
  • the first information can also be used to indicate the resource type of the slice resource used in each time period, for example, the resource type used on January 1, 2020 from 10:00-11:00 is S-NSSAI 1a , the resource type used from 11:00-11:30 on January 1, 2020 is S-NSSAI 1b, and the resource type used from 11:00-12:30 on January 1, 2020 is S-NSSAI 1c.
  • the first network element may instruct the first access network device to report to the first network element when a certain resource type changes. For example, when switching from another resource type to the subscribed resource type, the first access network device reports to the first network element, or when switching from the subscribed resource type to another resource type, the first access network device The device is then reported to the first network element.
  • the first access network device may determine that the number of sessions or QoS flows in which the resource type is changed in the network slice is between the number of all sessions or QoS flows included in the network slice and report the ratio to the first network element, so as to report the resource type change information of the network slice at the granularity of the network slice.
  • the granularity of the bearer unit in the context sent by the second access network device to the first access network device is the same as that notified by the first access network device.
  • the granularity of the bearer units for the first network element may be the same or different. If the two granularities are different, the first access network device may further determine whether the resource type corresponding to the bearer unit reported to the first network element has changed according to the resource type corresponding to the bearer unit in the context. For example, the first network element instructs the access network device (the first access network device and/or the second access network device) to report when the resource type of the slice resource used by the network slice 1 changes.
  • the second access network device may send the resource type corresponding to each session in all sessions included in the network slice 1 as a context to the first access network device, and the first access network device may further use the received data of each session according to The corresponding resource type and the resource type of the slice resource scheduled by the first access network device for each session determine whether the slice resource type used by the network slice 1 has changed, so as to report to the first network element with network slice granularity.
  • the above-mentioned first bearer unit may be the bearer unit indicated in the second indication information in step S101, therefore, the first access network device may notify the first access network device of the first bearer according to the second indication information
  • the resource type of the tile resource used by the cell has changed.
  • the first network element receives a notification from the first access network device, and determines, according to the notification, that the resource type of the slice resource used by the first bearer unit has changed.
  • the first access network device notifies the first network element that the type of the slice resource used by the first bearer unit has changed, so that the first network element can determine the resource of the slice resource used by the first bearer unit according to the notification Type changes.
  • the first network element sends slice resource information to the charging network element in response to a change in the resource type of the slice resource used by the first bearer unit.
  • the first network element may notify the charging network element of the change in the resource type of the slice resource used by the second bearer unit in response to the change of the resource type of the slice resource used by the first bearer unit.
  • the second bearer unit may be the bearer unit indicated in the first indication information in step S100. Therefore, the first network element may notify the charging network element of the slice used by the second bearer unit according to the first indication information The resource type of the resource has changed.
  • the second bearer unit may be the same as the first bearer unit, that is, the granularity reported by the first access network device to the first network element is the same as the granularity reported by the first network element to the charging network element, for example, the first The access network device notifies the first network element that the resource type of the slice resource used by the session 1 changes, and the first network element notifies the charging network element that the resource type of the slice resource used by the session 1 changes.
  • the second bearer unit may be a subset of the first bearer unit, that is, the granularity reported by the first access network device to the first network element is larger than the granularity reported by the first network element to the charging network element, for example, the One network element is an SMF, the first access network device notifies the SMF that the resource type of the slice resource used by session 1 has changed, and the SMF notifies the charging network element that the resource type of the slice resource used by the service 1 in the session 1 has changed.
  • the resource types of slice resources used by all bearer units in the first bearer unit may be the same, that is, the resource types of slice resources used by all services in session 1 are the same.
  • the first bearer unit may be a subset of the second bearer unit, that is, the granularity reported by the first access network device to the first network element is smaller than the granularity reported by the first network element to the charging network element, for example, the first A network element is an AMF, the first access network device notifies the AMF that the resource types of the slice resources used by session 1 and session 2 in the network slice have changed, and the number of all sessions included in the network slice is 3, then the AMF determines that the network The resource type of the slice resources used by 2/3 of the sessions in the slice changes. Further, the AMF notifies the charging network element that the resource type of the slice resources used by the 2/3 sessions in the network slice changes, so that the AMF uses the network slice granularity. Notify the charging network element that the resource type has changed.
  • the first A network element is an AMF
  • the first access network device notifies the AMF that the resource types of the slice resources used by session 1 and session 2 in the network slice have changed, and the number of all sessions included
  • the first network element sends slice resource information to the charging network element, where the slice resource information may be used to indicate that the resource type of the slice resource used by the second bearer unit has changed.
  • the resource type corresponding to the network slice includes two types. If the resource type of the slice resource initially used by the second bearer unit is known, the first network element can indicate to the charging network element that the resource type has changed, and the charging network element can obtain the changed use of the second bearer unit.
  • the resource type of the sliced resource may also be used to indicate the resource type of the slice resource used by the second bearer unit after the change.
  • the first network element For example, when the resource type of the slice resource used by the second bearer unit changes, the first network element The resource type of the slice resource used by the changed second bearer unit is indicated to the charging network element.
  • the slice resource information can also be used to indicate the resource type of the slice resource used by the second bearer unit in each time period.
  • the resource type used is S-NSSAI 1a at 11:00-11:30 on January 1, 2020
  • the resource type used by the second bearer unit is S-NSSAI 1b at 11:00-11 January 2020 At 12:30
  • the resource type used by the second bearer unit is S-NSSAI 1c.
  • the charging network element may instruct the first network element to report to the charging network element when a certain resource type changes. For example, when switching from other resource types to the subscribed resource type, the first network element reports to the billing network element, or when switching from the subscribed resource type to other resource types, the first network element reports to the billing network element. Billing network element.
  • the first network element may determine the ratio of the number of sessions or QoS flows whose resource types are changed in the network slice to the number of all sessions or QoS flows contained in the network slice , and send slice resource information to the charging network element, where the slice resource information includes the ratio, and may further include the resource type after switching of the network slice, so that the first network element reports the resource type of the network slice at the network slice granularity Change information.
  • the charging network element receives the slice resource information from the first network element, and determines, for the second bearer unit, a charging processing manner corresponding to the changed resource type of the slice resource used by the second bearer unit.
  • the charging network element may determine, according to the slice resource information, the resource type of the slice resource used by the changed second bearer unit.
  • the charging network element knows the slice initially used by the second bearer unit.
  • the resource type of the resource For example, the resource type of the slice resource initially used by the second bearer unit is the default configuration.
  • the charging network element can determine the difference between the slice resource and the changed slice resource used by the second bearer unit. resource type, so as to determine the charging processing method corresponding to the resource type of the slice resource used by the changed second bearer unit.
  • the charging network element may obtain the changed resource type of the slice resource used by the second bearer unit according to the slice resource information, A charging processing manner corresponding to the resource type of the slice resource used by the changed second bearer unit is further determined.
  • the charging processing manner corresponding to the resource type after the change may be different from the charging processing manner corresponding to the resource type before the change, or may be the same.
  • FIG. 5 is a schematic flowchart of another information transmission method provided by an embodiment of the present application
  • FIGS. 1 a to 1 e may be examples of network architectures to which the information transmission method is applied.
  • Figures 3a to 3c may be examples of scenarios in which the information transmission method is applied.
  • the method may include: S200-S204.
  • the execution sequence of each step is not limited in this embodiment of the present application.
  • the information transmission method of the embodiment of the present application includes but is not limited to the following steps:
  • the first access network device sends first resource status information to the first network element.
  • the second access network device sends second resource status information to the first network element.
  • the charging network element may send first indication information to the first network element, where the first indication information is used to indicate the slice resource used by the first network element in the second bearer unit.
  • the charging network element is notified when the resource type changes.
  • the first network element sends second indication information to the first access network device accessed by the terminal device, where the second indication information is used to indicate that the first access network device is in the first bearer unit
  • the first network element is notified when the resource type of the used slice resource changes.
  • the terminal device moves from the coverage area of the first access network device to the coverage area of the second access network device, that is, the access area accessed by the terminal device
  • the network device is switched from the first access network device to the second access network device.
  • the access network device through which the user plane connection of the first bearer unit of the terminal device passes is switched from the first access network device to the second access network device.
  • the first access network device may transmit the resource type change event of the first bearer unit subscribed by the first network element to the first access network device to the second access network device, or the first network element The resource type change event of the first bearer unit may be subscribed to the second access network device.
  • the resource type of the slice resource scheduled by the first access network device for the first bearer unit of the terminal device may be different from the resource type of the slice resource scheduled by the second access network device for the first bearer unit of the terminal device.
  • the first access network device sends first resource status information to the first network element, the first resource The status information is used to indicate the resource type of the slice resource scheduled by the first access network device for the first bearer unit.
  • the second access network device sends second resource state information to the first network element, where the second resource state information is used to indicate the resource type of the slice resource scheduled by the second access network device for the first bearer unit.
  • the first access network device and the second access network device may send resource status information to the first network element in a handover scenario.
  • the first bearer unit may be one of a network slice, a session or a QoS flow.
  • the first bearer unit may be a bearer unit subscribed by the first network element to the access network device (the first access network device and/or the second access network device).
  • the first network element determines, according to the first resource state information and the second resource state information, that the resource type of the slice resource used by the first bearer unit has changed.
  • the first network element may compare the resource type of the slice resource scheduled by the first access network device for the first bearer unit of the terminal device with the resource type of the slice resource scheduled by the second access network device for the first bearer unit of the terminal device Whether the resource types of the slice resources are the same, so as to determine whether the resource type of the slice resources used by the first bearer unit has changed.
  • the first resource state information may be stored in the first network element, and the two are compared when the second resource state information is received.
  • the first network element in response to the change of the resource type of the slice resource used by the first bearer unit, the first network element sends slice resource information to the charging network element.
  • the charging network element receives the slice resource information from the first network element, and determines, for the second bearer unit, a charging processing manner corresponding to the changed resource type of the slice resource used by the second bearer unit.
  • step S203 and step S204 may refer to the description of step S105 and step S106 in the embodiment of FIG. 4 , which will not be repeated here.
  • the access network device, the first network element, and the charging network element include hardware structures and/or software modules corresponding to executing each function.
  • the units and method steps of each example described in conjunction with the embodiments disclosed in the present application can be implemented in the form of hardware, software, or a combination of hardware and software. Whether a function is performed by hardware, software, or computer software-driven hardware depends on the specific application scenarios and design constraints of the technical solution.
  • FIG. 6 is a schematic block diagram of a communication apparatus provided by an embodiment of the present application.
  • the communication device 10 may include a processing unit 11 and a transceiver unit 12 .
  • the processing unit 11 and the transceiver unit 12 may be software, hardware, or a combination of software and hardware.
  • the transceiver unit 12 may include a sending unit and a receiving unit, the sending unit is used to implement the sending function, the receiving unit is used to implement the receiving function, and the transceiver unit 12 may implement the sending function and/or the receiving function.
  • the transceiver unit can also be described as a communication unit.
  • the transceiver unit 12 may be configured to receive information sent by other devices, and may also be configured to send information to other devices.
  • the processing unit 11 may be used to perform internal processing of the device.
  • the communication apparatus 10 may correspond to the first access network device in the above method embodiment, for example, the communication apparatus 10 may be the first access network device or the first access network device chip in the device.
  • the communication apparatus 10 may include a unit for performing operations performed by the first access network device in the above method embodiments, and each unit in the communication apparatus 10 is respectively used to implement the above method embodiments by the first access network device. The operation performed by the networked device.
  • the processing unit 11 is configured to determine that the resource type of the slice resource used by the first bearer unit has changed;
  • the transceiver unit 12 is configured to notify the first network element in response to a change in the resource type of the slice resource used by the first bearer unit.
  • the processing unit 11 is configured to determine that the access network device through which the user plane connection of the first bearer unit passes is switched.
  • the first access network device may be the access network device through which the user plane connection of the first bearer unit passes before the handover, that is, the source access network device, or the first access network device may also be the handover After that, the access network device through which the user plane of the first bearer unit is connected, that is, the target access network device.
  • the transceiver unit 12 is configured to send resource status information to the first network element, where the resource status information is used to indicate that the first access network device is the first access network device.
  • the resource type of the slice resource scheduled by the first bearer unit is configured to send resource status information to the first network element.
  • the communication device 10 may correspond to the first network element, or may be a chip in the first network element.
  • the communication apparatus 10 may include a unit for performing the operations performed by the first network element in the above method embodiments, and each unit in the communication apparatus 10 is respectively configured to implement the operations performed by the first network element in the above method embodiments. action performed.
  • the processing unit 11 is configured to determine that the resource type of the slice resource used by the first bearer unit has changed;
  • the transceiver unit 12 is configured to, in response to a change in the resource type of the slice resource used by the first bearer unit, send slice resource information to the charging network element, where the slice resource information is used to indicate the slice resource used by the second bearer unit The resource type of the resource is changed, or the slice resource information indicates the resource type of the slice resource used by the second bearer unit after the change;
  • the first bearing unit is a subset of the second bearing unit, or the second bearing unit is a subset of the first bearing unit, or the first bearing unit and the second bearing unit
  • the carrying unit is the same.
  • the communication device 10 may correspond to a charging network element, or may be a chip in the charging network element.
  • the communication apparatus 10 may include a unit for performing the operations performed by the charging network element in the above method embodiments, and each unit in the communication apparatus 10 is respectively configured to implement the operations performed by the charging network element in the above method embodiments. action performed.
  • the transceiver unit 12 is configured to receive slice resource information from the first network element, where the slice resource information is used to indicate that the resource type of the slice resource used by the first bearer unit changes, or the slice resource information indicates that the resource type of the slice resource used by the changed first bearer unit;
  • the processing unit 11 is configured to determine, for the first bearer unit, a charging processing manner corresponding to the changed resource type of the slice resource used by the first bearer unit.
  • the transceiver unit 12 in the communication apparatus 10 may be an input/output interface.
  • the transceiver unit 12 in the communication device 10 may correspond to the communication interface 21 shown in FIG. 7
  • the processing unit 11 may correspond to the processor 22 shown in FIG. 7 .
  • FIG. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application. It should be understood that the communication apparatus 20 shown in FIG. 7 is only an example, and the communication apparatus in this embodiment of the present application may further include other components, or include components with functions similar to those of the respective components in FIG. All parts.
  • the communication device 20 includes a communication interface 21 and at least one processor 22 .
  • the communication apparatus 20 may correspond to any one of the first access network equipment, the first network element or the charging network element.
  • the communication interface 21 is used to send and receive signals, and at least one processor 22 executes program instructions, so that the communication device 20 implements the corresponding process of the method executed by the corresponding network element in the above method embodiments.
  • the communication apparatus 20 may correspond to the first access network device in the foregoing method embodiment, for example, the communication apparatus 20 may be the first access network device or the first access network device chip in the device.
  • the communication apparatus 20 may include components for performing the operations performed by the first access network device in the above method embodiments, and each component in the communication apparatus 10 is respectively in order to implement the above method embodiments by the first access network device. The operation performed by the networked device.
  • the processor 22 is configured to determine that the resource type of the slice resource used by the first bearer unit changes
  • the communication interface 21 is configured to notify the first network element in response to a change in the resource type of the slice resource used by the first bearer unit.
  • the processor 22 is configured to determine that the access network device through which the user plane connection of the first bearer unit passes is switched.
  • the first access network device may be the access network device through which the user plane connection of the first bearer unit passes before the handover, that is, the source access network device, or the first access network device may also be the handover After that, the access network device through which the user plane of the first bearer unit is connected, that is, the target access network device.
  • the communication interface 21 is configured to send resource status information to the first network element, where the resource status information is used to indicate that the first access network device is the The resource type of the slice resource scheduled by the first bearer unit.
  • the communication device 20 may correspond to the first network element, or may be a chip in the first network element.
  • the communication apparatus 20 may include components for performing the operations performed by the first network element in the above method embodiments, and each component in the communication apparatus 10 is respectively used to implement the above method embodiments performed by the first network element. action performed.
  • the processor 22 is configured to determine that the resource type of the slice resource used by the first bearer unit has changed
  • the communication interface 21 is configured to send slice resource information to the charging network element in response to a change in the resource type of the slice resource used by the first bearer unit, where the slice resource information is used to indicate the slice resource used by the second bearer unit The resource type of the resource is changed, or the slice resource information indicates the resource type of the slice resource used by the second bearer unit after the change;
  • the first bearing unit is a subset of the second bearing unit, or the second bearing unit is a subset of the first bearing unit, or the first bearing unit and the second bearing unit
  • the carrying unit is the same.
  • the communication device 20 may correspond to a charging network element, or may be a chip in the charging network element.
  • the communication device 20 may include components for performing the operations performed by the charging network element in the above method embodiments, and each component in the communication device 10 is designed to implement the operations performed by the charging network element in the above method embodiments, respectively. action performed.
  • the communication interface 21 is configured to receive slice resource information from the first network element, where the slice resource information is used to indicate that the resource type of the slice resource used by the first bearer unit has changed, or the slice resource information indicates that the resource type of the slice resource used by the changed first bearer unit;
  • the processor 22 is configured to determine, for the first bearer unit, a charging processing manner corresponding to the changed resource type of the slice resource used by the first bearer unit.
  • the communication device 20 may also include a memory.
  • the memory may store program instructions, and at least one processor 22 may read the program instructions stored in the memory and execute the program instructions.
  • the communication device may be a chip or a chip system
  • the chip 30 shown in FIG. 8 includes a processor 31 and an interface 32 .
  • the number of processors 31 may be one or more, and the number of interfaces 32 may be multiple. It should be noted that the respective functions of the processor 31 and the interface 32 can be implemented by hardware design, software design, or a combination of software and hardware, which is not limited here.
  • the chip may further include a memory 33 for storing necessary program instructions and data.
  • the processor 31 may be configured to call the information transmission method provided by one or more embodiments of this application from the memory to one or more devices in the first access network device, the first network element or the charging network element or the implementation program of the network element, and execute the instructions contained in the program.
  • the interface 32 can be used to output the execution result of the processor 31 .
  • the interface 32 may be specifically used to output various messages or information of the processor 31 .
  • the processor in this embodiment of the present application may be a central processing unit (Central Processing Unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), application specific integrated circuits (application specific integrated circuits) integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code runs on a computer, the computer is made to execute any of the foregoing method embodiments The method on the side of the first access network device, the first network element or the charging network element in the above.
  • a communication system is further provided, where the communication system includes a first network element and a charging network element.
  • the communication system may further include access network equipment, and optionally, the communication system may further include terminal equipment.
  • the first network element, charging network element, access network device, and terminal device may be the first network element, charging network element, access network device, and The terminal device is used to perform the steps performed by the corresponding network element in any of the embodiments in FIG. 4 or FIG. 5 .
  • An embodiment of the present application further provides a processing apparatus, including a processor and an interface, where the processor is configured to execute the method in any of the foregoing method embodiments.
  • the above processing device may be a chip.
  • the processing device may be a field programmable gate array (FPGA), a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC) , off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, can also be system on chip (system on chip, SoC), can also be central processing It can be a central processor unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), or a microcontroller (MCU) , it can also be a programmable logic device (PLD) or other integrated chips.
  • FPGA field programmable gate array
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • FPGA field programmable gate array
  • FPGA field programmable gate array
  • FPGA field programmable gate array
  • FPGA field programmable gate
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line, DSL) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media.
  • the available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, high-density digital video discs (DVDs)), or semiconductor media (eg, solid state discs, SSD)) etc.
  • the access network equipment, the first network element, and the charging network element in the above apparatus embodiments are completely corresponding to the access network equipment, the first network element, and the charging network element in the method embodiments, and are composed of corresponding modules or units.
  • the communication unit transmits the step of receiving or sending in the method embodiment, and other steps except sending and receiving may be performed by the processing unit (processor).
  • the processing unit performs the step of receiving or sending in the method embodiment, and other steps except sending and receiving may be performed by the processing unit (processor).
  • the number of processors may be one or more.
  • a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, or a computer.
  • an application running on a computing device and the computing device may be components.
  • One or more components may reside within a process or thread of execution, and a component may be localized on one computer or distributed among 2 or more computers.
  • these components can execute from various computer readable media having various data structures stored thereon.
  • a component may, for example, pass a signal through a local system based on a signal having one or more data packets (such as data from two components interacting with another component between a local system, a distributed system, or a network, such as the Internet interacting with other systems through signals). or remote process to communicate.
  • a signal having one or more data packets (such as data from two components interacting with another component between a local system, a distributed system, or a network, such as the Internet interacting with other systems through signals). or remote process to communicate.
  • B corresponding to A indicates that B is associated with A, and B can be determined according to A.
  • determining B according to A does not mean that B is only determined according to A, and B may also be determined according to A and/or other information.
  • the meanings of expressions similar to "the item includes one or more of the following: A, B, and C" usually mean that the item can be any of the following: A; B, unless otherwise specified. ;C;A and B;A and C;B and C;A,B and C;A and A;A,A and A;A,A and B;A,A and C,A,B and B;A , C and C; B and B, B, B and B, B, B and C, C and C; C, C and C, and other combinations of A, B and C.
  • a total of three elements of A, B and C are used as examples above to illustrate the optional items of the item.
  • the access network device, the first network element, and the charging network element may perform some or all of the steps in the embodiments of the present application. These steps or operations are only examples, and the embodiments of the present application also further Other operations or variations of the various operations may be performed. In addition, various steps may be performed in different orders presented in the embodiments of the present application, and may not be required to perform all the operations in the embodiments of the present application.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: a U disk, a removable hard disk, a read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供了一种信息传输方法及通信装置，其中，信息传输方法包括：第一接入网设备确定第一承载单元使用的切片资源的资源类型发生改变；响应于所述第一承载单元使用的切片资源的资源类型发生改变，所述第一接入网设备通知第一网元。采用本申请，可以实现计费公平。

Description

信息传输方法及通信装置 技术领域
本申请涉及通信技术领域，尤其涉及一种信息传输方法及通信装置。
背景技术
网络切片是通过切片技术在一个通用硬件基础上虚拟出多个端到端的网络，每个网络具有不同网络功能，适配不同类型服务需求。通常采用单网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)来标识一个网络切片，为了保证网络切片内业务的连续性，对于每个支持的S-NSSAI，无线接入网(radio access network，RAN)节点配置有重映射S-NSSAI列表，该S-NSSAI列表中包括为该网络切片配置的各种资源类型的切片资源的标识。若RAN上为网络切片配置的某种资源类型的切片资源不足时，可以使用一部分其他资源类型的切片资源，从而保证业务的连续性。如果采用现有技术中相同的计费方式进行计费，会影响公平。
发明内容
本申请实施例提供了一种信息传输方法及通信装置，能够实现计费公平。
第一方面，本申请实施例提供了一种信息传输方法，其中，该方法可以由第一接入网设备执行，也可以由第一接入网设备的部件(例如处理器、芯片、或芯片***等)执行。该信息传输方法可以包括：第一接入网设备确定第一承载单元使用的切片资源的资源类型发生改变。第一承载单元的粒度可以是会话粒度，或者也可以是QoS流粒度，或者还可以是网络切片粒度。其中，若第一承载单元是网络切片粒度，则第一承载单元使用的切片资源的资源类型发生改变可以是指：该第一承载单元中存在所使用的切片资源的资源类型发生改变的会话或QoS流。其中，切片资源的资源类型可以通过为网络切片所配置的S-NSSAI列表中子组的标识所确定。S-NSSAI列表中不同子组的标识是用于标识为该网络切片服务的不同资源类型的切片资源。第一接入网设备可以为网络切片内不同会话或不同QoS流调度该网络切片对应的S-NSSAI列表中不同资源类型的切片资源，或者也可以调度该网络切片对应的S-NSSAI列表中相同资源类型的切片资源。
响应于第一承载单元使用的切片资源的资源类型发生改变，第一接入网设备通知第一网元。可选的，如果第一承载单元是网络切片，则第一接入网设备可以确定该网络切片内资源类型发生改变的会话的数量或QoS流的数量与该网络切片内包含的所有会话的数量或QoS流的数量之间的比值，并将该比值通知给第一网元。
进一步，第一网元根据通知确定第一承载单元使用的切片资源的资源类型发生改变，并向计费网元通知第二承载单元使用的切片资源的资源类型发生改变，从而让计费网元确定与改变后的第二承载单元的资源类型对应的计费方式。其中，该第二承载单元是第一承载单元的子集，或第一承载单元是第二承载单元的子集，或第一承载单元与第二承载单元相同。
通过实施第一方面所描述的方法，可以让第一网元感知到第一承载单元使用的切片资 源的资源类型发生改变，并向计费网元通知第二承载单元使用的切片资源的资源类型发生改变，从而让计费网元感知到资源类型的改变，从而采用与改变后的资源类型对应的计费方式进行计费，实现计费公平。
在一种可能的设计中，第一接入网设备通知第一网元的通知方式可以是，第一接入网设备向第一网元发送第一信息，该第一信息可以用于表示第一承载单元使用的切片资源的资源类型发生改变，或者，该第一信息可以用于表示改变后的第一承载单元使用的切片资源的资源类型。
示例性的，资源类型的数量可以包括两种，则第一接入网设备可以通过第一信息通知第一网元该第一承载单元使用的切片资源的资源类型发生改变，该第一网元即可确定改变后的第一承载单元使用的切片资源的资源类型。
通过实施该方法，第一接入网设备可以通过多种方式通知第一网元该第一承载单元使用的切片资源的资源类型发生改变，从而便于第一网元确定改变后的第一承载单元使用的切片资源的资源类型。
在一种可能的设计中，在第一承载单元的用户面连接所经过的接入网设备由第二接入网设备切换到第一接入网设备的情况下，该第一接入网设备可以从第二接入网设备接收第一承载单元对应的切片资源的资源类型，该资源类型是该第二接入网设备为该第一承载单元所调度的切片资源的资源类型。
第一接入网设备进一步确定该第一接入网设备为该第一承载单元所调度的切片资源的资源类型，并根据所接收的第一承载单元对应的切片资源的资源类型和该第一接入网设备为该第一承载单元所调度的切片资源的资源类型，确定该第一承载单元所使用的切片资源的资源类型是否发生改变。
通过实施该方法，可以实现在切换场景下，第一接入网设备确定第一承载单元使用的切片资源的资源类型是否发生改变。
在一种可能的设计中，第一承载单元为会话、QoS流或网络切片中的一种。
在一种可能的设计中，第一接入网设备可以从第一网元接收指示信息，响应于该指示信息，该第一接入网设备在第一承载单元使用的切片资源的资源类型发生改变的情况下，通知第一网元。
通过实施该方法，第一网元可以向第一接入网设备指示需要上报的承载单元，从而便于第一接入网设备有针对性的进行上报，节省网络传输资源。
在一种可能的设计中，指示信息可以用于指示第一接入网设备在第一承载单元使用的切片资源的资源类型发生改变的情况下，通知第一网元；或者，指示信息可以用于指示向第一接入网设备订阅第一承载单元的资源类型改变事件。
在一种可能的设计中，第一网元可以是接入及移动管理功能(access and mobility management function，AMF)或者会话管理功能(session management function，SMF)。
第二方面，本申请实施例提供了一种信息传输方法，其中，该方法可以由第一网元执行，也可以由第一网元的部件(例如处理器、芯片、或芯片***等)执行。该信息传输方法可以包括：第一网元确定第一承载单元使用的切片资源的资源类型发生改变，响应于该第一承载单元使用的切片资源的资源类型发生改变，该第一网元通知计费网元第二承载单 元使用的切片资源的资源类型发生改变。其中，所述第一承载单元是所述第二承载单元的子集，或者，所述第二承载单元是所述第一承载单元的子集，或者所述第一承载单元与所述第二承载单元相同。
具体的，第一网元通知计费网元的方式可以是，该第一网元向计费网元发送切片资源信息，该切片资源信息用于表示第二承载单元使用的切片资源的资源类型发生改变，或，该切片资源信息表示改变后的第二承载单元使用的切片资源的资源类型。
通过实施第二方面所描述的方法，在第一网元感知到第一承载单元使用的切片资源类型发生改变的情况下，该第一网元通知计费网元第二承载单元使用的切片资源类型发生改变，从而让计费网元感知到资源类型的改变，从而采取与改变后的资源类型对应的计费方式进行计费，实现计费公平。
在一种可能的设计中，第一网元确定第一承载单元使用的切片资源的资源类型发生改变的确定方式可以是：第一网元从接入网设备接收通知，并根据该通知确定第一承载单元使用的切片资源的资源类型发生改变。其中，该通知可以指示第一承载单元使用的切片资源的资源类型发生改变，或者，该通知可以指示改变后的第一承载单元使用的切片资源的资源类型。
通过实施该方法，第一网元可以通过从接入网设备所接收的通知，快速确定第一承载单元使用的切片资源的资源类型发生改变。
在一种可能的设计中，第一网元确定第一承载单元使用的切片资源的资源类型发生改变的确定方式可以是：在第一承载单元的用户面连接所经过的接入网设备由第一接入网设备切换到第二接入网设备时，该第一网元从第一接入网设备接收第一资源状态信息，该第一资源状态信息用于指示第一接入网设备为该第一承载单元调度的切片资源的资源类型。
第一网元从第二接入网设备接收第二资源状态信息，该第二资源状态信息用于指示第二接入网设备为该第一承载单元调度的切片资源的资源类型。
进一步，第一网元可以根据所述第一资源状态信息和所述第二资源状态信息，确定第一承载单元使用的切片资源的资源类型发生改变。
通过实施该方法，可以实现在切换场景下，方便第一网元确定第一承载单元使用的切片资源的资源类型是否发生改变。
在一种可能的设计中，第一承载单元为会话、QoS流或网络切片中的一种。
在一种可能的设计中，若第一网元为AMF网元，则第二承载单元为网络切片、会话或QoS流中的一种。
若第一网元为SMF网元，第二承载单元为网络切片、会话、QoS流或业务中的一种。
通过实施该方法，第一网元向计费网元上报的粒度可以有多种选择。
在一种可能的设计中，该方法还包括：第一网元从计费网元接收第一指示信息，响应于该第一指示信息，第一网元在第一承载单元使用的切片资源的资源类型发生改变的情况下，向计费网元发送切片资源信息。
通过实施该方法，计费网元可以向第一网元指示需要上报的承载单元，从而便于第一网元有针对性的进行上报，节省网络传输资源。
在一种可能的设计中，第一指示信息用于指示第一网元在第二承载单元使用的切片资 源的资源类型发生改变的情况下，通知计费网元；或者，第一指示信息可以用于指示计费网元向第一网元订阅第二承载单元的资源类型改变事件。
在一种可能的设计中，该方法还可以包括：响应于第一网元从计费网元所接收的第一指示信息，该第一网元可以向接入网设备发送第二指示信息，该接入网设备可以是指终端设备所接入的接入网设备。该第二指示信息可以用于指示该接入网设备在第一承载单元使用的切片资源的资源类型发生改变的情况下，通知第一网元。
通过实施该方法，在计费网元向第一网元订阅第二承载单元的资源类型改变事件的情况下，该第一网元向接入网设备订阅第一承载单元的资源类型改变事件，从而让接入网设备有针对性的上报承载单元，节省网络传输资源。
第三方面，本申请实施例提供了一种信息传输方法，其中，该方法可以由计费网元执行，也可以由计费网元的部件(例如处理器、芯片、或芯片***等)执行。该信息传输方法可以包括：计费网元从第一网元接收切片资源信息，该切片资源信息用于表示第一承载单元使用的切片资源的资源类型发生改变，或，该切片资源信息表示改变后的第一承载单元使用的切片资源的资源类型。
该计费网元为第一承载单元确定与改变后的第一承载单元使用的切片资源的资源类型对应的计费处理方式。示例性的，若切片资源信息用于表示第一承载单元使用的切片资源的资源类型发生改变，若资源类型包括两种，该第一承载单元初始使用的切片资源的资源类型已知，则第一网元可以根据切片资源信息确定改变后的第一承载单元使用的切片资源的资源类型。
通过实施第三方面所描述的方法，计费网元可以感知到承载单元使用的切片资源的资源类型发生改变，从而采用与改变后的资源类型对应的计费方式进行计费，实现计费公平。
在一种可能的设计中，所述方法还包括：该计费网元向第一网元发送指示信息，该指示信息用于指示第一网元在第一承载单元使用的切片资源的资源类型发生改变的情况下，通知计费网元。
通过实施该方法，该计费网元指示第一网元有针对性的对承载单元的资源类型改变事件进行上报，从而节省网络传输资源。
第四方面，本申请实施例提供了一种信息传输方法，其中，该方法可以由第一接入网设备执行，也可以由第一接入网设备的部件(例如处理器、芯片、或芯片***等)执行。该信息传输方法可以包括：第一接入网设备确定第一承载单元的用户面连接所经过的接入网设备发生切换。其中，该第一接入网设备可以为切换之前该第一承载单元的用户面连接所经过的接入网设备，即源接入网设备，或者，该第一接入网设备也可以为切换之后该第一承载单元的用户面连接所经过的接入网设备，即目标接入网设备。
响应于第一承载单元的用户面连接所经过的接入网设备发生切换，该第一接入网设备向第一网元发送资源状态信息，该资源状态信息用于指示第一接入网设备为该第一承载单元调度的切片资源的资源类型。
通过实施第四方面所描述的方法，在第一承载单元的用户面连接所经过的接入网设备发生切换，源接入网设备和目标接入网设备将为该第一承载单元所调度的切片资源的资源类型上报给第一网元，从而便于第一网元确定第一承载单元使用的切片资源的资源类型是 否发生改变。
在一种可能的设计中，该方法还可以包括：第一接入网设备从第一网元接收指示信息；响应于该指示信息，该第一接入网设备在第一承载单元的用户面连接所经过的接入网设备发生切换的情况下，向第一网元发送资源状态信息。
可选的，指示信息用于指示第一接入网设备在第一承载单元使用的切片资源的资源类型发生改变的情况下，通知第一网元。
通过实施该方法，第一接入网设备可以根据指示信息确定需要上报给第一网元的承载单元的资源状态信息，从而有针对性的上报，节省传输资源。
第五方面，本申请实施例提供了一种通信装置，该通信装置可以是第一接入网设备，也可以是第一接入网设备的部件(例如处理器、芯片、或芯片***等)，该通信装置可以包括收发单元和处理单元；
处理单元，用于确定第一承载单元使用的切片资源的资源类型发生改变；
收发单元，用于响应于所述第一承载单元使用的切片资源的资源类型发生改变，通知第一网元。
在一种可能的设计中，所述收发单元具体用于向第一网元发送第一信息，第一信息用于表示所述第一承载单元使用的切片资源的资源类型发生改变，或者，所述第一信息用于表示改变后的所述第一承载单元使用的切片资源的资源类型。
在一种可能的设计中，所述收发单元还用于从第二接入网设备接收所述第一承载单元对应的切片资源的资源类型；
所述处理单元还用于确定所述第一接入网设备为所述第一承载单元调度的切片资源的资源类型。
在一种可能的设计中，所述第一承载单元为会话、服务质量QoS流或网络切片中的一种。
在一种可能的设计中，所述收发单元还用于从所述第一网元接收指示信息；
所述收发单元还用于响应于所述指示信息，在所述第一承载单元使用的切片资源的资源类型发生改变的情况下，通知所述第一网元。
在一种可能的设计中，所述指示信息用于指示所述第一接入网设备在所述第一承载单元使用的切片资源的资源类型发生改变的情况下，通知所述第一网元。
在一种可能的设计中，所述第一网元为接入和移动管理功能AMF网元或者会话管理功能SMF网元。
第六方面，本申请实施例提供了一种通信装置，该通信装置可以是第一网元，也可以是第一网元的部件(例如处理器、芯片、或芯片***等)，该通信装置可以包括收发单元和处理单元；
处理单元，用于确定第一承载单元使用的切片资源的资源类型发生改变；
收发单元，用于响应于所述第一承载单元使用的切片资源的资源类型发生改变，向计费网元发送切片资源信息，所述切片资源信息用于表示第二承载单元使用的切片资源的资源类型发生改变，或，所述切片资源信息表示改变后的第二承载单元使用的切片资源的资源类型；
其中，所述第一承载单元是所述第二承载单元的子集，或者，所述第二承载单元是所述第一承载单元的子集，或者所述第一承载单元与所述第二承载单元相同。
在一种可能的设计中，所述收发单元还用于从接入网设备接收通知；
所述处理单元具体用于根据所述通知确定所述第一承载单元使用的切片资源的资源类型发生改变。
在一种可能的设计中，所述收发单元还用于从第一接入网设备接收第一资源状态信息，所述第一资源状态信息用于指示所述第一接入网设备为所述第一承载单元调度的切片资源的资源类型；
所述收发单元还用于从第二接入网设备接收第二资源状态信息，所述第二资源状态信息用于指示所述第二接入网设备为所述第一承载单元调度的切片资源的资源类型；
所述处理单元具体用于根据所述第一资源状态信息和所述第二资源状态信息，确定所述第一承载单元使用的切片资源的资源类型发生改变。
在一种可能的设计中，所述第一承载单元为会话、服务质量QoS流或网络切片中的一种。
在一种可能的设计中，若所述第一网元为接入和移动管理功能AMF网元，所述第二承载单元为网络切片、会话或QoS流中的一种；
若所述第一网元为会话管理功能SMF网元，所述第二承载单元为网络切片、会话、QoS流或业务中的一种。
在一种可能的设计中，所述收发单元还用于从所述计费网元接收第一指示信息；
所述收发单元还用于响应于所述第一指示信息，在所述第一承载单元使用的切片资源的资源类型发生改变的情况下，向所述计费网元发送切片资源信息。
在一种可能的设计中，所述第一指示信息用于指示所述第一网元在所述第二承载单元使用的切片资源的资源类型发生改变的情况下，通知所述计费网元。
在一种可能的设计中，所述收发单元还用于响应于所述第一指示信息，向接入网设备发送第二指示信息，所述第二指示信息用于指示所述接入网设备在所述第一承载单元使用的切片资源的资源类型发生改变的情况下，通知所述第一网元。
第七方面，本申请实施例提供了一种通信装置，该通信装置可以是计费网元，也可以是计费网元的部件(例如处理器、芯片、或芯片***等)，该通信装置可以包括收发单元和处理单元；
收发单元，用于从第一网元接收切片资源信息，所述切片资源信息用于表示第一承载单元使用的切片资源的资源类型发生改变，或，所述切片资源信息表示改变后的第一承载单元使用的切片资源的资源类型；
处理单元，用于为所述第一承载单元确定与改变后的所述第一承载单元使用的切片资源的资源类型对应的计费处理方式。
在一种可能的设计中，所述收发单元还用于向所述第一网元发送指示信息，所述指示信息用于指示所述第一网元在所述第一承载单元使用的切片资源的资源类型发生改变的情况下，通知所述计费网元。
第八方面，本申请实施例提供了一种通信装置，该通信装置可以是第一接入网设备， 也可以是第一接入网设备的部件(例如处理器、芯片、或芯片***等)，该通信装置可以包括收发单元和处理单元；
处理单元，用于确定第一承载单元的用户面连接所经过的接入网设备发生切换；
收发单元，用于响应于第一承载单元的用户面连接所经过的接入网设备发生切换，该第一接入网设备向第一网元发送资源状态信息，该资源状态信息用于指示第一接入网设备为该第一承载单元调度的切片资源的资源类型。
其中，该第一接入网设备可以为切换之前该第一承载单元的用户面连接所经过的接入网设备，即源接入网设备，或者，该第一接入网设备也可以为切换之后该第一承载单元的用户面连接所经过的接入网设备，即目标接入网设备。
在一种可能的设计中，收发单元还用于从第一网元接收指示信息；
收发单元还用于响应于该指示信息，在第一承载单元的用户面连接所经过的接入网设备发生切换的情况下，向第一网元发送资源状态信息。
在一种可能的设计中，指示信息用于指示第一接入网设备在第一承载单元使用的切片资源的资源类型发生改变的情况下，通知第一网元。
第九方面，本申请实施例提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第一方面至第四方面任一方面的方法。可选地，该通信装置还包括存储器。可选地，该通信装置还包括通信接口，处理器与通信接口耦合。
第十方面，本申请实施例提供了一种处理器，包括：输入电路、输出电路和处理电路。所述处理电路用于通过所述输入电路接收信号，并通过所述输出电路发射信号，使得所述处理器执行第一方面至第四方面任一方面的方法。
在具体实现过程中，上述处理器可以为一个或多个芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第十一方面，本申请实施例提供了一种处理装置，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过接收器接收信号，通过发射器发射信号，以执行第一方面至第四方面任一方面的方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
应理解，相关的数据交互过程例如发送信息可以为从处理器输出信息的过程，接收信息可以为处理器接收信息的过程。具体地，处理器输出的数据可以输出给发射器，处理器接收的输入数据可以来自接收器。其中，发射器和接收器可以统称为收发器。
上述第八方面中的处理装置可以是一个或多个芯片。该处理装置中的处理器可以通过硬件来实现也可以通过软件来实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第十二方面，本申请实施例提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行上述第一方面至第四方面任一方面的方法。
第十三方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一方面至第四方面任一方面的方法。
第十四方面，本申请实施例提供了一种通信***，包括前述第一网元和计费网元。
可选的，该通信***还可以包括接入网设备。
第十五方面，提供了一种芯片***，该芯片***包括处理器和接口，处理器用于从存储器中调用并运行存储器中存储的计算机程序(也可以称为代码，或指令)，以实现第一方面至第四方面任一方面所涉及的功能，在一种可能的设计中，该芯片***还包括存储器，存储器用于保存必要的程序指令和数据。该芯片***，可以由芯片构成，也可以包括芯片和其他分立器件。
附图说明
图1a-图1f是本申请实施例提供的网络***架构图；
图2a和图2b是本申请实施例提供的网络切片的示意图；
图3a-图3e是本申请实施例提供的应用场景示意图；
图4是本申请实施例提供的一种信息传输方法的流程示意图；
图5是本申请实施例提供的另一种信息传输方法的流程示意图；
图6是本申请提供的一种通信装置的示意性框图；
图7是本申请实施例提供的另一通信装置的示意性框图；
图8是本申请实施例提供的一种芯片的结构示意图。
具体实施方式
本申请实施例的技术方案可以应用于各种通信***，例如：长期演进(long term evolution，LTE)***、通用移动通信***(universal mobile telecommunication system，UMTS)、第五代(5th generation，5G)***、新无线(new radio，NR)以及随着技术的发展出现的其他新的***等。在各种通信***中，本申请实施例的技术方案又可以应用于各种场景，例如，在5G***中，本申请实施例的技术方案既可用于基于服务化接口的网络架构中，又可以用于基于参考点的网络架构中，还可应用于漫游场景或非漫游场景等等。
如图1a和图1b所示，是本申请实施例提供的非漫游场景下的5G网络架构图。图1a是非漫游场景下，基于参考点的5G网络架构；图1b是非漫游场景下，基于服务化接口的5G网络架构。
如图1c-图1f所示，是本申请实施例提供的漫游场景下的5G网络架构图。其中，图1c是本地疏导(Local breakout，LBO)漫游场景下基于服务化接口的5G网络架构图，图1d是LBO漫游场景下基于参考点的5G网络架构图，图1e是归属地路由(home routed)漫游场景下基于服务化接口的5G网络架构图，图1f是归属地路由漫游场景下基于参考点的5G网络架构图。
下面以图1a所示非漫游场景下，基于参考点的5G网络架构进行举例介绍，如图1a所示，该***可以分为接入网和核心网两部分。接入网用于实现无线接入有关的功能，主要包括接入网络(access network，AN)设备102，接入网络设备包括了无线接入网络(radio access network，RAN)设备以及其它通过空口接入的设备(比如WiFi)。核心网主要包括以下几个关键逻辑网元：用户面功能(user plane function)103、接入及移动管理功能(access and mobility management function，AMF)105、会话管理功能(session management function)106、策略控制功能(policy control function，PCF)107、统一数据管理功能(unified data management)109。该***100还可以包括用户设备(user equipment，UE)101、数据网络(data network，DN)104和应用功能(application function，AF)108中的一项或多项。各网元之间的接口如图1a中所示。应理解，网元之间还可以采用服务化接口进行通信。
UE，也可以称为终端设备。终端设备可以经AN设备与一个或多个核心网(core network，CN)进行通信。终端设备可称为接入终端、终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线网络设备、用户代理或用户装置。终端可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless localloop，WLL)站、个人数字处理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它设备、车载设备、可穿戴设备或物联网、车辆网中的终端设备以及未来网络中的任意形态的终端设备等。
AN设备，是一种将终端设备接入到无线网络的设备，具体可以为基站。基站可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。具体可以为：无线局域网(wireless local area network，WLAN)中的接入点(access point，AP)，全球移动通信***(global system for mobile communications，GSM)或码分多址接入(code division multiple access，CDMA)中的基站(base transceiver station，BTS)，也可以是宽带码分多址(wideband code division multiple access，WCDMA)中的基站(NodeB，NB)，还可以是LTE中的演进型基站(Evolved Node B，eNB或eNodeB)，或者中继站或接入点，或者车载设备、可穿戴设备以及5G***中的下一代节点B(the next generation Node B，gNB)或者未来演进的公用陆地移动网(public land mobile network，PLMN)网络中的基站等。
UDM，具备管理用户的签约数据，生成用户的认证信息等功能。
AMF，主要负责UE的注册管理、UE的连接管理、UE的可达性管理、UE的接入授权和接入鉴权、UE的安全功能，UE的移动性管理，网络切片(network slice)选择，SMF选择等功能。AMF作为N1/N2接口信令连接的锚点并为SMF提供N1/N2接口会话管理(session management，SM)消息的路由，维护和管理UE的状态信息。AMF是5G***中的一种移动管理网元。
SMF，主要负责UE会话管理的所有控制面功能，包括UPF的选择与控制，网络互连 协议(internet protocol，IP)地址分配及管理，会话的服务质量(quality of service，QoS)管理，从PCF获取策略与计费控制(policy and charging control，PCC)策略等。SMF还作为非接入层(non-access stratum，NAS)消息中SM部分的终结点。
PCF，具备向控制面功能实体提供策略规则等功能。
AF，可以是应用服务器，其可以属于运营商，也可以属于第三方。
UPF，主要负责对用户报文进行处理，如转发、计费等，可以作为协议数据单元(protocol data unit，PDU)会话(session)连接的锚定点，即PDU会话锚点(PDU session anchor，PSA)，负责对UE的数据报文过滤、数据传输/转发、速率控制、生成计费信息、用户面QoS处理、上行传输认证、传输等级验证、下行数据包缓存及下行数据通知触发等。UPF还可以作为多宿主(multi-homed)PDU会话的分支点。
DN，为用户提供数据传输服务的网络，例如，IP多媒体业务(IP Multi-media service,IMS)、互联网等。DN中可以包括应用服务器(application server，AS)，AS是一种软件框架，提供一个应用程序运行的环境，用于为应用程序提供安全、数据、事务支持、负载平衡大型分布式***管理等服务。UE通过与AS通信获取应用报文。需要说明的是，上述AF为AS的控制面。
应理解，本申请实施例并不限定只应用于图1a所示的***架构中。例如，可以应用本申请实施例的信息传输方法的通信***中可以包括更多或更少的网元或设备。图1a中的设备或网元可以是硬件，也可以是从功能上划分的软件或者以上二者的结合。图1a中的设备或网元之间可以通过其他设备或网元通信。
在详细介绍本申请的方法之前，首先对本申请涉及的一些概念作简单介绍。
1、网络切片
网络切片(network slicing)是通过切片技术在一个通用硬件基础上虚拟出多个端到端的网络，每个网络具有不同网络功能，适配不同类型服务需求。各行各业对网络功能的需求多种多样，但是这些需求都可以解析成对网络带宽、连接数、时延、可靠性等网络功能的需求。如图2a所示，5G标准也将不同业务对网络功能的需求特点归纳为三大典型场景，增强型移动宽带(enhance mobile broadband，eMBB)业务、大规模机器通信(massive machine type communication，mMTC)业务以及超可靠低时延通信(Ultra-reliable andLowLatencyCommunications，URLLC)业务。相应的这三大典型场景对应的网络切片的类型分别是eMBB切片、mMTC切片、uRLLC切片。
如图2b所示，5G网络切片架构示意图如图所示，运营商购买物理资源后，针对大众上网业务使用物理资源虚拟出一个eMBB切片网络，之后再针对垂直行业中某些厂商的智能抄表需求，使用物理资源再虚拟出一个mMTC切片网络，两个切片网络分别为不同业务场景提供服务，不同的切片网络对应不同的物理资源，从而实现切片网络之间的资源隔离。
2、S-NSSAI
S-NSSAI用来标识一个网络切片。S-NSSAI包括切片/服务类型(slice/service type，SST)和切片差异(slice differentiator，SD)两部分。其中，SST是指在特性和服务方面预期的网络切片行为。SST的标准取值范围为1、2、3，取值1表示eMBB切片类型、2表示 URLLC切片类型、3表示mMTC切片类型。SD是一个可选信息，用来补充SST以区分同一个切片/业务类型的多个网络切片。SST和SD两部分结合起来表示切片类型及同一切片类型的多个切片。例如S-NSSAI取值为0x01000000、0x02000000、0x03000000分别表示eMBB类型切片、uRLLC类型切片、mMTC类型切片。而S-NSSAI取值为0x01000001、0x01000002则表示eMBB类型切片，分别服务于用户群1和用户群2，即分别标识两个具体的网络切片。
3、重映射策略
RAN节点预先由操作维护管理(operation administration and maintenance，OAM)网元配置重映射策略。重映射策略的粒度为每网络切片，即对于每个支持的S-NSSAI，RAN节点配置有可能的重映射列表，该重映射列表中包括多个子组，不同子组可用于标识不同资源类型的切片资源。例如，为S-NSSAI 1配置的重映射列表为(S-NSSAI 1a,S-NSSAI 1b)。S-NSSAI 1a和S-NSSAI 1b可以分别标识为S-NSSAI 1对应的网络切片服务的两种资源类型的切片资源。
不同子组的切片资源之间可以相互映射，即某一个子组的切片资源不足时，可以使用另一个子组的切片资源。以S-NSSAI 1为例，若RAN上S-NSSAI1a的切片资源不足，可以使用一部分S-NSSAI 1b的切片资源(S-NSSAI 1b仍有富余资源)。
切片资源的资源类型包括但不限于共享资源(shared resources)、优先级资源(priortized resources)或专用资源(dedicated resources)。
需要说明的是，S-NSSAI-1a和S-NSSAI-1b只是资源标识的一个示例，不代表该资源仅仅是为S-NSSAI1服务的。比如S-NSSAI-1b所标识的切片资源可以是S-NSSAI2的优先级资源，即S-NSSAI-1b所标识的切片资源在保证S-NSSAI2使用的前提下，如果有空闲的资源可供其他S-NSSAI使用。在一些场景下，S-NSSAI-1b所标识的切片资源可以是共享资源，即不同的S-NSSAI均可以使用该S-NSSAI-1b所标识的切片资源，但不能保证在需要使用时该S-NSSAI-1b所标识的切片资源存在空闲的资源。
通常RAN调度不同资源类型的切片资源时，资源处理方式可能不同。继续以S-NSSAI1为例，比如RAN对S-NSSAI 1a所标识的切片资源的调度，资源处理更优(比如S-NSSAI-1a是S-NSSAI-1的专用资源，S-NSSAI-1不使用时也不能由其他S-NSSAI使用)；而对S-NSSAI1b所标识的切片资源的调度稍差一些。但是为了业务的连续性，可以接受使用S-NSSAI 1b的切片资源为网络切片进行服务。
可以理解的是，资源处理方式不同，则可能会导致QoS的区别，例如，资源处理更优，则网络时延更小，带宽更高，相应的，用户体验也更好。资源处理方式不同，也可能会有其他处理上的不同，比如数据包调度方式等，在此不一一赘述。
4、承载单元
本申请实施例中的承载单元可以是指用于传输数据的传输单元。具体的，承载单元的粒度可以有多种，例如，承载单元可以是会话、服务质量(quality of service，QoS)流、网络切片或业务中的一种。一个网络切片可以与多个会话关联，一个会话可以包括多个QoS流。一个会话也可以包括多个业务。业务可以是指某个具体的业务数据流(service data flow，SDF)，或者可以是以计费键(charging key)所标识的一个或多个业务数据流。其中，同一 计费键所标识的一个或多个业务数据流的计费处理方式相同。
本申请实施例中的第一承载单元与第二承载单元可以是用于区分不同的粒度，或者，第一承载单元与第二承载单元的粒度可以相同，在第一承载单元与第二承载单元的粒度相同的情况下，第一承载单元可以是与第二承载单元相同的承载单元，比如，第一承载单元与第二承载单元为同一网络切片。
5、关于本申请实施例中的“响应于**，执行某种操作”，可以理解为执行该操作是以**为基础的，其中，“响应于**”可以被替换为“根据**”，或者也可以被替换为“基于**”，或者也可以被替换为“在**的触发下”等等。
在具体描述本申请实施例的信息传输方法之前，下面结合附图3a-附图3e对本申请实施例所应用的场景进行举例介绍，可以理解的是，图3a-图3e中的RAN可以是图1a-图1f中所示网络架构中的RAN，图3a-图3e中的UE可以是图1a-图1f中所示网络架构中的UE。
场景一，如图3a所示，RAN1和RAN2属于同一个注册区(registration area，RA)。随着UE的移动，UE从RAN1的覆盖范围移动到RAN2的覆盖范围，即该UE接入的RAN由RAN1切换到RAN2。其中，RAN1和RAN2为特定网络切片(例如网络切片1)配置不同资源类型的切片资源，例如，为该网络切片1配置重映射列表。当UE从RAN1切换到RAN2时，RAN1为该UE的网络切片1调度的切片资源的资源类型与RAN2为该UE的网络切片1调度的切片资源的资源类型发生改变。比如，RAN1为该UE的网络切片1调度资源处理更优的切片资源，而RAN2比较拥塞，即使用网络切片1的切片资源的UE比较多，RAN2为网络切片1配置的切片资源中，资源处理更优的切片资源不足，则RAN2可以为该UE的网络切片1调度资源处理稍差的切片资源。可以理解的是，也可以是网络切片1中的一个或多个会话或网络切片1中的一个或多个QoS流的切片资源的资源类型发生改变，例如，RAN2为网络切片1中部分会话调度资源处理稍差的切片资源。
本申请实施例中，在RAN2确定第一承载单元使用的切片资源的资源类型发生改变，则将该资源类型的改变通知给AMF或SMF，进一步，AMF或SMF上报给CHF或PCF，以进行区别计费，实现计费公平。其中，该第一承载单元可以是上述网络切片1，或者也可以是网络切片1中的部分会话，或者也可以是会话中包含的部分QoS流，可选的，上报粒度可以根据对应网元的订阅粒度所确定。
场景二，如图3b所示，RAN1和RAN2属于不同RA，RAN1属于RA1，RAN2属于RA2。随着UE的移动，UE从RAN1的覆盖范围移动到RAN2的覆盖范围，即该UE接入的RAN由RAN1切换到RAN2。其中，RAN1为该UE的网络切片1调度的切片资源的资源类型与RAN2为该UE的网络切片1调度的切片资源的资源类型可能发生改变。RAN2可以将该资源类型的改变通知给AMF或SMF，进一步，AMF或SMF上报给CHF或PCF，以进行区别计费。具体可以参照场景一的描述，在此不再赘述。
场景三，如图3c所示，RAN1和RAN2属于不同RA，RAN1属于RA1，RAN2属于RA2，或者，RAN1和RAN2也可以属于同一个RA。随着UE的移动，UE从RAN1的覆盖范围移动到RAN2的覆盖范围，再从RAN2的覆盖范围移动到RAN1的覆盖范围，即该UE接入的RAN由RAN1切换到RAN2，再由RAN2切换到RAN1，可选的，若RAN1和 RAN2属于不同RA，则场景三可以是基于场景二切换回RAN1的场景。若RAN1和RAN2是属于同一RA，则场景三可以是基于场景一切换回RAN1的场景。其中，RAN2为该UE的网络切片1调度的切片资源的资源类型与RAN1为该UE的网络切片1调度的切片资源的资源类型可能发生改变。比如，RAN2比较拥塞，即使用网络切片1的切片资源的UE比较多，RAN2为网络切片1配置的切片资源中，资源处理更优的切片资源不足，则RAN2可以为该UE的网络切片1调度资源处理稍差的切片资源。而RAN1并不拥塞，即使用网络切片1的切片资源的UE比较少，则RAN1可以为网络切片1调度资源处理更优的切片资源。
可以理解的是，也可以是网络切片1中的一个或多个会话或网络切片1中的一个或多个QoS流的切片资源的资源类型发生改变，例如，RAN1为网络切片1中部分会话调度资源处理更优的切片资源。
本申请实施例中，在RAN1确定第一承载单元使用的切片资源的资源类型发生改变，则将该资源类型的改变通知给AMF或SMF，进一步，AMF或SMF上报给CHF或PCF，以进行区别计费，实现计费公平。其中，该第一承载单元可以是上述网络切片1，或者也可以是网络切片1中的部分会话，或者也可以是会话中包含的部分QoS流，可选的，上报粒度可以根据对应网元的订阅粒度所确定。
场景四，如图3d所示，RAN1和RAN2是双连接(dual-connectivity，DC)场景下的主站和从站，RAN2(从站)为该UE的网络切片1调度的切片资源的资源类型可能发生改变。例如，RAN2可能从不拥塞变为拥塞，即RAN2在不拥塞时，为该UE的网络切片1调度资源处理更优的切片资源，而RAN2比较拥塞时，即使用网络切片1的切片资源的UE比较多，RAN2可以为该UE的网络切片1调度资源处理稍差的切片资源。可以理解的是，也可以是网络切片1中的一个或多个会话或网络切片1中的一个或多个QoS流的切片资源的资源类型发生改变，例如，RAN2为网络切片1中部分会话调度资源处理稍差的切片资源。需要说明的是，RAN2也可能从拥塞变为不拥塞，在RAN2拥塞时，RAN2可以为该UE的网络切片1调度资源处理稍差的切片资源，而在RAN2不拥塞时，RAN2为该UE的网络切片1调度资源处理更优的切片资源。
本申请实施例中，在RAN2确定第一承载单元使用的切片资源的资源类型发生改变，则将该资源类型的改变通知给AMF或SMF，进一步，AMF或SMF上报给CHF或PCF，以进行区别计费，实现计费公平。其中，该第一承载单元可以是上述网络切片1，或者也可以是网络切片1中的部分会话，或者也可以是会话中包含的部分QoS流，可选的，上报粒度可以根据对应网元的订阅粒度所确定。
场景五，如图3e所示，UE接入RAN1，UE在非移动场景下，RAN1为该UE的网络切片1调度的切片资源的资源类型可能发生改变。例如，RAN1可能从不拥塞变为拥塞，或者从不拥塞变为拥塞，RAN1为UE1的网络切片1调度的切片资源的资源类型可能发生改变。RAN1在不拥塞时，为该UE的网络切片1调度资源处理更优的切片资源，而RAN1比较拥塞时，RAN1可以为该UE的网络切片1调度资源处理稍差的切片资源。可以理解的是，也可以是网络切片1中的一个或多个会话或网络切片1中的一个或多个QoS流的切片资源的资源类型发生改变，例如，RAN1为网络切片1中部分会话调度资源处理稍差的切 片资源。
本申请实施例中，在RAN1确定第一承载单元使用的切片资源的资源类型发生改变，则将该资源类型的改变通知给AMF或SMF，进一步，AMF或SMF上报给CHF或PCF，以进行区别计费，实现计费公平。其中，该第一承载单元可以是上述网络切片1，或者也可以是网络切片1中的部分会话，或者也可以是会话中包含的部分QoS流，可选的，上报粒度可以根据对应网元的订阅粒度所确定。
下面分别结合附图4和附图5对本申请实施例的信息传输方法进行阐述，其中，图4可以是由接入网设备确定第一承载单元使用的切片资源的资源类型发生改变，并将该资源类型的改变通知给第一网元，进一步由第一网元以第二承载单元的粒度上报给计费网元进行计费。图5可以是在切换场景中，第一接入网设备和第二接入网设备分别向第一网元上报资源状态信息，由第一网元根据第一接入网设备和第二接入网设备上报的资源状态信息确定第一承载单元使用的切片资源的资源类型发生改变，并将该资源类型的改变通知给第一网元，进一步由第一网元以第二承载单元的粒度上报给计费网元进行计费。示例性的，在图4和图5所示实施例中，第一网元可以是AMF或SMF，计费网元可以是CHF或PCF。下面分别对图4和图5所示实施例的具体步骤进行介绍。
请参照图4，为本申请实施例提供的一种信息传输方法的流程示意图，图1a至图1e可以为该信息传输方法所应用的网络架构示例。图3a至图3e可以为该信息传输方法所应用的场景示例。如图4所示，该方法可以包括：S102-S106，可选的，还可以包括订阅过程和切换过程中的一个或两个。其中，订阅过程可以包括S100和S101，切换过程可以包括S10和S11。其中，各个步骤的执行顺序，本申请实施例不作限制。如图所示，本申请实施例的信息传输方法包括但不限于以下步骤：
S100，计费网元向第一网元发送第一指示信息。
在一个实施例中，计费网元可以向第一网元订阅第二承载单元的资源类型改变事件。示例性的，计费网元向第一网元发送第一指示信息，该第一指示信息可以用于指示第一网元在第二承载单元使用的切片资源的资源类型发生改变的情况下，向计费网元发送切片资源信息；或者，第一指示信息可以用于指示计费网元向第一网元订阅第二承载单元；或者，该第一指示信息可以用于指示在第二承载单元使用的切片资源的资源类型发生改变时需要上报给计费网元；或者该第一指示信息可以用于指示第一网元在第二承载单元使用的切片资源的资源类型发生改变的情况下通知给计费网元。可选的，第一指示信息可以是通过订阅请求发送给第一网元。作为一种实现方式，计费网元可以同时发送第二承载单元标识(如S-NSSAI，QoS流标识，业务数据流模板，PDU会话标识等)和第一指示信息，代表第二承载单元的资源类型发生改变时需要进行上报，该种实现方式中第一指示信息可以是用于指示资源类型发生改变时进行上报的指示。可以理解的是，第二承载单元标识也可以是在第一指示信息中，本申请不作限定。
其中，该第二承载单元的粒度可以是网络切片粒度，即当某一个或多个网络切片使用的切片资源的资源类型发生改变时需要上报给计费网元；该第二承载单元的粒度还可以是会话粒度，即当某一个或多个会话使用的切片资源的资源类型发生改变时需要上报给计费 网元；该第二承载单元的粒度还可以是QoS流粒度，即当某一个或多个QoS流使用的切片资源的资源类型发生改变时需要上报给计费网元；可选的，该第二承载单元的粒度还可以是业务粒度，比如，第一网元为SMF，该第二承载单元的粒度可以是业务粒度，即当某一个或多个业务使用的切片资源的资源类型发生改变时需要上报给计费网元。可以理解的是，第二承载单元还可以是其他粒度，本申请不作限定。若第一网元为AMF网元，则第二承载单元可以为会话、或网络切片中的一种。若第一网元为SMF网元，则第二承载单元可以为网络切片、会话、QoS流或业务中的一种。其中业务粒度，可以是指某个具体的SDF，或者可以是以计费键所标识的一个或多个业务数据流，通常同一计费键所标识的业务数据流的计费处理方式相同。
在一些实施例中，若计费网元为CHF，该CHF也可以通过PCF向第一网元进行订阅。比如CHF向PCF订阅资源类型改变事件。PCF收到订阅后向第一网元订阅第二承载单元的资源类型改变事件。其中，CHF向PCF订阅的粒度与PCF向第一网元的订阅粒度可以相同，也可以不同。
示例性的，当计费网元向SMF订阅的为业务粒度时，SMF向第一接入网设备订阅的为QoS流粒度时，SMF可以将具有订阅需求的业务数据流绑定至同一QoS流，即SMF将具有不同订阅需求(比如有订阅需求和没有订阅需求的，或者订阅的具体内容不同的等)的业务数据流绑定至不同QoS流，其中，属于同一QoS流的业务数据流的处理规则相同，该处理规则包括属于同一QoS流的业务数据流的资源类型改变方式是相同的。可选的，当计费网元是PCF时，PCF可以将携带有绑定参数的策略与计费控制(policy and charging control，PCC)规则发送给SMF，PCC规则与业务数据流具有对应关系。其中，上述第一指示信息也可以是通过PCC规则发送给SMF，可选的，上述第一指示信息可以作为绑定参数。SMF接收到PCC规则后，当PCC规则中的绑定参数与当前QoS流的绑定参数完全相同时，SMF将该PCC规则绑定至该QoS流，即SMF将该PCC规则对应的业务数据流绑定至该QoS流。若当前没有QoS流的绑定参数与该PCC规则中的绑定参数完全相同，SMF可以根据该PCC规则中的绑定参数建立新的QoS流，并将该PCC规则绑定至该新的QoS流。在一种实现方式中，若第一指示信息作为绑定参数，则PCC规则中的绑定参数与当前QoS流的绑定参数相同可以是指，该PCC规则中的指示信息与绑定到该QoS流的其他PCC规则中的指示信息相同，即SMF将所有具有相同指示信息的PCC规则绑定到同一个QoS流。之后，如S101所述，SMF可以向第一接入网设备发送第二指示信息，该第二指示信息可以用于指示该QoS流的资源类型发生改变时需要进行上报。
S101，第一网元响应于第一指示信息，向第一接入网设备发送第二指示信息。
在一个实施例中，第一网元接收到计费网元的订阅之后，可以向第一接入网设备订阅第一承载单元的资源类型改变事件。即第一网元接收到计费网元的第一指示信息后，响应于该第一指示信息，向第一接入网设备发送第二指示信息，第二指示信息也可以被称为切片资源信息改变上报指示，该第二指示信息可以用于指示第一接入网设备在第一承载单元使用的切片资源的资源类型发生改变的情况下，通知第一网元；或者，该第二指示信息可以用于指示第一网元向第一接入网设备订阅第一承载单元。作为一种实现方式，第一网元可以同时发送第一承载单元标识(如S-NSSAI，QoS流标识，业务数据流模板，PDU会话 标识等)和第二指示信息，代表第一承载单元的资源类型发生改变时需要进行上报，该种实现方式中第二指示信息可以是用于指示资源类型发生改变时进行上报的指示。可以理解的是，第一承载单元标识也可以是在第二指示信息中，本申请不作限定。
其中，该第一承载单元的粒度可以是网络切片粒度，即当某一个或多个网络切片使用的切片资源的资源类型发生改变时需要上报给第一网元；该第二承载单元的粒度还可以是会话粒度，即当某一个或多个会话使用的切片资源的资源类型发生改变时需要上报给第一网元；该第二承载单元的粒度还可以是QoS流粒度，即当某一个或多个QoS流使用的切片资源的资源类型发生改变时需要上报给第一网元。可以理解的是，第一承载单元还可以是其他粒度，本申请不作限定。
其中，第一承载单元的粒度与第二承载单元的粒度可以相同，也可以不同。若第一承载单元的粒度与第二承载单元的粒度相同，则第一承载单元与第二承载单元可以相同，例如，计费网元可以向第一网元指示在网络切片1使用的切片资源的资源类型发生改变的情况下通知给计费网元，第一网元可以向第一接入网设备指示在网络切片1使用的切片资源的资源类型发生改变的情况下通知给第一网元。若第一承载单元的粒度与第二承载单元的粒度不同，则第一承载单元可以是第二承载单元的子集，或者，第二承载单元可以是第一承载单元的子集。例如，第二承载单元可以是网络切片1，第一承载单元可以是网络切片1中的会话，即第一承载单元是第二承载单元的子集，计费网元可以向第一网元指示在网络切片1使用的切片资源的资源类型发生改变的情况下通知给计费网元，第一网元可以向第一接入网设备指示在会话1、会话2以及会话3使用的切片资源的资源类型发生改变的情况下通知给第一网元，该会话1、会话2以及会话3属于网络切片1。
在一些可选的实施例中，在计费网元向第一网元订阅的第二承载单元的粒度小于第一网元向第一接入网设备订阅的第一承载单元的粒度时，即第二承载单元是第一承载单元的子集，为了第一网元能准确的确定第二承载单元的资源类型是否改变，该第一承载单元中包含的所有承载单元所使用的切片资源的资源类型可以均相同，或者，该第一承载单元中包含的所有承载单元所使用的切片资源的资源类型均发生改变。
通过以上步骤S100和步骤S101，计费网元向第一网元完成第二承载单元的资源类型改变事件订阅，第一网元向第一接入网设备完成第一承载单元的资源类型改变事件订阅。其中，第一接入网设备可以是终端设备所接入的接入网设备。
需要说明的是，在一些实施例中，在终端设备所接入的接入网设备发生切换时，第一网元向第一接入网设备的订阅事件(包括所订阅的承载单元)可以作为上下文传递给切换后的接入网设备，或者，也可以不将该订阅事件进行传递，而是第一网元向切换后的接入网设备再次订阅资源类型改变事件，具体可以参照前述实施例中第一网元向第一接入网设备订阅的过程(即步骤S101所示)。同理，在第一网元发生切换时，计费网元向第一网元的订阅事件(包括所订阅的承载单元)也可以作为上下文传递给切换后的第一网元。或者，也可以不将该订阅事件进行传递，而是计费网元向切换后的第一网元再次订阅资源类型改变事件，具体可以参照前述实施例中计费网元向第一网元订阅的过程(即步骤S100所示)。
S102，第一接入网设备确定第一承载单元使用的切片资源的资源类型发生改变。
在一个实施例中，第一网元向第一接入网设备订阅第一承载单元的资源类型改变事件。 可选的，该第一承载单元可以是网络切片，或者也可以是网络切片中的会话，或者也可以是网络切片中会话的QoS流等等。具体的，OAM可以在该第一接入网设备中预先配置为该网络切片服务的多种资源类型的切片资源。例如，第一接入网设备中配置重映射列表，该该重映射列表中包括多个子组，不同子组可用于标识不同资源类型的切片资源。例如，S-NSSAI 1标识网络切片1，为S-NSSAI 1配置的重映射列表为(S-NSSAI 1a,S-NSSAI 1b)。S-NSSAI 1a和S-NSSAI 1b可以分别标识为网络切片1服务的两种资源类型的切片资源。例如，S-NSSAI 1a对应的切片资源为优先级资源，S-NSSAI 1b对应的切片资源为共享资源。
第一接入网设备可以为网络切片内的不同会话调度该网络切片对应的不同资源类型的切片资源，当然，在某种资源类型的切片资源充足的情况下，第一接入网设备也可以为网络切片内的不同会话调度相同资源类型的切片资源。同理，第一接入网设备也可以为同一会话内不同QoS流调度不同资源类型的切片资源，或者，在某种资源类型的切片资源充足的情况下，第一接入网设备也可以为不同QoS流调度相同资源类型的切片资源。可以理解的是，第一接入网设备可以优先为网络切片内的会话或QoS流调度资源处理更优的资源类型的切片资源，在资源处理更优的资源类型的切片资源不足的情况下，可以调度资源处理稍差的资源类型的切片资源给网络切片内的会话或QoS流。下面以会话粒度举例说明第一接入网设备为网络切片内的会话调度切片资源的资源状态示意图，如表格一所示，第一接入网设备为会话1调度S-NSSAI 1a对应的切片资源，为会话2调度S-NSSAI 1b对应的切片资源。
PDU会话标识 切片资源状态
1 S-NSSAI 1a
2 S-NSSAI 1b
表格一
可以理解的是，不仅限于表格一所示以会话粒度维护切片资源状态的上下文，第一接入网设备也可能维护其他粒度的上下文，比如QoS流标识及对应的切片资源状态，或者S-NSSAI及对应的切片资源状态。
本申请实施例中，第一接入网设备确定第一承载单元使用的切片资源的资源类型发生改变的确定方法可以包括但不限于以下两种可选的实施方式：
第一种可选的实施方式，由第一接入网设备的状态转换(例如在拥塞状态和非拥塞状态之间的转换)导致第一承载单元使用的切片资源的资源类型发生改变。
示例性的，终端设备所接入的第一接入网设备可能由拥塞状态转换为非拥塞状态，例如，接入该第一接入网设备且使用某个网络切片(例如网络切片1)的终端设备的数量由多变少，第一接入网设备为终端设备的第一承载单元调度的切片资源的资源类型可能发生改变，比如，该第一接入网设备为终端设备的第一承载单元调度的切片资源可能由资源处理稍差的切片资源切换为资源处理更优的切片资源。
示例性的，终端设备所接入的第一接入网设备可能由非拥塞状态转换为拥塞状态，例如，接入该第一接入网设备且使用某个网络切片(例如网络切片1)的终端设备的数量由少变多，第一接入网设备为终端设备的第一承载单元调度的切片资源的资源类型可能发生改变，例如，该第一接入网设备为终端设备的第一承载单元调度的切片资源可能由资源处 理较优的切片资源切换为资源处理稍差的切片资源。
其中，上述第一承载单元可以是网络切片，或者可以是网络切片中的会话，或者也可以是网络切片中会话的QoS流等等。需要说明的是，若第一承载单元为网络切片，则该网络切片使用的切片资源的资源类型发生改变可以是指，该网络切片内存在资源类型发生改变的会话或QoS流。
第二种可选的实施方式，由第一承载单元的用户面连接所经过的接入网设备由第二接入网设备切换到第一接入网设备导致第一承载单元使用的切片资源的资源类型发生改变。
具体的，可以是随着终端设备的移动(如前述的图3a至图3c的场景)，该终端设备从第二接入网设备的覆盖范围移动到第一接入网设备的覆盖范围，即该终端设备所接入的接入网设备由第二接入网设备切换到第一接入网设备，相应的，该终端设备的第一承载单元的用户面连接所经过的接入网设备由第二接入网设备切换到第一接入网设备。其中，第二接入网设备为该终端设备的第一承载单元调度的切片资源的资源类型与第一接入网设备为该终端设备的第一承载单元调度的切片资源的资源类型可能不同。
在该种实施方式中，为了便于第一接入网设备确定为该终端设备的第一承载单元调度的切片资源的资源类型是否改变，第二接入网设备可以将为第一承载单元对应的切片资源的资源类型发送给第一接入网设备，以便于第一接入网设备确定为该终端设备的第一承载单元调度的切片资源的资源类型是否改变，具体可以参照图4所示中的步骤S10和S11；
S10，第一接入网设备从第二接入网设备接收第一承载单元对应的切片资源的资源类型。
具体的，第二接入网设备可以通过上下文将第一承载单元对应的切片资源的资源类型发送给第一接入网设备，该第一承载单元对应的切片资源的资源类型是该第二接入网设备为该第一承载单元所调度的切片资源的资源类型。其中，该第一承载单元可以是第一网元向第二接入网设备所订阅的承载单元。可以理解的是，第一网元可以向第二接入网设备订阅与一个或多个网络切片关联的一个或多个第一承载单元，则第二接入网设备可以向第一接入网设备发送与一个或多个网络切片关联的一个或多个第一承载单元分别对应的切片资源的资源类型，下面以第一承载单元为会话作为举例说明，如表格二所示，为第二接入网设备为各个会话所调度的切片资源的资源类型的上下文示例，其中，S-NSSAI 2标识网络切片2，第二接入网设备为网络切片2中的会话3调度S-NSSAI 2a对应的切片资源：
PDU会话标识 切片资源状态
1 S-NSSAI 1a
2 S-NSSAI 1b
3 S-NSSAI 2a
表格二
可以理解的是，不仅限于表格二所示以会话粒度维护切片资源状态的上下文，第二接入网设备也可能维护其他粒度的上下文，比如QoS流标识及对应的切片资源状态，或者S-NSSAI及对应的切片资源状态。
示例性的，第二接入网设备可以通过Xn接口将上述上下文传递给第一接入网设备；或者，第二接入网设备可以将上述上下文经由核心网(如AMF)传递给第一接入网设备。
S11，第一接入网设备确定该第一接入网设备为第一承载单元调度的切片资源的资源类 型。
具体的，第一接入网设备可以根据该第一接入网设备的拥塞状态，确定为该第一承载单元调度的切片资源的资源类型。示例性的，若接入该第一接入网设备且使用该网络切片(例如网络切片1)的终端设备的数量比较多，则第一接入网设备为该第一承载单元调度资源处理稍差的切片资源；若接入该第一接入网设备且使用该网络切片的终端设备的数量比较少，资源处理更优的切片资源充足，则可以为该第一承载单元调度资源处理更优的切片资源。
进一步，第一接入网设备可以根据第二接入网设备为该第一承载单元所调度的切片资源的资源类型和该第一接入网设备为该第一承载单元所调度的切片资源的资源类型，确定第一承载单元使用的切片资源的资源类型是否发生改变。
S103，第一接入网设备响应于第一承载单元使用的切片资源的资源类型发生改变，通知第一网元。
在一个实施例中，第一接入网设备确定第一承载单元使用的切片资源的资源类型发生改变，并通知第一网元。具体的，第一接入网设备通知第一网元的通知方式可以有多种，例如，第一接入网设备可以向第一网元发送第一信息，可选的，该第一信息可以用于表示第一承载单元使用的切片资源的资源类型发生改变，比如，网络切片对应的资源类型包括两种，该第一承载单元初始使用的切片资源的资源类型已知，则第一接入网设备可以向第一网元指示资源类型发生改变，第一网元即可获得改变后的第一承载单元使用的切片资源的资源类型。可选的，该第一信息可以用于表示改变后的第一承载单元使用的切片资源的资源类型，比如，在第一承载单元使用的切片资源的资源类型发生改变时，第一接入网设备向第一网元指示改变后的第一承载单元使用的切片资源的资源类型。可选的，第一信息还可以用于表示各个时间段内所使用的切片资源的资源类型，例如，在2020年1月1日10:00-11:00使用的资源类型为S-NSSAI 1a，在2020年1月1日11:00-11:30使用的资源类型为S-NSSAI 1b，在2020年1月1日11:00-12:30使用的资源类型为S-NSSAI 1c。
在一些实施例中，如果网络切片对应的资源类型包括两种，第一网元可以指示第一接入网设备在某一种资源类型改变时，即上报给第一网元。比如，由其他资源类型切换为所订阅的资源类型时，第一接入网设备即上报给第一网元，或者，由该所订阅的资源类型切换为其他资源类型时，第一接入网设备即上报给第一网元。
其中，若第一承载单元为网络切片，第一接入网设备可以确定该网络切片内发生资源类型改变的会话或QoS流的数量占该网络切片内包含的所有会话或QoS流的数量之间的比值，并向第一网元上报该比值，从而以网络切片粒度上报该网络切片的资源类型改变信息。
可以理解的是，在切换场景(即上述第二种可选的实施方式)中第二接入网设备发送给第一接入网设备的上下文中承载单元的粒度与第一接入网设备通知给第一网元的承载单元的粒度可以相同，也可以不同。如果两者粒度不同，则第一接入网设备可以根据上下文中承载单元所对应的资源类型，进一步确定上报给第一网元的承载单元所对应的资源类型是否发生改变。比如，第一网元指示接入网设备(第一接入网设备和/或第二接入网设备)在网络切片1使用的切片资源的资源类型发生改变时上报，在进行切换时，第二接入网设备可以将该网络切片1中所包含的所有会话中各个会话所对应的资源类型作为上下文发送 给第一接入网设备，第一接入网设备进一步根据所接收的各个会话所对应的资源类型和该第一接入网设备为各个会话所调度的切片资源的资源类型，确定网络切片1所使用的切片资源类型是否改变，从而以网络切片粒度上报给第一网元。
其中，上述第一承载单元可以是步骤S101中第二指示信息中所指示的承载单元，因此，第一接入网设备可以是根据第二指示信息，向第一接入网设备通知第一承载单元使用的切片资源的资源类型发生改变。
S104，第一网元从第一接入网设备接收通知，并根据通知确定第一承载单元使用的切片资源的资源类型发生改变。
在一个实施例中，第一接入网设备向第一网元通知第一承载单元使用的切片资源类型发生改变，从而第一网元可以根据该通知确定第一承载单元使用的切片资源的资源类型发生改变。
S105，第一网元响应于第一承载单元使用的切片资源的资源类型发生改变，向计费网元发送切片资源信息。
具体的，该第一网元可以响应于第一承载单元使用的切片资源的资源类型发生改变，向计费网元通知第二承载单元使用的切片资源的资源类型发生改变。其中，该第二承载单元可以是步骤S100中第一指示信息中所指示的承载单元，因此，第一网元可以是根据第一指示信息，向计费网元通知第二承载单元使用的切片资源的资源类型发生改变。
可选的，第二承载单元可以是第一承载单元相同，即第一接入网设备向第一网元上报的粒度与第一网元向计费网元上报的粒度相同，例如，第一接入网设备向第一网元通知会话1使用的切片资源的资源类型发生改变，则第一网元向计费网元通知会话1使用的切片资源的资源类型发生改变。
可选的，第二承载单元可以是第一承载单元的子集，即第一接入网设备向第一网元上报的粒度大于第一网元向计费网元上报的粒度，例如，第一网元为SMF，第一接入网设备向SMF通知会话1使用的切片资源的资源类型发生改变，SMF向计费网元通知该会话1中的业务1使用的切片资源的资源类型发生改变。可以理解的是，在该种场景下，第一承载单元中所有承载单元使用的切片资源的资源类型可以相同，即会话1中所有业务使用的切片资源的资源类型相同。
可选的，第一承载单元可以是第二承载单元的子集，即第一接入网设备向第一网元上报的粒度小于第一网元向计费网元上报的粒度，例如，第一网元为AMF，第一接入网设备向AMF通知网络切片中会话1和会话2使用的切片资源的资源类型发生改变，该网络切片内包含的所有会话的数量为3，则AMF确定网络切片内2/3的会话使用的切片资源的资源类型发生改变，进一步，AMF向计费网元通知网络切片内2/3的会话使用的切片资源的资源类型发生改变，从而AMF以网络切片粒度向计费网元通知资源类型发生改变。
其中，第一网元向计费网元通知第二承载单元使用的切片资源的资源类型发生改变的通知方式可以有多种。示例性的，第一网元向计费网元发送切片资源信息，该切片资源信息可以用于表示第二承载单元使用的切片资源的资源类型发生改变，比如，网络切片对应的资源类型包括两种，该第二承载单元初始使用的切片资源的资源类型已知，则第一网元可以向计费网元指示资源类型发生改变，计费网元即可获得改变后的第二承载单元使用的 切片资源的资源类型。可选的，该切片资源信息还可以用于表示改变后的第二承载单元使用的切片资源的资源类型，比如，在第二承载单元使用的切片资源的资源类型发生改变时，第一网元向计费网元指示改变后的第二承载单元使用的切片资源的资源类型。可选的，切片资源信息还可以用于表示各个时间段内第二承载单元所使用的切片资源的资源类型，例如，在2020年1月1日10:00-11:00，第二承载单元使用的资源类型为S-NSSAI 1a，在2020年1月1日11:00-11:30，第二承载单元使用的资源类型为S-NSSAI 1b，在2020年1月1日11:00-12:30，第二承载单元使用的资源类型为S-NSSAI 1c。
在一些实施例中，如果网络切片对应的资源类型包括两种，计费网元可以指示第一网元在某一种资源类型改变时，即上报给计费网元。比如，由其他资源类型切换为所订阅的资源类型时，第一网元即上报给计费网元，或者，由该所订阅的资源类型切换为其他资源类型时，第一网元即上报给计费网元。
其中，若第二承载单元为网络切片，第一网元可以确定该网络切片内发生资源类型改变的会话或QoS流的数量占该网络切片内包含的所有会话或QoS流的数量之间的比值，并向计费网元发送切片资源信息，该切片资源信息包括该比值，进一步，还可以包括该网络切片切换后的资源类型，从而第一网元以网络切片粒度上报该网络切片的资源类型改变信息。
S106，计费网元从第一网元接收切片资源信息，为第二承载单元确定与改变后的第二承载单元使用的切片资源的资源类型对应的计费处理方式。
在一个实施例中，计费网元在接收到切片资源信息后，可以根据该切片资源信息确定改变后的第二承载单元使用的切片资源的资源类型。
示例性的，若切片资源信息表示第二承载单元使用的切片资源的资源类型发生改变，比如，网络切片对应的资源类型包括两种，计费网元已知该第二承载单元初始使用的切片资源的资源类型，比如第二承载单元初始使用的切片资源的资源类型为默认配置，则计费网元在接收到切片资源信息后，可确定与改变后的第二承载单元使用的切片资源的资源类型，从而确定与改变后的第二承载单元使用的切片资源的资源类型对应的计费处理方式。
示例性的，若切片资源信息表示改变后的第二承载单元使用的切片资源的资源类型，则计费网元可以根据切片资源信息获得改变后的第二承载单元使用的切片资源的资源类型，进一步确定与改变后的第二承载单元使用的切片资源的资源类型对应的计费处理方式。
可以理解的是，改变后的资源类型对应的计费处理方式与改变前的资源类型对应的计费处理方式可以不同，也可以相同。
请参照图5，为本申请实施例提供的另一种信息传输方法的流程示意图，图1a至图1e可以为该信息传输方法所应用的网络架构示例。图3a至图3c可以为该信息传输方法所应用的场景示例。如图5所示，该方法可以包括：S200-S204。其中，各个步骤的执行顺序，本申请实施例不作限制。如图所示，本申请实施例的信息传输方法包括但不限于以下步骤：
S200，第一接入网设备向第一网元发送第一资源状态信息。
S201，第二接入网设备向第一网元发送第二资源状态信息。
可选的，在步骤S200和步骤S201之前，计费网元可以向第一网元发送第一指示信息， 该第一指示信息用于指示第一网元在第二承载单元使用的切片资源的资源类型发生改变时通知计费网元。第一网元响应于该第一指示信息，向终端设备所接入的第一接入网设备发送第二指示信息，该第二指示信息用于指示第一接入网设备在第一承载单元使用的切片资源的资源类型发生改变时通知第一网元。其中，计费网元向第一网元发送第一指示信息，以及，第一网元向第一接入网设备发送第二指示信息的具体描述请参照图4所示实施例中步骤S100和步骤S101的描述，在此不再赘述。
在一个实施例中，可以是随着终端设备的移动，该终端设备从第一接入网设备的覆盖范围移动到第二接入网设备的覆盖范围，即该终端设备所接入的接入网设备由第一接入网设备切换到第二接入网设备，相应的，该终端设备的第一承载单元的用户面连接所经过的接入网设备由第一接入网设备切换到第二接入网设备。可选的，第一接入网设备可以将第一网元向该第一接入网设备订阅的第一承载单元的资源类型改变事件传递给第二接入网设备，或者，第一网元可以向第二接入网设备订阅第一承载单元的资源类型改变事件。
其中，第一接入网设备为该终端设备的第一承载单元调度的切片资源的资源类型与第二接入网设备为该终端设备的第一承载单元调度的切片资源的资源类型可能不同。为了便于第一网元确定第一承载单元使用的切片资源的资源类型是否发生改变，本申请实施例中，第一接入网设备向第一网元发送第一资源状态信息，该第一资源状态信息用于指示第一接入网设备为该第一承载单元调度的切片资源的资源类型。第二接入网设备向第一网元发送第二资源状态信息，该第二资源状态信息用于指示第二接入网设备为该第一承载单元调度的切片资源的资源类型。示例性的，第一接入网设备和第二接入网设备可以是在切换场景下向第一网元发送资源状态信息。
其中，第一承载单元可以是网络切片、会话或QoS流中的一种。该第一承载单元可以是第一网元向接入网设备(第一接入网设备和/或第二接入网设备)所订阅的承载单元。
S202，第一网元根据第一资源状态信息和第二资源状态信息，确定第一承载单元使用的切片资源的资源类型发生改变。
在一个实施例中，第一网元可以比较第一接入网设备为终端设备的第一承载单元调度的切片资源的资源类型与第二接入网设备为该终端设备的第一承载单元调度的切片资源的资源类型是否相同，从而确定第一承载单元使用的切片资源的资源类型是否发生改变。
作为一种实现方式，第一网元中可以存储第一资源状态信息，当接收到第二资源状态信息时将二者进行比较。
S203，响应于第一承载单元使用的切片资源的资源类型发生改变，第一网元向计费网元发送切片资源信息。
S204，计费网元从第一网元接收切片资源信息，为第二承载单元确定与改变后的第二承载单元使用的切片资源的资源类型对应的计费处理方式。
其中，步骤S203和步骤S204的具体描述可以参照图4实施例中的步骤S105和步骤S106的描述，在此不再赘述。
以上，结合图4和图5详细说明了本申请实施例提供的方法。以下，结合图6至图8详细说明本申请实施例提供的装置。
可以理解的是，为了实现上述实施例中功能，接入网设备、第一网元以及计费网元包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本申请中所公开的实施例描述的各示例的单元及方法步骤，本申请能够以硬件、软件、或硬件和软件相结合的形式来实现。某个功能究竟以硬件、软件、或是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用场景和设计约束条件。
图6是本申请实施例提供的通信装置的示意性框图。如图6所示，该通信装置10可以包括处理单元11和收发单元12。处理单元11和收发单元12可以是软件，也可以是硬件，或者是软件和硬件结合。
其中，收发单元12可包括发送单元和接收单元，发送单元用于实现发送功能，接收单元用于实现接收功能，收发单元12可以实现发送功能和/或接收功能。收发单元也可以描述为通信单元。
可选的，收发单元12可以用于接收其他装置发送的信息，还可以用于向其他装置发送信息。处理单元11可以用于进行装置的内部处理。
在一种可能的设计中，该通信装置10可对应于上述方法实施例中的第一接入网设备，如该通信装置10可以是第一接入网设备，也可以是第一接入网设备中的芯片。该通信装置10可以包括用于执行上述方法实施例中由第一接入网设备所执行的操作的单元，并且，该通信装置10中的各单元分别为了实现上述方法实施例中由第一接入网设备所执行的操作。
示例性的，所述处理单元11用于确定第一承载单元使用的切片资源的资源类型发生改变；
收发单元12，用于响应于所述第一承载单元使用的切片资源的资源类型发生改变，通知第一网元。
示例性的，所述处理单元11用于确定第一承载单元的用户面连接所经过的接入网设备发生切换。其中，该第一接入网设备可以为切换之前该第一承载单元的用户面连接所经过的接入网设备，即源接入网设备，或者，该第一接入网设备也可以为切换之后该第一承载单元的用户面连接所经过的接入网设备，即目标接入网设备。
响应于第一承载单元的用户面连接所经过的接入网设备发生切换，收发单元12用于向第一网元发送资源状态信息，该资源状态信息用于指示第一接入网设备为该第一承载单元调度的切片资源的资源类型。
在一种可能的设计中，该通信装置10可对应于第一网元，也可以是第一网元中的芯片。该通信装置10可以包括用于执行上述方法实施例中由第一网元所执行的操作的单元，并且，该通信装置10中的各单元分别为了实现上述方法实施例中由第一网元所执行的操作。
示例性的，处理单元11，用于确定第一承载单元使用的切片资源的资源类型发生改变；
收发单元12，用于响应于所述第一承载单元使用的切片资源的资源类型发生改变，向计费网元发送切片资源信息，所述切片资源信息用于表示第二承载单元使用的切片资源的资源类型发生改变，或，所述切片资源信息表示改变后的第二承载单元使用的切片资源的资源类型；
其中，所述第一承载单元是所述第二承载单元的子集，或者，所述第二承载单元是所述第一承载单元的子集，或者所述第一承载单元与所述第二承载单元相同。
在一种可能的设计中，该通信装置10可对应于计费网元，也可以是计费网元中的芯片。该通信装置10可以包括用于执行上述方法实施例中由计费网元所执行的操作的单元，并且，该通信装置10中的各单元分别为了实现上述方法实施例中由计费网元所执行的操作。
示例性的，收发单元12，用于从第一网元接收切片资源信息，所述切片资源信息用于表示第一承载单元使用的切片资源的资源类型发生改变，或，所述切片资源信息表示改变后的第一承载单元使用的切片资源的资源类型；
处理单元11，用于为所述第一承载单元确定与改变后的所述第一承载单元使用的切片资源的资源类型对应的计费处理方式。
应理解，上述通信装置10为配置于第一接入网设备、第一网元或计费网元的芯片时，该通信装置10中的收发单元12可以为输入/输出接口。
应理解，该通信装置10为第一接入网设备、第一网元或计费网元时，该通信装置10中的收发单元12可对应于图7中示出的通信接口21，处理单元11可对应于图7中示出的处理器22。
请参照图7，是本申请一个实施例的通信装置的示意性结构图。应理解，图7示出的通信装置20仅是示例，本申请实施例的通信装置还可包括其他部件，或者包括与图7中的各个部件的功能相似的部件，或者并非要包括图7中所有部件。
通信装置20包括通信接口21和至少一个处理器22。
该通信装置20可以对应第一接入网设备、第一网元或计费网元中的任一网元或设备。通信接口21用于收发信号，至少一个处理器22执行程序指令，使得通信装置20实现上述方法实施例中由对应网元所执行的方法的相应流程。
在一种可能的设计中，该通信装置20可对应于上述方法实施例中的第一接入网设备，如该通信装置20可以是第一接入网设备，也可以是第一接入网设备中的芯片。该通信装置20可以包括用于执行上述方法实施例中由第一接入网设备所执行的操作的部件，并且，该通信装置10中的各部件分别为了实现上述方法实施例中由第一接入网设备所执行的操作。
示例性的，所述处理器22用于确定第一承载单元使用的切片资源的资源类型发生改变；
通信接口21，用于响应于所述第一承载单元使用的切片资源的资源类型发生改变，通知第一网元。
示例性的，所述处理器22用于确定第一承载单元的用户面连接所经过的接入网设备发生切换。其中，该第一接入网设备可以为切换之前该第一承载单元的用户面连接所经过的接入网设备，即源接入网设备，或者，该第一接入网设备也可以为切换之后该第一承载单元的用户面连接所经过的接入网设备，即目标接入网设备。
响应于第一承载单元的用户面连接所经过的接入网设备发生切换，通信接口21用于向第一网元发送资源状态信息，该资源状态信息用于指示第一接入网设备为该第一承载单元调度的切片资源的资源类型。
在一种可能的设计中，该通信装置20可对应于第一网元，也可以是第一网元中的芯片。该通信装置20可以包括用于执行上述方法实施例中由第一网元所执行的操作的部件，并且，该通信装置10中的各部件分别为了实现上述方法实施例中由第一网元所执行的操作。
示例性的，所述处理器22，用于确定第一承载单元使用的切片资源的资源类型发生改变；
通信接口21，用于响应于所述第一承载单元使用的切片资源的资源类型发生改变，向计费网元发送切片资源信息，所述切片资源信息用于表示第二承载单元使用的切片资源的资源类型发生改变，或，所述切片资源信息表示改变后的第二承载单元使用的切片资源的资源类型；
其中，所述第一承载单元是所述第二承载单元的子集，或者，所述第二承载单元是所述第一承载单元的子集，或者所述第一承载单元与所述第二承载单元相同。
在一种可能的设计中，该通信装置20可对应于计费网元，也可以是计费网元中的芯片。该通信装置20可以包括用于执行上述方法实施例中由计费网元所执行的操作的部件，并且，该通信装置10中的各部件分别为了实现上述方法实施例中由计费网元所执行的操作。
示例性的，通信接口21，用于从第一网元接收切片资源信息，所述切片资源信息用于表示第一承载单元使用的切片资源的资源类型发生改变，或，所述切片资源信息表示改变后的第一承载单元使用的切片资源的资源类型；
所述处理器22，用于为所述第一承载单元确定与改变后的所述第一承载单元使用的切片资源的资源类型对应的计费处理方式。
可选地，通信装置20还可以包括存储器。该存储器可以存储程序指令，至少一个处理器22可以读取存储器所存储的程序指令并执行该程序指令。
对于通信装置可以是芯片或芯片***的情况，可参见图8所示的芯片的结构示意图。图8所示的芯片30包括处理器31和接口32。其中，处理器31的数量可以是一个或多个，接口32的数量可以是多个。需要说明的，处理器31、接口32各自对应的功能既可以通过硬件设计实现，也可以通过软件设计来实现，还可以通过软硬件结合的方式来实现，这里不作限制。
可选的，芯片还可以包括存储器33，存储器33用于存储必要的程序指令和数据。
本申请中，处理器31可用于从存储器中调用本申请的一个或多个实施例提供的信息传输方法在第一接入网设备、第一网元或计费网元中一个或多个设备或网元的实现程序，并执行该程序包含的指令。接口32可用于输出处理器31的执行结果。本申请中，接口32可具体用于输出处理器31的各个消息或信息。关于本申请的一个或多个实施例提供的信息传输方法可参考前述图4和图5所示各个实施例，这里不再赘述。
本申请实施例中的处理器可以是中央处理单元(Central Processing Unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行前述任一方法实施例中第一接入网设备、第一网元或计费网元侧的方法。
本申请的另一实施例中，还提供一种通信***，该通信***包括第一网元和计费网元。可选的，该通信***还可以包括接入网设备，可选的，该通信***还可以包括终端设备。示例性的，第一网元、计费网元、接入网设备以及终端设备可以为图4或图5任一实施例所提供的第一网元、计费网元、接入网设备以及终端设备，且用于执行图4或图5任一实施例中相应网元执行的步骤。
本申请实施例还提供了一种处理装置，包括处理器和接口；所述处理器用于执行上述任一方法实施例中的方法。
应理解，上述处理装置可以是一个芯片。例如，该处理装置可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，还可以是***芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的***和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中， 或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disc，SSD))等。
上述各个装置实施例中的接入网设备、第一网元以及计费网元和方法实施例中的接入网设备、第一网元以及计费网元完全对应，由相应的模块或单元执行相应的步骤，例如通信单元(收发器)执行方法实施例中接收或发送的步骤，除发送、接收外的其它步骤可以由处理单元(处理器)执行。具体单元的功能可以参考相应的方法实施例。其中，处理器可以为一个或多个。
在本说明书中使用的术语“部件”、“模块”、“***”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程或执行线程中，部件可位于一个计算机上或分布在2个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地***、分布式***或网络间的另一部件交互的二个部件的数据，例如通过信号与其它***交互的互联网)的信号通过本地或远程进程来通信。
应理解，说明书通篇中提到的“实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各个实施例未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。
应理解，在本申请实施例中，编号“第一”、“第二”…仅仅为了区分不同的对象，比如为了区分不同的网络设备，并不对本申请实施例的范围构成限制，本申请实施例并不限于此。
还应理解，在本申请中，“当…时”、“若”以及“如果”均指在某种客观情况下网元会做出相应的处理，并非是限定时间，且也不要求网元实现时一定要有判断的动作，也不意味着存在其它限定。
还应理解，在本申请各实施例中，“A对应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
还应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
本申请中出现的类似于“项目包括如下中的一项或多项：A，B，以及C”表述的含义， 如无特别说明，通常是指该项目可以为如下中任一个：A；B；C；A和B；A和C；B和C；A，B和C；A和A；A，A和A；A，A和B；A，A和C，A，B和B；A，C和C；B和B，B，B和B，B，B和C，C和C；C，C和C，以及其他A，B和C的组合。以上是以A，B和C共3个元素进行举例来说明该项目的可选用条目，当表达为“项目包括如下中至少一种：A，B，……，以及X”时，即表达中具有更多元素时，那么该项目可以适用的条目也可以按照前述规则获得。
可以理解的，本申请实施例中，接入网设备、第一网元和计费网元可以执行本申请实施例中的部分或全部步骤，这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者各种操作的变形。此外，各个步骤可以按照本申请实施例呈现的不同的顺序来执行，并且有可能并非要执行本申请实施例中的全部操作。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种信息传输方法，其特征在于，包括：
    第一接入网设备确定第一承载单元使用的切片资源的资源类型发生改变；
    响应于所述第一承载单元使用的切片资源的资源类型发生改变，所述第一接入网设备通知第一网元。
  2. 如权利要求1所述的方法，其特征在于，所述第一接入网设备通知第一网元，包括：
    所述第一接入网设备向第一网元发送第一信息，第一信息用于表示所述第一承载单元使用的切片资源的资源类型发生改变，或者，所述第一信息用于表示改变后的所述第一承载单元使用的切片资源的资源类型。
  3. 如权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述第一接入网设备从第二接入网设备接收所述第一承载单元对应的切片资源的资源类型；
    所述第一接入网设备确定所述第一接入网设备为所述第一承载单元调度的切片资源的资源类型。
  4. 如权利要求1-3任一项所述的方法，其特征在于，所述第一承载单元为会话、服务质量QoS流或网络切片中的一种。
  5. 如权利要求1-4任一项所述的方法，其特征在于，所述方法还包括：
    所述第一接入网设备从所述第一网元接收指示信息；
    所述响应于所述第一承载单元使用的切片资源的资源类型发生改变，第一接入网设备通知第一网元，包括：
    响应于所述指示信息，所述第一接入网设备在所述第一承载单元使用的切片资源的资源类型发生改变的情况下，通知所述第一网元。
  6. 如权利要求5所述的方法，其特征在于，所述指示信息用于指示所述第一接入网设备在所述第一承载单元使用的切片资源的资源类型发生改变的情况下，通知所述第一网元。
  7. 如权利要求1-6任一项所述的方法，其特征在于，所述第一网元为接入和移动管理功能AMF网元或者会话管理功能SMF网元。
  8. 一种信息传输方法，其特征在于，包括：
    第一网元确定第一承载单元使用的切片资源的资源类型发生改变；
    响应于所述第一承载单元使用的切片资源的资源类型发生改变，所述第一网元向计费网元发送切片资源信息，所述切片资源信息用于表示第二承载单元使用的切片资源的资源 类型发生改变，或，所述切片资源信息表示改变后的第二承载单元使用的切片资源的资源类型；
    其中，所述第一承载单元是所述第二承载单元的子集，或者，所述第二承载单元是所述第一承载单元的子集，或者所述第一承载单元与所述第二承载单元相同。
  9. 如权利要求8所述的方法，其特征在于，所述第一网元确定第一承载单元使用的切片资源的资源类型发生改变，包括：
    所述第一网元从接入网设备接收通知，根据所述通知确定所述第一承载单元使用的切片资源的资源类型发生改变。
  10. 如权利要求8所述的方法，其特征在于，所述第一网元确定第一承载单元使用的切片资源的资源类型发生改变，包括：
    所述第一网元从第一接入网设备接收第一资源状态信息，所述第一资源状态信息用于指示所述第一接入网设备为所述第一承载单元调度的切片资源的资源类型；
    所述第一网元从第二接入网设备接收第二资源状态信息，所述第二资源状态信息用于指示所述第二接入网设备为所述第一承载单元调度的切片资源的资源类型；
    所述第一网元根据所述第一资源状态信息和所述第二资源状态信息，确定所述第一承载单元使用的切片资源的资源类型发生改变。
  11. 如权利要求8-10任一项所述的方法，其特征在于，所述第一承载单元为会话、服务质量QoS流或网络切片中的一种。
  12. 如权利要求8-11任一项所述的方法，其特征在于，若所述第一网元为接入和移动管理功能AMF网元，所述第二承载单元为网络切片、会话或QoS流中的一种；
    若所述第一网元为会话管理功能SMF网元，所述第二承载单元为网络切片、会话、QoS流或业务中的一种。
  13. 如权利要求8-12任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网元从所述计费网元接收第一指示信息；
    所述响应于所述第一承载单元使用的切片资源的资源类型发生改变，所述第一网元向计费网元发送切片资源信息，包括：
    响应于所述第一指示信息，所述第一网元在所述第一承载单元使用的切片资源的资源类型发生改变的情况下，向所述计费网元发送切片资源信息。
  14. 如权利要求13所述的方法，其特征在于，所述第一指示信息用于指示所述第一网元在所述第二承载单元使用的切片资源的资源类型发生改变的情况下，通知所述计费网元。
  15. 如权利要求13或14所述的方法，其特征在于，所述方法还包括：
    响应于所述第一指示信息，所述第一网元向接入网设备发送第二指示信息，所述第二指示信息用于指示所述接入网设备在所述第一承载单元使用的切片资源的资源类型发生改变的情况下，通知所述第一网元。
  16. 一种信息传输方法，其特征在于，包括：
    计费网元从第一网元接收切片资源信息，所述切片资源信息用于表示第一承载单元使用的切片资源的资源类型发生改变，或，所述切片资源信息表示改变后的第一承载单元使用的切片资源的资源类型；
    所述计费网元为所述第一承载单元确定与改变后的所述第一承载单元使用的切片资源的资源类型对应的计费处理方式。
  17. 如权利要求16所述的方法，其特征在于，所述方法还包括：
    所述计费网元向所述第一网元发送指示信息，所述指示信息用于指示所述第一网元在所述第一承载单元使用的切片资源的资源类型发生改变的情况下，通知所述计费网元。
  18. 一种通信装置，其特征在于，所述通信装置应用于第一接入网设备，所述装置包括：
    处理单元，用于确定第一承载单元使用的切片资源的资源类型发生改变；
    收发单元，用于响应于所述第一承载单元使用的切片资源的资源类型发生改变，通知第一网元。
  19. 如权利要求18所述的装置，其特征在于，所述收发单元具体用于向第一网元发送第一信息，第一信息用于表示所述第一承载单元使用的切片资源的资源类型发生改变，或者，所述第一信息用于表示改变后的所述第一承载单元使用的切片资源的资源类型。
  20. 如权利要求18或19所述的装置，其特征在于，
    所述收发单元还用于从第二接入网设备接收所述第一承载单元对应的切片资源的资源类型；
    所述处理单元还用于确定所述第一接入网设备为所述第一承载单元调度的切片资源的资源类型。
  21. 如权利要求18-20任一项所述的装置，其特征在于，
    所述收发单元还用于从所述第一网元接收指示信息；
    所述收发单元还用于响应于所述指示信息，在所述第一承载单元使用的切片资源的资源类型发生改变的情况下，通知所述第一网元。
  22. 如权利要求18-21任一项所述的方法，其特征在于，所述第一网元为接入和移动管理功能AMF网元或者会话管理功能SMF网元。
  23. 一种通信装置，其特征在于，所述通信装置应用于第一网元，所述装置包括：
    处理单元，用于确定第一承载单元使用的切片资源的资源类型发生改变；
    收发单元，用于响应于所述第一承载单元使用的切片资源的资源类型发生改变，向计费网元发送切片资源信息，所述切片资源信息用于表示第二承载单元使用的切片资源的资源类型发生改变，或，所述切片资源信息表示改变后的第二承载单元使用的切片资源的资源类型；
    其中，所述第一承载单元是所述第二承载单元的子集，或者，所述第二承载单元是所述第一承载单元的子集，或者所述第一承载单元与所述第二承载单元相同。
  24. 如权利要求23所述的装置，其特征在于，所述收发单元还用于从接入网设备接收通知；
    所述处理单元具体用于根据所述通知确定所述第一承载单元使用的切片资源的资源类型发生改变。
  25. 如权利要求23所述的装置，其特征在于，
    所述收发单元还用于从第一接入网设备接收第一资源状态信息，所述第一资源状态信息用于指示所述第一接入网设备为所述第一承载单元调度的切片资源的资源类型；
    所述收发单元还用于从第二接入网设备接收第二资源状态信息，所述第二资源状态信息用于指示所述第二接入网设备为所述第一承载单元调度的切片资源的资源类型；
    所述处理单元具体用于根据所述第一资源状态信息和所述第二资源状态信息，确定所述第一承载单元使用的切片资源的资源类型发生改变。
  26. 如权利要求23-25任一项所述的装置，其特征在于，
    所述收发单元还用于从所述计费网元接收第一指示信息；
    所述收发单元还用于响应于所述第一指示信息，在所述第一承载单元使用的切片资源的资源类型发生改变的情况下，向所述计费网元发送切片资源信息。
  27. 一种通信装置，其特征在于，所述通信装置应用于计费网元，所述装置包括：
    收发单元，用于从第一网元接收切片资源信息，所述切片资源信息用于表示第一承载单元使用的切片资源的资源类型发生改变，或，所述切片资源信息表示改变后的第一承载单元使用的切片资源的资源类型；
    处理单元，用于为所述第一承载单元确定与改变后的所述第一承载单元使用的切片资源的资源类型对应的计费处理方式。
  28. 如权利要求27所述的装置，其特征在于，
    所述收发单元还用于向所述第一网元发送指示信息，所述指示信息用于指示所述第一网元在所述第一承载单元使用的切片资源的资源类型发生改变的情况下，通知所述计费网 元。
  29. 一种通信装置，其特征在于，包括：处理器，当所述处理器调用存储器中的计算机程序或指令时，如权利要求1至7或者如权利要求8至15或者如权利要求16至17任一项所述的方法被执行。
  30. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质包括计算机程序或指令，当所述计算机程序或指令在计算机上运行时，使得计算机执行如权利要求1至7或者如权利要求8至15或者如权利要求16至17任一项所述的方法。
PCT/CN2021/071767 2021-01-14 2021-01-14 信息传输方法及通信装置 WO2022151155A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202180088636.4A CN116711458A (zh) 2021-01-14 2021-01-14 信息传输方法及通信装置
PCT/CN2021/071767 WO2022151155A1 (zh) 2021-01-14 2021-01-14 信息传输方法及通信装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/071767 WO2022151155A1 (zh) 2021-01-14 2021-01-14 信息传输方法及通信装置

Publications (1)

Publication Number Publication Date
WO2022151155A1 true WO2022151155A1 (zh) 2022-07-21

Family

ID=82447711

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/071767 WO2022151155A1 (zh) 2021-01-14 2021-01-14 信息传输方法及通信装置

Country Status (2)

Country Link
CN (1) CN116711458A (zh)
WO (1) WO2022151155A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110431859A (zh) * 2017-03-20 2019-11-08 Lg电子株式会社 用于无线通信***中层之间交互的方法及其设备
CN110999431A (zh) * 2017-06-17 2020-04-10 Lg电子株式会社 用于在无线通信***中注册终端的方法及其设备

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110431859A (zh) * 2017-03-20 2019-11-08 Lg电子株式会社 用于无线通信***中层之间交互的方法及其设备
CN110999431A (zh) * 2017-06-17 2020-04-10 Lg电子株式会社 用于在无线通信***中注册终端的方法及其设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SAMSUNG: "Policy update on DNN replacement", 3GPP DRAFT; S2-2002178, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Elbonia; 20200224 - 20200227, 19 February 2020 (2020-02-19), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051855694 *

Also Published As

Publication number Publication date
CN116711458A (zh) 2023-09-05

Similar Documents

Publication Publication Date Title
US20210219364A1 (en) Resource establishing method, and device
WO2020019764A1 (zh) 信息传输方法、设备及计算机可读存储介质
US11968565B2 (en) User plane information reporting method and apparatus
WO2020224622A1 (zh) 一种信息配置方法及装置
WO2022016948A1 (zh) 一种通信方法及装置
US20230254922A1 (en) Multipath transmission method and communication apparatus
US20230262793A1 (en) Method for communication between user terminal and network, and terminal, network device and apparatus
US20200170073A1 (en) Method for Repeatedly Transmitting Data and Device
KR20220044341A (ko) 보안 보호 모드 결정 방법 및 장치
WO2022028276A1 (zh) 业务处理方法、信息指示方法、终端和网络设备
US20240172084A1 (en) Data transmission method and apparatus
WO2020252710A1 (zh) 无线通信方法和设备
WO2023035925A1 (zh) 一种业务处理方法、装置和***
JP2022521088A (ja) ポリシー管理方法及び装置
WO2022047803A1 (zh) 通信方法及装置
US20230254859A1 (en) Downlink Transmission Method and Communication Apparatus
WO2022151155A1 (zh) 信息传输方法及通信装置
KR102179212B1 (ko) 제어 정보에 대한 송신 방법 및 장치
WO2021218244A1 (zh) 通信方法、装置及***
WO2021147672A1 (zh) 会话处理方法及通信装置
WO2021147105A1 (zh) 通信方法及装置
TW202015482A (zh) 通訊方法和設備
WO2023202503A1 (zh) 通信方法和装置
WO2024055871A1 (zh) 一种通信***中传输数据的方法和通信装置
WO2024032603A1 (zh) 一种通信方法及装置

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: 21918364

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180088636.4

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21918364

Country of ref document: EP

Kind code of ref document: A1